[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 58

[jira] Commented: (COCOON-1238) Improvements for CustomJXPathBinding

[ http://issues.apache.org/jira/browse/COCOON-1238?page=comments#action_12364955 ] Bart Molenkamp commented on COCOON-1238: The patch looks good to me. If I look at the files that I have here, they don't look the same as those that I uploaded. I

Futher block-fw development

Daniel Fagerstrom wrote: I have not that much problem with the sitemap stuff, it shouldn't be that hard to migrate them. I'm more concerned about the Core and Settings objects, that is part of the trunk contract and that doesn't fit well into a splited up non-monolithic architecture. Hmm,

Re: 2.1 portal won't compile in jdk 1.3

I was able to recompile the jar we use. I will check it in this afternoon when I get home from work. FYI - The whole bridges project will not compile with JDK 1.3. At least the JSF support requires JDK 1.4. Ralph Carsten Ziegeler wrote: Antonio Gallardo wrote If the code

Re: Improvements for CustomJXPathBinding

Dear committers, Could you please comment on this? Are we allowed to break backwards compatibility on custom Java bindings? See http://issues.apache.org/jira/browse/COCOON-1238 -- Jean-Baptiste Quenot http://caraldi.com/jbq/

ForrestBot build for cocoon-docs FAILED

Automated build for cocoon-docs FAILED Log attached. -- Forrestbot run ended at 02 February 05:02 PM Using Forrest 0.8-dev Forrestbot administrator: ForrestBot -- [echo] ... Forrest render START 2006-02-02 05:02:16 ... Rendering docs in

Re: Component parameterization

Reinhard Poetz skrev: Daniel Fagerstrom wrote: Reinhard Poetz skrev: Daniel Fagerstrom wrote: We can also release with non OSGi blocks. The blocks are ongoing work, the most important thing that lacks is two level configuration. As discussed before the component configuration is part of

why user-roles?

What is the benefit of declaring custom roles in a user-role file outside cocoon.xconf, if you can do it together with the configuration inside cocoon.xconf? Is there any? I don't see the point Stefan

[jira] Commented: (COCOON-1238) Improvements for CustomJXPathBinding

[ http://issues.apache.org/jira/browse/COCOON-1238?page=comments#action_12364985 ] Stefan Podkowinski commented on COCOON-1238: Your latest version will work much better by leaving the decision to the custom binding impl how to handle paths.

Re: Futher block-fw development

Reinhard Poetz skrev: Daniel Fagerstrom wrote: ... Do you have a roadmap on what's open? * Component handling - design issues ok, that's the main question that needs to be answered * Logging - I put it in the BlocksManager but didn't give it much thought, here is a new chance for all

portal urls and validation

Hello, I'm trying to get our portal to validate according to W3C standards. One of the main problems is the portal urls that get created. These use the ampersand character () instead of the entity for ampersand (amp;) for appending parameters, which is incorrect. I tried changing the character

ForrestBot build for cocoon-docs FAILED

Automated build for cocoon-docs FAILED Log attached. -- Forrestbot run ended at 02 February 08:02 PM Using Forrest 0.8-dev Forrestbot administrator: ForrestBot -- [echo] ... Forrest render START 2006-02-02 08:02:06 ... Rendering docs in

Re: why user-roles?

Stefan Pietschmann wrote: What is the benefit of declaring custom roles in a user-role file outside cocoon.xconf, if you can do it together with the configuration inside cocoon.xconf? Is there any? I don't see the point … Simple separation of concerns. Declaring roles in a separate file

Re: why user-roles?

Stefan Pietschmann wrote: What is the benefit of declaring custom roles in a user-role file outside cocoon.xconf, if you can do it together with the configuration inside cocoon.xconf? Is there any? I don't see the point … Stefan It helps with conciseness in the cocoon.xconf. For

Re: Component parameterization

Daniel Fagerstrom wrote: Do you mean how the parameters from wiring.xml finally arrive in the component configuration? Yes. Parameters from the wiring get to the servlet as servlet context parameters, but how to solve it for components is unclear. Not talking about that I don't think that

[jira] Created: (COCOON-1764) Component handling

Component handling -- Key: COCOON-1764 URL: http://issues.apache.org/jira/browse/COCOON-1764 Project: Cocoon Type: New Feature Components: - Blocks Framework Reporter: Reinhard Poetz see

[jira] Created: (COCOON-1765) Logging

Logging --- Key: COCOON-1765 URL: http://issues.apache.org/jira/browse/COCOON-1765 Project: Cocoon Type: New Feature Components: - Blocks Framework Reporter: Reinhard Poetz [...] But my main thoughts is that logging need to be a centralized service,

[jira] Created: (COCOON-1766) Multi part MIME handling

Multi part MIME handling Key: COCOON-1766 URL: http://issues.apache.org/jira/browse/COCOON-1766 Project: Cocoon Type: New Feature Components: - Blocks Framework Reporter: Reinhard Poetz I think it makes most sense to let multi part

[jira] Created: (COCOON-1767) Error handling

Error handling -- Key: COCOON-1767 URL: http://issues.apache.org/jira/browse/COCOON-1767 Project: Cocoon Type: New Feature Components: - Blocks Framework Reporter: Reinhard Poetz There is sophisticated creation of error messages in the

Re: bug? dupliate triggers/jobs with cron block

Concretely, the difference is Tomcat doing a HostConfig.deployDescriptors() vs a HostConfig.deployDirectories().

ForrestBot build for cocoon-docs FAILED

Automated build for cocoon-docs FAILED Log attached. -- Forrestbot run ended at 03 February 05:02 AM Using Forrest 0.8-dev Forrestbot administrator: ForrestBot -- [echo] ... Forrest render START 2006-02-03 05:02:06 ... Rendering docs in

Cocoon zone services are down again (Was: ForrestBot build for cocoon-docs FAILED)

These failures are because the Cocoon zone services are down again. -David [EMAIL PROTECTED] wrote: Automated build for cocoon-docs FAILED Log attached. [snip ] Cocoon will report the status of each document: - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). [java]

Re: 2.1 portal won't compile in jdk 1.3

OK. So I was able to compile it with the updated bridges jar. Now it dies when I log in to the portal. My guess is that WSRP4J requires servlet 2.3? 22:17:43.283 WARN!! Error for /samples/blocks/portal/auth?resource=portal java.lang.NoSuchMethodError at

Re: 2.1 portal won't compile in jdk 1.3

Nope. WSRPException does a super on Exception(String message, Throwable t) which is only available in JDK 1.4 So either this class needs to be modified or the doc at http://portals.apache.org/wsrp4j/gettingstarted/installation.html is wrong and wsrp4j requires JDK 1.4. The subversion history

Re: 2.1 portal won't compile in jdk 1.3

Ralph Goers wrote: OK. So I was able to compile it with the updated bridges jar. Now it dies when I log in to the portal. My guess is that WSRP4J requires servlet 2.3? 22:17:43.283 WARN!! Error for /samples/blocks/portal/auth?resource=portal java.lang.NoSuchMethodError at

[jira] Commented: (COCOON-1238) Improvements for CustomJXPathBinding

[ http://issues.apache.org/jira/browse/COCOON-1238?page=comments#action_12365050 ] Bart Molenkamp commented on COCOON-1238: I agree with your point, I don't mind breaking backward compatibility either. But I thought it was worth mentioning it.