Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: users@cxf.apache.org
Subject: Re: Code generation
Date: Tue, 19 May 2009 12:27:07 -0400
User-Agent: KMail/1.11.3 (Linux/2.6.29-gentoo; KDE/4.2.3; x86_64; ; )
Cc: tog <guillaume.alleon@gmail.com>
References: <a0a50dbb0905170253o5940b91fq19302f20530700b6@mail.gmail.com>
 <200905181614.01084.dkulp@apache.org>
 <a0a50dbb0905190738p7724d30erc179e1d96316b9da@mail.gmail.com>
In-Reply-To: <a0a50dbb0905190738p7724d30erc179e1d96316b9da@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905191227.08182.dkulp@apache.org>

On Tue May 19 2009 10:38:17 am tog wrote:
> Hi Dan
>
> Yes I read this, it makes thing clear how setter/getter names are derived
> from the elements. Anyway I had some hope that at least the field name was
> customizable ... it should be in some way ...
>
> Digging in the dyamic client if found those 2 lines:
>
>         TypeClassInitializer visitor = new TypeClassInitializer(svcfo,
> intermediateModel);
>         visitor.walk();
>
> what are they for ?

They walk over the service model and wires the classes into the appropriate 
parts so that we have the right Class objects when we need to 
serialize/deserialize the parts.  

Dan


>
>
> Cheers
> Guillaume
>
> On Tue, May 19, 2009 at 4:14 AM, Daniel Kulp <dkulp@apache.org> wrote:
> > I think this is part of the JAXB spec.  You might want to read through
> > Appendix D of the JAXB spec which dictates the whole algorithm for
> > mapping XML
> > names to various things.
> >
> > Dan
> >
> > On Sun May 17 2009 5:53:11 am tog wrote:
> > > Hi,
> > >
> > > Before going to the Jaxb mailing list I would like to have your advice.
> > > I am working with groovy and the following wsdl
> > > http://webservices.daehosting.com/services/isbnservice.wso?WSDL
> > >
> > > Whatever is the mean to generate the classes (wsdl2java or
> >
> > DynamicClient),
> >
> > > I always get a class that looks like this
> > >
> > > @XmlAccessorType(XmlAccessType.FIELD)
> > > @XmlType(name = "", propOrder = {
> > >     "sisbn"
> > > })
> > > @XmlRootElement(name = "IsValidISBN13")
> > > public class IsValidISBN13 {
> > >
> > >     @XmlElement(name = "sISBN", required = true)
> > >     protected String sisbn;
> > >
> > >     public String getSISBN() {
> > >         return sisbn;
> > >     }
> > >
> > >     public void setSISBN(String value) {
> > >         this.sisbn = value;
> > >     }
> > > }
> > >
> > > Is there a good reason for this generated class not to respect the
> >
> > JavaBean
> >
> > > conventions ?
> > >
> > > Best Regards
> > > Guillaume
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog