There is a sample binding file in the examples/SourceGenerator
directory.

--Keith


James Carter wrote:
> 
> Hi Jim,
> 
> >From earlier posts this week (that I saved because I'm needing an
> example binding file to jump-start also):
> 
> Jim Carter
> 
> -----------------------------------------------------------
> 
> Hi Micheal,
> 
> Try something like the following:
> 
>  <cbf:elementBinding name="/test/a">
>              <cbf:java-class name="A1"/>
>  </cbf:elementBinding>
> 
> I'll have to double check on the path, but that should get you started
> in the right direction.
> 
> --Keith
> 
> "Lin, Michael" wrote:
> >
> > > Below is a sample schema I'm having problems with.  I have two
> complextype
> > > elements with the same name and I want to generate different class
> names
> > > for them.  How can I do this with a binding file?  Any help is
> > > appreciated.  Thanks.
> > >
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > > elementFormDefault="qualified" attributeFormDefault="unqualified">
> > >       <xs:element name="test">
> > >               <xs:annotation>
> > >                       <xs:documentation>Comment describing your
> root
> > > element</xs:documentation>
> > >               </xs:annotation>
> > >               <xs:complexType>
> > >                       <xs:sequence>
> > >                               <xs:element name="a">
> > >                                       <xs:complexType>
> > >                                               <xs:sequence>
> > >                                                       <xs:element
> name="b"
> > > type="xs:string"/>
> > >                                                       <xs:element
> name="c"
> > > type="xs:string"/>
> > >                                               </xs:sequence>
> > >                                       </xs:complexType>
> > >                               </xs:element>
> > >                       </xs:sequence>
> > >               </xs:complexType>
> > >       </xs:element>
> > >       <xs:element name="test2">
> > >               <xs:complexType>
> > >                       <xs:sequence>
> > >                               <xs:element name="a">
> > >                                       <xs:complexType>
> > >                                               <xs:sequence>
> > >                                                       <xs:element
> name="m"
> > > type="xs:string"/>
> > >                                               </xs:sequence>
> > >                                       </xs:complexType>
> > >                               </xs:element>
> > >                       </xs:sequence>
> > >               </xs:complexType>
> > >       </xs:element>
> > > </xs:schema>
> > >
> > >
> >
> > -----------------------------------------------------------
> > 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
> 
> 
>                       "Brain, Jim"
>                       <[EMAIL PROTECTED]        To:       [EMAIL PROTECTED]
>                       com>                     cc:
>                                                Subject:  Re: [castor-dev] Local 
> defined elements with unique types
>                       12/04/2003 12:58
>                       PM
>                       Please respond to
>                       castor-dev
> 
> 
> 
> Are there examples of this binding file I can use to jump start?
> 
> Jim
> 
>              Jim Brain, [EMAIL PROTECTED]
>              "Researching tomorrow's solutions today."
>              (319) 369-2070 (work)
>              APPLICATIONS ARCHITECT, AFP-IT
> 
> -----Original Message-----
> From: Rhett Sutphin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 04, 2003 11:49 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [castor-dev] Local defined elements with unique types
> 
> Brain, Jim wrote:
> > Notice that each type has an element named Extension, but each has a
> 
> > different type.  When I run it through Castor, it creates the first
> > Extension class and names it Extension, but then when it gets to the
> 
> > second one, it creates a new Extension class and overwrites the
> first one.
> 
> >
> > Is there a way to prevent that from occurring?
> 
> Yes.  Use a binding file to give the extension elements' java classes
> different names.
> 
> Rhett
> 
> -----------------------------------------------------------
> 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

Reply via email to