Don't use the borked j2ee.jar from the java.net or java.net2 maven
repositories.
I had the same problem. Basically, the j2ee.jar on the java.net repos is
not a real jar, just stripped classes that have no method bodies, but just
the method definitions.
The borked jar is only good for compiling.
By the way, the individual component jars that go to make up j2ee.jar are
fine, so all you need to do is figure out which parts of the j2ee spec you
need and include the relevant artifact, i.e. mail, servlet, ejb, etc
On Jan 24, 2008 8:59 AM, Stephen Connolly [EMAIL PROTECTED]
wrote:
Don't use
Hello,
For my j2ee-components I use the jars provided by geronimo for building
To solve you problem you could switch to the following:
dependency
groupIdorg.apache.geronimo.javamail/groupId
artifactIdgeronimo-javamail_1.4_mail/artifactId
version1.3/version
/dependency
Stephen Connolly [EMAIL PROTECTED] schrieb:
Don't use the borked j2ee.jar from the java.net or java.net2 maven
repositories.
I had the same problem. Basically, the j2ee.jar on the java.net repos is
not a real jar, just stripped classes that have no method bodies, but just
the method
Yes, its a perfect use case for classifier. I just wish they'd use it...
As Marco already pointed out, the Geronimo dependencies are much more
useful than the API-only j2ee.jar file. I use them in all my J2EE
projects.
Wayne
On 1/24/08, Simon Kitching [EMAIL PROTECTED] wrote:
Stephen
