Databases
StackOverflow2013
Postsdbo
POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
    primarykey
    data
    text
    <p>I got the error <code>Unable to locate NamespaceHandler when using context:annotation-config</code> running (java -jar) a jar assembled by the maven-assembly-plugin and containing my project and all its dependencies.</p> <p>As other people correctly spotted on the forum.springsource.org <a href="http://forum.springsource.org/showthread.php?t=48787">thread (message #7/8)</a> the problem occurs because the files <code>META-INF/spring.handlers</code> and <code>META-INF/spring.schemas</code> that are present in different jars, get overwritten when the maven-assembly-plugin repackages the jars in a single file.</p> <p>Looking at the content of two spring-*.jar files you can see the files sits in the same position relatively to the classpath</p> <pre><code>$ jar tf spring-oxm-3.0.3.RELEASE.jar META-INF/spring.handlers META-INF/spring.schemas org/springframework/oxm/GenericMarshaller.class ... $ jar tf spring-context-3.0.3.RELEASE.jar META-INF/spring.handlers META-INF/spring.schemas org/springframework/context/ApplicationContext.class </code></pre> <p>Isn't it is possible to put the META-INF folder in a specific package? If so the idea I'd suggest, (hope it's applicable) is to put the <code>META-INF/spring.shemas</code> and <code>META-INF/spring.handlers</code> files under the package they refer to.</p> <pre><code>$ jar tf spring-oxm-3.0.3.RELEASE.jar org/springframework/oxm/META-INF/spring.schemas org/springframework/oxm/META-INF/spring.handlers org/springframework/oxm/GenericMarshaller.class ... $ jar tf spring-context-3.0.3.RELEASE.jar org/springframework/context/META-INF/spring.handlers org/springframework/context/META-INF/spring.schemas org/springframework/context/ApplicationContext.class </code></pre> <p>This way they won't conflict when merged in a single jar. What do you think about it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjavanna
    1. USlogic.town
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. USWillie Wheeler
      1. VTFavorite
    2. VO
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. This table or related slice is empty.
      1. VTUpMod
    1. COProbably won't work. I would expect whatever code reads these files would use a `ClassLoader.getResource()` call, which looks in the root of the classpath. Or (more likely) explicitly examines the files in the classpath.
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. USAnon
    2. COYes, it won't work by just moving the files in that location without changing the code that loads it. I wonder if that's a better way to organize that information, as it keep things in separate packages (aka. namespaces). I'd like to submit a request for enhancement to SpringSrouce if the idea is good.
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. USlogic.town
    3. COYou might want to mark the 26+ question as an answer @Xan.
      singulars
      1. POIdea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar
      1. USGray
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload