Re: Help: Element is referenced but not defined

What is your Axis2 version ? Try to use Axis2 1.6.1 version I didn't get mentioned exception for given WSDL file using Axis2 1.6.1. Thanks ! On Thu, Feb 9, 2012 at 11:52 AM, luckyjun85 wrote: > > Hi, I get this error when i try to run wsdl2java > > > java.io.IOException: Element Service is ref

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

Hi Filippo, IMO not many people use this kind of a communication pattern to establish a security context. To my experience I haven't seen this is implemented in other popular frameworks also (I maybe wrong). I think for the same reason interoperability is also not clearly defined for this kind of

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

Hi Amila, thanks for your response. So you suggest to use http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT, instead of http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue? I've already think about this, but i don't understand what are the ad

[Axis2] [Rampart] two questions

Hi, Two questions: Introduction: I use Rampart 1.5.0 and Axis2 1.5.1. The SOAP server is WCF and it works ok. The policy is embedded in the SOAP and the AXIS2 client works after engaging Rampart without specifying a policy file. The authentication is done on the SOAP server. For each c

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

How WS-SecureConversation fits in here. Similar type of tokens are supposed to be exchanged. I think Ramprt supports ws-SecureConversation. From: FILIPPO AGAZZI To: java-user@axis.apache.org Sent: Thursday, 9 February 2012, 12:03 Subject: Re: [Axis2] [Ram

Axis2 wsdl2java - cannot be resolved error using choice in extension base for a complexcontent

Hi, I get a compile error, "cannot be resolved" for code generated with Axis2 wsdl2java when the schema has an extension base with a choice. Here's the example:

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

Hi, On Thu, Feb 9, 2012 at 5:22 AM, Amila Jayasekara wrote: > Hi Filippo, > > IMO not many people use this kind of a communication pattern to > establish a security context. To my experience I haven't seen this is > implemented in other popular frameworks also (I maybe wrong). I think > for the s

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

On Thu, Feb 9, 2012 at 7:03 AM, FILIPPO AGAZZI wrote: > Hi Amila, > thanks for your response. So you suggest to use > http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT, instead of > http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue ? I've already think > about this, but i don't understand wh

Re: Help: Element is referenced but not defined

There are two things here: 1. The WSDL is not WS-I compliant because it violates the following requirement: R2105 All xsd:schema elements contained in a wsdl:types element of a DESCRIPTION MUST have a targetNamespace attribute with a valid and non-null value, UNLESS the xsd:schema element has xsd

Re: [Axis2] [Rampart] ws-trust negotiation and challenge extension support

Hi Filippo, On Thu, Feb 9, 2012 at 3:51 PM, Ruchith Fernando wrote: > On Thu, Feb 9, 2012 at 7:03 AM, FILIPPO AGAZZI > wrote: >> Hi Amila, >> thanks for your response. So you suggest to use >> http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT, instead of >> http://schemas.xmlsoap.org/ws/2005/0

Re: [Axis2] [Rampart] two questions

Hi James, On Thu, Feb 9, 2012 at 7:37 AM, James Annesley < james.annes...@infoshare-is.com> wrote: > Hi, > > ** ** > > Two questions: > > ** ** > > Introduction: > > ** ** > > I use Rampart 1.5.0 and Axis2 1.5.1. The SOAP server is WCF and it works > ok. The policy is embedded in the