Hi,
it all depends.
Can you please give me a sample of what's going wrong after switching to
Castor 1.3rc1 without regenerating the Java POJOs ?
Regards
Werner
jpshields wrote:
> Hi,
>
> I'm pretty sure this question has already been answered before and I just
> missed it in the older posts because my problem seems just to big.
>
> I'm updating my castor framework from 1.0.3 to 1.3rc1 and the validations
> made by the marshalling framework does not work anymore and invalid values
> are slipping into my output xml files.
>
> My pojos were generated by castor 1.0.3 and I wanted to use the lenient
> properties (with 1.3rc1) to keep them and avoid unnecessary code rewriting
> based on those pojos. In my new castor.properties file, I kept the
> marshalling validation option to true like this:
>
> # True if all documents should be validated by the marshaling framework
> # Defaults to true.
> #
> org.exolab.castor.marshalling.validation=true
>
> I've doubled checked the validation parameter after the Marshaller
> instantiation and it outputs to "true" (like it should).
>
> Marshaller marshaller = new Marshaller(aWriter);
> String validate =
> marshaller.getProperty("org.exolab.castor.marshalling.validation");
>
> With the same code (generated by castor 1.0.3), if I change my
> castor.properties file and add the new jar, marshalling validation doesn't
> work anymore.
>
> I'm also using the new features with java 5.0 to use the internal JDK
> Xerces:
> org.exolab.castor.xml.serializer.factory=org.exolab.castor.xml.XercesJDK5XMLSerializerFactory
>
> I've also tried to generate new pojos with the 1.3rc1 source generator, but
> the same problem arise. I'm out of ideas. Is there another property I missed
> in the config file or some features that needs enabling?
>
> thanks in advance.
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
