Hi Bharath,
I am not quite sure there is a common way to get this kind of things get
going for a app server. May be some other expert in the list might help
us on this regard. I will explain you how it works in Geronimo below in
a web container of Jetty with Axis2 as JAXWS implementation, since we
have only Axis for JAX-RPC implementation. ;-)
As you might already know Geronimo works with GBeans architecture with
dependency injection. When you deploy a WAR module it will be picked up
by a JettyWebModuleBuilder and it has been associated with 2
WebServiceBuilder classes (one for JAX-RPC and JAXWS) in G 2.0 (JEE
version). Based on the information given in the XML files or the
annotations on the class files in the module it will create a GBean for
each web service. If one of the WebService Builder doesn't pickup your
module it will be passed to the other one, so in the Axis2 Geronimo
integration side we need not to implement JAX-RPC based implementation
:-) .
Thanks,
Lasantha
Bharath Ganesh wrote:
Hi Lasantha
So isnt there a standard way to do that? If else, how does Geronimo
does it?
-Bharath
On 1/25/07, *Lasantha Ranaweera* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
Do you need Geronimo specific way of working or not? I think this
might
be application server specific.
Thanks,
Lasantha
Bharath Ganesh wrote:
> Hi Lin
>
> webservices.xml with namepace and version <webservices
> xmlns="http://java.sun.com/xml/ns/j2ee
<http://java.sun.com/xml/ns/j2ee>" version="1.1"> would certainly
> mean it has to be jax-rpc based.
>
> But with namespace & version <webservices
> xmlns=" 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.
>
> Thoughts?
>
> -Bharath
> http://jroller.com/page/bharath
>
>
>
> On 1/25/07, *Lin Sun* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> 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=" http://java.sun.com/xml/ns/j2ee";
version="1.1">
>
> Then it is JAX-RPC.
>
> If it has:
>
> <webservices xmlns=" http://java.sun.com/xml/ns/javaee"; ...
> version="1.2"
>
> Then it is JAX-WS.
>
> Thoughts?
>
> Lin
> ________________________________________
> From: Bharath Ganesh [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>]
> Sent: Wednesday, January 24, 2007 7:19 AM
> To: user@geronimo.apache.org
<mailto:user@geronimo.apache.org> <mailto:user@geronimo.apache.org
<mailto:user@geronimo.apache.org>>
> Subject: Configuring if JAX-WS or JAX-RPC based
>
> Hi
> 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
> service
> 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
> criteria
> for determing if its JAX-WS/JAX-RPC.
> So what else is the criteria?
>
> Thanks
> Bharath
> http://jroller.com/page/bharath
<http://jroller.com/page/bharath>
>
>
>
>
