> Can you run the Glassfish Verifier tool
My GF 3.1.2 doesn't seem to contain this tool. When I try to deploy with
the "verify" option checked, the process and logs don't tell me any
additional information.
> What other differences (other than timestamps) are you finding?
* 1.8 ear file size is smaller.
* There was an auto-generated empty persistance.xml in mycoservicesclient
module. That file is included in the jar when packaging with MEAR 2.7, but
not 2.8.
* The manifest for the ear has different ordering of items and the
created-by now includes the maven version number in 2.8.
* The manifest for the ejb jar has different ordering, and as mentioned, no
values for the class-path in 2.8.
Why the jars for mycoservicesclient and mycoservicesejb change when I just
change the version of MEAR is what seems strangest to me.
> Dumb question: why is there anything at all in the Manifest?
I'm not sure that's a dumb question. To be honest, I've never bothered
much to look at the manifests before, so I'm not entirely sure what should
and shouldn't be in each one. I'm new to the ear thing (coming from
Spring/Tomcat). Right now all of our dependant jars are at the root of the
ear (This is touched on by Jörg in his response). That seemed
unconventional, but I don't have a good arguement to convince others that
it should be structured any differently. As for how the dependencies made
it into the manifest, my guess is something about our pom config (again,
Jörg seems to point to that as the reason).
If you're interested, here is what's in the manifest for the classpath.
Class-Path: mycoservicesclient.jar ehcache-core.jar slf4j-api.jar
commons-io.jar commons-lang3.jar hamcrest-all.jar mycoservicescore.jar
json-simple.jar mycocommon.jar mycodatasourceclient.jar commons-dbutils.jar
commons-configuration.jar commons-lang.jar commons-logging.jar
commons-beanutils.jar commons-codec.jar mvel2.jar guava.jar
> It seems that for the new version something has been changed for the
generated default "application.xml".
The application.xml didn't change between the 2 ears.
<?xml version="1.0" encoding="UTF-8"?>
<application ... version="6">
<display-name>mycoservicesear</display-name>
<module><ejb>mycoservicesejb.jar</ejb></module>
<module><web>
<web-uri>mycoserviceswar.war</web-uri>
<context-root>mycoservices</context-root>
</web></module>
</application>
Since the pom configurations come into play, I've pasted the relevant
sections of several of the poms here: http://pastebin.com/FiPFGxmb
> Your ear should end up with a structure like...
Am I correct in assuming the mycoservicesclient.jar should also go in lib?
It just contains @Local interfaces and @Entity POJOs.
> Try to define the "defaultJavaBundleDir" to "lib".
Thanks, I'll give that a shot.
