So isnt there a standard way to do that? If else, how does Geronimo does it?
On 1/25/07, Lasantha Ranaweera <firstname.lastname@example.org> wrote:
Do you need Geronimo specific way of working or not? I think this might
be application server specific.
Bharath Ganesh wrote:
> Hi Lin
> webservices.xml with namepace and version <webservices
" version="1.1"> would certainly
> mean it has to be jax-rpc based.
> But with namespace & version <webservices
http://java.sun.com/xml/ns/javaee" ... version="1.2" does not
> mean it has to be jax-ws based.
> It could be jax-rpc based also since WebServices for J2EE 1.2 supports
> both jax-ws and jax-rpc based web services. There could be two
> webservice-descriptions in the same webservices.xml(1.2) and one of
> them could be jax-rpc based and one be jax-ws based. (spec says)
> But how does the deployer configure whether it is jax-ws based or
> jax-rpc based.
> On 1/25/07, *Lin Sun* <
> <mailto:email@example.com>> wrote:
> Hi, I just looked at JSR 109 too per your concern. Seems we
> should use the
> value of the XML namespace(xmlns) defined in webservices.xml to
> determine if
> this is JAX-RPC or not. For example, if it has:
> <webservices xmlns="
> Then it is JAX-RPC.
> If it has:
> <webservices xmlns="
> Then it is JAX-WS.
> From: Bharath Ganesh [mailto:firstname.lastname@example.org
> Sent: Wednesday, January 24, 2007 7:19 AM
> To: email@example.com <mailto:firstname.lastname@example.org>
> Subject: Configuring if JAX-WS or JAX-RPC based
> I was just trying out some JSR 109(Webservcies for Java EE 1.2) web
> servcies. I wanted to know if there is a standard way be means of
> which I
> can tell the container whether my EJB/ Java class exposed as a web
> is a JAX-WS webservice or a JAX-RPC webservice.
> Obviously if my module did not have a webservices.xml it means my web
> service has to be JAX-WS based. But think of the case when I havethe
> deployment descriptorto override the annotations. In such a case
> how can
> the container decide whether to use jax-rpc or jax-ws?
> Also the spec says if the webservices.xml has a
> jaxrpc-mapping-file defined,
> it would ignore this file for JAX-WS webservices, which is
> correct. So the
> presence/absence of JAX-RPC mapping file does not seem to be the
> for determing if its JAX-WS/JAX-RPC.
> So what else is the criteria?