Keith, thanks for the feedback, > > <elementBinding name="complexType:createUser/status">
This format gets me further. > > You can also nest component bindings as such to make it more readable: > > <complexTypeBinding name="createUser"> > <elementBinding name="status"> > ... > </elementBinding> > </complexTypeBinding> This format doesn't seem to work since castor complains of Stack Trace for :ValidationException: The field '_componentBindingTypeChoice' is a required field.; Looking at http://www.castor.org/binding.xsd it appears that each binding must have java-class,interface or method defined within it. If I place in my binding file the following: <cbf:elementBinding name="complexType:createUser/status"> <cbf:java-class name="createStatus"/> </cbf:elementBinding> I get problems such as the generated class having a circular reference class CreateStatus extends CreateStatus. If I change the binding to <cbf:elementBinding name="complexType:createUser/status"> <cbf:java-class name="createStatus2"/> </cbf:elementBinding> Everything seems to sort itself out but I'm not exactly sure why or how this works and the previous one doesn't. Any insignt? Thanks, Alex. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-user
