gmane.text.xml.cocoon.devel

[jira] Created: (COCOON-2242) Running registration sample on ocj4 10.1.3.4.0

Sebastian Sadowski (JIRA — 2008-08-29T13:51:44

Running registration sample on ocj4 10.1.3.4.0 ---------------------------------------------- Key: COCOON-2242 URL: https://issues.apache.org/jira/browse/COCOON-2242 Project: Cocoon Issue Type: Bug Components: Blocks: Forms Affects Versions: 2.2 Reporter: Sebastian Sadowski Priority: Blocker Hi I try to run simple registration application from site: http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html on oc4j 10.1.3.4.0 and I get error: 2008-08-29 15:40:46,578 DEBUG RMICallHandler-74 org.springframework.web.context.request.RequestContextListener - Bound request context to thread: com.evermind.server.http.EvermindHttpServletRequest< at >116d7a5 2008-08-29 15:40:46,578 ERROR RMICallHandler-74 cocoon - Problem in multipart filter. Unable to create request. org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.apache.cocoon.servletservice.spring.BlockServletMap' is defined at org.sp

Help... how can I setFeature() on JaxpParser

Mark Lundquist — 2008-08-28T17:22:31

Hi, I very much need to set the feature "http://apache.org/xml/features/nonvalidating/load-external-dtd " (see http://xerces.apache.org/xerces-j/features.html#load-external-dtd) on the Xerces parser wrapped by a JaxpParser instance (returned by manager lookup of SAXParser.role). I don't see a way to do it... it looks like JaxpParser doesn't expose an interface for it. JaxpParser buries the factory instances and the parser instances pretty thoroughly and doesn't provide any handles to set features, even in the component configuration. This is for a project that's stuck on Cocoon 2.1.8, BTW. I guess I can always just create my own parser instance if it comes down to that. Before I bother, does anybody know of a way to avoid the bother? Maybe I'm missing something... cheers, —ml—

[jira] Subscription: COCOON-open-with-patch

2008-08-27T17:41:45

Issue Subscription Filter: COCOON-open-with-patch (108 issues) Subscriber: cocoon Key Summary COCOON-2233 Update archetypes to current trunk artifact versions https://issues.apache.org/jira/browse/COCOON-2233 COCOON-2222 Add SaxParser configuration properties https://issues.apache.org/jira/browse/COCOON-2222 COCOON-2217 HttpServletResponseBufferingWrapper throws NPE when response body is empty https://issues.apache.org/jira/browse/COCOON-2217 COCOON-2216 IncludeCacheManager can not perfom parallel includes https://issues.apache.org/jira/browse/COCOON-2216 COCOON-2212 jx:attribute does not check name is correct before proceeding https://issues.apache.org/jira/browse/COCOON-2212 COCOON-2211 Support for jx:element https://issues.apache.org/jira/browse/COCOON-2211 COCOON-2210 The field 'type' in GenerateNode in corona-sitemap should not be final https://issues.apache.org/jira/browse/COCOON-2210 COCOON-2197 Making the co

java.lang.ClassNotFoundException:org.springframework.scripting.config.LangNamespace Handler

Thorsten Scherler — 2008-08-26T12:48:27

Hi all, I am using for Apache droids and was annoyed by the java.lang.ClassNotFoundException that was thrown in debug mode. After starting a thread in the spring forum I found the root cause http://forum.springframework.org/showthread.php?p=198137&posted=1#post198137 spring-beans-2.0.6.jar does not have the Handler definitions. Does it makes sense to update our dependency to e.g. spring-beans-2.5.5.jar? salu2

Component versioning in JIRA

Jasha Joachimsthal — 2008-08-26T06:54:58

Good morning, I tried to close two issues but couldn't find the right fix version for the mail-block and the pipeline component. Shouldn't there be a 1.1.0 fix version? Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646

Jira karma

Jasha Joachimsthal — 2008-08-25T19:05:07

Hi there, could someone please give me more karma in Jira so I can assign issues to myself en resolve them? Thanks, Jasha

org.apache.cocoon.util.log.CocoonTargetFactory < at >deprecated

Thorsten Scherler — 2008-08-25T10:45:24

Hi all, since forrest is extending the CocoonTargetFactory we now get warnings while building forrest. This is not really nice and we are looking how we overcome this warnings. Seeing "< at >deprecated This class will be removed in 2.2" makes me wonder which class to use instead. Somebody has an idea? TIA. salu2

Please add me to jira admins

Thorsten Scherler — 2008-08-25T10:07:56

Hi all, please add me to the jira group that can link to issues and manage them. TIA salu2

[jira] Created: (COCOON-2241) The commandline is not working since cocoon-1985

Thorsten Scherler (JIRA — 2008-08-25T10:07:44

The commandline is not working since cocoon-1985 ------------------------------------------------ Key: COCOON-2241 URL: https://issues.apache.org/jira/browse/COCOON-2241 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Affects Versions: 2.1.12-dev (Current SVN) Reporter: Thorsten Scherler Fix For: 2.1.12-dev (Current SVN) Updating forrest to use cocoon-2.1.x, I found a problem in the AbstractCachingProcessingPipeline. I am not sure whether someone is using the cocoon cli ATM. Forrest is based around this component. https://issues.apache.org/jira/browse/FOR-955?focusedCommentId=12624340#action_12624340 I found that in org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline line 245 Object lock = env.getObjectModel().get(HttpEnvironment.HTTP_REQUEST_OBJECT); the lock is null which causes the NPE in the end. The problem is that the cli environment does not store the requested o

Problems with latest changes in Servlet-Services-Framework

Gabriel Gruber — 2008-08-24T15:02:51

Hi guys, just wanted to inform you, that latest trunk changes in ServletServiceFramework broke the ability of the form block to submit correctly, if ajax is enabled. I traced the issue down to this class: HttpServletResponseBufferingWrapper there have been some changes lately in connection with buffering and forewarding. It seems that those reworks actually broke the correct functioning of this snippet inside Form.js (which is responsible to give dojo back the information, that form validation worked correctly): line 221 and following... cocoon.sendStatus(200); var httpResponse = objectModel.get(org.apache.cocoon.environment.http.HttpEnvironment.HTTP_RESPONSE_OBJECT); if (httpResponse) { var text =""; if (cocoon.request.getParameter("dojo.transport")== "iframe") { //MSIE accepts only HTML content when using the iframe //dojo transport, so we have to wrap everyth

HOWTO: enable Flowscript debugger

Gabriel Gruber — 2008-08-24T14:35:25

Hello guys, as I just stumbled across it again, I want to give a short description how you can enable flowscript-debugger for your cocoon project. It is crucial that you use the latest version (cocoon-flowscript-impl 1.1.0). As all properties are handled now by spring configurator, you have several options: a) define system property at startup of servlet container. -Dorg.apache.cocoon.flowscript.debugger=enabled b) define it in your properties file. f.i. create a properties file under src/main/resources/META-INF/cocoon/properties/myProps.properties and put this property reference inside org.apache.cocoon.flowscript.debugger=enabled c) use more sophisticated setup. create one properties file for development and a second for production and turn on flowscript debugger only in dev-mode... It is important to use the word "enabled" instead of a pure boolean value... cheers, Gabriel ----- Forwarded by Gabriel Gruber/Workflow on 24.08.2008 16:23 ----- Grzegorz Kossakowski tuffmail.com> 21

Servlet Service Framework without Cocoon tutorial

Kamal — 2008-08-23T23:18:25

Hi I would like to play with the Servlet Service Framework in non-Cocoon environment. Can someone point me to some resources or provide me an example of this use case? Thanks.

[vote] Cocoon 3: Versioning, SVN, Maven, namespaces, issue tracking and CI

Reinhard Pötz — 2008-08-21T21:53:05

After having already discussed the details, let's make a formal decision about versioning, SVN, Maven, namespaces issue tracking and CI for Cocoon 3. Versioning ------------------------------- Cocoon 3 will follow the alpha/beta/rc release scheme (like Mozilla, Maven, Apache Commons, etc.). The first release will be 3.0-alpha-1. This will be a clear marker that is already visible when you add Cocoon as a dependency to your build or download the artifacts manually. Additionally all release artifacts will contain a warning message and an explanation what "alpha" means. SVN ------------------------------- In order to make the life easier for people who use git-svn, I propose to use the standard SVN directory structure: http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk http://svn.apache.org/repos/asf/cocoon/cocoon3/tags Maven ------------------------------- We use functional names for all artifacts: org.apache.cocoon.pipeline:cocoon-pipeline:3.0.0 org.apache.cocoon.sitemap:cocoon-sitemap:3.0.0 org.apa

[2.1] AbstractCachingProcessingPipeline and cocoon CLI

Thorsten Scherler — 2008-08-21T12:18:03

Hi all, still updating forrest to use cocoon-2.1.x and I found a problem in the AbstractCachingProcessingPipeline. I am not sure whether someone is using the cocoon cli ATM. Forrest is based around this component. https://issues.apache.org/jira/browse/FOR-955?focusedCommentId=12624340#action_12624340 I found that in org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline line 245 Object lock = env.getObjectModel().get(HttpEnvironment.HTTP_REQUEST_OBJECT); the lock is null which causes the NPE in the end. I changed it the following way: Object lock = env.getObjectModel().get(HttpEnvironment.HTTP_REQUEST_OBJECT); + if (null==lock){ + lock = env.getObjectModel().get(ObjectModelHelper.REQUEST_OBJECT); + } try { and now it is working as before. Can somebody verify that it is a bug? Should I commit the patch? TIA for any feedback. salu2

Release of cocoon-flowscript-impl

Grzegorz Kossakowski — 2008-08-21T10:54:45

Hi, Just wanted to let you know that I'm planning to prepare 1.0.1 release of cocoon-flowscript-impl that contain one but important bug-fix: it fixes Flowscript debugger that was broken in 1.0.0. I would like ask anyone to not commit to this block, please.

[jira] Created: (COCOON-2240) Building all blocks from parent block doesn't work

Stephan (JIRA — 2008-08-21T10:28:46

Building all blocks from parent block doesn't work -------------------------------------------------- Key: COCOON-2240 URL: https://issues.apache.org/jira/browse/COCOON-2240 Project: Cocoon Issue Type: Bug Components: - Build System: Maven Affects Versions: 2.2 Reporter: Stephan This seems to be similar to https://issues.apache.org/jira/browse/COCOON-2007. I created two cocoon blocks and a webapp like this: webapp block1 block2 Then, I created a parent pom that referes to these modules in order to be able to build all at once. But when I execute "mvn install" within my parent project, I got this error: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-war-plugin :2.0.2:war': Unable to find the mojo 'org.apache.maven.plugins:maven-war-plugin:2.0.2:war' in the plugin 'org.apache.maven.plugins:maven-war-plugin' at org.apache.m

[vote] Release of cocoon-template-impl-1.0.0 and cocoon-forms-impl-1.0.0

Grzegorz Kossakowski — 2008-08-21T10:15:13

Hello Cocoon community, I've prepared artifacts for the release of our two blocks: Cocoon Forms Impl 1.0.0 ~~~~~~~~~~~~~~~~~~~~~~~ This is Avalon-based (contrary to the 1.1.0 release that has been already published and is Spring-based) version of Cocoon Forms. However, this version is already using SSF for serving resources. Cocoon Template Impl 1.0.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~ Similarly to the Forms block, template block is also based on Avalon. There are no other differences compared to 1.1.0 version which was already published as well. - o - The idea of releasing both artifacts is to make migration to Cocoon 2.2 easier for people that have their own extensions to the given blocks. With use of 1.1.0 versions they would be forced to migrate those extensions to Spring immediately which makes migration more difficult. - o - The proposed artifacts can be tested either with Cocoon Core 2.2.0 or trunk. For testing on your own add a 'c

[jira] Subscription: COCOON-open-with-patch

2008-08-20T17:40:50

Issue Subscription Filter: COCOON-open-with-patch (109 issues) Subscriber: cocoon Key Summary COCOON-2233 Update archetypes to current trunk artifact versions https://issues.apache.org/jira/browse/COCOON-2233 COCOON-2228 StripNameSpacesTransformer does not strip namespace prefix of attributes https://issues.apache.org/jira/browse/COCOON-2228 COCOON-2222 Add SaxParser configuration properties https://issues.apache.org/jira/browse/COCOON-2222 COCOON-2217 HttpServletResponseBufferingWrapper throws NPE when response body is empty https://issues.apache.org/jira/browse/COCOON-2217 COCOON-2216 IncludeCacheManager can not perfom parallel includes https://issues.apache.org/jira/browse/COCOON-2216 COCOON-2212 jx:attribute does not check name is correct before proceeding https://issues.apache.org/jira/browse/COCOON-2212 COCOON-2211 Support for jx:element https://issues.apache.org/jira/browse/COCOON-2211 COCOON-2210 The field '

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

2008-08-20T15:23:39

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=109832&projectId=51 Build statistics: State: Ok Previous State: Building Started at: Wed 20 Aug 2008 08:10:54 -0700 Finished at: Wed 20 Aug 2008 08:22:47 -0700 Total time: 11m 53s Build Trigger: Schedule Build Number: 334 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: **************************************************************************** Changed: anathaniel < at > Fri 30 May 2008 13:54:

[2.1] AbstractEnvironment - NPE in release(...)

Thorsten Scherler — 2008-08-20T12:40:07

Hi all, I found a bug that just some time happens and I am not sure why. In AbstractEnvironment the method release throw SOMETIMES a NPE: /** * Releases a resolved resource */ public void release(final org.apache.excalibur.source.Source source) { if (null != source) { this.sourceResolver.release(source); } } I have found that under certain circumstances this.sourceResolver is already null. I do not understand ATM why and when this can happen. Does somebody has an idea? salu2

How to get an org.apache.cocoon.environment.SourceResolver?

Thorsten Scherler — 2008-08-20T11:13:30

Hi all, in forrest we are in the middle of updating our version of cocoon. In the middle of this process I ran into following problem: https://svn.apache.org/repos/asf/forrest/branches/update_cocoon_2.1.12-dev/main/java/org/apache/forrest/locationmap/lm/ActNode.java in the locate method we had till now: this.resolver = (SourceResolver)m_manager.lookup(SourceResolver.ROLE); which will resolve the SourceResolver BUT from type of org.apache.excalibur.source.SourceResolver and not org.apache.cocoon.environment.SourceResolver which later on need when I invoke an action (line 145): Map substitutions = m_action.act(redirector, resolver, objectModel, m_src, parameters); With our former version (very old version of 2.2 - before maven) this did not produced an error, now however it throws a ClassCastException: ERROR (2008-08-20) 11:12.00:245 [core.modules.mapper.lm] (/index.html) PoolThread-4/MountNode: Failure processing LocationMap. java.lang.ClassCastException: org.apache.cocoon.components.CocoonComponentManag