Re: [castor-dev] bad generated java class names using namingXML

2003-06-03 Thread Mazz Golf
Thanks Arnaud. It was my misunderstanding of which namespace the elements inside of the Fault complex type go in. I thought since the target namespace was defined and Fault was in that namespace, that its children also go in the target namespace. Thanks for fixing the prefix/suffix duplication p

Re: [castor-dev] binding file -- element

2003-06-03 Thread Ostermueller, Erik
Here's a use case. Consider an 'anyNode', especially like the one in the element of the SOAP schema. We don't have enough info to unmarshal : -'s parent () doesn't store the package name of because it is an

Re: [castor-dev] Prevent insert for field

2003-06-03 Thread tek1
Can you show your source code and mapping? At 09:09 03/06/02 +0200, you wrote: Hi there. I have class Employee which incorporate Company object. Company is independent from Employee. When I'm creating new Employee I set Company field quried through OQL. Both Company and Employee are TimeStamable.

Re: [castor-dev] bad generated java class names using namingXML

2003-06-03 Thread Arnaud Blandin
Hi John, Thanks for your mail, I will take the opportunity to clarify the behavior of Castor since it seems to be a frequently experienced problem: When generating source for an element, Castor will check the targetNamespace of that element and then it will associate a java package to the corresp