RE: Too much java in xsp
OK, why not writing a generator. But how can I get the values from the form to my generator? With the xsp generator it was easy, I only had to use :xsp:request get-parameter ... At 12:31 12/02/2003 -0500, you wrote: Well, Robert's suggestion is a good one and I've already written a tutorial about that (http://xml.apache.org/cocoon/tutorial/tutorial-generator.htmlhttp://xml.apache.org/cocoon/tutorial/tutorial-generator.html) But if that seems out of reach, you can use something like: xsp:page xsp:structure xsp:includeyourpackage.*/xsp:include /xsp:structure ... to include any java class in your xsp and use it like you would anywhere else: yourpackage.YourHelper.doSomethingComplicated(object); or whatever. In the end, your xsp winds up as a java file (a Generator) so you can do whatever can be done in java from within an xsp (except inheritance??) including code encapsulation. See http://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concepts.html#java-logicsheetshttp://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concepts.html#java-logicsheets for some specific things to look out for when doing that - the doc is aimed at logicsheet development, but applies to this as well. Some of the logicsheets do this as well, and would make good examples, though they are slightly more complicated because they introduce one layer of abstraction from an xsp. Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:03 PM To: [EMAIL PROTECTED] Subject: RE: Too much java in xsp Please, can you give me more information (hints) about the helper Geoff ? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.htmlhttp://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: Too much java in xsp
I'll write a generator. FInally it's a good idea. Thanks for the advices. At 09:29 13/02/2003 +0100, you wrote: OK, why not writing a generator. But how can I get the values from the form to my generator? With the xsp generator it was easy, I only had to use :xsp:request get-parameter ... At 12:31 12/02/2003 -0500, you wrote: Well, Robert's suggestion is a good one and I've already written a tutorial about that (http://xml.apache.org/cocoon/tutorial/tutorial-generator.htmlhttp://xml.apache.org/cocoon/tutorial/tutorial-generator.html) But if that seems out of reach, you can use something like: xsp:page xsp:structure xsp:includeyourpackage.*/xsp:include /xsp:structure ... to include any java class in your xsp and use it like you would anywhere else: yourpackage.YourHelper.doSomethingComplicated(object); or whatever. In the end, your xsp winds up as a java file (a Generator) so you can do whatever can be done in java from within an xsp (except inheritance??) including code encapsulation. See http://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concepts.html#java-logicsheetshttp://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concepts.html#java-logicsheets for some specific things to look out for when doing that - the doc is aimed at logicsheet development, but applies to this as well. Some of the logicsheets do this as well, and would make good examples, though they are slightly more complicated because they introduce one layer of abstraction from an xsp. Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:03 PM To: [EMAIL PROTECTED] Subject: RE: Too much java in xsp Please, can you give me more information (hints) about the helper Geoff ? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.htmlhttp://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: Too much java in xsp
Title: RE: Too much java in xsp From your other message sounds like you figured it out, but request parameters are handled in the tutorial I sent a link to. Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 3:30 AM To: [EMAIL PROTECTED] Subject: RE: Too much java in xsp OK, why not writing a generator. But how can I get the values from the form to my generator? With the xsp generator it was easy, I only had to use :xsp:request get-parameter ... At 12:31 12/02/2003 -0500, you wrote: Well, Robert's suggestion is a good one and I've already written a tutorial about that (http://xml.apache.org/cocoon/tutorial/tutorial-generator.ht mlhttp://xml.apache.org/cocoon/tutorial/tutorial-generator.html) But if that seems out of reach, you can use something like: xsp:page xsp:structure xsp:includeyourpackage.*/xsp:include /xsp:structure ... to include any java class in your xsp and use it like you would anywhere else: yourpackage.YourHelper.doSomethingComplicated(object); or whatever. In the end, your xsp winds up as a java file (a Generator) so you can do whatever can be done in java from within an xsp (except inheritance??) including code encapsulation. See http://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concept s.html#java-logicsheetshttp://xml.apache.org/cocoon/userdocs/ xsp/logicsheet-concepts.html#java-logicsheets for some specific things to look out for when doing that - the doc is aimed at logicsheet development, but applies to this as well. Some of the logicsheets do this as well, and would make good examples, though they are slightly more complicated because they introduce one layer of abstraction from an xsp. Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:03 PM To: [EMAIL PROTECTED] Subject: RE: Too much java in xsp Please, can you give me more information (hints) about the helper Geoff ? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.htmlhttp://xml.apach e.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: Too much java in xsp
II figured it out. It was a stupid question from me. - 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]
Too much java in xsp
I'm using an xsp in which I manipulate some code (xsp:request parameters, for example). But unfortunately, There is too much code java in it and so the xsp is very HUGE. I was thinking about using an action in the sitemap to modify my document instead of java code in the xsp, is it a good idea ? am I on the right way ? - 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: Too much java in xsp
Probably a generator actually. Use generators for things that are more complex. XSP should be used, IMHO, only for generation with small amounts of code. -- Robert - Original Message - From: Lionel Crine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 12, 2003 5:40 PM Subject: Too much java in xsp I'm using an xsp in which I manipulate some code (xsp:request parameters, for example). But unfortunately, There is too much code java in it and so the xsp is very HUGE. I was thinking about using an action in the sitemap to modify my document instead of java code in the xsp, is it a good idea ? am I on the right way ? - 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: Too much java in xsp
Title: RE: Too much java in xsp why don't you create a helper class with your heavy duty java in it? Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 11:40 AM To: [EMAIL PROTECTED] Subject: Too much java in xsp I'm using an xsp in which I manipulate some code (xsp:request parameters, for example). But unfortunately, There is too much code java in it and so the xsp is very HUGE. I was thinking about using an action in the sitemap to modify my document instead of java code in the xsp, is it a good idea ? am I on the right way ? - 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: Too much java in xsp
Please, can you give me more information (hints) about the helper Geoff ? - 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: Too much java in xsp
Robert, Here is my issue : I have create a portal : When I come to the form page : 1/An xsp file is generated from the form. 2/This xsp get the request parameters and modify the structure as I want it to be 3/A transformer Get the SAX events of the xsp generator, get information from XML DB and return a response 4/ Finally I dispay the result in the browser. I think creating a new generator would be an error. - 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: Too much java in xsp
Title: RE: Too much java in xsp Well, Robert's suggestion is a good one and I've already written a tutorial about that (http://xml.apache.org/cocoon/tutorial/tutorial-generator.html) But if that seems out of reach, you can use something like: xsp:page xsp:structure xsp:includeyourpackage.*/xsp:include /xsp:structure ... to include any java class in your xsp and use it like you would anywhere else: yourpackage.YourHelper.doSomethingComplicated(object); or whatever. In the end, your xsp winds up as a java file (a Generator) so you can do whatever can be done in java from within an xsp (except inheritance??) including code encapsulation. See http://xml.apache.org/cocoon/userdocs/xsp/logicsheet-concepts.html#java-logicsheets for some specific things to look out for when doing that - the doc is aimed at logicsheet development, but applies to this as well. Some of the logicsheets do this as well, and would make good examples, though they are slightly more complicated because they introduce one layer of abstraction from an xsp. Geoff -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:03 PM To: [EMAIL PROTECTED] Subject: RE: Too much java in xsp Please, can you give me more information (hints) about the helper Geoff ? - 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: Too much java in xsp
Yes, Sir. Absolutely use an action and remove JAVA as much as possible from the xsp. When you do this and know how to pass a STRING ARRAY into the XML/XSL without the need of the XSP - please let me know - it is the only thing that i still rely on an XSP for. -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 11:40 AM To: [EMAIL PROTECTED] Subject: Too much java in xsp I'm using an xsp in which I manipulate some code (xsp:request parameters, for example). But unfortunately, There is too much code java in it and so the xsp is very HUGE. I was thinking about using an action in the sitemap to modify my document instead of java code in the xsp, is it a good idea ? am I on the right way ? - 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]
