-
1. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
marius.bogoevici Apr 12, 2010 12:46 PM (in response to kevinpauli)Hi Kevin,
This might be a bug, but you can always package your Spring archive with the .jar extension and the deployer will still figure one out (the documentation does not state that explicitly, but in a fixed version it will). So, could you just use the .jar extension and see how that works?
Hope this helps,
Marius
-
2. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
alesj Apr 12, 2010 12:47 PM (in response to kevinpauli)Trying to deploy a .war that is inside of an .ear in jBoss 5.1 with Spring Deployer 3.2. It seems to detect *.spring archives directly inside the .ear, but not ones that are down under the war's WEB-INF/lib directory. Is there something else I'm supposed to configure, or is this not supported?
No, the deployer is only picking up (sub)deployments.
Jars inside WEB-INF/lib are just plain classpath entries.
-
3. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
marius.bogoevici Apr 12, 2010 1:48 PM (in response to alesj)Ales,
Placing a jar with META-INF/jboss-spring.xml inside a war will trigger the deployer, though.
Marius
-
4. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
alesj Apr 12, 2010 3:21 PM (in response to marius.bogoevici)Placing a jar with META-INF/jboss-spring.xml inside a war will trigger the deployer, though.
Ah yes, but that is actually considered a bug: https://jira.jboss.org/jira/browse/JBDEPLOY-232
Unless this is explicitly supported alternative, we should only pick-up (sub)deployments.
-
5. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
marius.bogoevici Apr 12, 2010 3:51 PM (in response to alesj)Ales,
I'm not sure that what you mean here, but in other instances entries from within WEB-INF/lib can contain deployment metadata info: e.g. a CDI bean deployment archive (library jar) may contain META-INF/beans.xml or a JPA PU deployment may contain META-INF/persistence.xml.
I suppose that the same could apply for META-INF/jboss-spring.xml (as it happens now in the case of JBoss AS 5.0 and JBoss AS 5.1).
Marius
-
6. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
alesj Apr 12, 2010 4:07 PM (in response to marius.bogoevici)I'm not sure that what you mean here, but in other instances entries from within WEB-INF/lib can contain deployment metadata info: e.g. a CDI bean deployment archive (library jar) may contain META-INF/beans.xml or a JPA PU deployment may contain META-INF/persistence.xml.
Sure, those are all valid alternative locations -- as per the spec.
But not all are. ;-)
e.g. see the JBDEPLOY-232 use case --> jboss-classloading.xml in some lib jar, treated as deployments metadata :-(
I suppose that the same could apply for META-INF/jboss-spring.xml (as it happens now in the case of JBoss AS 5.0 and JBoss AS 5.1).
Sure, all I'm saying you need to re-think if this is still valid,
and if yes, then mark the deployers as the one that accepts alternative locations.
Otherwise it will not pick up metadata in lib's -- in after-jbdeploy-232 Deployers versions.
-
7. Re: Is Spring Deployer supposed to detect *.spring files inside a war's WEB-INF/lib directory?
marius.bogoevici Apr 12, 2010 4:17 PM (in response to alesj)OK, seems like we're on the same page here (both literally and figuratively ) - I suppose that the deployers change will come into effect only for JBoss AS 6, is that correct?