you can use AbstractInvoker << ONLY >> inside methods of your service
implementations on server side.

On 4/26/07, craig w <[EMAIL PROTECTED]> wrote:
When I try, AbstractInvoker.getContext() it is always returning NULL.

Example:

HelloServiceClient service = new HelloServiceClient();

HelloServiceSoap client = service.getHelloServiceSoap();

Holder<UserInfo> holder = new Holder<UserInfo>();

SayHelloResult result = client.sayHello("bob", holder);
System.out.println(AbstractInvoker.getContext());

that prints out null.

any idea why?


On 4/26/07, Tomek Sztelak <[EMAIL PROTECTED]> wrote:
>
> You can use AbstractInvoker.getContext only from within your service
> implementation, not from client.
>
> On 4/26/07, craig w <[EMAIL PROTECTED]> wrote:
> > I see that the latest snapshot is out, is the change that I need:
> >
> > XFIRE-964        Support for accessing MessageContext from within
service
> > implementation
> >
> > How do I get to the AbstractInvoker?   Here is the sample code I am
using...
> >
> >  HelloServiceClient service = new HelloServiceClient();
> >
> > HelloServiceSoap client = service.getHelloServiceSoap();
> >
> > thanks
> >
> >
> >
> >
> > On 4/23/07, craig wickesser <[EMAIL PROTECTED]> wrote:
> > > thanks for that, any idea on an ETA?  i appreciate your help.
> > >
> > >
> > >
> > > On 4/23/07, Tomek Sztelak <[EMAIL PROTECTED] > wrote:
> > > > I'll post info about snapshot on mailing list when it will be ready
to
> > downalod.
> > > >
> > > > On 4/23/07, craig wickesser < [EMAIL PROTECTED]> wrote:
> > > > > ok, what should I look for when I download?  ...when can I
download
> > it?
> > > > >
> > > > > thanks again!
> > > > >
> > > > >
> > > > > On 4/22/07, Tomek Sztelak < [EMAIL PROTECTED] > wrote:
> > > > > >
> > > > > > I hope i fixed it in svn. I'll publish a snapshot in next few
days,
> > so
> > > > > > you can test if it works for you. Just ping me ( here or on irc
)
> > and
> > > > > > remember me about it ;)
> > > > > >
> > > > > > On 4/22/07, craig wickesser <[EMAIL PROTECTED]> wrote:
> > > > > > > anyone have any ideas?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 4/19/07, craig wickesser < [EMAIL PROTECTED] > wrote:
> > > > > > > >
> > > > > > > > I am trying to access an existing web service and I used the
> > XFire
> > > > > eclipse
> > > > > > > plugin to generate java code from a WSDL.
> > > > > > > >
> > > > > > > > I essentially have:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > HelloServiceClient service = new HelloServiceClient();
> > > > > > > >
> > > > > > > > HelloServiceSoap client = service.getHelloServiceSoap();
> > > > > > > >
> > > > > > > > Holder<UserInfo> holder = new Holder<UserInfo>();
> > > > > > > >
> > > > > > > > SayHelloResult result = client.sayHello ("bob", holder);
> > > > > > > >
> > > > > > > > System.out.println("Result: " + result.getHelloMessage());
> > > > > > > >
> > > > > > > > System.out.println("UserInfo: "+ holder.value);
> > > > > > > >
> > > > > > > > OUTPUT:
> > > > > > > >
> > > > > > > > Result: Hello bob
> > > > > > > >
> > > > > > > > UserInfo: null
> > > > > > > >
> > > > > > > > If I access the same web service using soapUI, I can see the
> > full XML
> > > > > > > response, and the response includes the UserInfo in the soap
> > header.  So
> > > > > I
> > > > > > > am wondering, how can I access the headers in the response
from
> > the code
> > > > > > > above??
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > -----
> > > > > > When one of our products stops working, we'll blame another
vendor
> > > > > > within 24 hours.
> > > > > >
> > > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > > To unsubscribe from this list please visit:
> > > > > >
> > > > > >     http://xircles.codehaus.org/manage_email
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > -----
> > > > When one of our products stops working, we'll blame another vendor
> > > > within 24 hours.
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe from this list please visit:
> > > >
> > > >    http://xircles.codehaus.org/manage_email
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> --
> -----
> When one of our products stops working, we'll blame another vendor
> within 24 hours.
>
>
---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>




--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to