Re: Hello ! Can I generate PDFs and XLS through a document object and Cocoon ?
Abuout the Xreporter you can find on http://xreporter.cocoondev.org/index.html Hello ! Does xreporter is samilar to Cocoon ? I can't search any tutorial of it ! Thank you ! What about using the cocoon xreporter? Hi Jonathon If you already have a class which generates a JDOM object, you could refer to it in an XSP (this is probably the easiest way), or write a Transformer that wraps the JDOM object and serializes it as SAX. Or, if you don't already have this Java class, you should consider doing the whole thing using existing Cocoon components, without Java programming, with a pipeline like this: 1) use the SQLTransformer to query the database 2) use an XSLT to convert the SQL results (XML) to another XML representation, appropriate to your data model 3) use another XSLT to convert to your presentation format (XLS) Cheers! Con Dear Joerg , Hello ! I am so pleased to hear it is possible . I want to design my application as : 1. some data are stored in a database 2. a class gets a resultset and create a JDOM document object . 3. the class fit the database data to the document object . 4. how can I match the JDOM document object to the corresponding XSL and generate a XLS ? So , possible ? Thank you ! --- Joerg Heinicke [EMAIL PROTECTED] wrote: Yes, should be possible by writing your own simple generator. Where do you get the JDOM object from? -- Best regards, Yury Mikhienko. IT ERP group head, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSPGen. RequestParameter Encoding
Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: AW: AW: File existence
Can you send the exact error and the stack trace you got ?
On 19/09/2003 09:32, Mustafa Ali, Halgurt wrote:
Hi,
I had 2 days ago a question about the way to test whether a file exist
or not, I got a lot of answers, the answers are list below, the last
suggestion was to write something like that:
map:pipeline
map:match pattern=handling
map:act type=resource-exists
map:parameter name=url value=context://{request-param:ID}.xml/
!-- if resource exists : --
map:generate type=file src={request-param:ID}.xml /
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true /
/map:transform
map:serialize type=html /
/map:act
!-- else --
map:generate type=file src=default.xml /
map:transform type=xslt src=form2data.xsl /
map:serialize type=html /
/map:match
/map:pipeline
but then I get an error message for the red marked line:
error while creating node generate at (red line)
Please help, I am really despaired.
Many thanks
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 17. September 2003 10:29
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: File existence
it is *{request-param:ID}* instead of {request-parameter:ID}
--
Olivier Billard
On 17/09/2003 09:41, Mustafa Ali, Halgurt wrote:
Oh it seems no to work, I got an Error, her eis it:
Invalid pattern '{request-parameter:ID}'
Do you have an idea what this is?
regards,
-Ursprüngliche Nachricht-
Von: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2003 15:11
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: File existence
Try to pass the value of {request-param:ID} to the stylesheet or debug
it in
another way and tell us if this works correctly.
Joerg
Mustafa Ali, Halgurt wrote:
But I am using different stylesheets, I made a mistake, I corrected my
pipeline and now the Otherwise part will be taken, never mind if the
file exists or not, I think there is an error in the red line.
Thanks,
Halgurt
-Ursprüngliche Nachricht-
Von: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2003 14:56
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
Hi:
I never used it. From your pipeline, it looks like your are always
generating from the same source no matter if the fileexists or not.
map:generate type=file src=default.xml /
Then you use a tranformer in both cases, the only diference is when you
the file exists, you send parameters to the tranformer:
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
But when the file does not exists you dont send them! Can be this the
source of the error?
Best Regards,
Antonio Gallardo
Mustafa Ali, Halgurt dijo:
Thank you, I tried it, but I have a Problem, I am getting an empty page,
here is my pipeline:
map:pipeline
map:match pattern=handling
map:select type=resource-exists
map:when test={request-param:ID}.xml
map:generate type=file src=default.xml /
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true /
/map:transform
/map:when
map:otherwise
map:generate type=file src=default.xml /
map:transform type=xslt src=form3data.xsl /
/map:otherwise
/map:select
map:serialize type=html /
/map:match
/map:pipeline
Am I doing something wrong?
Many thanks,
Halgurt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: File existence
Sorry, I think I misinterpreted your goal in your pipe...
To fit what you want, the red line whould be :
map:generate type=file src=default.xml /
--
Olivier Billard
On 19/09/2003 09:32, Mustafa Ali, Halgurt wrote:
Hi,
I had 2 days ago a question about the way to test whether a file exist
or not, I got a lot of answers, the answers are list below, the last
suggestion was to write something like that:
map:pipeline
map:match pattern=handling
map:act type=resource-exists
map:parameter name=url value=context://{request-param:ID}.xml/
!-- if resource exists : --
map:generate type=file src={request-param:ID}.xml /
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true /
/map:transform
map:serialize type=html /
/map:act
!-- else --
map:generate type=file src=default.xml /
map:transform type=xslt src=form2data.xsl /
map:serialize type=html /
/map:match
/map:pipeline
but then I get an error message for the red marked line:
error while creating node generate at (red line)
Please help, I am really despaired.
Many thanks
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 17. September 2003 10:29
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: File existence
it is *{request-param:ID}* instead of {request-parameter:ID}
--
Olivier Billard
On 17/09/2003 09:41, Mustafa Ali, Halgurt wrote:
Oh it seems no to work, I got an Error, her eis it:
Invalid pattern '{request-parameter:ID}'
Do you have an idea what this is?
regards,
-Ursprüngliche Nachricht-
Von: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2003 15:11
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: File existence
Try to pass the value of {request-param:ID} to the stylesheet or debug
it in
another way and tell us if this works correctly.
Joerg
Mustafa Ali, Halgurt wrote:
But I am using different stylesheets, I made a mistake, I corrected my
pipeline and now the Otherwise part will be taken, never mind if the
file exists or not, I think there is an error in the red line.
Thanks,
Halgurt
-Ursprüngliche Nachricht-
Von: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2003 14:56
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
Hi:
I never used it. From your pipeline, it looks like your are always
generating from the same source no matter if the fileexists or not.
map:generate type=file src=default.xml /
Then you use a tranformer in both cases, the only diference is when you
the file exists, you send parameters to the tranformer:
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
But when the file does not exists you dont send them! Can be this the
source of the error?
Best Regards,
Antonio Gallardo
Mustafa Ali, Halgurt dijo:
Thank you, I tried it, but I have a Problem, I am getting an empty page,
here is my pipeline:
map:pipeline
map:match pattern=handling
map:select type=resource-exists
map:when test={request-param:ID}.xml
map:generate type=file src=default.xml /
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true /
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true /
/map:transform
/map:when
map:otherwise
map:generate type=file src=default.xml /
map:transform type=xslt src=form3data.xsl /
/map:otherwise
/map:select
map:serialize type=html /
/map:match
/map:pipeline
Am I doing something wrong?
Many thanks,
Halgurt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSPGen. RequestParameter Encoding
On Fri, 19 Sep 2003 09:00:44 +0200 Christoph Strehl [EMAIL PROTECTED] wrote: Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi,Christoph! My experience small in use JSP, if you asked, how inquiry with HTML as Parameter name = query to receive with the coding distinct from ISO-8859-1, I did(made) it as follows: myfile.jsp: ... String requestEnc = request.getCharacterEncoding(); if( requestEnc==null ) requestEnc=ISO-8859-1; String clientEnc = request.getParameter(charset); if( clientEnc==null ) clientEnc=Cp1251; String queryString = new String(request.getParameter(query).getBytes(requestEnc),clientEnc); ... Vladimir Yuryev. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: File existence
Hi Halgurt,
Have you tried without the context:// in the url parameter of the action ?
On 19/09/2003 11:13, Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no matter whether the file exists or not, it ignores the act.../act part, do you have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules: ComponentSelector could not find the component for hint [request-parameter] (key [request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: File existence
Can you send the exact error and the stack trace you got ?
--
--
Olivier BILLARD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: File existence
You seem to be having a lot of trouble with this. Have you considered
using flow? With the below, if the file exists, the pattern=exists
pipeline will be shown, otherwise the pattern=non-existent pipeline
will be shown.
map:match pattern=page
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exist-uri value=exists/
map:parameter name=non-exist-uri value=non-existent/
/map:call
/map:match
map:match pattern=exists
whatever
/map:match
map:match pattern=non-existent
whatever
/map:match
In your sitemap, just before the map:pipelines element:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
Create a file called flow/exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
HTH. Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no matter whether the file exists or not, it ignores the act.../act part, do you have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules: ComponentSelector could not find the component for hint [request-parameter] (key [request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: File existence
Can you send the exact error and the stack trace you got ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: File existence
Hello,
I did it as you said, but I got this error message:
(Exists is not a function)
Another question, when I call the Pipeline handling, I don't have just ID as
parameter, even more, how can I pass these parameters to the non-exists pipeline?
Here is my pipelines:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
map:pipelines
map:pipeline
map:match pattern=handling
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exists-uri value=exists/
map:parameter name=non-exists-uri value=non-exists/
/map:call
/map:match
/map:pipeline
map:pipeline
map:match pattern=exists
map:generate type=file src={request-param:ID}.xml/
map:transform type=xslt src=form3data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
/map:pipeline
map:pipeline
map:match pattern=non-exists
map:generate type=file src=default.xml/
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 11:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
You seem to be having a lot of trouble with this. Have you considered
using flow? With the below, if the file exists, the pattern=exists
pipeline will be shown, otherwise the pattern=non-existent pipeline
will be shown.
map:match pattern=page
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exist-uri value=exists/
map:parameter name=non-exist-uri value=non-existent/
/map:call
/map:match
map:match pattern=exists
whatever
/map:match
map:match pattern=non-existent
whatever
/map:match
In your sitemap, just before the map:pipelines element:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
Create a file called flow/exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
HTH. Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no
matter whether the file exists or not, it ignores the act.../act part, do you
have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so
sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules:
ComponentSelector could not find the component for hint [request-parameter] (key
[request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: File existence
Can you send the exact error and the stack trace you got ?
-
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]
Re: AW: AW: File existence
Mustafa Ali, Halgurt wrote:
Hello,
I did it as you said, but I got this error message:
(Exists is not a function)
Note that Javascript is case sensitive. Have you got it as Exists or as
exists?
Another question, when I call the Pipeline handling, I don't have just ID as parameter, even more, how can I pass these parameters to the non-exists pipeline?
You should be able to get at the request parameter inside the non-exists
pipeline just as in any other, e.g. with map:parameter name=filename
value={request-param:id}.xml/
Regards, Upayavira
Here is my pipelines:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
map:pipelines
map:pipeline
map:match pattern=handling
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exists-uri value=exists/
map:parameter name=non-exists-uri value=non-exists/
/map:call
/map:match
/map:pipeline
map:pipeline
map:match pattern=exists
map:generate type=file src={request-param:ID}.xml/
map:transform type=xslt src=form3data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
/map:pipeline
map:pipeline
map:match pattern=non-exists
map:generate type=file src=default.xml/
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 11:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
You seem to be having a lot of trouble with this. Have you considered
using flow? With the below, if the file exists, the pattern=exists
pipeline will be shown, otherwise the pattern=non-existent pipeline
will be shown.
map:match pattern=page
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exist-uri value=exists/
map:parameter name=non-exist-uri value=non-existent/
/map:call
/map:match
map:match pattern=exists
whatever
/map:match
map:match pattern=non-existent
whatever
/map:match
In your sitemap, just before the map:pipelines element:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
Create a file called flow/exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
HTH. Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no matter whether the file exists or not, it ignores the act.../act part, do you have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules: ComponentSelector could not find the component for hint [request-parameter] (key [request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: File existence
Can you send the exact error and the stack trace you got ?
-
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]
AW: AW: AW: File existence
Hello,
I've got it as exists, her ist he content of my exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
Have I forgotten anything?
regards
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 13:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: File existence
Mustafa Ali, Halgurt wrote:
Hello,
I did it as you said, but I got this error message:
(Exists is not a function)
Note that Javascript is case sensitive. Have you got it as Exists or as
exists?
Another question, when I call the Pipeline handling, I don't have just ID as
parameter, even more, how can I pass these parameters to the non-exists pipeline?
You should be able to get at the request parameter inside the non-exists
pipeline just as in any other, e.g. with map:parameter name=filename
value={request-param:id}.xml/
Regards, Upayavira
Here is my pipelines:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
map:pipelines
map:pipeline
map:match pattern=handling
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exists-uri value=exists/
map:parameter name=non-exists-uri value=non-exists/
/map:call
/map:match
/map:pipeline
map:pipeline
map:match pattern=exists
map:generate type=file src={request-param:ID}.xml/
map:transform type=xslt src=form3data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
/map:pipeline
map:pipeline
map:match pattern=non-exists
map:generate type=file src=default.xml/
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 11:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
You seem to be having a lot of trouble with this. Have you considered
using flow? With the below, if the file exists, the pattern=exists
pipeline will be shown, otherwise the pattern=non-existent pipeline
will be shown.
map:match pattern=page
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exist-uri value=exists/
map:parameter name=non-exist-uri value=non-existent/
/map:call
/map:match
map:match pattern=exists
whatever
/map:match
map:match pattern=non-existent
whatever
/map:match
In your sitemap, just before the map:pipelines element:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
Create a file called flow/exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
HTH. Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no
matter whether the file exists or not, it ignores the act.../act part, do you
have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so
sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules:
ComponentSelector could not find the component for hint [request-parameter] (key
[request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: File existence
Re: AW: AW: AW: File existence
What error are you getting? Can you show me the code you put into your
sitemap?
Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Hello,
I've got it as exists, her ist he content of my exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
Have I forgotten anything?
regards
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 13:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: File existence
Mustafa Ali, Halgurt wrote:
Hello,
I did it as you said, but I got this error message:
(Exists is not a function)
Note that Javascript is case sensitive. Have you got it as Exists or as
exists?
Another question, when I call the Pipeline handling, I don't have just ID as parameter, even more, how can I pass these parameters to the non-exists pipeline?
You should be able to get at the request parameter inside the non-exists
pipeline just as in any other, e.g. with map:parameter name=filename
value={request-param:id}.xml/
Regards, Upayavira
Here is my pipelines:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
map:pipelines
map:pipeline
map:match pattern=handling
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exists-uri value=exists/
map:parameter name=non-exists-uri value=non-exists/
/map:call
/map:match
/map:pipeline
map:pipeline
map:match pattern=exists
map:generate type=file src={request-param:ID}.xml/
map:transform type=xslt src=form3data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
/map:pipeline
map:pipeline
map:match pattern=non-exists
map:generate type=file src=default.xml/
map:transform type=xslt src=form2data.xsl
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=write-source
map:parameter name=use-request-parameters value=true/
/map:transform
map:transform type=xslt src=form2html.xsl mime-type=text/xml
map:parameter name=use-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:match
-Ursprüngliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 11:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: File existence
You seem to be having a lot of trouble with this. Have you considered
using flow? With the below, if the file exists, the pattern=exists
pipeline will be shown, otherwise the pattern=non-existent pipeline
will be shown.
map:match pattern=page
map:call function=exists
map:parameter name=test-uri value=context://{request-param:ID}.xml/
map:parameter name=exist-uri value=exists/
map:parameter name=non-exist-uri value=non-existent/
/map:call
/map:match
map:match pattern=exists
whatever
/map:match
map:match pattern=non-existent
whatever
/map:match
In your sitemap, just before the map:pipelines element:
map:flow language=javascript
map:script src=flow/exists.js/
/map:flow
Create a file called flow/exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
HTH. Regards, Upayavira
Mustafa Ali, Halgurt wrote:
Oh, you are right, I changed it, but the pipeline still choose the second part, no matter whether the file exists or not, it ignores the act.../act part, do you have an Idea what is perhaps wrong?
Thanks,
Halgurt
PS: I am a Kurd and my first name is Halgurt, we don't have surnames, Mustafa is my
father and Ali my Grandfather.
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 10:02
An: [EMAIL PROTECTED]
Betreff: Re: File existence
Hi Halgurt (I'm french and didn't manage to see what is your name and first name, so sorry
if i'm wrong),
Please check if you *really* didn't wrote {request-parameter:ID} instead of
{request-param:ID}, because the error seem to point a mistake of this type...
see :
cause: org.apache.avalon.framework.component.ComponentException: *input-modules*:
ComponentSelector could not find the component for hint [*request-parameter*] (key
[*request-parameter*])
- this should be request-param...
--
Olivier
On 19/09/2003 10:30, Mustafa Ali, Halgurt wrote:
Sure, here is it:
snip/
cause: org.apache.avalon.framework.component.ComponentException: input-modules: ComponentSelector could not find the component for hint [request-parameter] (key [request-parameter])
-Ursprüngliche Nachricht-
Von: Olivier Billard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 09:19
An: [EMAIL
Re: AW: AW: AW: File existence
Mustafa Ali, Halgurt wrote:
Hello,
I've got it as exists, her ist he content of my exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
Have I forgotten anything?
A closing paren at the end of each sendPage call...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JSP in C2.1.1
After about 5 hours of building cocoon-distributions, testing and googling I am quite despaired about using JSP in cocoon. Cocoon runs fine but if it comes to JSPs not even the built-in examples work. org.apache.cocoon.ProcessingException: ServletException in JSPReader.generate() is the exception I get with no further detail what could be wrong. I have read about this problem in mailing list archives and unfortunately there wasn't anyone who had a clear answer or solution for that problem although it has been asked more than once. Earlier this morning I had C2.0.4 working in Tomcat 4.0.12 but there I stumbled over a bug that was reported in some mailing lists: jsp:include ../ doesn't work properly in a Cocoon-pipeline and again - no suitable solution on the web, only some people who discovered the same thing. Is there anyone out there who had already successfully worked with JSPs in Cocoon2.1.1? -Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: AW: File existence
You are right, but that was even not the reason, I changed it and am still getting the
same error.
-Ursprüngliche Nachricht-
Von: Geoff Howard [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 19. September 2003 14:08
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: File existence
Mustafa Ali, Halgurt wrote:
Hello,
I've got it as exists, her ist he content of my exists.js:
function exists() {
var file = new java.io.File(cocoon.parameters[test-uri]);
if (file.exists()) {
cocoon.sendPage(cocoon.parameters[exists-uri];
} else {
cocoon.sendPage(cocoon.parameters[non-exist-uri];
}
}
Have I forgotten anything?
A closing paren at the end of each sendPage call...
-
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]
serializer kicking in before transformer finished
Hi,
In my custom transformer (extends AbstractDOMTransformer implements
LogEnabled, Cacheable) I have the following :
public void endDocument() throws SAXException {
super.endDocument(); // required
try {
helper.endDocument(); // this call potentially takes a few
seconds
} catch (Exception e) {
throw new SAXException(e);
}
}
sitemap snip:
...
map:transform type=custom/
map:serialize type=blob/
..
The result of this is that the blob-serializer seems to kick in before
the custom transformer is fully finished. The output i'm getting is the
output as if the transformation never occured. The logfile entries
indicate the same, blob logentries appear in between my transformer entries.
Can i get around this? Is this expected behaviour ?
rgds
Jorg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: create a transformer that is a combinaison of transformers
Tim: here is work toward this, search on the dev list for Virtual Pipeline Components. I do not believe this has been implemented yet, but would be glad to be proved wrong. Sounds like something I would be interested in as well. In the mean time, you can define a map:resource that contains your transforms. Then you can call the resource where you wish to have the compound transform performed. It gives you the same effect of modularity, just with a different syntax. The only issue here is that map:call never returns (last I checked...be nice if it had a parameter so that you could set return=true)so it limits the flexibility of this approach. Once you call a map resource, your flow of control in the main pipeline is terminated. Any ideas on how to get around that? Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP in XSL
Jose Antonio Rosa dos Santos Junior wrote: Hi I´m trying to put some java code in my XSL file but it seems to be not working. Every xsp tag i put in it is ignored, and the java code is viewed in the generated HTML page. I also made a separated logic sheet, but it only works in my XSP file. If i put it in the XSL file it is ignored too. Am i doing something wrong? Jose Antonio wait, XSP is a interpreted by a generator, while XSL is used in a transformer... aren't you mixing the two concepts ? Could you provide us with the relevant sitemap portion ? Regards, -- Luca Morandini GIS Consultant [EMAIL PROTECTED] http://space.virgilio.it/kumora/index.html -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: XSP in XSL
hmmm.. Maybe. Haven´t thought that way. Can i link two pipelines to do that instead?
I´m sending what i am trying to do:
stemap.xmap:
...
map:pipeline
map:match type=wildcard pattern=*.xsp
map:generate type=serverpages src={1}.xsp/
map:transform type=xslt src=pagina-fnde2html.xsl/
map:serialize type=html/
/map:match
/map:pipeline
...
pagina-fnde2html.xsl:
...
xsl:template match=pagina
...
!-- this doesn´t work --
xsp:logic
SimpleDateFormat format = new SimpleDateFormat(dd/MM/);
/xsp:logic
xsp:expr
format.format(new Date())
/xsp:expr
...
/xsl:template
...
teste.xsp:
?xml version='1.0' encoding='ISO-8859-1'?
xsp:page
xmlns:xsp=http://apache.org/xsp;
pagina
tituloNheco nheco/titulo
conteudo
!-- this works --
xsp:expr
new Date()
/xsp:expr
/conteudo
/pagina
/xsp:page
Jose Antonio
-Mensagem original-
De: Luca Morandini [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira, 19 de setembro de 2003 13:10
Para: [EMAIL PROTECTED]
Assunto: Re: XSP in XSL
Jose Antonio Rosa dos Santos Junior wrote:
Hi
I´m trying to put some java code in my XSL file but it seems to be not working.
Every xsp tag i put in it is ignored, and the java code is viewed in the generated
HTML page.
I also made a separated logic sheet, but it only works in my XSP file. If i put it
in the XSL file it is ignored too.
Am i doing something wrong?
Jose Antonio
wait, XSP is a interpreted by a generator, while XSL is used in a
transformer... aren't you mixing the two concepts ?
Could you provide us with the relevant sitemap portion ?
Regards,
--
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://space.virgilio.it/kumora/index.html
--
-
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]
Re: RES: XSP in XSL
Jose Antonio Rosa dos Santos Junior wrote:
hmmm.. Maybe. Haven´t thought that way. Can i link two pipelines to do that instead?
I´m sending what i am trying to do:
stemap.xmap:
...
map:pipeline
map:match type=wildcard pattern=*.xsp
map:generate type=serverpages src={1}.xsp/
map:transform type=xslt src=pagina-fnde2html.xsl/
map:serialize type=html/
/map:match
/map:pipeline
...
pagina-fnde2html.xsl:
...
xsl:template match=pagina
...
!-- this doesn´t work --
xsp:logic
SimpleDateFormat format = new SimpleDateFormat(dd/MM/);
/xsp:logic
xsp:expr
format.format(new Date())
/xsp:expr
...
/xsl:template
...
teste.xsp:
?xml version='1.0' encoding='ISO-8859-1'?
xsp:page
xmlns:xsp=http://apache.org/xsp;
No, you cannot.
Specifically, you cannot use XSP tags in your XSL: XSP is interpreted
only in the generation stage.
What XSL does is just to transform (using the XSL language, not the XSP
one) the output produced by the XSP.
If you really can't do without Java in the XSL, take a look at the XSL
extension of Xalan, using which you will be able call Java within an
XSL, like:
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:java=http://xml.apache.org/xslt/java;
... xsl:variable name=formatter
select=java:java.text.SimpleDateFormat.new('dd-MM-')/
xsl:variable name=dateselect=java:java.util.Date.new()/
xsl:value-of select=java:format($formatter, $date)/
...
...which, coincidentally, you were trying to achieve in the first place
I suppose :)
Regards,
--
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://space.virgilio.it/kumora/index.html
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: create a transformer that is a combinaison of transformers
--- Andrzej Jan Taramina [EMAIL PROTECTED] wrote: Tim: In the mean time, you can define a map:resource that contains your transforms. Then you can call the resource where you wish to have the compound transform performed. It gives you the same effect of modularity, just with a different syntax. The only issue here is that map:call never returns (last I checked...be nice if it had a parameter so that you could set return=true)so it limits the flexibility of this approach. Once you call a map resource, your flow of control in the main pipeline is terminated. Any ideas on how to get around that? The documentation is confused on this issue, but resources *can* return when using cocoon-2.1, as mentioned here: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=105939689524200w=2 Since the feature is part of the interpreted sitemap, you *might* even be able to do this with cocoon-2.0 if you configure Cocoon to use the interpreted sitemap (TreeProcessor) implementation. Let me know if you need help with this. This page documents the change: http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html#Calling+resources Here are some examples you could follow: http://wiki.cocoondev.org/Wiki.jsp?page=CleanerSiteMapsThroughResources --Tim Larson __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
A stupid Question on Portal Framework
Hello, I am sorry for a probably stupid question, but I just wanted to try the portal framework with the sunspotdemo-portal, but I get an exception directly after starting it on the left side of the frameset (see below). Maybe someone knows the solution, before I try to find the problem by myself? Regards, Hauke An Error Occurred Unable to get transformer handler for styles/login-html.xsl org.apache.cocoon.ProcessingException: Unable to get transformer handler for styles/login-html.xsl: org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in creating Transform Handler cause: java.lang.NullPointerException full exception chain stacktrace[hide] Original Exception: org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in creating Transform Handler at org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAnd Validity(XSLTProcessorImpl.java:380) at org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.j ava:302) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPi peline(AbstractProcessingPipeline.java:394) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe line.setupPipeline(AbstractCachingProcessingPipeline.java:652) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.prepare Pipeline(AbstractProcessingPipeline.java:508) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process (AbstractProcessingPipeline.java:470) at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke( SerializeNode.java:150) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i nvoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P ipelineNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:161) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:327) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:309) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun tNode.java:133) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i nvoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P ipelineNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:161) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:327) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:309) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun tNode.java:133) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i nvoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P ipelineNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:161) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:327) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:309) at org.apache.cocoon.Cocoon.process(Cocoon.java:639) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1096) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:286) at
SOLVED: Executing multiple pipelines for a request?
I had asked: I have a situation where I need to transform a single input XML document into multiple (3 or 4 actually) output documents (which will be stored in a database). It's code generation functiohnality (using Cocoon to generate Cocoon code itself) which is where the need for the multiple files arises. I haven't come up with a good way to accomplish this in a single request. Now that I know that map:call (thanks Tom) in 2.1.1 will return (it's a gosub now, not a goto), that solves the problem very nicely. All I need to do is to create a resource for each branch that I want to execute and then do as many map:calls in a row as I need. The sub pipes (resources) can also be set up to return status information on whether they succeeded or not, so that can be used to control whether to stop the main pipeline in the even of an error. It would also be possible to make each sub pipe acts as an identity transform, then it becomes easy to create a pipeline that takes a single input document and creates 4 different outputs from it (each output would be stored into a database in my case). Though I'm not sure that it wouldn't be easier for the subpipe to just use it's own generator to get the original starting document. Awesome! Thanks for all the help from everyone Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSPGen. RequestParameter Encoding
Tony ( others), Is this the same problem we talked about last week on wsproxy parameter encoding? http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h tml That thread was left hanging. Jeff -Original Message- From: Christoph Strehl [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 12:01 AM To: [EMAIL PROTECTED] Subject: JSPGen. RequestParameter Encoding Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - 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]
Re: JSPGen. RequestParameter Encoding
Jeff Ramsdale wrote: Tony ( others), Is this the same problem we talked about last week on wsproxy parameter encoding? http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h tml That thread was left hanging. Hrm.. it seems similar, but I'm not too sure. As far as the wsproxy, goes, perhaps we can try to track down where the spaces are being fiddled with. I would be curious to find out if the wsproxy generator is changing the spaces or if it's coming from somewhere else. Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [PATCH QUEUE] Summary September 20 2003
--- This mail is generated automatically using Jakarta Ant. Contents are automatically downloaded from Apache's Bugzilla. --- Please do not reply to this mail. --- *** COCOON PATCH QUEUE UPDATE patches in queue: 26 *** --- 17063:[PATCH] XSP Request docs, demo out of sync with logicsheet --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17063 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 9728:[PATCH] CocoonServlet getClassPath() enhancements Tomcat4 --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9728 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 14144:[Patch] add CompressionFilter declaration to web.xml --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14144 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 14845:[PATCH] Patch to generate a key with new resources in XMLDBT --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14845 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 15100:[patch]/[donation] Sample app xml form popup with sourcewrit --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15100 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 15150:[PATCH]: HSSFSerializer Support for Gnumeric MergedRegions --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15150 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 16537:[PATCH] fixed redirect under JRun 3.1 --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16537 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 16718:[PATCH] Using only one connection in SQLTransformer --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16718 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 17771:[PATCH] new logging category never set when using log logics --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17771 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 19138:[Contrib]/[Patch] Made SQLTransformer paginatable. --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19138 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 19638:[PATCH] Same cell definitions blows document (problem with --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19638 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 19641:[PATCH] HSSFSerializer Support for FreezePane --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19641 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 20185:[PATCH] TidySerializer --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20185 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 20271:[PATCH] General background task manager leveraging Avalon --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20271 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 20296:[PATCH] Modularized DirectoryGenerator's --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20296 REVIEWER:[EMAIL PROTECTED]
