Re: cocoon struts together
All, There seems to be some confusion about Struts on this mailing-list. As mentioned in one of the replies, Struts was designed to be an MVC (Model/View/Controller) framework based on Model 2 (a hybrid servlet/JSP architecture, as opposed to 100% servlet-based or 100% jsp-based architectures). This means that for each Web page, you write an action class (that implements the MVC model) and a JSP page (that implements the MVC view). The MVC controller is the configurable Struts controller, that you usually leave alone. The model and the view can be modified independently. If you define the interface between model and view correctly, which comes down to defining what JavaBeans the model sends to the JSP, you can achieve a very good separation of business logic and presentation logic. This is what Struts was designed for! About the business logic: using Struts has nothing to do at all with whether you use EJB or not. You can implement your business logic directly in Struts action classes if you want, or delegate to your business logic components, including session EJBs. Struts, like Cocoon, is mainly a presentation framework. About the presentation logic: Struts provides tag libraries that make it easier to write JSP pages (by the way, a lot of the concepts present in those tag libraries have made it into JSTL, the JSP Standard Tag Library, that makes much of the Struts tag libraries obsolete). But the fact is that you don't have to use JSP with Struts, you can use an XML-based presentation layer if you want. So yes, it makes sense to use at least a subset of Cocoon with Struts. You may want to leave dispatching, form handling, and the interaction with the business logic to Struts, and use Cocoon to implement flexible XML pipelines handling the look and feel, multiple device support, etc. You can even use a combination of both JSP and XML pipelines if you want. Have the JSP generate bare-bones HTML or XML, plug a Cocoon generator to parse the JSP output, and off you go. Why use Struts and Cocoon instead of using 100% Cocoon? Well, whether you like it or not, many people and companies use Struts. Its feature set is not too impressive, but the underlying architecture is conceptually sound. It is often easier to sell to you manager the use of Struts than the use of Cocoon. Also, you can incrementally add XML processing to an existing application instead of starting from scratch with Cocoon. There is a JavaWorld article about how to combine Struts and XSLT that you may find interesting: http://www.javaworld.com/javaworld/jw-02-2002/jw-0201-strutsxslt.html A follow-up to this article will be published on TheServerSide.com next week. The article even mentions Cocoon, in addition to our own OXF! -Erik [EMAIL PROTECTED] wrote: Hi, has someone any experiences with the comosition of struts and cocoon? I have a middleware on EJB and JCA which connects to some Systems like SAP. On this connects a webapplication which should be done with with struts. Some areas of this application should be transformed by cocoon in different outputs. My idea was to run some views with cocoon. A struts action would connect a pipeline from cocoon and passe the file which has to be transformed and visualized. Any suggestions or practices? Juraj - 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]
Re: cocoon struts together
Hi there, We have started development for a project, which uses both Struts and Cocoon. Our developers are facing lot of technical issues while using this combo -- taking more time to resolve -- more issues - less productivity. We had success in earlier projects which used these products separately. We are using Cocoon and Struts in the same web-app. Issues start right.. when JSPs interact with Cocoon. If you have experience, please let me know your suggestions/comments/lessons learnt/advice when you use both these products together. Thanks. --- On Tue 02/04, Robert Simmons [EMAIL PROTECTED] wrote: From: Robert Simmons [mailto: [EMAIL PROTECTED]] To: [EMAIL PROTECTED] Date: Wed, 5 Feb 2003 01:55:01 +0100 Subject: Re: cocoon struts together It was a painful road and I'm still nursing the bruises. But ya, I see its value. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:55 AM Subject: Re: cocoon struts together Thanks for the answer. Good speach. I saw you now as a Cocoon fan! :-) You finally saw the light at the end of the pipeline. ;-) Best Regards, Antonio Gallardo. Robert Simmons dijo: Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - 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
Re: cocoon struts together
From: Anecss [EMAIL PROTECTED] Hi there, We have started development for a project, which uses both Struts and Cocoon. Our developers are facing lot of technical issues while using this combo -- taking more time to resolve -- more issues - less productivity. We had success in earlier projects which used these products separately. We are using Cocoon and Struts in the same web-app. Issues start right.. when JSPs interact with Cocoon. Why would you need to use JSP when you have Cocoon? You can simply forward control to Cocoon after Struts handled the request, performed actions, etc. If you use JSP then why you use Cocoon? -- Konstantin If you have experience, please let me know your suggestions/comments/lessons learnt/advice when you use both these products together. Thanks. --- On Tue 02/04, Robert Simmons [EMAIL PROTECTED] wrote: From: Robert Simmons [mailto: [EMAIL PROTECTED]] To: [EMAIL PROTECTED] Date: Wed, 5 Feb 2003 01:55:01 +0100 Subject: Re: cocoon struts together It was a painful road and I'm still nursing the bruises. But ya, I see its value. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:55 AM Subject: Re: cocoon struts together Thanks for the answer. Good speach. I saw you now as a Cocoon fan! :-) You finally saw the light at the end of the pipeline. ;-) Best Regards, Antonio Gallardo. Robert Simmons dijo: Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - Please check that your question has not already been
Re: cocoon struts together
I dont think that using struts would be useful within an efficient cocoon
site. Cocoon takes another approach to web development that is, in my
opinion, superior to the jsp/struts approach. I do admit that the learnign
curve is high. in fact many on this list can tell you that ive been beatign
up cocoon over that issue a bit. However, I do think that it is worth it in
the end.
-- Robert
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 5:05 PM
Subject: AW: cocoon struts together
Hi Matthew,
Yes of course ;-) There is some experience with struts allready. With cocoon
not so much. And this question is a study about the possibilities. I think
the synergy of both frameworks can (perhaps) realize very powerful
solutioons.
Juraj
-Ursprüngliche Nachricht-
Von: Matthew Langham [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 3. Februar 2003 16:58
An: [EMAIL PROTECTED]
Betreff: RE: cocoon struts together
Hi Juraj,
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
why are you considering Struts (at all)? I am interested in this as we often
meet this kind of setup/discussion and we try to convince people to go for a
Cocoon-only solution (of course) :-)
Matthew
--
Open Source Group Cocoon { Consulting, Training, Projects }
=
Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de
-
Cocoon book:
http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20
Weblogs:
http://radio.weblogs.com/0103021/
http://www.oreillynet.com/weblogs/author/1014
=
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 4:46 PM
To: [EMAIL PROTECTED]
Subject: cocoon struts together
Hi,
has someone any experiences with the comosition of struts and cocoon?
I have a middleware on EJB and JCA which connects to some Systems
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
transformed by cocoon in different outputs. My idea was to run
some views with cocoon. A struts action would connect a pipeline
from cocoon and passe the file which has to be transformed and visualized.
Any suggestions or practices?
Juraj
-
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]
-
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]
-
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]
-
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]
Re: cocoon struts together
Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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]
Re: cocoon struts together
Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - 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]
[OT] RE: cocoon struts together
Re the comment Frameworks like struts mix functionality with presentation The presumption that functionality and presentation are mixed in Struts needs qualification. Struts is an application framework. It's most valuable component is the application layer. The presentation layer don't have to be JSP/taglib. You can serve out xml for presentation if you wish, or (shudder) even Flash. Reasonable separation of functionality and presentation can be achieved using any framework, if you follow 2 simple rules: Rule 1 - ensure that the application layer does not generate any presentation. Rule 2 - ensure that the presentation layer does not make any decisions. I use a tiles-based template system, with screens defined in an XML doc, but y'know, what-ever. I'm not trying to sell Struts to hardened Cocoon users. I use both Cocoon and Struts, but not together. Cocoon for data delivery systems, because of its fantastic separation of content and presentation, and Struts for business applications simply because it's such a good application framework. I don't believe either of these technologies should be considered to be a panacaea for the ills of the web world. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: cocoon struts together Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - 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] - Please check that your question has not already been answered in the FAQ before
Re: [OT] RE: cocoon struts together
Struts is a horrible basis for business logic for a thousand reasons. Business logic best lives within an enterprise container and an application server. The basis of concurrency, fault tolerance, transaction management, clustering and the rest of the EJB contract make it pretty psycho to NOT use it. I would NEVER EVER do anything important in any web framework, be it cocoon or struts. No thanks the J2EE environment is the god of business logic as cocoon is, IMHO, the god of web presentation. Cocoon should be a CONSUMER of the J2EE functionality and not make any decisions whatsoever. Many people whip up some struts-JSP based applications, which basically become servlets, and then pretend that the problems are solved. I could list a thousand ways this paradigm is garbage, but I really don't have to because other books do it quite well for me. My advice to you is to use EJB and J2EE on the back end, cocoon on the web end, JDO for persistence and Swing for complex clients. -- Robert - Original Message - From: Todd Pierce [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:36 AM Subject: [OT] RE: cocoon struts together Re the comment Frameworks like struts mix functionality with presentation The presumption that functionality and presentation are mixed in Struts needs qualification. Struts is an application framework. It's most valuable component is the application layer. The presentation layer don't have to be JSP/taglib. You can serve out xml for presentation if you wish, or (shudder) even Flash. Reasonable separation of functionality and presentation can be achieved using any framework, if you follow 2 simple rules: Rule 1 - ensure that the application layer does not generate any presentation. Rule 2 - ensure that the presentation layer does not make any decisions. I use a tiles-based template system, with screens defined in an XML doc, but y'know, what-ever. I'm not trying to sell Struts to hardened Cocoon users. I use both Cocoon and Struts, but not together. Cocoon for data delivery systems, because of its fantastic separation of content and presentation, and Struts for business applications simply because it's such a good application framework. I don't believe either of these technologies should be considered to be a panacaea for the ills of the web world. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: cocoon struts together Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together
Re: cocoon struts together
Thanks for the answer. Good speach. I saw you now as a Cocoon fan! :-) You finally saw the light at the end of the pipeline. ;-) Best Regards, Antonio Gallardo. Robert Simmons dijo: Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - 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] - 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]
Re: cocoon struts together
It was a painful road and I'm still nursing the bruises. But ya, I see its value. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:55 AM Subject: Re: cocoon struts together Thanks for the answer. Good speach. I saw you now as a Cocoon fan! :-) You finally saw the light at the end of the pipeline. ;-) Best Regards, Antonio Gallardo. Robert Simmons dijo: Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you are able to react quickly to the demands of your users, your company or customers win. The guy that slapped it together with low development costs may make some sales coming out the door, but will bleed customers as they seek more stable solutions with faster turn-around time for new features and fault correction. I guess that is a long way of saying, put all your work into the back end. Cocoon is perfect for this because you can develop custom generators to deliver data and let a web designer with a couple weeks of training worry about the XSLT translation. In the meantime your valuable programmer resources are implementing new features and stabilizing the product. Well that's my opinion on the matter. -- Robert - Original Message - From: Antonio Gallardo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 04, 2003 11:48 PM Subject: Re: cocoon struts together Robert Simmons dijo: I dont think that using struts would be useful within an efficient cocoon site. Cocoon takes another approach to web development that is, in my opinion, superior to the jsp/struts approach. Thanks for the comment. I was trying to start learning about this stuff. As a bean specialist (a book writer) what tools you recommend to manage all the beans stuff (creation, changes, etc.) Thanks for the comments. Antonio Gallardo - 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] - 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] - 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] - 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]
Re: [OT] RE: cocoon struts together
Robert Simmons wrote: My advice to you is to use EJB and J2EE on the back end, cocoon on the web end, JDO for persistence and Swing for complex clients. -- Robert After your previous comments I'm surprised you aren't pushing CMP 2 over JDO. -- Ryan Hoegg ISIS Networks http://www.isisnetworks.net - 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]
RE: [OT] RE: cocoon struts together
Interesting set of inferences ; P Many people whip up some struts-JSP based applications, which basically become servlets, and then pretend that the problems are solved. I could list a thousand ways this paradigm is garbage... - So that's what I do? Struts is a horrible basis for business logic for a thousand reasons. - Where did I say I use Struts for business logic? My advice to you is to use EJB and J2EE on the back end - Right on, baby Cocoon on the web - Hmm JDO for persistence - BMP We use Struts for controlling requests, on web-tier, application layer. We use templated JSPs for presentation, web-tier, presentation layer. You can use Cocoon for this if you like, but I think cocoon's strength is publishing data. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 11:49 AM To: [EMAIL PROTECTED] Subject: Re: [OT] RE: cocoon struts together Struts is a horrible basis for business logic for a thousand reasons. Business logic best lives within an enterprise container and an application server. The basis of concurrency, fault tolerance, transaction management, clustering and the rest of the EJB contract make it pretty psycho to NOT use it. I would NEVER EVER do anything important in any web framework, be it cocoon or struts. No thanks the J2EE environment is the god of business logic as cocoon is, IMHO, the god of web presentation. Cocoon should be a CONSUMER of the J2EE functionality and not make any decisions whatsoever. Many people whip up some struts-JSP based applications, which basically become servlets, and then pretend that the problems are solved. I could list a thousand ways this paradigm is garbage, but I really don't have to because other books do it quite well for me. My advice to you is to use EJB and J2EE on the back end, cocoon on the web end, JDO for persistence and Swing for complex clients. -- Robert - Original Message - From: Todd Pierce [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:36 AM Subject: [OT] RE: cocoon struts together Re the comment Frameworks like struts mix functionality with presentation The presumption that functionality and presentation are mixed in Struts needs qualification. Struts is an application framework. It's most valuable component is the application layer. The presentation layer don't have to be JSP/taglib. You can serve out xml for presentation if you wish, or (shudder) even Flash. Reasonable separation of functionality and presentation can be achieved using any framework, if you follow 2 simple rules: Rule 1 - ensure that the application layer does not generate any presentation. Rule 2 - ensure that the presentation layer does not make any decisions. I use a tiles-based template system, with screens defined in an XML doc, but y'know, what-ever. I'm not trying to sell Struts to hardened Cocoon users. I use both Cocoon and Struts, but not together. Cocoon for data delivery systems, because of its fantastic separation of content and presentation, and Struts for business applications simply because it's such a good application framework. I don't believe either of these technologies should be considered to be a panacaea for the ills of the web world. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: cocoon struts together Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts is for amateurs but it kind of is. It has low complexity and thus low functionality. It also has high cost in terms of content delivery and maintenance costs. I personally chose to avoid all that and let Java objects do all the work and let the framework just concentrate on presentation. Enter cocoon. My programs consist of allot of specially designed generators that generate pure data. Then I use XSLT to translate that into the appropriate media. I also use XSLT to output the forms though I am experimenting with reflexive techniques that I have used in GUI applications to make generation of forms be based on reflexive command analysis. Frameworks like struts mix functionality with presentation, which IMHO is a very bad thing. Its a high maintenance cost solution with a low development cost. That is the wrong way around. To be professional you want high development cost and low maintenance cost. This causes your feature turn around, post release, to be much faster. Since you
Re: [OT] RE: cocoon struts together
Don't be so defensive. You cant infer anything that I didn't say. I have no clue what you personally do. I merely commented on what I have seen others do in some 7 years of professional consulting. I don't advocate BMP because it doesn't take advantage of lazy loading. Its an all or nothing approach. You either load the entire object or none of it. If this object is a purchase order then it probably isn't a big deal. If its a genetic research mouse that has over 300 properties including 90 sets, lazy loading becomes IMPERATIVE. 99% of the time I just need 4 or 5 of those attributes. Loading them all would be a waste of resources and slow things down dramatically. JDO caching paradigm is heavily based on lazy loading. --Robert - Original Message - From: Todd Pierce [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 2:39 AM Subject: RE: [OT] RE: cocoon struts together Interesting set of inferences ; P Many people whip up some struts-JSP based applications, which basically become servlets, and then pretend that the problems are solved. I could list a thousand ways this paradigm is garbage... - So that's what I do? Struts is a horrible basis for business logic for a thousand reasons. - Where did I say I use Struts for business logic? My advice to you is to use EJB and J2EE on the back end - Right on, baby Cocoon on the web - Hmm JDO for persistence - BMP We use Struts for controlling requests, on web-tier, application layer. We use templated JSPs for presentation, web-tier, presentation layer. You can use Cocoon for this if you like, but I think cocoon's strength is publishing data. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 11:49 AM To: [EMAIL PROTECTED] Subject: Re: [OT] RE: cocoon struts together Struts is a horrible basis for business logic for a thousand reasons. Business logic best lives within an enterprise container and an application server. The basis of concurrency, fault tolerance, transaction management, clustering and the rest of the EJB contract make it pretty psycho to NOT use it. I would NEVER EVER do anything important in any web framework, be it cocoon or struts. No thanks the J2EE environment is the god of business logic as cocoon is, IMHO, the god of web presentation. Cocoon should be a CONSUMER of the J2EE functionality and not make any decisions whatsoever. Many people whip up some struts-JSP based applications, which basically become servlets, and then pretend that the problems are solved. I could list a thousand ways this paradigm is garbage, but I really don't have to because other books do it quite well for me. My advice to you is to use EJB and J2EE on the back end, cocoon on the web end, JDO for persistence and Swing for complex clients. -- Robert - Original Message - From: Todd Pierce [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 1:36 AM Subject: [OT] RE: cocoon struts together Re the comment Frameworks like struts mix functionality with presentation The presumption that functionality and presentation are mixed in Struts needs qualification. Struts is an application framework. It's most valuable component is the application layer. The presentation layer don't have to be JSP/taglib. You can serve out xml for presentation if you wish, or (shudder) even Flash. Reasonable separation of functionality and presentation can be achieved using any framework, if you follow 2 simple rules: Rule 1 - ensure that the application layer does not generate any presentation. Rule 2 - ensure that the presentation layer does not make any decisions. I use a tiles-based template system, with screens defined in an XML doc, but y'know, what-ever. I'm not trying to sell Struts to hardened Cocoon users. I use both Cocoon and Struts, but not together. Cocoon for data delivery systems, because of its fantastic separation of content and presentation, and Struts for business applications simply because it's such a good application framework. I don't believe either of these technologies should be considered to be a panacaea for the ills of the web world. -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 February 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: cocoon struts together Actually I'm an EJB specialist and I don't generally work on projects conducive to web interfaces. The complexity level of the stuff I do is too high. (Pharmaceutical industry and genetic research). My customers generally require a higher range of functionality than a web interface can provide. That being said, I do, however, do some web work which is why I took up the idea of cocoon. I use the same technique that I use for GUI programming. Basically a command centric architecture. I hate to say struts
Re: [OT] RE: cocoon struts together
I dislike CMP for a number of reasons. Not the least of which is that it is a sledgehammer solution to put a thumbtack in a wall. The other reasons run a wide spectrum and include things like lack of dynamic searches, inability to convert objects to transient state and then back to persistent, the primary key mechanism, having no access to the property methods and therefore not being able to perform data validation and on and on. IMHO CMP = total garbage. Its the one part of J2EE that is so poorly conceived that it should just be torn out completely. -- Robert - Original Message - From: Ryan Hoegg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 05, 2003 2:37 AM Subject: Re: [OT] RE: cocoon struts together Robert Simmons wrote: My advice to you is to use EJB and J2EE on the back end, cocoon on the web end, JDO for persistence and Swing for complex clients. -- Robert After your previous comments I'm surprised you aren't pushing CMP 2 over JDO. -- Ryan Hoegg ISIS Networks http://www.isisnetworks.net - 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] - 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]
RE: [OT] RE: cocoon struts together
Robert Are we talking about the same Struts? The Struts I know allows for a separation of logic and presentation. Actually, its developers recommend not to mix logic into Struts components. Struts is regarded as a standard Model2 (MVC a la J2EE) approach. So, you have JSPs for views; Servlet Controller + Actions for control and navigation. The logic is supposed to be out of Struts, it can be in EJBs, e.g. In my current system, the logic will be in the set of API classes. Even JSPs are not mandatory, it's just most people use Struts with them. Finally, I'm afraid it's not appropriate to refer to other Apache projects as horrible :) I'm a great fan of Cocoon too, but Struts is not bad, and sometimes fits requirements very well. thanks, Argyn -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 4:49 PM To: [EMAIL PROTECTED] Subject: Re: [OT] RE: cocoon struts together Struts is a horrible basis for business logic for a thousand reasons. Business logic best lives within an enterprise container and an application server. The basis of concurrency, fault tolerance, transaction management, clustering and the rest of the EJB contract make it pretty psycho to NOT use it. I would NEVER EVER do anything important in any web framework, be it cocoon or struts. No thanks the J2EE environment is the god of business logic as cocoon is, IMHO, the god of web presentation. Cocoon should be a CONSUMER of the J2EE functionality and not make any decisions whatsoever. - 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]
cocoon struts together
Hi, has someone any experiences with the comosition of struts and cocoon? I have a middleware on EJB and JCA which connects to some Systems like SAP. On this connects a webapplication which should be done with with struts. Some areas of this application should be transformed by cocoon in different outputs. My idea was to run some views with cocoon. A struts action would connect a pipeline from cocoon and passe the file which has to be transformed and visualized. Any suggestions or practices? Juraj - 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]
RE: cocoon struts together
Hi Juraj,
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
why are you considering Struts (at all)? I am interested in this as we often
meet this kind of setup/discussion and we try to convince people to go for a
Cocoon-only solution (of course) :-)
Matthew
--
Open Source Group Cocoon { Consulting, Training, Projects }
=
Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de
-
Cocoon book:
http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20
Weblogs:
http://radio.weblogs.com/0103021/
http://www.oreillynet.com/weblogs/author/1014
=
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 4:46 PM
To: [EMAIL PROTECTED]
Subject: cocoon struts together
Hi,
has someone any experiences with the comosition of struts and cocoon?
I have a middleware on EJB and JCA which connects to some Systems
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
transformed by cocoon in different outputs. My idea was to run
some views with cocoon. A struts action would connect a pipeline
from cocoon and passe the file which has to be transformed and visualized.
Any suggestions or practices?
Juraj
-
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]
-
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]
RE: cocoon struts together
We're working on a similar setup - Struts-based form logic, with views of the data processed by cocoon into html/pdf/excel. Currently we simply pull html cocoon content into jsp's with an http request (using: http://jakarta.apache.org/taglibs/doc/io-doc/index.html). It seems to work quite well for our needs, but it would be nice to be able to call the cocoon pipelines programmatically. Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 03 February 2003 15:46 To: [EMAIL PROTECTED] Subject: cocoon struts together Hi, has someone any experiences with the comosition of struts and cocoon? I have a middleware on EJB and JCA which connects to some Systems like SAP. On this connects a webapplication which should be done with with struts. Some areas of this application should be transformed by cocoon in different outputs. My idea was to run some views with cocoon. A struts action would connect a pipeline from cocoon and passe the file which has to be transformed and visualized. Any suggestions or practices? Juraj - 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] - 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]
AW: cocoon struts together
Hi Matthew,
Yes of course ;-) There is some experience with struts allready. With cocoon not so
much. And this question is a study about the possibilities. I think the synergy of
both frameworks can (perhaps) realize very powerful solutioons.
Juraj
-Ursprüngliche Nachricht-
Von: Matthew Langham [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 3. Februar 2003 16:58
An: [EMAIL PROTECTED]
Betreff: RE: cocoon struts together
Hi Juraj,
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
why are you considering Struts (at all)? I am interested in this as we often
meet this kind of setup/discussion and we try to convince people to go for a
Cocoon-only solution (of course) :-)
Matthew
--
Open Source Group Cocoon { Consulting, Training, Projects }
=
Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de
-
Cocoon book:
http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20
Weblogs:
http://radio.weblogs.com/0103021/
http://www.oreillynet.com/weblogs/author/1014
=
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 4:46 PM
To: [EMAIL PROTECTED]
Subject: cocoon struts together
Hi,
has someone any experiences with the comosition of struts and cocoon?
I have a middleware on EJB and JCA which connects to some Systems
like SAP. On this connects a webapplication which should be done
with with struts. Some areas of this application should be
transformed by cocoon in different outputs. My idea was to run
some views with cocoon. A struts action would connect a pipeline
from cocoon and passe the file which has to be transformed and visualized.
Any suggestions or practices?
Juraj
-
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]
-
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]
-
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]
AW: cocoon struts together
Hi Richard, I am not sure if my idea can work. My Struts controller gets some data from the EJB. This data can be serialized(castor) into a directory. The cocoon pipeline is configured to process all request of this directory. After serializing the xml data the controller forwards to the xml document. Castory will be activated and will transform the data. Can this work? Juraj -Ursprüngliche Nachricht- Von: Richard Bounds [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 3. Februar 2003 17:06 An: [EMAIL PROTECTED] Betreff: RE: cocoon struts together We're working on a similar setup - Struts-based form logic, with views of the data processed by cocoon into html/pdf/excel. Currently we simply pull html cocoon content into jsp's with an http request (using: http://jakarta.apache.org/taglibs/doc/io-doc/index.html). It seems to work quite well for our needs, but it would be nice to be able to call the cocoon pipelines programmatically. Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 03 February 2003 15:46 To: [EMAIL PROTECTED] Subject: cocoon struts together Hi, has someone any experiences with the comosition of struts and cocoon? I have a middleware on EJB and JCA which connects to some Systems like SAP. On this connects a webapplication which should be done with with struts. Some areas of this application should be transformed by cocoon in different outputs. My idea was to run some views with cocoon. A struts action would connect a pipeline from cocoon and passe the file which has to be transformed and visualized. Any suggestions or practices? Juraj - 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] - 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] - 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]
RE: cocoon struts together
http://jakarta.apache.org/taglibs/doc/io-doc/index.html). It seems to work quite well for our needs, but it would be nice to be able to call the cocoon pipelines programmatically. Check out the CocoonBean, recently added to the dev version 2.1 in CVS (org.apache.cocoon.bean.CocoonBean). It allows you to have cocoon generate a page or pages and save them to disc (or send them to any 'Destination'). Alternatively, you can write the content for a specific page to an output stream. Looking at the code, the latter functionality looks broken to me at the moment - I'll give it a go now. If you want to use this, let me know and I may be able to send you a patch. Regards, Upayavira - 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]
