Thank you, Peter, for this: --- "Hunsberger, Peter" <[EMAIL PROTECTED]> schrieb: > > We do not use J2EE as Cocoon datasources directly. > Our application logic is > invoked as Cocoon generators, Cocoon actions and in > some cases as XSLT > extensions. All of our code, in theory, could be > ported to a framework > other than Cocoon, the only issue being replacing > the sitemap (most likely > that would be done as explicit switch statements in > a servlet) and in fact > started life running from a highly modified version > of the LotusXSL servlet > many years ago... As a result, the application code > invokes the J2EE code > through proxy classes. The J2EE code then resolves > any other datasources > from the jBoss JNDI definitions and Cocoon is not > aware of what is going on. Seems like very nice and scallable solution for me, but I still have lasting questions: a) Did you ever try to migrate to JBoss 3x? b) Do you have to write the proxies for every EJB manually or is there automatized solution? c) Are you able to use load balancing and other administration of JBoss fully with no negatives on running system? d) Do the efforts with J2EE pay off really better performance and manageability against simple Tomcat approach according your experience? e) Do you use JBoss in any custom or standarized means also for authentification and authorisation for Cocoon resources or would it be too complicated to implement? Last, but not least: f) Would you be so nice to post some (almost out of the box) working demo illustrating your application workflow? I think I'm going to owe you much :) Peter.
__________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
