Re: [C2.1-CVS] Problem using 2 pipelines
Hi Antonio!
I really tried to answer to your question about the auth-framework, but
couldn't connect to my mailserver at all! :( Now it works again... But it
seems that you're going through the same steps than I did a while ago.
(With my own help)
At this moment, the option of using 2 pipelines the way you are
doing, with the cocoon: pseudo-protocol doesn't work. This is due to
a major bug
in the cocoon component handling. It has been reported, but no actions
have been taken yet. BUT: There IS a way around this!
I have my authentication resource generated with XSP and ESQL (Username
and pwd are
checked against db, and user data is being returned in the
authentication section
of that generated resource). In addition, I added another line inside the
authentication section, which places the users ID in a session
attribute. Now it can be used in XSP later on.
authentication
IDesql:get-int column=id//ID
xsp-session:set-attributeesql:get-int column=id//xsp-session:set-attribute
/authentication
Hope this helps.
-Tuomo
On Tue, 24 Sep 2002, Antonio Gallardo Rivera wrote:
The first pipeline get and XML - XSLT - XML
map:match pattern=*-*.xml
map:act type=auth-protect
map:parameter name=handler value=agshandler/
map:match pattern=*-*.xml
map:generate src=docs/{1}-{2}.xsp/
map:transform type=session/
map:serialize type=xml/
/map:match
/map:act
/map:match
The second read from the first pipeline making an XSP tranformation:
map:match pattern=*-*.html
map:generate src=cocoon://{1}-{2}.xml
type=serverpages encoding=ISO-8859-1/
map:transform src=stylesheets/agssa.xsl/
map:serialize/
/map:match
I call only this second pipeline, but It returns:
Exception during source resolving.
org.apache.cocoon.ProcessingException: Exception during source resolving.:
org.apache.excalibur.source.SourceException: Exception during processing of
cocoon://usr-cambiar.xml: org.apache.cocoon.ProcessingException: Failed to
execute pipeline.: java.lang.NullPointerException
If I call directly the fisrt pipeline it returns me a valid XML file. What I
am doing wrong?
Thanks in advance,
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: [C2.1-CVS] Problem using 2 pipelines
Many thanks!
Its a nice workaround. But what about to built the final logicsheet? many
people will use it. I am trying to do that. I am sure you will welcome it.
BTW, why is the XSL transform support first than the XSP? I feel like I am
doing this in the wrong way, like I need to prefer XSL tranform over XSP. I
saw that many people in thi maillist prefer make XSLT tranforms and few
people use XSP. Why?
Antonio Gallardo
El Miércoles, 25 de Septiembre de 2002 00:58, Tuomo Henrikki Lesonen escribió:
Hi Antonio!
I really tried to answer to your question about the auth-framework, but
couldn't connect to my mailserver at all! :( Now it works again... But it
seems that you're going through the same steps than I did a while ago.
(With my own help)
At this moment, the option of using 2 pipelines the way you are
doing, with the cocoon: pseudo-protocol doesn't work. This is due to
a major bug
in the cocoon component handling. It has been reported, but no actions
have been taken yet. BUT: There IS a way around this!
I have my authentication resource generated with XSP and ESQL (Username
and pwd are
checked against db, and user data is being returned in the
authentication section
of that generated resource). In addition, I added another line inside the
authentication section, which places the users ID in a session
attribute. Now it can be used in XSP later on.
authentication
IDesql:get-int column=id//ID
xsp-session:set-attributeesql:get-int
column=id//xsp-session:set-attribute /authentication
Hope this helps.
-Tuomo
On Tue, 24 Sep 2002, Antonio Gallardo Rivera wrote:
The first pipeline get and XML - XSLT - XML
map:match pattern=*-*.xml
map:act type=auth-protect
map:parameter name=handler value=agshandler/
map:match pattern=*-*.xml
map:generate src=docs/{1}-{2}.xsp/
map:transform type=session/
map:serialize type=xml/
/map:match
/map:act
/map:match
The second read from the first pipeline making an XSP tranformation:
map:match pattern=*-*.html
map:generate src=cocoon://{1}-{2}.xml
type=serverpages encoding=ISO-8859-1/
map:transform src=stylesheets/agssa.xsl/
map:serialize/
/map:match
I call only this second pipeline, but It returns:
Exception during source resolving.
org.apache.cocoon.ProcessingException: Exception during source
resolving.: org.apache.excalibur.source.SourceException: Exception during
processing of cocoon://usr-cambiar.xml:
org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
java.lang.NullPointerException
If I call directly the fisrt pipeline it returns me a valid XML file.
What I am doing wrong?
Thanks in advance,
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: [C2.1-CVS] Problem using 2 pipelines
On Wed, 25 Sep 2002, Antonio Gallardo Rivera wrote:
Many thanks!
Its a nice workaround. But what about to built the final logicsheet? many
people will use it. I am trying to do that. I am sure you will welcome it.
BTW, why is the XSL transform support first than the XSP? I feel like I am
doing this in the wrong way, like I need to prefer XSL tranform over XSP. I
saw that many people in thi maillist prefer make XSLT tranforms and few
people use XSP. Why?
Antonio Gallardo
If you're talking about the logicsheet, you have to do the XSLT first to
extend the XSP page with more Java. Then it's pushed through the
ServerPagesGenerator and processed. Logicsheet is easier to maintain than
writing the same XSP every time on every page it's needed.
-Tuomo
El Miércoles, 25 de Septiembre de 2002 00:58, Tuomo Henrikki Lesonen escribió:
Hi Antonio!
I really tried to answer to your question about the auth-framework, but
couldn't connect to my mailserver at all! :( Now it works again... But it
seems that you're going through the same steps than I did a while ago.
(With my own help)
At this moment, the option of using 2 pipelines the way you are
doing, with the cocoon: pseudo-protocol doesn't work. This is due to
a major bug
in the cocoon component handling. It has been reported, but no actions
have been taken yet. BUT: There IS a way around this!
I have my authentication resource generated with XSP and ESQL (Username
and pwd are
checked against db, and user data is being returned in the
authentication section
of that generated resource). In addition, I added another line inside the
authentication section, which places the users ID in a session
attribute. Now it can be used in XSP later on.
authentication
IDesql:get-int column=id//ID
xsp-session:set-attributeesql:get-int
column=id//xsp-session:set-attribute /authentication
Hope this helps.
-Tuomo
On Tue, 24 Sep 2002, Antonio Gallardo Rivera wrote:
The first pipeline get and XML - XSLT - XML
map:match pattern=*-*.xml
map:act type=auth-protect
map:parameter name=handler value=agshandler/
map:match pattern=*-*.xml
map:generate src=docs/{1}-{2}.xsp/
map:transform type=session/
map:serialize type=xml/
/map:match
/map:act
/map:match
The second read from the first pipeline making an XSP tranformation:
map:match pattern=*-*.html
map:generate src=cocoon://{1}-{2}.xml
type=serverpages encoding=ISO-8859-1/
map:transform src=stylesheets/agssa.xsl/
map:serialize/
/map:match
I call only this second pipeline, but It returns:
Exception during source resolving.
org.apache.cocoon.ProcessingException: Exception during source
resolving.: org.apache.excalibur.source.SourceException: Exception during
processing of cocoon://usr-cambiar.xml:
org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
java.lang.NullPointerException
If I call directly the fisrt pipeline it returns me a valid XML file.
What I am doing wrong?
Thanks in advance,
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: [C2.1-CVS] Problem using 2 pipelines
Hi Antonio!
I really tried to answer to your question about the auth-framework, but
couldn't connect to my mailserver at all! :( Now it works again... But it
seems that you're going through the same steps than I did a while ago.
(With my own help)
At this moment, the option of using 2 pipelines the way you are
doing, with the cocoon: pseudo-protocol doesn't work. This is due to
a major bug
in the cocoon component handling. It has been reported, but no actions
have been taken yet. BUT: There IS a way around this!
I have my authentication resource generated with XSP and ESQL (Username
and pwd are
checked against db, and user data is being returned in the
authentication section
of that generated resource). In addition, I added another line inside the
authentication section, which places the users ID in a session
attribute. Now it can be used in XSP later on.
authentication
IDesql:get-int column=id//ID
xsp-session:set-attributeesql:get-int column=id//xsp-session:set-attribute
/authentication
Hope this helps.
-Tuomo
On Tue, 24 Sep 2002, Antonio Gallardo Rivera wrote:
The first pipeline get and XML - XSLT - XML
map:match pattern=*-*.xml
map:act type=auth-protect
map:parameter name=handler value=agshandler/
map:match pattern=*-*.xml
map:generate src=docs/{1}-{2}.xsp/
map:transform type=session/
map:serialize type=xml/
/map:match
/map:act
/map:match
The second read from the first pipeline making an XSP tranformation:
map:match pattern=*-*.html
map:generate src=cocoon://{1}-{2}.xml
type=serverpages encoding=ISO-8859-1/
map:transform src=stylesheets/agssa.xsl/
map:serialize/
/map:match
I call only this second pipeline, but It returns:
Exception during source resolving.
org.apache.cocoon.ProcessingException: Exception during source resolving.:
org.apache.excalibur.source.SourceException: Exception during processing of
cocoon://usr-cambiar.xml: org.apache.cocoon.ProcessingException: Failed to
execute pipeline.: java.lang.NullPointerException
If I call directly the fisrt pipeline it returns me a valid XML file. What I
am doing wrong?
Thanks in advance,
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: [C2.1-CVS] Problem using 2 pipelines
I saw that many people in thi maillist prefer make XSLT tranforms and few people use XSP. Why? A couple of reasons why I avoid using XSP: 1) It's more or less proprietary (though that is sort of changing). XSLT can be run with many different application servers. 2) XSLT is functional programming and thus lends itself well to rule based processing. XSP is (mostly) procedural programming and in some ways isn't as well suited for the job of sorting and merging tree nodes. Putting point two differently: XSLT is designed specifically for manipulating XML. Java is a general programming language not at all specialized for handling XML, XSP only partly bridges the gap. My personal approach is to try and write generic XSLT for general tasks: eg. filtering the contents of a XML tree based on the contents of a second tree; merging the attributes of two XML trees with similar node names. I then use these as building blocks to create more specific tasks: filtering an XML tree based on what a user is authorized to see; adding presentation attributes to a nodeset based on the final use of the XML. In this way, I can write XSLT that is driven by XML rules that just about any one can author (and maintain). If I was writing XSP and the business rules changed making similar changes would be (I believe) a much harder process. In our case we have (literally) 1000's of business rules to implement, any of which can change on a weekly basis (such is the nature of clinical trials). So having an easy way to dynamically build up applications based on business rules is important to us. If your application is more static and processing speed is more of an issue then a different architecture may make more sense for you. Somewhat off topic, but a general rule at how to pick a particular way of implementing systems: With any large application it's always a good ideas to first build up a conceptual systems architecture based on business requirements. Then build a logical architecture -- based on both the conceptual architecture, the current state of your business and application specific requirements -- before you pick a physical architecture. Only once you have a physical architecture should you start to match up a physical implementation (detail design) with the physical architecture. I know this sounds like a lot of analysis, but its been shown that if you can hit the target of 1/3 analysis, 1/3 development, 1/3 testing, your project life cycle will be much shorter than if you have other proportions of analysis to development and testing... - 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: [C2.1-CVS] Problem using 2 pipelines
Thanks,
El Miércoles, 25 de Septiembre de 2002 01:32, Tuomo Lesonen escribió:
On Wed, 25 Sep 2002, Antonio Gallardo Rivera wrote:
Many thanks!
Its a nice workaround. But what about to built the final logicsheet? many
people will use it. I am trying to do that. I am sure you will welcome
it.
BTW, why is the XSL transform support first than the XSP? I feel like I
am doing this in the wrong way, like I need to prefer XSL tranform over
XSP. I saw that many people in thi maillist prefer make XSLT tranforms
and few people use XSP. Why?
Antonio Gallardo
If you're talking about the logicsheet, you have to do the XSLT first to
extend the XSP page with more Java. Then it's pushed through the
ServerPagesGenerator and processed. Logicsheet is easier to maintain than
writing the same XSP every time on every page it's needed.
-Tuomo
El Miércoles, 25 de Septiembre de 2002 00:58, Tuomo Henrikki Lesonen
escribió:
Hi Antonio!
I really tried to answer to your question about the auth-framework, but
couldn't connect to my mailserver at all! :( Now it works again... But
it seems that you're going through the same steps than I did a while
ago. (With my own help)
At this moment, the option of using 2 pipelines the way you are
doing, with the cocoon: pseudo-protocol doesn't work. This is due to
a major bug
in the cocoon component handling. It has been reported, but no actions
have been taken yet. BUT: There IS a way around this!
I have my authentication resource generated with XSP and ESQL (Username
and pwd are
checked against db, and user data is being returned in the
authentication section
of that generated resource). In addition, I added another line inside
the authentication section, which places the users ID in a session
attribute. Now it can be used in XSP later on.
authentication
IDesql:get-int column=id//ID
xsp-session:set-attributeesql:get-int
column=id//xsp-session:set-attribute /authentication
Hope this helps.
-Tuomo
On Tue, 24 Sep 2002, Antonio Gallardo Rivera wrote:
The first pipeline get and XML - XSLT - XML
map:match pattern=*-*.xml
map:act type=auth-protect
map:parameter name=handler value=agshandler/
map:match pattern=*-*.xml
map:generate src=docs/{1}-{2}.xsp/
map:transform type=session/
map:serialize type=xml/
/map:match
/map:act
/map:match
The second read from the first pipeline making an XSP tranformation:
map:match pattern=*-*.html
map:generate src=cocoon://{1}-{2}.xml
type=serverpages encoding=ISO-8859-1/
map:transform src=stylesheets/agssa.xsl/
map:serialize/
/map:match
I call only this second pipeline, but It returns:
Exception during source resolving.
org.apache.cocoon.ProcessingException: Exception during source
resolving.: org.apache.excalibur.source.SourceException: Exception
during processing of cocoon://usr-cambiar.xml:
org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
java.lang.NullPointerException
If I call directly the fisrt pipeline it returns me a valid XML file.
What I am doing wrong?
Thanks in advance,
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]
-
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:
