>> I have used Castor 1.2 for handling the XML binding of some classes, but now
>> I have to integrate them into Documentum 5.3 that use Castor 0.9.5.2.
> :-(. Any chances of convincing them to upgrade ?
Unfortunately no: Documentum 5.3 is quite old. Maybe they have upgraded their
Castor version in Documentum 6, but I'm not sure (and I cannot upgrade to
Documentum 6).
>> Unfortunately Castor version shipped with Documentum is not compatible with
>> my version, so I tryed to repackage Castor 1.2 using JarJar Links.
>>
>> I solved the previous exceptions, but now I get the following error:
>>
>> Invalid mapping: No mapping loader/factory for:
>> SourceType=CastorXmlMapping / BindingType=xml
> Without a complete stack trace this is nearly impossible. Yes, you might
> be correct that you need to supply a re-arrangeed castor.properties
> file, but I am not sure. Bear in minnd that normally Castor ships a
> (default) properties file as part of its JAR(s). As such, deleting
> everything from your (custom) castor.properties that is a duplication of
> default values is a good starting point.
These are the latest log messages related to Castor
ERROR [com.capgemini.bof.rbt.impl.lib.org.castor.mapping.MappingLoaderRegistry]
No mapping loader/factory for: SourceType=CastorXmlMapping /
BindingType=xml
FATAL [com.capgemini.dam.xml.XMLHandler] Invalid mapping: No mapping
loader/factory for: SourceType=CastorXmlMapping / BindingType=xml
Exception in thread "50000" java.lang.ExceptionInInitializerError
..............................
Caused by: java.lang.RuntimeException: Invalid mapping: No mapping
loader/factory for: SourceType=CastorXmlMapping / BindingType=xml
I'll try to modify the castor.properties file.
--
Claudio
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
