way dynamic generation in xsp works (not the implementation of which I know next to nothing,
but the fact that your classes are always up to date) is a very strong convenience feature.
If that could be extended to the application jar's (e.g. cocoon/WB-INF/lib, not tomcat/libs) in the
way the sitemap has a check-reload that would make it so much easier to develop web applications,
especially since development seems to shift away from xsp to flowscript, with the flowscript
acting as a controller and not containing the business logic.
Leon
Ralph Goers wrote:
What presentation framework allows you to replace a jar without redeploying?
Ralph
-----Original Message-----
From: Leon Widdershoven [mailto:[EMAIL PROTECTED] Sent: Saturday, May 08, 2004 3:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Business Objects vs Data Objects [was Re: JXTemplates-what' s
in a name?]
Compared to a full distributed application container it probably is "just".
In comparison with anything else it isn't.
And restarting your cocoon when adding a jar (cause you updated a feature, removed
a bug, or added an application) will also not make larger sites very happy.
Leon
Ralph Goers wrote:
Antonio,use
People who say Cocoon is "just" a web publishing framework are nuts. We
very little flowscript and find it to be a very powerful presentation framework. I saw a comparison of various frameworks a while ago and Cocoon easily came out on top except that it had no built in support for Business Delegates. I spent some time and implemented that myself and Cocoon is working great so far.
Ralph
-----Original Message-----
From: Antonio Gallardo [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 1:09 AM
To: [EMAIL PROTECTED]
Subject: RE: Business Objects vs Data Objects [was Re: JXTemplates-what' s
in a name?]
BEAWARE: I am far to be a guru in this area.
Currently, I found myself asking about the "viability" of using EJB for the overall task in some applications. Recently, Ralph's posts, triggered in my mind the idea of how will be the best approach to use J2EE (that include EJB) with Cocoon. I read some articles about that too. And there are diferent approach. Some articles tell you that Cocoon need to be used just as a publishing framework while using J2EE. But I think: This was before flow. But, now we have Flow and I don't like the idea of stripdown Cocoon wings when I know how much it can do and help.... Of course this is a very large discussion and a interesting one.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
