Peter Gerstbach wrote:
Hi,
I've generated with Axis-1.1 stubs for the Google-webservice and built a
working client. Then I've built an EJB session bean in JBoss were I call
the google-webservice. I use the same (copy-paste) methods in the bean
as in the axis-client but every time I invoke the bean-
no other traffic goes out during the capture, you get just the
conversation between client and server.
The output can look messy, but the soap traffic is easily readable.
Peter
--
Peter Mount
[EMAIL PROTECTED]
http://www.retep.org/
http://retep.net/
Tel: +44 (0) 1622 749439
Fax: +44 (0) 870
ormance reasons (cut
the runtime down by 70%).
However, all the other services I've written use the default serializers
because they are public, and the client app could be any target language.
Peter
--
Peter Mount
[EMAIL PROTECTED]
http://www.retep.org/
http://retep.net/
Tel: +44 (0
rg.apache.axis.client.AdminClient \
-l http://127.0.0.1:8080/retep/servlet/AxisServlet \
deploy.wsdd
Peter
--
Peter Mount
[EMAIL PROTECTED]
http://www.retep.org/
http://retep.net/
Tel: +44 (0) 1622 749439
Fax: +44 (0) 8701 361620
Mobile: +44 (0) 7838 191423
IM-MSN: [EMAIL PROTECTED]
IM-AOL/ICQ: retepworld
On Mon, 18 Aug 2003, Jakob Skovenborg wrote:
> Hej Jim
> How does that work with concurrent WebServices? Wont you get a
> MessageContext belongs to another session.
> /Jakob
It uses ThreadLocal, so it returns the current MessageContext for that
Thread.
Peter
--
Peter Mount
[EMA
