Commentaires sur : An operation with name  » already exists in this service http://planet.petalslink.com/home/chamerling/2009/05/14/an-operation-with-name-already-exists-in-this-service/ Things around SOA, Web Services, Open Source and more... Tue, 13 Oct 2009 10:09:57 +0000 hourly 1 http://wordpress.org/?v=3.1.2 Par : Christophe Hamerling http://planet.petalslink.com/home/chamerling/2009/05/14/an-operation-with-name-already-exists-in-this-service/comment-page-1/#comment-321 Christophe Hamerling Thu, 16 Jul 2009 06:17:04 +0000 http://blog.ebmwebsourcing.com/home/chamerling/?p=107#comment-321 <a href="#comment-320" rel="nofollow">@SD</a> Strange that you have the exception again. Are you using CXF? Sorry it is a typo you are right, I am going to fix it right now. You are also right on the second point but the reason, we always have to put annotation on the interface when we can. In that case imagine that you can not, solutions are : 1. Put annotations on the implementation 2. Create sort of a facade and do not care about annotations. For point number one, CXF really takes the right operation name when generating WSDL at runtime. A tool such as java2WSDL may also take the right operation name if you define to use the implementation and not the interface @SD
Strange that you have the exception again. Are you using CXF?
Sorry it is a typo you are right, I am going to fix it right now.
You are also right on the second point but the reason, we always have to put annotation on the interface when we can. In that case imagine that you can not, solutions are :
1. Put annotations on the implementation
2. Create sort of a facade and do not care about annotations.
For point number one, CXF really takes the right operation name when generating WSDL at runtime. A tool such as java2WSDL may also take the right operation name if you define to use the implementation and not the interface

]]> Par : SD http://planet.petalslink.com/home/chamerling/2009/05/14/an-operation-with-name-already-exists-in-this-service/comment-page-1/#comment-320 SD Wed, 15 Jul 2009 21:28:42 +0000 http://blog.ebmwebsourcing.com/home/chamerling/?p=107#comment-320 I have tried what you said, but still continue to get the same exception. Need some clarification. In your message text you say use @WebParam, but your code sample uses @WebMethod. I think @WebParam is a typo, but thought I would ask. Second, are you sure we can get away with this by simply using the annotation on the method implementations? Doesn't the WSDL generator look at the service interface? I'm thinking we need to put this on the service interface and not implementation. Thoughts? I have tried what you said, but still continue to get the same exception.

Need some clarification. In your message text you say use @WebParam, but your code sample uses @WebMethod. I think @WebParam is a typo, but thought I would ask.

Second, are you sure we can get away with this by simply using the annotation on the method implementations? Doesn’t the WSDL generator look at the service interface? I’m thinking we need to put this on the service interface and not implementation.

Thoughts?

]]> Par : Christophe Hamerling http://planet.petalslink.com/home/chamerling/2009/05/14/an-operation-with-name-already-exists-in-this-service/comment-page-1/#comment-302 Christophe Hamerling Wed, 24 Jun 2009 09:23:06 +0000 http://blog.ebmwebsourcing.com/home/chamerling/?p=107#comment-302 Good to know, thanks Good to know, thanks

]]> Par : Raul Raja http://planet.petalslink.com/home/chamerling/2009/05/14/an-operation-with-name-already-exists-in-this-service/comment-page-1/#comment-299 Raul Raja Tue, 23 Jun 2009 23:03:35 +0000 http://blog.ebmwebsourcing.com/home/chamerling/?p=107#comment-299 I have seen this issue not only with overloaded methods but also when extending and implementing interfaces in the same hierarchy and using generics :( I have seen this issue not only with overloaded methods but also when extending and implementing interfaces in the same hierarchy and using generics :(

]]>