But in my example at the bottom of the email, auto-complete is already set to false and i' ve got the error on the field "OBJECT_STATE".
-----Message d'origine----- De : Keith Visco [mailto:[EMAIL PROTECTED] Envoy� : jeudi 26 f�vrier 2004 19:00 � : [EMAIL PROTECTED] Objet : Re: [castor-dev] Error in Interface during marshalling Hi Jerome, Castor will, by default, try to marshal fields from interfaces implemented by the class. You can prevent this, by not using auto-complete. If you really want to use auto-complete, then you can specify the fields that you don't want: <class name="classA" auto-complete="true"> <field name="OBJECT_STATE" type="integer" transient="true"/> </class> > Pastre Jer�me wrote: > > Hi all, > > Did you have troubles with interface during the marshalling ? > > Let say classA implements interfaceB > > public interface interfaceB > { > public static final int OBJECT_STATE = 1; > } > > I've mapped "classA" (auto-complete=false) but not "interfaceB". > The field mapped for "classA" doesn't refer to "interfaceB". > > Therefore, Castor should not go into "interfaceB". > > But I get that error on "OBJECT_STATE" : > > > org.exolab.castor.mapping.MappingException: The field OBJECT_STATE > in class > > > interfaceB is not accessible -- the field must be public, not > static and not > > > transient > > Even if i remove "static", i still have the same error. > Notice that i don't want to marshall OBJECT_STATE. > > What could i do to avoid that ? > > thanks a lot > > ______________________________________ > > J�r�me PASTRE > Axway. (a Sopra Group company.) > R&D Axway Annecy > 8 e-mail : [EMAIL PROTECTED] > ( phone : (+33) (0)4 50 33 33 64 ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
