On 10.02.2003 16:15:48 reto.blunschi wrote: > I do agree very much with you about the concerns on EJB usage, though > unfortunately "drop the EJB idea" is not an option. > EJB is the chosen environment in this company (my client). Since XSL:FO has > also been chosen as "strategic" technology, we are bound to find a way for > the two to coexist. Having a special service for the rendering may be an > option, but in the end this comes down to the same issues than doing it > inside the EJB using seperate ThreadPools, JMS and the like, this is a > long-discussed topic in EJB lists...
I know CSS (the company, not the style thingy) makes use of CORBA services. Maybe you could wrap FOP as a CORBA service and call that one from your MDB. But I think the Servlet idea could be a good approach because you'll most likely have servlet support in your J2EE container. That could save you a lot of trouble and is easy to implement. > It seems obvious that you have not noticed the problems we see, because the > issue is most probably in AWTRenderer and its use of AWT classes > (java.awt.Font, java.awt.FontMetrics, java.awt.graphics). I've just now realized that you guys don't talk about the PDF renderer at all. Fr�d�ric probably got it wrong to say he was producing PDF in his first mail. > Your suggestion is a good way forward: I will try write a TestCase that > reproduces the problems outside EJB and we see how we can go on from there. > > Is the testcase you used in november available as a starter? I have it here. Just give me a little time to get it running again (I've got to check if it's still compatible with the latest Avalon Fortress version. I'll post a URL when I'm finished. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
