Follow-up, I figured this out. I need to specify the -W option since I
was using doc/literal and not wrapped. Works fine now.
markg
-Original Message-
From: Griffin, Mark
Sent: Friday, November 18, 2005 1:30 PM
To: 'axis-user@ws.apache.org'
Subject: WSDL2Java with DocumentLiteral Issue
No. wrapped is not a valid option for the WSDL style attribute. The WSDL is correct.On 11/18/05, Ebert, Chris
[EMAIL PROTECTED] wrote:I think you need to say 'wrapped' in the binding instead of 'document'.
Chris-Original Message-From: Greg Adams [mailto:[EMAIL PROTECTED]]Sent: Friday,
I suspect that Axis's ability to recognize the wrapped convention isn't
sophisticated enough to deal with header parts. Please submit an
enhancement request.
AnneOn 11/18/05, Greg Adams [EMAIL PROTECTED] wrote:
Well, what I mean is that the deploy.wsdd created by WSDL2Java from the WSDL below has
Is there any difference in case the Web Services are made out of Session
EJBs? Or does WSS4J work the same way in that case?
Thanks!
Michael
you may want to look at WSS4J and UsernameTokens. they're pretty
straight-forward as long as your client can support them. they are part of
the
by Web Services are made out of Session EJBs you mean you have Session
EJBs that expose a SOAP-over-HTTP interface? WSS4J uses 2 handlers, one
client-side and one server-side (WSDoAllSender (client) and
WSDoAllReceiver (server)) which plug into the handler chain supported by
Axis to intercept
