Hi,

I've just upgraded Castor from 1.2 to 1.3.2 & I'm seeing strange behaviour. I 
configure my castor marshaller like so:

<!-- Responsible for marshalling & un-marshalling of XML into pojos. -->
 <bean id="castorMarshaller" 
class="org.springframework.oxm.castor.CastorMarshaller" >
  <property name="mappingLocations" >
   <array>
    <value>${castor.mapping.ws.serveranalyzer.path}</value>
    <value>${castor.mapping.ws.serverdiscovery.path}</value>
    <value>${castor.mapping.ws.serversession.path}</value>
    <value>${castor.mapping.ws.servergeneral.path}</value>
   </array>
  </property>
        <property name="ignoreExtraElements" value="true" />
        <property name="ignoreExtraAttributes" value="true" />
 <property name="suppressXsiType" value="true" />
 </bean>


Now, I happen to have 2 classes called LoginRequest. One lives in the 
${castor.mapping.ws.serversession.path} & the other lives in  
${castor.mapping.ws.servergeneral.path}

These 2 classes have different packages, & map to different namespaces. 
However, I am getting the following exception:


Castor unmarshalling exception; nested exception is 
org.exolab.castor.xml.MarshalException: The class for the root element 
'LoginRequest' could not be found.

This was never a problem in castor 1.2 & If I remove the other  mapping  file 
then everything works as expected.

Can anybody shed any light?

Thanks in advance,

Kevin.

Reply via email to