Hi Nick,
Nicholas L Gallardo wrote:
Keith,
Are you talking about a JAX-WS specific deployer, or the POJO
deployer? I'm not aware of a JAX-WS specific one, but certainly agree
that one is needed.
My guess as to what's happening...
Right now, we have POJO deployment, but we don't have good JAX-WS
integration into the deployment infrastructure. You're bean is being
picked up as a POJO and deployed as such which is where the
"echoMethod" entry is coming from.
Then, when your request hits the JAXWSMessageReceiver the first time,
the JAX-WS layer goes through its own metadata initialization. This
includes building up not only a
EndpointDescription/OperationDescription, but a set of
AxisService/AxisOperation objects to match. These are being mapped to
"echomethodString" which is where the other entry comes from.
When you say "It takes echoMethod and echomethodString as two
different methods.", what exactly do you mean there? They are
reflected as two operations in the WSDL?
If you deploy the jax-ws service and access http://localhost:8080/axis2,
you should see the above two methods as available operations of the
service. As I explained in the first mail, I did not include a wsdl in
the service jar.
To the point of the WSDL 1.1 generation, that leads me to believe this
isn't being deployed as a JAX-WS endpoint at all. We've known for a
while that since we don't have formal tooling for JAX-WS that there is
no generation. I'm guessing that you're endpoint is being deployed as
a normal POJO endpoint using the base Axis2 runtime instead of JAX-WS.
Regards,
-Nick
Inactive hide details for "keith chapman"
<[EMAIL PROTECTED]>"keith chapman" <[EMAIL PROTECTED]>
*"keith chapman" <[EMAIL PROTECTED]>*
11/20/2007 01:49 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: JAX-WS: problems with annotated methods
Hi,
This is due to a bug in the jaxws deployer and MessageReceiver. This
can be solved as follows,
During deployment name the axisOperation according to the annotation
("echomethodString") in this case and put a parameter into the
axisOperation stating the actual method name, therefore in the
messageReceiver we know which method to call. Can somebody familiar
with JaxWS code do this fix please.
Thanks,
Keith.
On Nov 20, 2007 11:42 AM, Charitha Kankanamge <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi devs,
I was trying to deploy jax-ws based service using axis2. Here is my
service impl class. please note that, I did not include any wsdl
inside
the service jar.
@WebService(name= "WSASJAX_Service2", targetNamespace =
"_http://www.webtest.org/jaxws_";)
public class jaxwsservice2 {
@WebMethod(operationName = "echomethodString")
public String echoMethod(String s){
return s;
}
}
Axis2 does not handle this service correctly. It takes
echoMethod and
echomethodString as two different methods. Also Axis2 was unable to
generate wsdl1.1 using the above service impl class. WSDL
generation was
successful when I removed the annotation members of @WEbMethod
annotation.
It seems that the Axis2 JAX-WS implementation is unable to
handle some
of the annotations which have annon members. I reported a JIRA
for this
issue at _https://issues.apache.org/jira/browse/AXIS2-3352_
since this is a fundamental scenario, it will be great if this is
resolved ASAP.
Please let me know if there are any issues in the above steps
which were
used to generate jax-ws service.
regards
Charitha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED] _
<mailto:[EMAIL PROTECTED]>
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers._
__http://wso2.org/_
--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070
A bug in the hand is better than one as yet undetected
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
