Sure:
<xs:complexType name="EventTrigger">
<xs:annotation>
<xs:documentation>The concrete "named-event"
trigger.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="Trigger">
<xs:sequence>
<xs:element name="event"
type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="NowTrigger">
<xs:annotation>
<xs:documentation>The concrete "now"
trigger.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="Trigger"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OnceTrigger">
<xs:annotation>
<xs:documentation>The concrete "once"
trigger.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="Trigger">
<xs:all>
<xs:element name="startTime"
type="xs:dateTime"/>
</xs:all>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Trigger" abstract="true">
<xs:annotation>
<xs:documentation>.The base trigger all triggers
extend.</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="schedulerJobType">
<xs:annotation>
<xs:documentation>Type for transferring scheduler
jobs</xs:documentation>
</xs:annotation>
<xs:all>
<xs:element name="trigger" type="Trigger"
minOccurs="0"/>
<xs:element name="JobExecutorJob"
type="jobExecutorJobType" minOccurs="0"/>
<xs:element name="ScheduleInfo"
type="scheduledJobInfo"/>
</xs:all>
</xs:complexType>
--ekiM
-----Original Message-----
From: John Weir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 5:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] A couple of questions.
Any chance of an xml snippet of the schema? - I do this all the time and it
works ok for me
-----Original Message-----
From: Mike Wannamaker [mailto:[EMAIL PROTECTED]
Sent: 16 June 2004 21:40
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] A couple of questions.
I tried that and it solves one problem with name clashing, however because
I'm using derived complexTypes things still don't work quite right.
Example:
Trigger extends TriggerCT and MyTrigger extends TriggerCT. I then have some
xml like this.
<job>
<trigger xsi:type="MyTrigger">
...
</trigger>
</job>
The job class has a method setTrigger(Trigger), where I would think because
trigger is of type TriggerCT the method should read setTrigger(TriggerCT);
If it did then I'd be away to the races, but it doesn't ;-(
--ekiM
-----Original Message-----
From: John Weir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 4:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] A couple of questions.
.or ... use a binding file and Give the Complex types a suffix (like CT)
that avoids the collision with the element of the same name. No issue with
Simple types since they will be in the type subpackage
see http://castor.exolab.org/sourcegen.html#Binding-File for more details
-----Original Message-----
From: Keith Visco [mailto:[EMAIL PROTECTED]
Sent: 14 June 2004 22:47
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] A couple of questions.
#1. Don't turn off the errors! :-)
#2. Switch to "type" centric source generation:
http://castor.exolab.org/sourcegen.html#Class-Creation/Mapping
--Keith
Mike Wannamaker wrote:
>
> I have a question:
>
> I have an abstract complexType called Trigger. I have two other
> complex types MyTrigger and YourTrigger which have a base = "Trigger"
> derivedBy extension. I then have an element job which has an element
> trigger. The trigger element is of type "Trigger".
>
> This causes problems when using source generator. I get a class
> Trigger which extends Trigger if I turn off errors in SourceGenerator.
> I think
what
> I would like is that there be no class generated for the trigger element?
> How would I do that? Or is there some other way I should be doing this?
>
> TIA
> --ekiM
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
