[jira] Commented: (COCOON-1909) Cache validity of XSLT stylesheets does not reflect included or imported stylesheets.
[
http://issues.apache.org/jira/browse/COCOON-1909?page=comments#action_12433063
]
Ard Schrijvers commented on COCOON-1909:
The problem is a little more sophisticated then depicted above:
First of all, the TraxTransformer allows you to set a parameter,
check-includes to true, to add the validity of imported/included stylesheets.
From the TraxTransformer:
// Get a Transformer Handler if we check for includes
// If we don't check the handler is get during setConsumer()
try {
if ( _checkIncludes ) {
XSLTProcessor.TransformerHandlerAndValidity handlerAndValidity =
this.xsltProcessor.getTransformerHandlerAndValidity(this.inputSource, null);
this.transformerHandler =
handlerAndValidity.getTransfomerHandler();
this.transformerValidity =
handlerAndValidity.getTransfomerValidity();
} else {
this.transformerValidity = this.inputSource.getValidity();
}
} catch (XSLTProcessorException se) {
throw new ProcessingException(Unable to get transformer handler
for + this.inputSource.getURI(), se);
}
So, the XSLTProcessor (org.apache.excalibur.xml.xslt.XSLTProcessor) returns the
validity of the imported/included stylesheets. Changing one of the imported
stylesheets now, will affect the (cached) pipeline, since one of the validities
in the AggregatedValidity is not valid anymore.
The only problem is, that this check for includes is not done recursively, and
only one level deep. Then again, this does not seem to be wrong in cocoon, but
merely in org.apache.excalibur.xml.xslt.XSLTProcessorImpl.
public TransformerHandlerAndValidity getTransformerHandlerAndValidity( Source
stylesheet, XMLFilter filter )
throws XSLTProcessorException
must be recursive for each included stylesheet to get this working. Not sure if
this is a little an overkill. Since we are used to work with many included xsl,
including other ones, etc, to have xsls generic, I implemented a monitor for
development mode, that simple clears my DefaultTransientStore cache, to get rid
of having to save parent xsls
Ard
Cache validity of XSLT stylesheets does not reflect included or imported
stylesheets.
-
Key: COCOON-1909
URL: http://issues.apache.org/jira/browse/COCOON-1909
Project: Cocoon
Issue Type: Bug
Components: - Components: Sitemap
Affects Versions: 2.1.9
Reporter: Conal Tuohy
XSLT stylesheets which either import or include other stylesheets are cached
too aggressively: if you change an imported or included stylesheet the change
does not take effect until you update the main stylesheet.
This bug is supposed to have been fixed years ago, but it still doesn't work
for us.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: using Cocoon in a existing project
Hola, first of all: welcome! I think that the easier thing is to develop a separate webapplication that get the data from the same db and produce the xmlformat that you want. For the integration if you don't have some security policy you can simply link the cocoon match from the struts application. Bye. Hi, i am new to Cocoon. So, i started in a company and they already have a webapplication where usres can get information from a database. They want me to export data from the databse in an xml-file and also users should get the possibility to download data from the the db in an xml-file. So, my first question, do you also think, that cocoon will be usefull for this task. Or ist it to big, means powerfull? And, if yes, how do i integrate cocoon in the project? we are developing with eclipse and yousing struts. Thanks for your help, Werz -- View this message in context: http://www.nabble.com/using-Cocoon-in-a-existing-project-tf2227359.html#a6172455 Sent from the Cocoon - Dev forum at Nabble.com. -- Daniele Madama (http://www.danysoft.org) Sourcesense - making sense of Open Source: (http://www.sourcesense.com)
Cocoon, Spring and OSGi
It seem like the Spring-OSGi integration work is taking of quite seriously http://www.osgi.org/blog/2006/08/osgi-and-spring_29.html. Key players from both OSGi, Spring and some large companies are working on it. For Cocoon I think the way to go forward is that we make the part of the blocks architecture that is about sitemap polymorphism, blocks protocol etc, Spring managed (like I have been talking about for some while and even started to work on, unfortunately I haven't been able to spend much time on Cocoon for the last months). For the Spring-OSGi bridge, that make inter block (bundle) component communication possible, we should move towards using the things the Spring community develops. I have subscribed to their mailing list and will see if their current direction solves our needs and otherwise take part in the discussions. /Daniel
[jira] Created: (COCOON-1911) [PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes
[PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes - Key: COCOON-1911 URL: http://issues.apache.org/jira/browse/COCOON-1911 Project: Cocoon Issue Type: Improvement Components: Blocks: JCR Affects Versions: 2.2-dev (Current SVN) Reporter: Lars Trieloff Attachments: cocoon-jcr-test-dependency.patch The Cocoon JRC block impl uses in its test cases the ContainerTestCase which is part of the test classes of cocoon-core. The attached patch adds a depdendency to the test-jar of cocoon-core for the test scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1911) [PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes
[ http://issues.apache.org/jira/browse/COCOON-1911?page=all ] Lars Trieloff updated COCOON-1911: -- Attachment: cocoon-jcr-test-dependency.patch To apply in cocoon/trunk [PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes - Key: COCOON-1911 URL: http://issues.apache.org/jira/browse/COCOON-1911 Project: Cocoon Issue Type: Improvement Components: Blocks: JCR Affects Versions: 2.2-dev (Current SVN) Reporter: Lars Trieloff Attachments: cocoon-jcr-test-dependency.patch The Cocoon JRC block impl uses in its test cases the ContainerTestCase which is part of the test classes of cocoon-core. The attached patch adds a depdendency to the test-jar of cocoon-core for the test scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COCOON-1911) [PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes
[ http://issues.apache.org/jira/browse/COCOON-1911?page=all ] Leszek Gawron closed COCOON-1911. - Resolution: Fixed Patch applied. Thank you [PATCH] cocoon-jcr-impl does not declare dependency to cocoon-core's test classes - Key: COCOON-1911 URL: http://issues.apache.org/jira/browse/COCOON-1911 Project: Cocoon Issue Type: Improvement Components: Blocks: JCR Affects Versions: 2.2-dev (Current SVN) Reporter: Lars Trieloff Attachments: cocoon-jcr-test-dependency.patch The Cocoon JRC block impl uses in its test cases the ContainerTestCase which is part of the test classes of cocoon-core. The attached patch adds a depdendency to the test-jar of cocoon-core for the test scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Creating a mavenized cocoon application
As I suck in writing documentation I decided to summarize first steps to create a cocoon application in a blog entry [1] If anybody finds it useful I will continue the tutorial. The best thing would be if somebody more english fluent ports it to cocoon docs. [1] http://ouzo.squash.eu.org/2006/09/creating_a_mavenized_cocoon_ap.html -- Leszek Gawron http://ouzo.squash.eu.org
