... you can publish static text from Struts like this:
- Store XML content in a db field. (from user input or RSS feed).
- XSLT it and cache HTML cache in a db field.
Or many variations such as Styxx browser side.
You can now approve it, secure it, WIKI it, RSS feed it, count clicks, find matching advertisements to display, display it in a struts tile that users can move around like my.netscape.com.
I would say it is a good practice to use Struts with XML for delivery of static and dynamic content.
.V
Johan wrote:
[EMAIL PROTECTED] wrote:here we go<knip>
http://www.javaworld.com/javaworld/jw-02-2002/strutsxslt/jw-0201-strutsxslt.
zip
http://www.oroad.com/opencode/stxx/download.html
these are two custom approachs (both with java sources), but if I can tell
my feeling on the question, I suggest -if your app is "large"- that you feed
cocoon with you're serialized XML ... but I don't own such an example.
I agree on using cocoon for publishing XML data. But IMHO we shouldn't mix two parts of the universe to much. Struts for webapplications and cocoon as a publishing framework.
I just started developing webapplications with struts. It's great for the application-part of the website, but for the publishing of static text I don't see much advantage using struts. For that I see a great advantage in using cocoon.
Now I didn't use cocoon yet. But for me the ideal combination would be that I could insert into a tiles-definition a jsp-page, a struts-action, a tiles-definition or a xml page. The first three would be handled by struts and the xml-page by cocoon.
Have anyone experience with this kind of use with cocoon and struts?
Johan
---
Nilling Software Design
Postbus 43
2280 AA Rijswijk ZH
www: http://www.nilling.nl
epost: mailto:[EMAIL PROTECTED]
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
