Tag: Apache

Work Day 23: Holy Cow…It WORKS!

This morning, after peering at files, searching for fo:table-layout=“auto”, tracing through all our code to see how a PDF export is triggered, scouring for ANY reference to Apache FOP (fun fact: FOP stands for Formatting Objects Processor) errors, I did a Google search on the specific error again and hit upon a reference about the columns widths needing to be specified. I check the two grids and THAT WAS THE DIFFERENCE. The grid that worked for the PDF export had column widths specified. The other grid had some specified, but not all. Once I added column widths and wrapLabel=“true” the PDF generated!

Now I just have to figure out how to unit-test. I did one test for one type of business and everything worked out perfectly. I’m having a devil of a time trying to test other business types due to the test data on my local machine being LAME. No other business type appears to have fully-fleshed-out claims with reserves and payment transactions to test for my change. If I could figure out how to query the db files for my local machine, I could get a better idea of what data is actually available.

The Alum suggested perhaps creating a “patch” for my coding changes, and then trying to figure out how to connect to one of the lower environments, employing my patch. I was confused back at “patch,” never mind the rest of that sentence.

And don’t even MENTION that dreaded “GUnit” test…

On a non-coding note, I’ve begun casting on for my new sweater! I still have to wash and block the sheep sweater I’ve been working on all summer. It’s probably going to be next Spring before I finish the new sweater, but at least it will be a nice, easy project to do during my continuing coding education saga.

Work Day 22: Day 2 of the “simple” story…

The next time I say that a user story is easy and a slam-dunk, someone tell me to shut up…

I’ve managed to get everything to work except for the PDF export for one of the grids. Weirdly, the seemingly wider PDF export is fine. The shorter one is still throwing a damn Apache FOP error. I had the Alum help me for two hours, and neither of us could make a dent in the issue. We even tried getting rid of a field, and even THAT didn’t work. I did google the error, and there are some suggestions online on how to deal with similar issues. However, I can’t figure out WHERE you’d plug in the code. I could just post my issue on one of the sites. My mentor is out until next Monday, or I would have asked him.

Thankfully, this user story is slated for the January release, so I still have plenty of time to figure it out.

Also, not to be too Pollyanna, but the other good news is that, in the process, the Alum showed me a lot of tricks to using Guidewire Studio that I hadn’t known. She showed me how to detach the debugging screen from the main window, so that you can a) get a larger view, and b) watch what’s going on as you do changes. Also, I couldn’t figure out for the life of me how to do a global search (tiny magnifying glass icon at the top right of the screen—DUH). The most valuable thing I learned was that if you click CTRL and then click on anything in the pcf code, you’re brought right to the underlying Gosu code!