On 19/06/2013 22:06, gelo1234 wrote:
I wonder if C2.2 flowscript request object can be followed here in C3:
http://cocoon.apache.org/2.2/blocks/flowscript/1.0/1383_1_1.html
Flowscript is not available in C3.
and we can use something like: {jexl:cocoon.request.serverName} or
On 19/06/2013 20:46, gelo1234 wrote:
Hi all,
I wonder if C3 still supports:
As you have already done, take [1] as general reference of what it is
possible in C3 sitemaps.
1. matchers in sitemap.xmap ?
e.g.
map:matchers default=wildcard
map:matcher logger=sitemap.matcher.wildcard
On 20/06/2013 09:07, Francesco Chicchiriccò wrote:
4. actions in sitemap.xmap ?
e.g.
map:actions
map:action logger=sitemap.action.request
name=request src=org.apache.cocoon.acting.RequestParamAction/
No.
It looks I might be wrong [1]: Thorsten, could you provide
On 19/06/2013 21:18, gelo1234 wrote:
Sorry for the mistyping: s/cutom/custom.
One more question: I saw map:select ... in examples sitemap.xmap
under map:match ...
Is it possible to put map:select ... straight under map:pipeline ?
No; if you like XSD, you can take a look at [1] to know
On 06/20/2013 09:15 AM, Francesco Chicchiriccò wrote:
On 20/06/2013 09:07, Francesco Chicchiriccò wrote:
4. actions in sitemap.xmap ?
e.g.
map:actions
map:action logger=sitemap.action.request
name=request src=org.apache.cocoon.acting.RequestParamAction/
No.
It
Thanks for clarifying this.
Greetings,
Greg
2013/6/20 Thorsten Scherler scher...@gmail.com
On 06/20/2013 09:15 AM, Francesco Chicchiriccò wrote:
On 20/06/2013 09:07, Francesco Chicchiriccò wrote:
4. actions in sitemap.xmap ?
e.g.
map:actions
map:action
I've got Cocoon site that hosts multiple www domains, all based on the
same sitemap.xmap with map:mount uri-prefix= src=domain_X
check-reload=yes/
so the configuration is as follows:
map:pipeline
map:select type=cutomDomainSelector
map:when
On 06/20/2013 03:02 PM, gelo1234 wrote:
I've got Cocoon site that hosts multiple www domains, all
based on the same sitemap.xmap with map:mount uri-prefix=
src=domain_X check-reload=yes/
so the configuration is as follows:
map:pipeline
Any idea how to get HTTP Header named Host ? or any other HTTP Header value
? [1]
tried cocoon.request.header['Host'], cocoon.request.header.host without
effect
I managed to get only requestURL:
map:parameter name=host value={jexl:cocoon.request.requestURL}/
Greetings,
Greg
[1]
Can you provide me with some simple example of that new language
interpreter (module) ? :)
Greetings,
Greg
2013/6/20 Thorsten Scherler scher...@gmail.com
On 06/20/2013 03:02 PM, gelo1234 wrote:
I've got Cocoon site that hosts multiple www domains, all based on the
same sitemap.xmap
On 20/06/2013 15:37, gelo1234 wrote:
Any idea how to get HTTP Header named Host ?
Doesn't jexl:cocoon.request.serverName work?
or any other HTTP Header value ? [1]
tried cocoon.request.header['Host'], cocoon.request.header.host
without effect
I managed to get only requestURL:
You meant Cocoon Spring Configurator Settings ?
Is it usable in spring config files only beans.../beans or within
sitemap.xmap also ?
Can you show the example usage of that settings in sitemap.xmap ?
Where do I define the namespace prefix for that Interpreter ?
Greetings,
Greg
2013/6/20
It looks like XSLT also got cut in functionality in C3. I tried to rerun
old XSL stylesheets with new C3 and gave up.
The error says nothing meaningful:
exception-report class=org.apache.cocoon.pipeline.SetupException
timestamp=Thu, 20 Jun 2013 19:58:23 +0200messageImpossible to read
XSLT from
Hi Greg,
El 20/06/2013 20:00, gelo1234 gelo1...@gmail.com escribió:
It looks like XSLT also got cut in functionality in C3. I tried to rerun
old XSL stylesheets with new C3 and gave up.
The error says nothing meaningful:
exception-report class=org.apache.cocoon.pipeline.SetupException
Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
doesn't help. I tried to clean work directory, and still
NullPointerException.
Any idea what might be wrong ?
And how to switch off imported xslt caching ?
INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
cze 20, 2013
OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
STRANGE!!
And also found that more detailed error info about not being able to
compile XSLT stylesheet was in Tomcat log.
It seems that with C3 xsl:variables../ cannot be inherited. The error
said about the same
2013/6/20 gelo1234 gelo1...@gmail.com
OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
STRANGE!!
Yeah, computer's stuff. :)
And also found that more detailed error info about not being able to
compile XSLT stylesheet was in Tomcat log.
It seems that with C3
Right, it was NOT Xalan, I used Saxon in my old config. Where could we
change Xalan to Saxon in C3 ?
Now I've got another strange XSL error:
XML document structures must start and end within the same entity.
What could that mean??? :)
That Xalan is making me scratching my head against the wall
Yes, it must be that problem with current Xalan.
Strange thing is that some XSLT variables are predefined like: requestURI
(?!).
So I cannot use:
xsl:param name=requestURI/ in stylesheet file.xsl even though Ive got:
map:transformer src=file.xsl
map:parameter name=requestURI value=/
19 matches
Mail list logo
