Jonas Kongslund wrote:
>
> 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() { ...}
No, not at the moment. There is no way to indicate this via the XML
Schema, so most likely it'll have to be added as a feature to the
binding file that Arnaud is working on.
--Keith
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
