Hello Remi,
> Thx Margaret, I've just done it and it works just fine :) I've attached
> both my CollectionInfo implementation as well as the factory for it. To
> use it, just edit the org/exolab/castor/castor.properties and add the
> following:
>
>
org.exolab.castor.builder.type.j3=com.webmotion.assistants.test.castor.Field
InfoFactoryJ3
>
> To use it when generating code, just use the -types option with a j3
> value, like this:
>
> .... -types j3 ....
>
> Anyway, I think i've also found a bug in FieldModler class (line 778,
> wrong test) that might be related to my previous post (Data[] object is
> a Object[] object, still castor say it is not the case), so in case this
> was really a bug (I might be mistaken) and will be fixed, then this j3
> solution is no longer required.
now, I've the same Problem, too. I got the Exception of the ClassMolder when
it reads the mapping. (org.exolab.castor.mapping.MappingException: The
return type for method public com.gastroeasy.xml.Attribut[]
com.gastroeasy.xml.Artikel.getAttribut() does not match the declared field
type [Ljava.lang.Object;).
I just fetched the latest CVS Version and have seen, that you have not
corrected these Bug. Would it be done in future?
Thanks,
Thomas
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
