xsl:import and xsl:include are your friends when you start getting
concerned about performance issues and want to do everything in one
pass! Of course though, if you generate one form of content, and then
transform it to another form of content (say, xml-docbook-html) you
are SOL. :(
One other thing...
I found that in order to get my JSPs working, I had to put a / at the
beginning of the src attribute.
For instance,
map:generate type=jsp src=jsp/{1}.jsp/
would have to become:
map:generate type=jsp src=/jsp/{1}.jsp/
in order to work for me. I only ever experienced this
shenoy, nitin wrote:
Q1) How do I pass the result of XSL transformations to an Action?
map:match pattern=ProcessOrder
map:generate type=file src=input/message.xml/
map:transform src=input/identity.xsl/
map:act type=load-order /
map:serialize/
/map:match
In the
Let's use this as an example of a possible action:
map:act name=session-validate
.. do something ..
/map:act
Now, what do you do if you want to action fails, yet you still want to
modify the pipeline based on that failed action? Well, of course, you
could always write the action as a
That's more or less how I view it. I tend to explain XSPs like this:
XSPs are an EASIER way of creating functionality like Java Tag
Libraries. Rather than exposing functionality through a set of
difficult to use and very limited Java APIs, you program your logic into
a more natural and more
Hey guys,
Is there a reason why changes to XSP files aren't picked up when I have the
application set to reloadable and pass the ?cocoon-reload=1 parameter to a page
request? Changes to JSP, XML, and sitemap files are caught, but if I change an XSP
file I get this error:
WARN(2001-12-02)
Comment out every entry in your sitemap.xmap file that contains 'svg'
minus the quotes. sitemap.xmap is located in the webapps/cocoon
directory. You might have to uncompress the war archive to modify it.
Restart tomcat, and everything should work EXCEPT for the svg stuff.
If you want to
BINGO!
I've been struggling with this for awhile now myself. I was using
Tomcat 3.3dev for a bit, and all the log files are completely different
in that version, so I wasn't sure where to look. Anyway, I downgraded
to 3.2.2 yesterday and spent some real time looking into the problem.
If
