This content has been marked as final.
Show 4 replies
-
1. Re: Error deploying RAR containing jaxb-xjc
alesj Oct 8, 2008 5:09 AM (in response to tomstrummer)"tomstrummer" wrote:
So yes, it's odd that there is a "1.0" folder in the JAR, but even moreso that JBoss seems to think it's an embedded archive and is trying to deploy it. This same archive deployed fine in JBoss 4.2.
Looks like JarStructure recognizes 1.0 as possible jar.
Guessing that 1.0 has META-INF directory?
Or you have DirStructure enabled? -
2. Re: Error deploying RAR containing jaxb-xjc
tomstrummer Oct 9, 2008 11:03 AM (in response to tomstrummer)"alesj" wrote:
Looks like JarStructure recognizes 1.0 as possible jar.
Guessing that 1.0 has META-INF directory?
Or you have DirStructure enabled?
Yup, there's definitely another META-INF directory under '1.0.' Like I said, it's odd that they do that, but unless there is some standard that says this is disallowed, I think JBoss5 is (unfortunately) going to have to learn to avoid it.
The JAR in question (or at least, a version of it) can be found here:
http://ibiblio.org/pub/packages/maven2/javax/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.jar
Although I have to ask... Once you've hit a JAR archive, do you really need to dig deeper? I've never heard of a JAR embedded in another JAR...
I'm using whatever is configured for the "default" profile in JBoss5 CR2.
Thanks for the response. -
3. Re: Error deploying RAR containing jaxb-xjc
alesj Oct 10, 2008 5:51 AM (in response to tomstrummer)"tomstrummer" wrote:
Although I have to ask... Once you've hit a JAR archive, do you really need to dig deeper? I've never heard of a JAR embedded in another JAR...
We treat .sar as a jar.
And sar definitely embeds other jars as its deployment units. -
4. Re: Error deploying RAR containing jaxb-xjc
alesj Oct 10, 2008 6:03 AM (in response to tomstrummer)"tomstrummer" wrote:
Yup, there's definitely another META-INF directory under '1.0.' Like I said, it's odd that they do that, but unless there is some standard that says this is disallowed, I think JBoss5 is (unfortunately) going to have to learn to avoid it.
The JAR in question (or at least, a version of it) can be found here:
http://ibiblio.org/pub/packages/maven2/javax/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.jar
Apart from the solution that I'm gonna propose,
I don't see what else you can do about it,
except that you 'fix' this weird jar.
What's actually going on here is the following thing:
- 1.0 has META-INF dir --> recognized as jar
- META-INF has manifest.mf, which has Main-Class attribute --> recignized as EJB Application Client
- hence JBossClientMetaData is present --> Ejb3ClientDeployer tries to deploy it
- Ejb3ClientDeployer complains about the 1.0 name, expecting only true .jar jars
But this is what you can do to avoid this 1.0 being used as deployment.
Use jboss-structure.xml in your app, describing what your actual deployments are.
See some examples of this jboss-structutre.xml in our Microcontainer/Deployers project.