No I'm not using spring 3.0 or any other upgrades. I have found the solution
but I need some maven help to incorporate it in the build process. When
there is no war, (I'm using appfuse-core), the build process is not merging
spring.schemas and spring.handlers from the spring.jar to
target/classes/META-INF. This causes namespace issues in multiple spring
context applications as they override each others. When I manually move
these two files under META-INF everything is fine.
I would like to make it as part of the build process, I have found this
maven plugin but my knowledge of maven is very limited and I do not know
what should activate this plugin if any.
Thanks for your help
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
<configuration>
<transformers>
<transformer
implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
<resource>META-INF/spring.handlers</resource>
</transformer>
<transformer
implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
<resource>META-INF/spring.schemas</resource>
</transformer>
</transformers>
</configuration>
</execution>
</executions>
</plugin>
--
View this message in context:
http://n4.nabble.com/Multi-context-Unable-to-locate-NamespaceHandler-for-namespace-tp1561265p1563183.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
