We tried it. The problem is that it generates different classes from what we
had before, and that leads to even more code changes. Any other ideas guys?
-----Original Message-----
From: Sebastien Gignoux [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 30, 2001 7:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] Problem with the newer version of Castor.
Take a look at:
http://www.castor.org/sourcegen.html
in the section called 'The type method' and 'The element
method'. Changing the castorbuilder.properties to use the 'type'
method might solve your problem.
Seb
Reynshteyn, Lenny writes:
> We are experiencing a problem where the new version of Castor behaves
> differently.
>
> We used version 0.8.11 and just swtched to 0.9.2.
>
> For the following case, it generated only regular public classes. But the
> new version generates laso abstract classes for each and the
corresponding
> implementation classes. Is there a way to do it the "old way" by
specifying
> some command-line arguments or using any other tricks?
>
> <xsd:complexType name="Record_type">
> <xsd:sequence>
> <xsd:element name="BookProperties" type="BookProperties"/>
> <xsd:element name="Book" type="Book"/>
> <xsd:element name="BookIntro" type="BookIntro"/>
> </xsd:sequence>
> </xsd:complexType>
>
>
> The new Castor generates something like:
>
> public class Book extends Book
> {
> .....
> .....
> }
>
> while the old version just generated one "Book" class. Any ideas?
>
> Many thanks.
> > _____________________________________________
> > Lenny Reynshteyn
> Firmwide Internet Group
> Goldman, Sachs & Co.
> > Tel: (212) 855-0332
> > Email: [EMAIL PROTECTED]
> >
> >
>
> -----------------------------------------------------------
> 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
