RE: [wtp-incubator-dev] Should we drop the POJO web service type in the

["Branekov, Danail" <danail.branekov@xxxxxxx>]

Hi Oisin,

I get the idea - with the interface you specify the service endpoint interface (SEI). With regards to JSR-181, the interface should be the "endpointInteface" parameter of the @WebService annotation. 
I am not an expert in Axis2, but I managed to create a bottom-up web service out of an interface without specifying implementation bean (at least the wizard did not ask me to). This is not the way it is supposed to work, right?

Regards, Danail

-----Original Message-----
From: wtp-incubator-dev-bounces@xxxxxxxxxxx [mailto:wtp-incubator-dev-bounces@xxxxxxxxxxx] On Behalf Of Oisin Hurley
Sent: Tuesday, August 25, 2009 2:43 PM
To: WTP Incubator Dev list
Subject: Re: [wtp-incubator-dev] Should we drop the POJO web service type in the Web Services wizard?

I think the best approach would be to have a single choice of
top-down/bottom-up, regardless of runtime, and allow the choice
of an interface as an option, which could be set if the runtime
supports that particular approach.

(i.e. what Keith wrote :)

Danail - JAX-WS allows the use of a Java interface to construct
the wsdl:portType. The JAX-WS tools currently allow you to
make one of these based on the class you have chosen, but
it should be possible for the user to choose an interface that
they have already created and have the tools mark that up.

But - I think that the user will then need to choose the impl.
class, or somehow have it inferred from the user-provided SEI.

Does that make sense?  I'm just back from vacation and have
forgotten absolutely everything :)

 --oh
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev