|
|
|
|
Re: Custom XML schema definition not found [message #718807 is a reply to message #718806] |
Thu, 25 August 2011 11:56 |
Barbara Rosi-Schwartz Messages: 448 Registered: July 2009 |
Senior Member |
|
|
spring.handlers:
http\://cocoon.apache.org/schema/configurator=org.apache.cocoon.spring.configurator.impl.ConfiguratorNamespaceHandler
spring.schemas:
http\://cocoon.apache.org/schema/configurator/cocoon-configurator-1.0.xsd=org/apache/cocoon/spring/configurator/schema/cocoon-configurator-1.0.xsd
http\://cocoon.apache.org/schema/configurator/cocoon-configurator-1.0.1.xsd=org/apache/cocoon/spring/configurator/schema/cocoon-configurator-1.0.1.xsd
http\://cocoon.apache.org/schema/configurator/cocoon-configurator-2.0.0.xsd=org/apache/cocoon/spring/configurator/schema/cocoon-configurator-2.0.0.xsd
http\://cocoon.apache.org/schema/configurator/cocoon-configurator-2.1.0.xsd=org/apache/cocoon/spring/configurator/schema/cocoon-configurator-2.1.0.xsd
and the OSGi-ified jar does have a schema folder in the org/apache/cocoon/spring/configurator directory which contains all those four xsds, as well as the ConfiguratorNamespaceHandler class in the package specified in the spring.handlers file above.
Thanks!
[Updated on: Thu, 25 August 2011 12:22] Report message to a moderator
|
|
|
Re: Custom XML schema definition not found [message #718816 is a reply to message #718807] |
Thu, 25 August 2011 12:31 |
Barbara Rosi-Schwartz Messages: 448 Registered: July 2009 |
Senior Member |
|
|
Hmmm...
Looking once again at the generated MANIFEST.MF for the OSGi-ified Configurator bundle, I have:
Build-Jdk: 1.6.0_24
Built-By: rosib
Bundle-Description: This OSGi bundle simply wraps cocoon-spring-configur
ator-2.1.0.jar artifact.
Bundle-DocURL: http://www.iggroup.com
Bundle-ManifestVersion: 2
Bundle-Name: ig-osgi-cocoon-spring-configurator
Bundle-SymbolicName: org.apache.cocoon.ig-osgi-cocoon-spring-configurato
r
Bundle-Vendor: IG Index
Bundle-Version: 2.1.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Embed-Directory: org/apache/cocoon/spring/configurator/schema
Export-Package: org.apache.cocoon.spring.configurator;uses:="org.apache.
commons.logging,javax.servlet,org.apache.cocoon.spring.configurator.imp
l";version="2.1.0.SNAPSHOT",org.apache.cocoon.spring.configurator.impl;
uses:="org.apache.commons.logging,org.apache.cocoon.configuration,org.w
3c.dom,javax.servlet,org.apache.cocoon.spring.configurator";version="2.
1.0.SNAPSHOT"
Ignore-Package: org.springframework.beans.factory.support,org.springfram
ework.web.context.request,org.springframework.util,org.springframework.
beans,org.springframework.core.io,org.springframework.beans.factory.xml
,org.springframework.context,org.springframework.beans.factory.config,o
rg.springframework.core.io.support,org.springframework.web.context,org.
springframework.web.context.support,org.springframework.beans.factory
Import-Package: javax.servlet;version="[2.5,3)",org.apache.cocoon.config
uration,org.apache.commons.logging;version="[1.1,2)",org.apache.log4j;v
ersion="[1.2,2)",org.apache.log4j.spi;version="[1.2,2)",org.apache.log4
j.xml;version="[1.2,2)",org.w3c.dom;version="[1.3,2)"
Tool: Bnd-1.43.0
(yes, I generated the bundle with the, dare I say it, Felix's maven-bundle-plugin... I was having problems with Bundlor and was in a hurry)
I am a bit worried about the line
Embed-Directory: org/apache/cocoon/spring/configurator/schema
Is that kosher?
|
|
|
|
|
Re: Custom XML schema definition not found [message #719219 is a reply to message #719187] |
Fri, 26 August 2011 12:54 |
|
A couple of questions on this
1. Should it be possible to do what Cocoon is attempting, i.e. providing a custom Spring schema, in a OSGi/Virgo environment? Or is the approach fundamentally flawed?
2. If it is not flawed how would you suggest analysing the problem. Are there logging options that will reveal what Spring DM configuration is doing during the parsing of bundles. Specifically I would be interested in looking at the mechanism that is picking up the custom schema.
3. If all else fails what are the other options for achieving runtime differentiation by environment. I know this can be achieved using Maven profiles, but that is at compile time. Barbara's goal is to use multiple config dirs to have environments launched from within single installation of Virgo. This means a more dynamic approach is called for.
Btw, I know that we can fall back to PropertyPlaceholderConfigurer on a bundle by bundle basis, but I am concerned that will tend to increase that maintenance overhead and lead to obscure bugs if the same variable is required in two or more bundles.
Thanks,
Joel
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04740 seconds