On Dec 6, 2005, at 15:16, Clifton Craig wrote:

Hi,

I understand my stylesheet snippets are amature because that's just what I was
when I started the project, an XSL amature.

Whoops, I hope I didn't give the impression that I was mocking your current level of understanding XSLT... Besides that, strictly speaking I'm an amateur myself, so don't worry. I just tried to raise some valid questions, based on the parts of the stylesheet you've shown us, and what I learned about XSLT over the years. Sometimes, you help people more by putting it as a question, so they will have to make the effort to answer it for themselves... Once you do, the logic behind it will remain apparent longer than if you get a fully worked-out solution on a platter. You will be able to profit from the gained knowledge in other scenarios as well.

No need to post the full stylesheet. I'd rather see *you* take a look at it, at the XSLT Rec and at some of the answers you already received, and try to make out whether any comments that were offered can be of use to you.

Now that that's out of the way:

<snip />
Here's a brief synopsis of how things work. A group of Java classes run multiple queries to pull data from the db and into a result set. Some more Java code transforms the data into XML (sort of an intermediate form for the report). my stylesheet then takes the resultset tranformed into XML and transforms it again into FO for the FOP engine. The data can be voluminous and we are looking into streamlining the process. My major bottleneck now has been the stylesheet creating FO that appears to be choking the FO engine. In a perfect world I'd love to just dump the report in one page sequence element and have the engine sort it out but it doesn't appear to work well that way.

So IIC, you need to make it look like it had all been placed under one page-sequence. (more or less: only the very last page in the document can be filled partly, but the rest needs to appear as if it were one fo:flow in one fo:page-sequence). Is that a correct assessment?


Cheers,

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to