You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2013/08/05 20:54:23 UTC
Generating proper Javadoc for SEI Implementation
Hi Users@,
I've been using Apache CXF 2.7.5 in Eclipse Juno Service Release 1... it is
going great and I am extremely happy with the service generation... it is
saving a lot of time.
I have one issue however...
When I generate the actual SEI from my Java class, no Javadoc annotations
are added to the generated Javacode meaning that when I look into the wsdl
file in the web services explorer and test the service, the arguments for
my service are being set to default arg0, arg1,... etc.
Is there something I've missed when auto generating the SEI that would lead
to the absence of the correct Javadoc.
To confirm, all of my Java classes are fully annotated BEFORE I generate
the SEI code.
Thank you very much for any advice, it is greatly appreciated.
Best
Lewis
--
*Lewis*
Re: Generating proper Javadoc for SEI Implementation
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Thank you Jason
On Mon, Aug 5, 2013 at 1:13 PM, Jason Pell <ja...@pellcorp.com> wrote:
> You should include @WebParam annotations to configure the parameter names.
> On 06/08/2013 4:54 AM, "Lewis John Mcgibbney" <le...@gmail.com>
> wrote:
>
> > Hi Users@,
> > I've been using Apache CXF 2.7.5 in Eclipse Juno Service Release 1... it
> is
> > going great and I am extremely happy with the service generation... it is
> > saving a lot of time.
> > I have one issue however...
> > When I generate the actual SEI from my Java class, no Javadoc annotations
> > are added to the generated Javacode meaning that when I look into the
> wsdl
> > file in the web services explorer and test the service, the arguments for
> > my service are being set to default arg0, arg1,... etc.
> > Is there something I've missed when auto generating the SEI that would
> lead
> > to the absence of the correct Javadoc.
> > To confirm, all of my Java classes are fully annotated BEFORE I generate
> > the SEI code.
> > Thank you very much for any advice, it is greatly appreciated.
> > Best
> > Lewis
> > --
> > *Lewis*
> >
>
--
*Lewis*
Re: Generating proper Javadoc for SEI Implementation
Posted by Jason Pell <ja...@pellcorp.com>.
You should include @WebParam annotations to configure the parameter names.
On 06/08/2013 4:54 AM, "Lewis John Mcgibbney" <le...@gmail.com>
wrote:
> Hi Users@,
> I've been using Apache CXF 2.7.5 in Eclipse Juno Service Release 1... it is
> going great and I am extremely happy with the service generation... it is
> saving a lot of time.
> I have one issue however...
> When I generate the actual SEI from my Java class, no Javadoc annotations
> are added to the generated Javacode meaning that when I look into the wsdl
> file in the web services explorer and test the service, the arguments for
> my service are being set to default arg0, arg1,... etc.
> Is there something I've missed when auto generating the SEI that would lead
> to the absence of the correct Javadoc.
> To confirm, all of my Java classes are fully annotated BEFORE I generate
> the SEI code.
> Thank you very much for any advice, it is greatly appreciated.
> Best
> Lewis
> --
> *Lewis*
>
Re: Generating proper Javadoc for SEI Implementation
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
Mmmm... followed both threads of advice and still in the same position.
I deleted my previously generated SEI, generated a new one with @WebMethod,
@WebParam, @RequestWrapper, @ResponseWrapper, @WebResult options activated
and stil getting the same resu;t
@WebMethod(operationName = "calculateBeltConveyorPowerRequirement",
action = "urn:CalculateBeltConveyorPowerRequirement")
@RequestWrapper(className =
"edu.stanford.eil.eilservicestack.conveyor.beltconveyor.jaxws.CalculateBeltConveyorPowerRequirement",
localName = "calculateBeltConveyorPowerRequirement", targetNamespace = "
http://beltconveyor.conveyor.eilservicestack.eil.stanford.edu/")
@ResponseWrapper(className =
"edu.stanford.eil.eilservicestack.conveyor.beltconveyor.jaxws.CalculateBeltConveyorPowerRequirementResponse",
localName = "calculateBeltConveyorPowerRequirementResponse",
targetNamespace = "
http://beltconveyor.conveyor.eilservicestack.eil.stanford.edu/")
@WebResult(name = "return")
public double calculateBeltConveyorPowerRequirement(@WebParam(name =
"arg0") double productLoading,
@WebParam(name = "arg1") double conveyorLength, @WebParam(name =
"arg2") double conveyorSpeed);
As you can see, at the bottom the params are not annotated. Unfortunately
there are plenty of private methods which are also not generated when the
SEI is generated...
@Dan
, you mentioned that this is Eclipse... should I head over there?
Thank you v much for the feedback so far.
Best
Lewis
On Mon, Aug 5, 2013 at 1:33 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I'm not very familiar with much of this stuff in eclipse. This is all
> part of Eclipse and the Apache CXF community doesn't really have input into
> that codebase.
>
> That said, if you click on the Eclipse preferences for the CXF generation,
> there is a "JAX-WS" tab where you can turn on the @WebParam annotation
> generation. I'm not really sure what that does, but you certainly would
> need to have the WebParam annotations generated to avoid the arg0… type
> naming.
>
> Dan
>
>
> On Aug 5, 2013, at 2:54 PM, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com> wrote:
>
> > Hi Users@,
> > I've been using Apache CXF 2.7.5 in Eclipse Juno Service Release 1... it
> is
> > going great and I am extremely happy with the service generation... it is
> > saving a lot of time.
> > I have one issue however...
> > When I generate the actual SEI from my Java class, no Javadoc annotations
> > are added to the generated Javacode meaning that when I look into the
> wsdl
> > file in the web services explorer and test the service, the arguments for
> > my service are being set to default arg0, arg1,... etc.
> > Is there something I've missed when auto generating the SEI that would
> lead
> > to the absence of the correct Javadoc.
> > To confirm, all of my Java classes are fully annotated BEFORE I generate
> > the SEI code.
> > Thank you very much for any advice, it is greatly appreciated.
> > Best
> > Lewis
> > --
> > *Lewis*
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
*Lewis*
Re: Generating proper Javadoc for SEI Implementation
Posted by Daniel Kulp <dk...@apache.org>.
I'm not very familiar with much of this stuff in eclipse. This is all part of Eclipse and the Apache CXF community doesn't really have input into that codebase.
That said, if you click on the Eclipse preferences for the CXF generation, there is a "JAX-WS" tab where you can turn on the @WebParam annotation generation. I'm not really sure what that does, but you certainly would need to have the WebParam annotations generated to avoid the arg0… type naming.
Dan
On Aug 5, 2013, at 2:54 PM, Lewis John Mcgibbney <le...@gmail.com> wrote:
> Hi Users@,
> I've been using Apache CXF 2.7.5 in Eclipse Juno Service Release 1... it is
> going great and I am extremely happy with the service generation... it is
> saving a lot of time.
> I have one issue however...
> When I generate the actual SEI from my Java class, no Javadoc annotations
> are added to the generated Javacode meaning that when I look into the wsdl
> file in the web services explorer and test the service, the arguments for
> my service are being set to default arg0, arg1,... etc.
> Is there something I've missed when auto generating the SEI that would lead
> to the absence of the correct Javadoc.
> To confirm, all of my Java classes are fully annotated BEFORE I generate
> the SEI code.
> Thank you very much for any advice, it is greatly appreciated.
> Best
> Lewis
> --
> *Lewis*
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com