Thanks for following up on this, Nandana. I tried to build from trunk so
I could try this WSDL with the current code, but the build doesn't work
for me at present (I get a failure running
org.apache.axis2.fastinfoset.FastInfosetTest).
- Dennis
Nandana Mihindukulasooriya wrote:
Yes, I agree,
Yes, I agree, I will look in to that and see whether we can handle this more
gracefully. There was an issue [1] and it is now fixed in the trunk.
thanks,
nandana
[1] - http://issues.apache.org/jira/browse/RAMPART-176
On Mon, Mar 16, 2009 at 12:37 PM, Dennis Sosnoski wrote:
> Yes, you're right
Yes, you're right that the WSDL I attached to the last email is invalid
according to the specification. It still needs to be handled in a better
way than just throwing an exception with the "can't serialize the
policy" message, though.
The same serialize problem happens with the attached versi
Hi Dennis,
If you look at the WS - SecurityPolicy specification, 8.3
TransportBinding Assertion definition, TransportToken is a mandatory element
in the TransportBinding. So I don't think this is really a bug, the policy
in the WSDL seem to be invalid.
thanks,
Nandana
[1] -
http://specs.xmls
Hi Nandana,
Yes, I understand that the Transport assertion is not contributing
anything useful in this case. AFAIK it's still valid, though, and needs
to be supported.
Is the error fixed in the current (and 1.5 branch) codebase? If not,
should I create a Jira?
Thanks,
- Dennis
Nandana
Hi Dennis,
I think the problem is with the serialization of Transport binding
assertion without a transport token. What are your security requirements ?
If you only need to have the username token , you can remove the Transport
binding assertion completely and have only the SupportingTokens as
ntent contained within this transmission.
> Date: Mon, 16 Mar 2009 11:42:29 +1300
> From: d...@sosnoski.com
> To: axis-user@ws.apache.org
> Subject: Re: Example for WS-SecurityPolicy in WSDL?
>
> Hi Nandana,
>
> I've attached one of several variations I've trie
Hi Nandana,
I've attached one of several variations I've tried which results in this
error. I did find that if I take out the TransportBinding part I don't
get the error.
Thanks for taking a look!
- Dennis
Nandana Mihindukulasooriya wrote:
Hi Dennis,
Can you post the WSDL you are
Hi Dennis,
Can you post the WSDL you are code generating against ?
thanks,
nandana
On Fri, Mar 13, 2009 at 3:09 AM, Dennis Sosnoski wrote:
> I've been trying to use the client-side code generation support for
> WS-SecurityPolicy in WSDL, with Axis2 1.4.1 and Rampart 1.4. I've tried
> se
Hi Alexis,
Yes, I'd seen your pleas for a working example when I checked my Axis2
mail folder before sending this one. I figured I'd give another try with
a more direct subject line in the hope that somebody might pick up on it.
Since the policy-in-WSDL support is supposed to be one of the ne
similar question here [1], some examples would be appreciated.
Thanks!
[1] http://markmail.org/thread/qsn6t4qwepoialud
Alexis
On Thu, Mar 12, 2009 at 2:39 PM, Dennis Sosnoski wrote:
> I've been trying to use the client-side code generation support for
> WS-SecurityPolicy in WSDL, with Axis2 1
I've been trying to use the client-side code generation support for
WS-SecurityPolicy in WSDL, with Axis2 1.4.1 and Rampart 1.4. I've tried
several variations of where I place the policy in the WSDL, including
using reference and embedding it directly in the , but
each time I get:
[java] Exce
12 matches
Mail list logo
