On Monday 10 December 2001 07:36, Keith Visco wrote:
> Jonas Kongslund wrote:
> > Using the SourceGenerator on the XML Schema below creates code for a
> > Project class and a Task class. Given a Project object I can reach all
> > associated Task objects but not the other way around. What should I
> > change in order to achieve a bi-directional one-to-many reference?
> >
> > I have tried to add
> > <xsd:element ref="project"/>
> > to the task sequence.
>
> That won't work. That simply means to reference an element declaration,
> it's not an element reference.
>
> You need to add the following to the Task definition:
>
> If there is one project to be referenced:
>
> <xsd:attribute name="project" type="xsd:IDREF"/>
Thanks. Is it possible to indicate the wanted qualification of the object?
For example I would like that
public java.lang.Object getProject() { ...}
becomes to
public foo.bar.Project getProject() { ...}
> > The SourceGenerator goes into an endless loop which
> > eventually is aborted by a StackOverflowException or OutOfMemory
> > exception.
>
> That's not good...we'll need to look into that, are you using the CVS
> version?
No, I was using release castor-0.9.3. Sorry for not testing against the CVS
version.
--
Jonas Kongslund <[EMAIL PROTECTED]> XNS: =Jonas Kongslund
When you want to change the world, you don't see the dawn by
getting up early - you see it by not sleeping through the night.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
