All, I have posted this on castor-user, but I think it is probably more relevant here on castor-dev. The problem I have is the same as described in http://hypermail.linklord.com/castor-dev/2004/Apr/3947.html and the end result of that discussion was that this might be a bug.
I ran with assumption that it was a bug and as it seemed there was no bug about this on bugzilla, I created http://bugzilla.exolab.org/show_bug.cgi?id=1699. In this bug description I described some steps I took in the source code to "solve" the problem as I understood it. I think it seems reasonable that if an enumerated simpleType is implemented as a java class that looks very very similar to the way in which IDL enums get implemented in java, then complex types that reference or use this type for a child element should be implemented in terms of the java class, not in terms of the restriction base that the simpleType extends. So I guess I am looking for someone who knows the code better than me (that can be a lot of people), to either validate my "fix" or suggest a better fix for me. I would rather have a patched official version of castor generating my code, than a personally "hacked" version, so if we all decide this is the way to go, then if I have to I can follow this through more completely. Thanks Eric ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
