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

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

Hi all,

 

Sorry for the probably stupid question, but what is the point of declaring an interface to be a web service endpoint? I had a look at Apache2 user guide (http://ws.apache.org/axis2/0_95/userguide2.html) and could not find where it states that an interface could be the service class. What should the behaviour of such an endpoint be? How the implementation class is figured out when the service is requested?

 

I would also like to state that bottom-up the web service wizard should allow using a java class (POJO) to be a service endpoint. Such a usecase is described in JSR-109, section 5.3.2:

“There are two ways a Service Implementation Bean can be implemented. This includes a Stateless Session EJB

and a JAX-RPC or JAX-WS service endpoint running in a web container”

 

 

Regards, Danail

 

---

From: wtp-incubator-dev-bounces@xxxxxxxxxxx [mailto:wtp-incubator-dev-bounces@xxxxxxxxxxx] On Behalf Of shane clarke
Sent: Tuesday, August 25, 2009 12:17 AM
To: kchong@xxxxxxxxxx
Cc: wtp-incubator-dev@xxxxxxxxxxx
Subject: [LIKELY JUNK]RE: [wtp-incubator-dev] Should we drop the POJO web service type in the Web Services wizard?

 

Hi Keith,

Yes, opening up the selection dialog would meet our needs.

I've had a look at the source behind the Java bean type object selection widget and if we can limit the Java search scope to sources and consider both classes and interfaces it'd be a straight replacement for the existing dialog.

I can log an enhancement request if we do decide to revert back to the Java bean type.

Thanks,
Shane

---

With Windows Live, you can organize, edit, and share your photos.