gmane.text.xml.cocoon.devel

[continuum] BUILD ERROR: Cocoon - Apache Cocoon [build root] -

2008-10-06T11:02:35

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=118393&projectId=51 Build statistics: State: Error Previous State: Ok Started at: Mon 6 Oct 2008 04:01:08 -0700 Finished at: Mon 6 Oct 2008 04:02:27 -0700 Total time: 1m 18s Build Trigger: Schedule Build Number: 0 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Builder version : Maven version: 2.0.9 Java version: 1.5.0_12 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" **************************************************************************** SCM Changes: **************************************************************************** No files changed **************************************************************************** Dependencies Changes: **************************************************************************** No dependencies changed **************************************************************************** Build Definition: **************************************************************************** POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Maven 2.0.9, Java 5, Large Memory Description: **************************************************************************** Test Summary: **************************************************************************** Tests: 0 Failures: 0 Total time: 0.0 **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/asf/cocoon/trunk' svn: PROPFIND of '/repos/asf/cocoon/trunk': Could not resolve hostname `svn.apache.org': Host not found (http://svn.apache.org) -------------------------------------------------------------------------------

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

Reinhard Poetz (JIRA — 2008-10-06T08:23:44

[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-3: --------------------------------- Fix Version/s: 3.0.0-alpha-2 Affects Version/s: 3.0.0-alpha-2

[jira] Closed: (COCOON3-2) Add an XSchema Validator as PipeLineComponent

Reinhard Poetz (JIRA — 2008-10-06T08:03:44

[ https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-2. -------------------------------- Resolution: Fixed I've applied the patch. Thanks Simone. This patch has reminded me that we have to do something about error handling. In the case of invalid XML, a RuntimeException is thrown ATM which isn't really helpful. OTOH, checked exceptions all over the place might not be helpful either.

[jira] Assigned: (COCOON3-2) Add an XSchema Validator as PipeLineComponent

Reinhard Poetz (JIRA — 2008-10-06T08:01:46

[ https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-2: ------------------------------------ Assignee: Reinhard Poetz (was: Cocoon Developers Team)

[jira] Closed: (COCOON3-1) Exceptions and Serializable classes should contain the serialVersionUID field

Reinhard Poetz (JIRA — 2008-10-06T07:39:44

[ https://issues.apache.org/jira/browse/COCOON3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-1. -------------------------------- Resolution: Fixed Thanks for the patch. I applied it and also went over the other modules and set the serialVersionUID on all serializeable classes.

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

Simone Tripodi (JIRA — 2008-10-06T07:37:44

[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated COCOON3-3: --------------------------------- Attachment: XInclude.patch As mentioned on http://cocoon.apache.org/3.0/roadmap.html, the XInclude support is one of the unscheduled feature for cocoon 3.0.0 The attached patch provides the porting to Cocoon3's pipeline of old XInclude Transformer already present in previous releases; some TestCase are also provided. Just few notes: - As described in http://www.w3.org/TR/xinclude/, I managed the 'accept' and 'accept-language' attributes that weren't previously implemented; - I maintained the deprecated xpointer support; - The dependencies from old Excalibur's org.apache.excalibur.xml.xpath.* have been replaced with Java5 provided javax.xml.xpath.* - they are very similar; - The XPointer grammar has been adapted to be managed by the maven-javacc-plugin (generation + report); - The original DOMStreamer has been simplified; - I only adapted the existing code to the new structure and used Java5 generics, iterators where possible. I really hope this helps! :)

[jira] Assigned: (COCOON3-1) Exceptions and Serializable classes should contain the serialVersionUID field

Reinhard Poetz (JIRA — 2008-10-06T07:37:44

[ https://issues.apache.org/jira/browse/COCOON3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-1: ------------------------------------ Assignee: Reinhard Poetz (was: Cocoon Developers Team)

[jira] Closed: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Reinhard Poetz (JIRA — 2008-10-06T06:49:44

[ https://issues.apache.org/jira/browse/COCOON3-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-4. -------------------------------- Resolution: Fixed Thanks for your patch. After creating a new module 'cocoon-optional' I've added it to it.

[jira] Assigned: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Reinhard Poetz (JIRA — 2008-10-06T06:47:44

[ https://issues.apache.org/jira/browse/COCOON3-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-4: ------------------------------------ Assignee: Reinhard Poetz (was: Cocoon Developers Team)

[jira] Created: (COCOON-2245) Not unique caching key for different blocks

Felix Knecht (JIRA — 2008-10-03T13:52:44

Not unique caching key for different blocks ------------------------------------------- Key: COCOON-2245 URL: https://issues.apache.org/jira/browse/COCOON-2245 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Affects Versions: 2.2, 2.2-dev (Current SVN) Reporter: Felix Knecht ExpiresCachingProcessingPipeline doesn't generates unique default caching key for different blocks. When having 2 blocks running, each containing an image '.../images/foo.png' the key for the cache is 'images/foo.png'. This is wrong as it doesn't respects that this are images of different blocks. The default cache key is generated in core/cocoon-pipeline/cocoon-pipeline-impl/src/main/java/org/apache/cocoon/components/pipeline/impl/ExpiresCachingProcessingPipeline.java:223: key = environment.getURIPrefix()+environment.getURI(); So the generation of the key is correct, but environment.getURIPrefix() is empty. I'm sure this is the part making the difference. I can't find where the URIPrefix is set (supposing it could be in core/cocoon-pipeline/cocoon-pipeline-impl/src/main/java/org/apache/cocoon/environment/http/HttpEnvironment.java) ...

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

Simone Tripodi (JIRA — 2008-10-03T06:24:44

[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636548#action_12636548 ] Simone Tripodi commented on COCOON3-3: -------------------------------------- I started working on it but it's not so easy (for me, at least ;) ). I should be able to provide an initial patch in a week

[jira] Commented: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Simone Tripodi (JIRA — 2008-10-03T06:20:44

[ https://issues.apache.org/jira/browse/COCOON3-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636546#action_12636546 ] Simone Tripodi commented on COCOON3-4: -------------------------------------- Yes of course you're right and I agree with you! If this patch will be accepted as "proof of concept", once the cocoon-pipeline-optional will be created I'll create a new patch for the new package

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

Reinhard Poetz (JIRA — 2008-10-03T06:10:44

[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636543#action_12636543 ] Reinhard Poetz commented on COCOON3-3: -------------------------------------- Usually the job of porting Cocoon 2.x components to Cocoon 3 is straight forward and in this case the best option IMO.

[jira] Commented: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Reinhard Poetz (JIRA — 2008-10-03T06:08:44

[ https://issues.apache.org/jira/browse/COCOON3-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636542#action_12636542 ] Reinhard Poetz commented on COCOON3-4: -------------------------------------- I think we should create a cocoon-pipeline-optional module that contains stuff that requires 3-party dependencies. There we should also set the scope of the dependencies to 'provided'. This prevents Maven from pulling in all libraries automatically.

[continuum] BUILD SUCCESSFUL: Cocoon - Apache Cocoon [build root] -

2008-10-03T01:38:52

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=117892&projectId=51 Build statistics: State: Ok Previous State: Error Started at: Thu 2 Oct 2008 18:24:05 -0700 Finished at: Thu 2 Oct 2008 18:37:39 -0700 Total time: 13m 33s Build Trigger: Schedule Build Number: 351 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Builder version : Maven version: 2.0.9 Java version: 1.5.0_12 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" **************************************************************************** SCM Changes: **************************************************************************** No files changed **************************************************************************** Dependencies Changes: **************************************************************************** No dependencies changed **************************************************************************** Build Definition: **************************************************************************** POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Maven 2.0.9, Java 5, Large Memory Description: **************************************************************************** Test Summary: **************************************************************************** Tests: 362 Failures: 0 Total time: 91.44399

[continuum] BUILD ERROR: Cocoon - Apache Cocoon [build root] -

2008-10-02T23:01:22

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=117756&projectId=51 Build statistics: State: Error Previous State: Ok Started at: Thu 2 Oct 2008 16:00:30 -0700 Finished at: Thu 2 Oct 2008 16:01:14 -0700 Total time: 43s Build Trigger: Schedule Build Number: 0 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Builder version : Maven version: 2.0.9 Java version: 1.5.0_12 OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix" **************************************************************************** SCM Changes: **************************************************************************** No files changed **************************************************************************** Dependencies Changes: **************************************************************************** No dependencies changed **************************************************************************** Build Definition: **************************************************************************** POM filename: pom.xml Goals: clean install Arguments: --batch-mode -P allblocks,it Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Maven 2.0.9, Java 5, Large Memory Description: **************************************************************************** Test Summary: **************************************************************************** Tests: 0 Failures: 0 Total time: 0.0 **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/asf/cocoon/trunk' svn: PROPFIND of '/repos/asf/cocoon/trunk': could not connect to server (http://svn.apache.org) -------------------------------------------------------------------------------

Re: [jira] Commented: (COCOON-2216) IncludeCacheManager can not perfom parallel includes

Grzegorz Kossakowski — 2008-10-02T20:34:17

imran pariyani (JIRA) pisze: Had a brief look and I fear that it's not that easy but I'm not an expert in this field. Yes, please. I have a really shaky internet access these days so any help is greatly appreciated. I hope others more experienced with multi-thread problems can give us some hints how finally tackle this problem.

[jira] Updated: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Simone Tripodi (JIRA — 2008-10-02T16:33:44

[ https://issues.apache.org/jira/browse/COCOON3-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated COCOON3-4: --------------------------------- Attachment: BeanGenerator.patch The provided patch implements a BeanGenerator, using the commons-betwixt library. I know that one of the main scopes of cocoon3 pipeline is limiting the dependencies, but the apache's commons-betwixt already implements a SAX writer that streams xml events to a content handler. Moreover, as reported on http://commons.apache.org/betwixt/guide/output.html (on the bottom), "SAXBeanWriter pushes events to a SAX content handler. This allows Betwixt to efficiently participate as a content generator in SAX-based pipelines such as cocoon"

[jira] Created: (COCOON3-4) Provide an XML generator based on Bean(s)/POJOs

Simone Tripodi (JIRA — 2008-10-02T16:27:52

Provide an XML generator based on Bean(s)/POJOs ----------------------------------------------- Key: COCOON3-4 URL: https://issues.apache.org/jira/browse/COCOON3-4 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 A Bean(s)/POJO(s) generator is a starter component for the pipeline that streams sax events, generated reading/intrsopecting the Object input, to an xml consumer. It could be useful when Objects are retrieved, i.e. from a persistence engine, and they have to be streamed in an XML format to implement a Rest API.

[jira] Commented: (COCOON-2216) IncludeCacheManager can not perfom parallel includes

imran pariyani (JIRA — 2008-10-02T15:29:44

[ https://issues.apache.org/jira/browse/COCOON-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636376#action_12636376 ] imran pariyani commented on COCOON-2216: ---------------------------------------- hi Grzegorz, in the article there was something about "Lack of a Standard Thread-Pooling Library " .. now there is a standard which comes with the JDK .. i don't know if we are using that or not .. but it is possible that it might take care of the ThreadLocal variables .. just a thought. should i forward this discussion to the dev mailing list ?

[jira] Commented: (COCOON-2216) IncludeCacheManager can not perfom parallel includes

Grzegorz Kossakowski (JIRA — 2008-10-02T13:31:45

[ https://issues.apache.org/jira/browse/COCOON-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636361#action_12636361 ] Grzegorz Kossakowski commented on COCOON-2216: ---------------------------------------------- Imran, It's my time to apologize. I didn't read your previous description carefully enough. Now I could reproduce your problem which is just a sign of much bigger problem. IncludeCacheManager uses thread pooling technique which does not play nicely with ThreadLocals, see: http://java.sys-con.com/node/37241 As I said this problem is not limited to the newly introduced Factory for ObjectModel. Servlet Service Fw and Spring itself use ThreadLocals as well. I think this is a right time to move this discussion to dev< at > list so others can comment. I'll be probably in favour of removing thread pooling completely but I don't know performance implications at the moment.