Why are there two *different* jboss-j2ee.jar files in the jboss module?
58456 Jun 21 15:52 ./src/client/jboss-j2ee.jar
61880 Jun 21 15:52 ./src/lib/jboss-j2ee.jar
Why are we compiling these sources and not using the distributions from sun?
I can understand that we might want to aggregate all of the jars from sun
into one big one, but why recompile?
I just ran into a very odd problem that could have been caused by this,
though I have not tracked down the fix for it yet:
java.io.InvalidClassException: javax.transaction.SystemException; Local
class not compatible: stream classdesc serialVersionUID=-513218974312200874
local class serialVersionUID=839699079412719325
I looked at the source in the jboss-j2ee module and there are not
serialVersionUID fields in SystemException, which means that every time this
module is recompiled it will not be compatible with any other version...
unless for some random lucky chance that javac re-generated all of the UID's
the same as a previous build... it could happen, and I could also start
thinking that Windows is the best software that the world has ever seen.
My guess is that I ran into this because I am using the jta.jar from sun
when building my components, though I am not 100% sure on this... close to
it though.
Can some one explain to me the rational for the jboss-j2ee module. I would
suggest either chaging the module to aggregate from the sun .jar files, or
to use the serialVersionUID from those jar files in the sources listed here.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
