[castor-dev] Castor mapping jar packaging issues with castor-1.3.3-core.jar, castor-1.3.3-xml.jar, and castor-1.3.3.jar

Werner Guttmann

2014-02-14 18:58:57 UTC

Hi Jeff,

you should NOT have the castor-1.3.3 JAR on your classpath, anyhow, as
you apparently decided to use the individual Castor modules (core, xml,
...).

Can you please remove the Über-JAR, and your problems should be gone.

Kind regards
Werner

Post by Jeff J Li
There are packaging issues with the following three jar files in the
_castor_ 1.3.3 GA version from the link
_http://dist.codehaus.org/castor/1.3.3/castor-1.3.3.zip_..
castor-1.3.3-core.jar
castor-1.3.3-xml.jar
castor-1.3.3.jar
Those three files cannot be placed in the CLASSPATH at the same time
because they are sealed packages as showing in the manifest files and
they also contain duplicate compiled classes. Some classes in the
package org.castor.mapping are duplicated in both _castor_-1.3.3-xml.jar
and _castor_-1.3.3.jar. The packaging issue will case java security
sealing violation.
The _castor_-1.3.3-core.jar, and _castor_-1.3.3-xml.jar cannot be used
without the _castor_-1.3.3.jar. The reason is that the
_castor_-1.3.3-xml.jar misses some compiled classes which are available
in _castor_-1.3.3.jar, such as AbstractMappingLoaderFactory.class,
JDOMappingLoaderFactory.class, XMLMappingLoaderFactory.class in the
org.castor.mapping package.
User may have to re-assembly those the jar files such as replacing
everything in the package org.castor.mapping in the
_castor_-1.3.3-xml.jar with the package org.castor.mapping in the
_castor_-1.3.3.jar.
I believe this needs to be repackaging and released to users.
Regards,
------------------------------------------------------------------------
*Jeff Li , Software Architect*
DataStageConnectivity and XML
Information Management
Phone: (561) 862-3614

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email