RE: New release 2.0.1 woes. Continue.
From: Alexander Smirnoff [mailto:[EMAIL PROTECTED]] OK. I've got it. Thanks. Welcome. I understand the motivation to exlude autocomplete is to speed up the pipeline process. So XSP developer must be responsible of consistent closing of his elements if he or she wants to return somewhere from the middle of XSP logic. Exactly. General note: it seems 2.0.1 compared with 2rc1 is significally slower for more or less complicated XSP. Can you pinpoint the reason of slowdown? I'm not sure that there are significant changes in the XSP machinery between these two versions. Vadim Alex. - Original Message - From: Vadim Gritsenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 13, 2002 1:04 PM Subject: RE: New release 2.0.1 woes. Continue. From: Alexander Smirnoff [mailto:[EMAIL PROTECTED]] Sorry for misleading about the global method, - it works fine. The problem actually is different: If I put return between open and close tags it results in empty document. Look at example: xsp:page language=java xmlns:xsp=http://apache.org/xsp; Sample xsp:logic if(true) return; /xsp:logic /Sample /xsp:page Quite important feature I would say. Return is prohibited in the main method of the XSP. Use it in own methods if you want, but with care. And even if you use it in the main XSP method (despite the fact that it is not recommended), XSP engine can cover your mistakes if you set autocomplete-documents to true. Of course this feature isn't for free, performance of you system will degrade. PS See ServerPagesGenerator javadoc or source for details. Vadim Alex. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New release 2.0.1 woes
Thanks, Vadim, for help it seems start to work. Just one intersting problem.
It looks like I missed many new features lately. One of those: I found out that on each
request context is changing to the directory where sitemap.xmap located. I do not use
multiple sitemap application and I would like to freeze context to some specific
lication
for each request.
Is there any way to do it?
Thanks,
Alex.
- Original Message -
From: Vadim Gritsenko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 05, 2002 3:24 PM
Subject: RE: New release 2.0.1 woes
From: Alexander Smirnoff [mailto:[EMAIL PROTECTED]]
Hi,
I was trying to integrate new cocoon 2.0.1 version with my old sitemap
and
apparently It was not able to compile sitemap.xmap file
because of the next errors (2.0rc1 works without errors):
javax.xml.transform.TransformerException: Sitemap pipeline with
map:generate|aggregate|transform must have map:serialize.
as I understand sitemap is not able to compile because I have used
something
like this:
map:match pattern=site/asset_mgmnt
map:generate src=xsp/asset_mgmnt.xsp
type=serverpages/
map:redirect-to resource=look-and-feel
target=asset_mgmnt/
/map:match
This construct has been deprecated in favor of map:call. Once you
replace it with map:call everything should be ok. From the sample
sitemap:
map:call resource=dynamic-page
map:parameter name=target
value={../target}/state{../../../0}{../../0}/
/map:call
Vadim
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.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/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
New release 2.0.1 woes
Hi,
I was trying to integrate new cocoon 2.0.1 version with my old sitemap and apparently
It was not able to compile sitemap.xmap file
because of the next errors (2.0rc1 works without errors):
javax.xml.transform.TransformerException: Sitemap pipeline with
map:generate|aggregate|transform must have map:serialize.
as I understand sitemap is not able to compile because I have used something like this:
map:match pattern=site/asset_mgmnt
map:generate src=xsp/asset_mgmnt.xsp type=serverpages/
map:redirect-to resource=look-and-feel target=asset_mgmnt/
/map:match
and this redirection is properly ended with:
map:resource name=look-and-feel
map:transform src=stylesheets/xsl/message_filter.xsl/
map:act type=gwvas-look-and-feel
map:parameter name=target value={target}/
map:transform src={path}/xsl/{../target}.xsl
map:parameter name=basepath value={basepath}/
/map:transform
map:serialize/
/map:act
map:serialize type=xml/
/map:resource
if I put map:serialize at the end of the first pipeline - I'll get next:
javax.xml.transform.TransformerException:
Sitemap pipeline with map:serialize|read|mount|redirect-to|call can not have any
components after them.
So what is the the solution?
Thanks,
Alex.
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: New release 2.0.1 woes
From: Alexander Smirnoff [mailto:[EMAIL PROTECTED]]
Hi,
I was trying to integrate new cocoon 2.0.1 version with my old sitemap
and
apparently It was not able to compile sitemap.xmap file
because of the next errors (2.0rc1 works without errors):
javax.xml.transform.TransformerException: Sitemap pipeline with
map:generate|aggregate|transform must have map:serialize.
as I understand sitemap is not able to compile because I have used
something
like this:
map:match pattern=site/asset_mgmnt
map:generate src=xsp/asset_mgmnt.xsp
type=serverpages/
map:redirect-to resource=look-and-feel
target=asset_mgmnt/
/map:match
This construct has been deprecated in favor of map:call. Once you
replace it with map:call everything should be ok. From the sample
sitemap:
map:call resource=dynamic-page
map:parameter name=target
value={../target}/state{../../../0}{../../0}/
/map:call
Vadim
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
