Now I did some small modifcations to my interfaces so I created a sample
service with a method declared like:
@WebMethod(operationName = doAdd)
String doAdd(
@WebParam(name = a) String a,
@WebParam(name = b) String b);
@WebMethod(operationName = doAdd)
@WebEndpoint(name=doAdd)
Future? doAddAsync(
Creating the async methods can be tricky as the request object gets unwrapped,
the the wrapper object is used for the callback.
My suggestion is to create your service, grab the wsdl, and generate a client
with it enabling the async methods. (with 2.4.2, you can pass -asyncMethods
flag).
Ok, I was considering that but all the samples I saw then depended on the
WSDL:s which we dont want.
But it seems you are saying that once I generated the wsdl:s and then
back-generated the code (to get it correct) I should be able to discard the
wsdl:s if we want and depend only on the code
Hi!
We declare our SOAP interfaces in java and then build the WSDL:s from the
java code since 99% of our clients are in java and to make it most
convenient for them we have decided to follow this path.
eg we might have a sample service declared like:
@WebService
public interface MyService
{
I tried ad-hoc and just wrote the interface myself as:
@WebService
public interface MyService
{
@WebMethod(operationName = doSomething)
Future? doSomething(
@WebParam(name = someParam) String someParam,
AsyncHandlerDoSomethingResult asyncHandler);
}
But with this I just god the error :
On Wednesday, August 17, 2011 4:17:58 PM Kent Närling wrote:
I tried ad-hoc and just wrote the interface myself as:
@WebService
public interface MyService
{
@WebMethod(operationName = doSomething)
Future? doSomething(
@WebParam(name = someParam) String someParam,
On 17 August 2011 23:21, Kent Närling kent.narl...@seamless.se wrote:
On 17 August 2011 18:08, Daniel Kulp dk...@apache.org wrote:
On Wednesday, August 17, 2011 4:17:58 PM Kent Närling wrote:
I tried ad-hoc and just wrote the interface myself as:
@WebService
public interface
