I can;t believe that this WSDL actually works in Axis 1. You have a fundamental error.
The binding references a portType called TestServiceSoap, which does not exist. Your portType is called PaymentServiceSoap. Anne On 7/4/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
It may work in Axis 1, but that doesn't mean it is correct. Axis1 is pretty lax about enforcing certain rules. e.g., 1- Fault messages must always be defined with a document/literal binding 2- A document/literal message must always reference an element, not a type. You must define elements for each of your three super exception types, and reference those elements rather than the complexTypes. Anne On 7/4/06, Atanas Ianev <[EMAIL PROTECTED]> wrote: > This is right! > But those types are defined as "complexType" in the XSD and are used as > super types for the rest of the exceptions. As mentioned this is working > already with Axis v1.4. The question was, why the defined package is > ignored by the WSDL2Java tool provided with Axis2 v1.0 and why there are > method calls in the "Stub"-class, which are not existing? > > Thank you! > Atanas. > > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 04. Juli 2006 17:48 > To: axis-user@ws.apache.org > Subject: Re: Axis2 WSDL2Java generator > > Could you also post the XSD file? > > There are some mistakes in the WSDL, though. A couple of your exception > messages are defined wrong -- they reference types rather than elements. > - objectNotFoundException > - duplicateObjectException > - paymentServiceException > > Anne > > On 7/4/06, Atanas Ianev <[EMAIL PROTECTED]> wrote: > > Hi, Ajith! > > > > Thank you for the answer! > > The strange thing is, when I use Axis v1.4 it works just fine. All the > > > types are created correctly and the package is also set to the defined > > > one. > > > > Please, find attached the WSDL file. There is also an additional XSD > > file for the defined types, which is currently in production and I > > could hardly believe there is something wrong on it. > > > > I am pretty confused by the fact that it works with Axis v1.4, but not > > > with Axis2 v1.0. Probably there are some differences in the way, how > > the WSDL and XSD are handled. Further, it is a .NET web service. > > > > I will be very glad, if you will be able to help me. > > Thank you! > > Atanas > > > > -----Original Message----- > > From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] > > Sent: Dienstag, 04. Juli 2006 15:56 > > To: axis-user@ws.apache.org > > Subject: Re: Axis2 WSDL2Java generator > > > > Hi, > > This is a typical error that happens when the WSDL is having > > unresolvable references. Can you please post the WSDL ? > > > > Ajith > > > > On 7/3/06, Atanas Ianev <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > I need to implement a WS client and want to use strong types defined > > > > in a XSD, but I came to the following problems: > > > > > > > > > > > > 1. The namespace deifined in the web service looks like this > > > "test.ws.com/ver2". When I execute the WSDL2Java tool with specified > > > > package "test.ws.com" it gets ignored and the created classes > > > become the package as specified in the namespace. Of course it comes > > > > to a compiler error, because of the invalid format. > > > > > > 2. In the "stub" class the following method is called, which > > does not > > > exist; org.apache.axiom.om.OMElement.newXMLStreamReader() > > > > > > This I found is probably some version mismatch. The method is now > > > called getXMLStreamReader. > > > > > > 3. Again in the "stub" class the method > > > "org.apache.axiom.om.OMElement.Factory.parse" is called in a static > > > way and could not be found in the provided packages. > > > > > > > > > > > > Could you, please, point me to some solution or alternative? > > > > > > I use Axis2 v1.0 with databinding name "xmlbeans". > > > > > > > > > > > > Thank you in advance. > > > > > > > > > > > > Br, > > > > > > Atanas > > > > > > > > > > > > -- > > Ajith Ranabahu > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
