I thought I'd respond to this thread again just to see if it gets some more
eyes. Does anyone know why my *synchronous* methods are *not* being
unwrapped using the wrapped doc/lit convention? This is driving me crazy
about axis 2. I liked the way Axis 1 handled it *way, way better*.
Cheers,
Scott S. McCoy
On Nov 14, 2007 5:39 PM, Scott S. McCoy <[EMAIL PROTECTED]> wrote:
> The wsdl and xsds are attached. My question isn't why are there
> *two*methods, I realize what they're for. What I'm wondering is why the
> *asynchronous* methods are the only ones which are being *unwrapped *.
> The *synchronous* methods receive only a warpper object for what seems
> like no good reason.
>
> Cheers,
> Scott S. McCoy
>
>
> On Nov 14, 2007 5:26 PM, Martin Gainty < [EMAIL PROTECTED]> wrote:
>
> > Hi Scott-
> >
> > the invoke method is synchronous
> > the asynch analog is handled via createAsyncResponseListener
> >
> > If you display the WSDL here we will use the wsdl source to generate the
> > necessary source
> >
> > ./axis2/jaxws/proxt/ProxyTests.java has a DocLitWrapped proxy example
> > you can use
> >
> > ProxyDocLitWrappedService service1 = new
> > ProxyDocLitWrappedService();
> > DocLitWrappedProxy proxy1 =
> > service1.getProxyDocLitWrappedPort();
> > BindingProvider p1 = (BindingProvider)proxy1;
> > p1.getRequestContext().put(
> > BindingProvider.ENDPOINT_ADDRESS_PROPERTY,axisEndpoint);
> > String response1 = proxy1.invoke(request);
> > Thanks/
> > M--
> >
> > ----- Original Message -----
> > *From:* Scott S. McCoy <[EMAIL PROTECTED]>
> > *To:* [email protected]
> > *Sent:* Wednesday, November 14, 2007 7:37 PM
> > *Subject:* Wrapped Doc/Lit services in Axis2
> >
> > So when Axis 2 first came out, I opted to not use it because if it's
> > lack of support for unwrapping doc/lit services. Now, it supports
> > it...supposedly. Using the same WSDLs I use in Axis 1.4, I try to
> > generate a wrapped doc/lit client. This appears to only work for *
> > asynchronous* operations. *Unwrapping* seems to *not* take place when
> > on the *synchronous* operations.
> >
> >
> > Here's an example:
> >
> > ----
> > /**
> > * Auto generated method signature
> > * @param revokeAccess59
> > */
> > public
> > com.enhance.plapi.service.account.RevokeAccessResponserevokeAccess(
> > com.enhance.plapi.service.account.RevokeAccess revokeAccess59)
> > throws java.rmi.RemoteException;
> >
> > /**
> > * Auto generated method signature for Asynchronous Invocations
> > * @param revokeAccess59
> > */
> > public void startrevokeAccess(
> > com.enhance.plapi.credentials.Credentials credentials60,
> > com.enhance.plapi.service.account.User user61,
> > com.enhance.plapi.service.account.Account account62,
> > final
> > com.enhance.plapi.service.account.AccountWebServiceCallbackHandlercallback)
> > throws java.rmi.RemoteException ;
> >
> > ----
> >
> > Is there any way I can get the synchronous operations to get method
> > signatures similarly to the asynchronous services? I'd like to not have to
> > pack and unpack all of these myself.
> >
> > Otherwise, has some tricky little detail changed that I need to know
> > about when it comes to wrapped doc/lit services?
> >
> >
>
