Re: [AXIS2] WSDL2Java: SchemaLocation and relative path / circular im ports
Oliver, Please log a bug report and upload the tar. So that we can track the problem. thanks, dims On 8/25/06, Oliver Grafe <[EMAIL PROTECTED]> wrote: Hi! I'm having problems to use Axis2 WSDL2Java with some test WSDL and schema files I made, see attached files. Some of the schemas are importing each other, I think that is confusing WSDL2Java. Command for code generation: C:\wsdltest>java org.apache.axis2.wsdl.WSDL2Java -uri ord.wsdl > error.txt 2>&1 error.txt: Retrieving schema at './xsd/ord.xsd', relative to 'file:/C:/wsdltest/'. Retrieving schema at './prod1.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Retrieving schema at './prod2.xsd', relative to 'file:/C:/wsdltest/xsd/prod1.xsd'. Retrieving schema at './prod1.xsd', relative to 'file:/C:/wsdltest/xsd/prod2.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/prod2.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/prod1.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Retrieving schema at './prod2.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Exception in thread "main" java.lang.StackOverflowError at java.util.ArrayList.get(Unknown Source) at sun.misc.URLClassPath.getLoader(Unknown Source) at sun.misc.URLClassPath.findResource(Unknown Source) at java.net.URLClassLoader$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findResource(Unknown Source) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.ClassLoader.getResourceAsStream(Unknown Source) at javax.xml.parsers.SecuritySupport$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.xml.parsers.SecuritySupport.getResourceAsStream(Unknown Source) at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source) at javax.xml.parsers.FactoryFinder.find(Unknown Source) at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:213) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:53) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:255) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:217) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:53) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:255) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:217) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) [... last 6 lines repeated over and over] Is this a bug or am I doing something wrong here? BTW, these files are working with Axis 1.4 wsdl2java. And according to XMLSpy my wsdl and schemas are valid, but that doesn't mean anything. Thanks you very much, Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] WSDL2Java: SchemaLocation and relative path / circular im ports
Hi! I'm having problems to use Axis2 WSDL2Java with some test WSDL and schema files I made, see attached files. Some of the schemas are importing each other, I think that is confusing WSDL2Java. Command for code generation: C:\wsdltest>java org.apache.axis2.wsdl.WSDL2Java -uri ord.wsdl > error.txt 2>&1 error.txt: Retrieving schema at './xsd/ord.xsd', relative to 'file:/C:/wsdltest/'. Retrieving schema at './prod1.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Retrieving schema at './prod2.xsd', relative to 'file:/C:/wsdltest/xsd/prod1.xsd'. Retrieving schema at './prod1.xsd', relative to 'file:/C:/wsdltest/xsd/prod2.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/prod2.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/prod1.xsd'. Retrieving schema at './common.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Retrieving schema at './prod2.xsd', relative to 'file:/C:/wsdltest/xsd/ord.xsd'. Exception in thread "main" java.lang.StackOverflowError at java.util.ArrayList.get(Unknown Source) at sun.misc.URLClassPath.getLoader(Unknown Source) at sun.misc.URLClassPath.findResource(Unknown Source) at java.net.URLClassLoader$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findResource(Unknown Source) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.ClassLoader.getResourceAsStream(Unknown Source) at javax.xml.parsers.SecuritySupport$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.xml.parsers.SecuritySupport.getResourceAsStream(Unknown Source) at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source) at javax.xml.parsers.FactoryFinder.find(Unknown Source) at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:213) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:53) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:255) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:217) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:53) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:255) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja va:217) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja va:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1 708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil der.java:126) [... last 6 lines repeated over and over] Is this a bug or am I doing something wrong here? BTW, these files are working with Axis 1.4 wsdl2java. And according to XMLSpy my wsdl and schemas are valid, but that doesn't mean anything. Thanks you very much, Oliver wsdl_import.tar.gz Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis vs. Axis2 handling of operation name and top level element (bugs?)
Hi, folks. I recently noticed a some strange discrepancies in how Axis handles the operation name versus how Axis2 does. I'm not sure if these are bugs or just a failure in my understanding. Basically, when I have a particular WSDL, as follows: http://www.c-corp.com/wsdl/2004-10-01/F"; xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F"; xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c"; xmlns:F="http://www.dummy-temp-address"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns="http://schemas.xmlsoap.org/wsdl/";> http://www.c-corp.com/wsdl/2004-10-01/F";> http://www.dummy-temp-address"; schemaLocation="F.xsd"/> http://www.c-corp.com/wsdl/2004-10-01/c";> F Port Type F Soap Binding http://schemas.xmlsoap.org/soap/http"/> F Web Service http://localhost:8080/axis/services/FService"/> My WSDL references the following XML schema: http://www.dummy-temp-address"; xmlns="http://www.dummy-temp-address"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation"; elementFormDefault="unqualified" attributeFormDefault="unqualified" version="DRAFT"> When I use my client code to create and send this message in Axis 1.4, I get a message that looks like this: POST /axis/services/FService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: 127.0.0.1 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 10458 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" xmlns:cauth="http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" xmlns:cauth="http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://www.c-corp.com/wsdl/2004-10-01/f"; xmlns:ns1="http://www.c-corp.com/wsdl/2004-10-01/f";> http://www.dummy-temp-address"; xmlns:ns2="http://www.dummy-temp-address";> QSenderOrganizationID QSenderCenterID 1 435 20040625 201225 -0400 20040625 221222 -0400 1234 1 4 accident However, when I do the same thing in the current Axis2 nightly build (XMLBeans binding), I get this: POST /axis2/services/FService HTTP/1.1 SOAPAction: acceptFEventAction User-Agent: Axis2 Host: 127.0.0.1 Content-Length: 8785 Content-Type: text/xml; charset=UTF-8 http://schemas.xmlsoap.org/soap/envelope/";>http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://www.dummy-temp-address";> QSenderOrganizationID QSenderCenterID 1 435 20040625 201225 -0400 20040625 221222 -0400 1234 1 4 accident There are several issues here: 1) The Axis2 version of the generated XML does not seem to include the 'acceptFEvent' element around the top-level message binding, which the Axis 1.4 did. I recall from discussions on the list that this seems to be expected behavior (something about the signature for each operation needing to be different, and sometimes having to use the SOAPAction field to disambiguate). However, I am a bit astounded at such a significant difference appearing between versions. It seems that no messages that were accepted by Axis 1.4 could be accepted by Axis2, or vice versa, for the same WSDL! I am at a loss to explain why I haven't heard more people complaining about this. Which version of the SOAP message is correct, and under what conditions? Is there a way to get both versions of Axis to do one or the other behavior (preferably the correct one)? We were expecting t
Axis vs. Axis2 handling of operation name and top level element (bugs?)
Hi, folks. I recently noticed a some strange discrepancies in how Axis handles the operation name versus how Axis2 does. I'm not sure if these are bugs or just a failure in my understanding. Basically, when I have a particular WSDL, as follows: http://www.c-corp.com/wsdl/2004-10-01/F"; xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F"; xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c"; xmlns:F="http://www.dummy-temp-address"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns="http://schemas.xmlsoap.org/wsdl/";> http://www.c-corp.com/wsdl/2004-10-01/F";> http://www.dummy-temp-address"; schemaLocation="F.xsd"/> http://www.c-corp.com/wsdl/2004-10-01/c";> F Port Type F Soap Binding http://schemas.xmlsoap.org/soap/http"/> F Web Service http://localhost:8080/axis/services/FService"/> My WSDL references the following XML schema: http://www.dummy-temp-address"; xmlns="http://www.dummy-temp-address"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation"; elementFormDefault="unqualified" attributeFormDefault="unqualified" version="DRAFT"> When I use my client code to create and send this message in Axis 1.4, I get a message that looks like this: POST /axis/services/FService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: 127.0.0.1 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 10458 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" xmlns:cauth="http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" xmlns:cauth="http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://www.c-corp.com/wsdl/2004-10-01/f"; xmlns:ns1="http://www.c-corp.com/wsdl/2004-10-01/f";> http://www.dummy-temp-address"; xmlns:ns2="http://www.dummy-temp-address";> QSenderOrganizationID QSenderCenterID 1 435 20040625 201225 -0400 20040625 221222 -0400 1234 1 4 accident However, when I do the same thing in the current Axis2 nightly build (XMLBeans binding), I get this: POST /axis2/services/FService HTTP/1.1 SOAPAction: acceptFEventAction User-Agent: Axis2 Host: 127.0.0.1 Content-Length: 8785 Content-Type: text/xml; charset=UTF-8 http://schemas.xmlsoap.org/soap/envelope/";>http://www.c-corp.com/wsdl/2004-10-01/c";>adminhttp://www.dummy-temp-address";> QSenderOrganizationID QSenderCenterID 1 435 20040625 201225 -0400 20040625 221222 -0400 1234 1 4 accident There are several issues here: 1) The Axis2 version of the generated XML does not seem to include the 'acceptFEvent' element around the top-level message binding, which the Axis 1.4 did. I recall from discussions on the list that this seems to be expected behavior (something about the signature for each operation needing to be different, and sometimes having to use the SOAPAction field to disambiguate). However, I am a bit astounded at such a significant difference appearing between versions. It seems that no messages that were accepted by Axis 1.4 could be accepted by Axis2, or vice versa, for the same WSDL! I am at a loss to explain why I haven't heard more people complaining about this. Which version of the SOAP message is correct, and under what conditions? Is there a way to get both versions of Axis to do one or the other behavior (preferably the correct one)? We were expecting t
RE: How could generate *only* deploy.wsdd?
You need to create the wsdd by hand and then use the deploy task below to deploy it. There may be a wsdd generator but I've never seen one. - Doug -Original Message- From: Angel Cervera Claudio [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 5:51 AM To: axis-user@ws.apache.org Subject: Re: How could generate *only* deploy.wsdd? Thanks bell, but i want _generate_ wsdd, no deploy them. I generated wsdl using axis-java2wsdl, but wsdd it's not generated with this task (it's this correct or i'm wrong?). Bell, Douglas wrote: > Hi Angel, > > I'm taking a guess that you are asking how to deploy the services > > > I do it via an ant task. You can also do it via the command line: > org.apache.axis.utils.Admin -Dserver=[PATH_TO_YOUR_WSDL] > > If you use the template below just make sure you have axis-ant.jar on your > classpath. > > > > > >quiet="true"/> >failonerror="true" dir="[OUTPUT_DIRECTORY_PROBABLY_WEB-INF]"> > > > > ... > > > > > Hope this helps, > > Doug > > -Original Message- > From: Angel Cervera Claudio [mailto:[EMAIL PROTECTED] > Sent: Thu 8/24/2006 4:07 AM > To: axis-user@ws.apache.org > Cc: > Subject: How could generate *only* deploy.wsdd? > > > > Hello people. > > I'm developing a web service. > I have generate wsdl using axis-java2wsdl. > Now i need generate a deploy.wsdd to deploy service. > If i use axis-wsdl2java, task generate deploy.wsdd and client/server > stub. > How could generate *only* deploy.wsdd? > > Thanks and apologies for my poor english. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Ángel Cervera Claudio Desarrollos j2ee web: http://www.acervera.com email: [EMAIL PROTECTED] tlf: 984050494 / 985308170 / 670819234 fax: 985308228 Avda. de la Argentina, 132 33213 - Gijón (Asturias) - Spain - Mensajería - msn: [EMAIL PROTECTED] yahoo: angelcervera aol: angelcervera jabber: angelcervera en jabber.org google talk: angelcervera skype: angelcervera Este mensaje y cualquier documento adjunto que lleve consigo es sólo para la persona o compañía a la que va dirigido y puede contener información privilegiada, confidencial o cuya revelación o uso esté prohibido. Si el receptor de esta transmisión no es la persona a quien iba dirigida, o el empleado o agente encargado de hacer llegar dicho material al receptor previsto, se le notifica que cualquier uso, forma de reproducción, difusión, copia, revelación, modificación, distribución y/o publicación de este mensaje o sus documentos adjuntos por cualquier otro que no sea su destinatario previsto está estrictamente prohibido por el remitente. Si ha recibido esto por error, por favor, devuélvalo al remitente y destruya el mensaje y/o las copias que pueda haber en su posesión. This message and any attachments to it is intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorized use. If the recipient of this transmission is not the intended recipient, or the employee or agent responsible for delivering such materials to the intended recipient, you are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by its intended recipient is strictly prohibited by the sender. If you have received it in error, please return it to the sender and destroy the message and/or copies in your possession. - 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]
Re: [axis2] NullPointerException with WSDL2Java
If it still shows that warning with latest nightly, please log a bug.
thanks,
dims
On 8/25/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Are you sure?
You might want to delete everything and start again clean.
Anne
On 8/25/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
>
>
> oups sorry for the typo !
> once fixed I still have my warning:
>
> Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
> Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
>
> I can't understand why
> any idea?
>
> Olivier
>
>
>
>
> "Anne Thomas Manes"
> <[EMAIL PROTECTED]>
> 25/08/2006 14:55 To: axis-user@ws.apache.org
> Please respond to axis-usercc:
>bcc:
>Subject: Re: [axis2]
NullPointerException with WSDL2Java
>
>
>
>
>
>
> Olivier,
>
> You have an extra ">" in your schema declaration that occurs before
> you declare the targetNamespace in your schema:
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <-- error
>xmlns="http://www.mynamespace.net";
>targetNamespace="http://www.mynamespace.net";>
>
> Anne
>
> On 8/24/06, CHAPELLIERE Olivier ORANGE-FT
> <[EMAIL PROTECTED]> wrote:
> >
> >
> > Thanks for your help Anne. As recommended I opened a bug request yesterday.
> > It is already fixed, so I tried latest nigthly build (08/24/2006).
> > But now I get warnings (see below) at client code generation.
> >
> > Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> > WARNING: Type {urn:myNamespace}myStatus_type0 missing!
> > Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> > WARNING: Type {urn:myNamespace}myStatus_type0 missing!
> >
> > and here is my new wsdl file:
> >
> >
> > http://schemas.xmlsoap.org/wsdl/";
> > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > targetNamespace="http://www.mynamespace.net";
> > xmlns="http://www.mynamespace.net";>
> >
> >
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> > xmlns="http://www.mynamespace.net";
> > targetNamespace="http://www.mynamespace.net";>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > http://schemas.xmlsoap.org/soap/http"/>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > http://localhost:8080/axis2/services/myWebServices"/>
> >
> >
> >
> >
> > my XMl schema seems valid so I can't understand why
> >
> > Olivier
> >
> >
> >
> > "Anne Thomas Manes"
> > <[EMAIL PROTECTED]>
> > 23/08/2006 21:02 To: axis-user@ws.apache.org
> > Please respond to axis-usercc:
> >bcc:
> >Subject: Re: [axis2]
NullPointerException with WSDL2Java
> >
> >
> >
> >
> >
> >
> > My guess is that the error is caused by the fact that you use the same
> > input message for both operations. Axis (and WS-I Basic Profile)
> > requires that each operation have a unique message signature (which is
> > the QName of the child element of the ). Both or your
> > operations use the same signature: "myNamespace"}myMethod.
> >
> > The error might also be caused by the fact that "myNamespace" is not a
> > valid URI. A namespace must be a valid URI.
> >
> > To fix your problem:
> > 1. Change the target namespace to a valid URI (e.g., "urn: ")
> > 2. Define unique input elements for your two operations
> >
> > Meanwhile, WSDL2Java should not generate an NPE, so please also file a JIRA.
> >
> > Anne
> >
> > On 8/23/06, CHAPELLIERE Olivier ORANGE-FT
> > <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi everybody,
> > >
> > > I have a NullPointerException while generating client code for a WSDL.
> > > I tried axis2 version 1.0 and nightly build of august 22th 2006 and I
always have the exception.
> > >
> > > My command line is:
> > > WSDL2Java.sh -uri bug.wsdl -o gen
> > >
> > > My wsdl file is the following:
> > > 1
> > > 2 > > 3xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > 4
xmlns:wsdlsoap="http://sch
RE: Java classes generated by wsdl2java don't compile
Oops. Thanks for catching that! Derek > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Friday, August 25, 2006 11:53 AM > To: axis-user@ws.apache.org; [EMAIL PROTECTED] > Subject: Re: Java classes generated by wsdl2java don't compile > > > Because this is an Axis 1.x issue, please file the bug in the > Axis 1 system: https://issues.apache.org/jira/browse/axis > > Anne > > On 8/25/06, Derek <[EMAIL PROTECTED]> wrote: > > > > WSDL2Java should either detect errors in the files, or it should > > produce valid code. Clearly in this case it is doing > neither. Please > > file a JIRA at http://issues.apache.org/jira/browse/AXIS2, > and include > > your WSDL and XSDs, as well as the command line that you > are using to > > invoke WSDL2Java. > > > > Thanks. > > > > Derek > > > > > -Original Message- > > > From: Jose Manuel Valladares Pernas [mailto:[EMAIL PROTECTED] > > > Sent: Friday, August 25, 2006 9:15 AM > > > To: axis-user@ws.apache.org > > > Subject: Java classes generated by wsdl2java don't compile > > > > > > > > > Hello, > > > I have an wsdl that imports several xsd schemas and I > > > used an ant task with WSDL2Java to produce the corresponding java > > > clases. > > > > > > I am working with axis 1.4 and java jsdk 1.5.0_06. > > > > > > WSDL2Java produces the classes and no errors. But some > > > of the generated classes don't compile. > > > > > > One of the classes has 2 constructor methods that are > > > the same. Other classes that inherite from some parent > classes have > > > the constructor parameters in the wrong order. > > > > > > If you want I can send you the wsdl and the xsd files. > > > They seem to be correct as they come from the OTA pecification. > > > > > > Have you seen this happening before? > > > Any hint? > > > > > > If you need more information, please, let me know. > > > > > > Thank you very much for your help, > > >Manuel Valladares > > > > > > - > > > - Jose Manuel Valladares Pernas > > > - [EMAIL PROTECTED] > > > - [EMAIL PROTECTED] > > > - > > > > > > __ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > http://mail.yahoo.com > > > > > > > > > > - > > > 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]
Re: [axis2] NullPointerException with WSDL2Java
Are you sure?
You might want to delete everything and start again clean.
Anne
On 8/25/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
oups sorry for the typo !
once fixed I still have my warning:
Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
I can't understand why
any idea?
Olivier
"Anne Thomas Manes"
<[EMAIL PROTECTED]>
25/08/2006 14:55 To: axis-user@ws.apache.org
Please respond to axis-usercc:
bcc:
Subject: Re: [axis2]
NullPointerException with WSDL2Java
Olivier,
You have an extra ">" in your schema declaration that occurs before
you declare the targetNamespace in your schema:
http://www.w3.org/2001/XMLSchema";> <-- error
xmlns="http://www.mynamespace.net";
targetNamespace="http://www.mynamespace.net";>
Anne
On 8/24/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
>
>
> Thanks for your help Anne. As recommended I opened a bug request yesterday.
> It is already fixed, so I tried latest nigthly build (08/24/2006).
> But now I get warnings (see below) at client code generation.
>
> Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {urn:myNamespace}myStatus_type0 missing!
> Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {urn:myNamespace}myStatus_type0 missing!
>
> and here is my new wsdl file:
>
>
> http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://www.mynamespace.net";
> xmlns="http://www.mynamespace.net";>
>
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> xmlns="http://www.mynamespace.net";
> targetNamespace="http://www.mynamespace.net";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
> http://localhost:8080/axis2/services/myWebServices"/>
>
>
>
>
> my XMl schema seems valid so I can't understand why
>
> Olivier
>
>
>
> "Anne Thomas Manes"
> <[EMAIL PROTECTED]>
> 23/08/2006 21:02 To: axis-user@ws.apache.org
> Please respond to axis-usercc:
>bcc:
>Subject: Re: [axis2]
NullPointerException with WSDL2Java
>
>
>
>
>
>
> My guess is that the error is caused by the fact that you use the same
> input message for both operations. Axis (and WS-I Basic Profile)
> requires that each operation have a unique message signature (which is
> the QName of the child element of the ). Both or your
> operations use the same signature: "myNamespace"}myMethod.
>
> The error might also be caused by the fact that "myNamespace" is not a
> valid URI. A namespace must be a valid URI.
>
> To fix your problem:
> 1. Change the target namespace to a valid URI (e.g., "urn: ")
> 2. Define unique input elements for your two operations
>
> Meanwhile, WSDL2Java should not generate an NPE, so please also file a JIRA.
>
> Anne
>
> On 8/23/06, CHAPELLIERE Olivier ORANGE-FT
> <[EMAIL PROTECTED]> wrote:
> >
> > Hi everybody,
> >
> > I have a NullPointerException while generating client code for a WSDL.
> > I tried axis2 version 1.0 and nightly build of august 22th 2006 and I
always have the exception.
> >
> > My command line is:
> > WSDL2Java.sh -uri bug.wsdl -o gen
> >
> > My wsdl file is the following:
> > 1
> > 2 > 3xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > 4
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> > 5xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > 6targetNamespace="mynamespace">
> > 7
> > 8
> > 9 > 10 targetNamespace="mynamespace"
> > 11 xmlns:mynamespace="mynamespace"
> > 12 xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> > 13
> > 14
> > 15
> >
Re: WS-routing
Apache WSS4J is a sample Axis handler. (It implements support for WS-Security.)
Anne
On 8/25/06, Reynir Hubner <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Anne,
thanx for the reply.
Yes I'm dealing with an old service, and I'm hoping it will be updated.
I also realized that I have to add some ws-routing header too, I was
thinking I might be able to put that in somehow.
How does one add a handler ? wich interfaces do I need to implement, are
there any simple handlers that I can copy to fake this behaviour ?
thanx again...
- -reynir
Anne Thomas Manes wrote:
> You must be dealing with an old service, because WS-Routing was
> superceded by WS-Addressing 3 years ago.
>
> In any case, what you need to do is add a handler to add and process
> the wsrp header. (Note that the return message is telling you that you
> need to include a WS-Routing header in your input message, so it's not
> just a matter of ignoring the header.)
>
> Anne
>
> On 8/24/06, Reynir Hubner <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I am getting the following error when trying to access a remote service
> (that I am not in control of), that uses WS-routing.
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
> faultSubcode:
> faultString: Did not understand "MustUnderstand" header(s):
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:
> at
>
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
>
>
> this is because I get this kind of header, with the mustUnderstand flag
> set:
>
>
> http://schemas.xmlsoap.org/soap/actor/next";
> soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp";>
> http://schemas.xmlsoap.org/soap/fault
> uuid:9e6d818f-2b6e-4689-9877-9b855f400b27
>
> 701
> WS-Routing Header Required
>
>
>
>
> And obviously Axis does not understand the wsrp headres, as it does not
> understand WS-routing standard.
>
>
> Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
> Does anyone by any change have implementation for WS-routing ?
> Can anyone explain in short how I would implement WS-routing handler (or
> show a sample of any simple handler) ?
>
> thank you very much.
> -reynir
>
>>
- -
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]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE7yle19KgIQihNwgRApPpAJ98tMmSyNimSMveH31RSnk5H7T/mwCg4v8w
hKDyHltOzXRbSvS0AGvXl/U=
=wPhD
-END PGP SIGNATURE-
-
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]
Re: Java classes generated by wsdl2java don't compile
Because this is an Axis 1.x issue, please file the bug in the Axis 1 system: https://issues.apache.org/jira/browse/axis Anne On 8/25/06, Derek <[EMAIL PROTECTED]> wrote: WSDL2Java should either detect errors in the files, or it should produce valid code. Clearly in this case it is doing neither. Please file a JIRA at http://issues.apache.org/jira/browse/AXIS2, and include your WSDL and XSDs, as well as the command line that you are using to invoke WSDL2Java. Thanks. Derek > -Original Message- > From: Jose Manuel Valladares Pernas [mailto:[EMAIL PROTECTED] > Sent: Friday, August 25, 2006 9:15 AM > To: axis-user@ws.apache.org > Subject: Java classes generated by wsdl2java don't compile > > > Hello, > I have an wsdl that imports several xsd schemas and I > used an ant task with WSDL2Java to produce the > corresponding java clases. > > I am working with axis 1.4 and java jsdk 1.5.0_06. > > WSDL2Java produces the classes and no errors. But some > of the generated classes don't compile. > > One of the classes has 2 constructor methods that are > the same. Other classes that inherite from some parent > classes have the constructor parameters in the wrong > order. > > If you want I can send you the wsdl and the xsd files. > They seem to be correct as they come from the OTA > pecification. > > Have you seen this happening before? > Any hint? > > If you need more information, please, let me know. > > Thank you very much for your help, >Manuel Valladares > > - > - Jose Manuel Valladares Pernas > - [EMAIL PROTECTED] > - [EMAIL PROTECTED] > - > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > 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]
Re: Axis- ns1:BadArguements
Agreed -- it would be nice if Axis provided a little more reason in the element. Please file a JIRA requesting this enhancement. As for solving you immediate problem, I suggest you capture the generated input SOAP message and discover for yourself where the problem lies. Anne On 8/25/06, Daniel Bridenbecker <[EMAIL PROTECTED]> wrote: I have a custom Deserializer (i.e. extends DeserializerImpl) and it throws a nice message about what is wrong, but the fault returned from the server is: http://www.w3.org/2003/05/soap-envelope"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> soapenv:Sender http://www.w3.org/2003/05/soap-rpc";> ns1:BadArguments string http://xml.apache.org/axis/";> BRIDEN-DELL2 Where this does tell me that one of the arguments to the method call is bad, it doesn't tell me something like "Invalid date format". It doesn't even tell which argument is bad. Does anyone know how I could get Axis to use the message in the exception? Thanks. Daniel Bridenbecker Solution Engineering, Inc. 425-402-3690 [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]
Axis- ns1:BadArguements
I have a custom Deserializer (i.e. extends DeserializerImpl) and it throws a nice message about what is wrong, but the fault returned from the server is: http://www.w3.org/2003/05/soap-envelope"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> soapenv:Sender http://www.w3.org/2003/05/soap-rpc";> ns1:BadArguments string http://xml.apache.org/axis/";> BRIDEN-DELL2 Where this does tell me that one of the arguments to the method call is bad, it doesn't tell me something like "Invalid date format". It doesn't even tell which argument is bad. Does anyone know how I could get Axis to use the message in the exception? Thanks. Daniel Bridenbecker Solution Engineering, Inc. 425-402-3690 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Java classes generated by wsdl2java don't compile
WSDL2Java should either detect errors in the files, or it should produce valid code. Clearly in this case it is doing neither. Please file a JIRA at http://issues.apache.org/jira/browse/AXIS2, and include your WSDL and XSDs, as well as the command line that you are using to invoke WSDL2Java. Thanks. Derek > -Original Message- > From: Jose Manuel Valladares Pernas [mailto:[EMAIL PROTECTED] > Sent: Friday, August 25, 2006 9:15 AM > To: axis-user@ws.apache.org > Subject: Java classes generated by wsdl2java don't compile > > > Hello, > I have an wsdl that imports several xsd schemas and I > used an ant task with WSDL2Java to produce the > corresponding java clases. > > I am working with axis 1.4 and java jsdk 1.5.0_06. > > WSDL2Java produces the classes and no errors. But some > of the generated classes don't compile. > > One of the classes has 2 constructor methods that are > the same. Other classes that inherite from some parent > classes have the constructor parameters in the wrong > order. > > If you want I can send you the wsdl and the xsd files. > They seem to be correct as they come from the OTA > pecification. > > Have you seen this happening before? > Any hint? > > If you need more information, please, let me know. > > Thank you very much for your help, >Manuel Valladares > > - > - Jose Manuel Valladares Pernas > - [EMAIL PROTECTED] > - [EMAIL PROTECTED] > - > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > 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]
[axis2]
The services.xml file has the signaturePropFile attribute set as follows: sec.properties And it is in the .aar file alongside the keystore (no package heirarchy in the path). Yet I get a server side error saying that the sec.properties file cannot be loaded. This error goes away if I jar up the file and drop it in the axis2/WEB-INF/lib, but I would rather not do that, I would rather the file be added to a given service's archive. How can I get the server side to see the file without having it in the global lib? Thanks, Alan J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MTOM Client
There is a slight bug in the code, which prevents this property from working correct. I've already done the fix in my local repo. Will take some time to make it to the SVN head. Hopefully by next week. Will send a mail to this thread when it's commited. ~Thilina On 8/25/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote: Does this property not work in the 1.0 release? Roshan Punnoose Phone: 301-497-6039 -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 5:23 PM To: axis-user@ws.apache.org Subject: Re: MTOM Client Oops, I meant: options.setProperty(org.apache.axis2.Constants.Configuration.CACHE_ATTAC HMENTS, Boolean.TRUE); On 8/24/06, robert lazarski <[EMAIL PROTECTED]> wrote: > Try: > > options.setProperty(org.apache.axis2.Constants.Configuration.ENABLE_MTOM , >Boolean.TRUE); > > Make sure your using the latest nightlies: > > http://people.apache.org/dist/axis2/nightly/ > > HTH, > Robert > http://www.braziloutsource.com > > On 8/24/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi, > > > > > > > > On the web page for Axis 2/MTOM, I saw that I could use the file system to > > cache large attachments being transferred; however, I only saw the server > > axis config file. How do I setup the client to do the same thing? Do I have > > to set it in the options? > > > > > > > > Server config: > > > > > > > > true > > temp > > directory > > 4000 > > . > > . > > > > > > > > > > > > Thanks! > > > > > > > > Roshan Punnoose > > > > Phone: 301-497-6039 > > > > > > - > > 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] -- "May the SourcE be with u" http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: where to put encryptionPropFile when using rampart encryption
Hi Wei, Client side : classpath Serverside : Service archive (.aar file) In the next release or Rampart we will be changing Rampart to look in the META-INF directory of the service archive to find the keystore file. As of now you can drop the file anywhere in the archive and specify the appropriate path in the .properties file. If you look in any of the generated service archives (e.g. sample05) then you can see these files. Thanks, Ruchith On 8/23/06, Wei Zhang <[EMAIL PROTECTED]> wrote: Hello, I am learning how to encrypt SOAP message using rampart. I followed the instructions of rampart tutorial (rampart-tute.zip). The sample01 and sample02 passed with Ruchith's help. Now I turned to sample05 for the encryption. The service container used is Tomcat. I was wondering where to put the encyptionPropFile (client.properties) and keystore file (client.jks) on both server and client sides? I mean how the server and the client can find the files at run time. Thank you! - Wei -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with encryption/signature using rampart module
Hi, Please add false in all server side and client side configurations (Both inflow and outflow). Thanks, ruchith On 8/24/06, Wei Zhang <[EMAIL PROTECTED]> wrote: Hello, I am trying to set up a sample signature/encryption example using rampart. I am running Tomcat-5.5.17 and Axis2 under CentOS4. I downloaded rampart-tute.zip and passed the first three samples. Unfortunately, I got error message for the sample04 and sample05. Could somebody help me find out the problem? Thank you in advance. Below is what I have when I ran the sample04 and sampe05: [EMAIL PROTECTED]:temp_client]$java org.apache.rampart.samples.sample04.Client http://localhost:8080/axis2/services/sample04 ../client_repositories/sample04 Exception in thread "main" org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: got a SC element, but no stored SV; nested exception is: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: got a SC element, but no stored SV at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:109) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:75) at org.apache.axis2.engine.Phase.invoke(Phase.java:381) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:355) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399) at org.apache.rampart.samples.sample05.Client.main(Unknown Source) Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: got a SC element, but no stored SV at org.apache.ws.security.handler.WSHandler.checkSignatureConfirmation(WSHandler.java:294) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:291) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:100) ... 9 more [EMAIL PROTECTED]:temp_client]$java org.apache.rampart.samples.sample05.Client http://localhost:8080/axis2/services/sample05 ../client_repositories/sample05 Exception in thread "main" org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: got a SC element, but no stored SV; nested exception is: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: got a SC element, but no stored SV at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:109) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:75) at org.apache.axis2.engine.Phase.invoke(Phase.java:381) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:355) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399) at org.apache.rampart.samples.sample05.Client.main(Unknown Source) Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: got a SC element, but no stored SV at org.apache.ws.security.handler.WSHandler.checkSignatureConfirmation(WSHandler.java:294) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:291) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:100) ... 9 more [EMAIL PROTECTED]:temp_client]$java org.apache.rampart.samples.sample05.Client http://localhost:8080/axis2/services/sample05 ../client_repositories/sample05 - We i Zhang -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-routing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Anne,
thanx for the reply.
Yes I'm dealing with an old service, and I'm hoping it will be updated.
I also realized that I have to add some ws-routing header too, I was
thinking I might be able to put that in somehow.
How does one add a handler ? wich interfaces do I need to implement, are
there any simple handlers that I can copy to fake this behaviour ?
thanx again...
- -reynir
Anne Thomas Manes wrote:
> You must be dealing with an old service, because WS-Routing was
> superceded by WS-Addressing 3 years ago.
>
> In any case, what you need to do is add a handler to add and process
> the wsrp header. (Note that the return message is telling you that you
> need to include a WS-Routing header in your input message, so it's not
> just a matter of ignoring the header.)
>
> Anne
>
> On 8/24/06, Reynir Hubner <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I am getting the following error when trying to access a remote service
> (that I am not in control of), that uses WS-routing.
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
> faultSubcode:
> faultString: Did not understand "MustUnderstand" header(s):
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
>
>
> this is because I get this kind of header, with the mustUnderstand flag
> set:
>
>
> http://schemas.xmlsoap.org/soap/actor/next";
> soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp";>
> http://schemas.xmlsoap.org/soap/fault
> uuid:9e6d818f-2b6e-4689-9877-9b855f400b27
>
> 701
> WS-Routing Header Required
>
>
>
>
> And obviously Axis does not understand the wsrp headres, as it does not
> understand WS-routing standard.
>
>
> Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
> Does anyone by any change have implementation for WS-routing ?
> Can anyone explain in short how I would implement WS-routing handler (or
> show a sample of any simple handler) ?
>
> thank you very much.
> -reynir
>
>>
- -
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]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE7yle19KgIQihNwgRApPpAJ98tMmSyNimSMveH31RSnk5H7T/mwCg4v8w
hKDyHltOzXRbSvS0AGvXl/U=
=wPhD
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Java classes generated by wsdl2java don't compile
Hello, I have an wsdl that imports several xsd schemas and I used an ant task with WSDL2Java to produce the corresponding java clases. I am working with axis 1.4 and java jsdk 1.5.0_06. WSDL2Java produces the classes and no errors. But some of the generated classes don't compile. One of the classes has 2 constructor methods that are the same. Other classes that inherite from some parent classes have the constructor parameters in the wrong order. If you want I can send you the wsdl and the xsd files. They seem to be correct as they come from the OTA pecification. Have you seen this happening before? Any hint? If you need more information, please, let me know. Thank you very much for your help, Manuel Valladares - - Jose Manuel Valladares Pernas - [EMAIL PROTECTED] - [EMAIL PROTECTED] - __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem in getting logging module example running.
Hi All, I am trying to get service archive (MyServiceWithModule.aar) from the samples provided by the axis2 documentatioin. If I follow the steps mentioned in the doc. I get following exception during the deployment. 2006-08-25 16:57:18,520 ERROR [org.apache.axis2.deployment.DeploymentEngine] Invalid service MyServiceWithModule.aar due to Invalid phases please recheck axis2.xml loggingPhase for the handler InFlowLogHandler org.apache.axis2.phaseresolver.PhaseException: Invalid phases please recheck axis2.xml loggingPhase for the handler InFlowLogHandler Document explaining the changes to do in axis2.xml is incomplete. I have tried to put phases in two different ways but exception is always same. 1) name="logging"/> 2) phase name="logging"> name="InFlowLogHandler" class="userguide.loggingmodule.LogHandler"> phase="loggingPhase" /> Is it correct way? I have copied .aar file and .mar file in proper location inside the war. Do I have to change something else? some other configuration file? Can experts here solve this small issue for me? Best Regards, -Prasad My entire axis2.xml looks like. name="AxisJava2.0"> name="hotdeployment" locked= "false">true name="hotupdate" locked= "false">false name="enableMTOM" locked= "false">false name="sendStacktraceDetailsWithFaults" locked= "false">true name="DrillDownToRootCauseForFaultReason" locked= "false">false name="userName" locked= "false">admin name="password" locked= "false">axis2 mep="http://www.w3.org/2004/08/wsdl/in-only" class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/> mep="http://www.w3.org/2004/08/wsdl/in-out" class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer"> name="port" locked= "false">6060 name="tcp" class="org.apache.axis2.transport.tcp.TCPServer"> name="port" locked= "false">6060 name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportSender"/> name="local" class="org.apache.axis2.transport.local.LocalTransportSender"/> name="jms" class="org.apache.axis2.transport.jms.JMSSender"/> name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"> name="PROTOCOL" locked= "false">HTTP/1.1 name="Transfer-Encoding" locked= "false">chunked name="https" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"> name="PROTOCOL" locked= "false">HTTP/1.1 name="Transfer-Encoding" locked= "false">chunked ref="addressing"/> type="inflow"> name="Transport"> name="RequestURIBasedDispatcher" class="org.apache.axis2.engine.RequestURIBasedDispatcher"> phase="Dispatch"/> name="SOAPActionBasedDispatcher" class="org.apache.axis2.engine.SOAPActionBasedDispatcher"> phase="Dispatch"/> name="Security"/> name="PreDispatch"/> name="Dispatch" class= "org.apache.axis2.engine.DispatchPhase"> name="AddressingBasedDispatcher" class="org.apache.axis2.engine.AddressingBasedDispatcher"> phase="Dispatch"/> name="SOAPMessageBodyBasedDispatcher" class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher"> phase="Dispatch"/> name="InstanceDispatcher" class="org.apache.axis2.engine.InstanceDispatcher"> phase="PostDispatch"/> name="OperationInPhase"/> name="logging"> name="InFlowLogHandler" class= "userguide.loggingmodule.LogHandler"> phase="loggingPhase"/> type="outflow"> name="OperationOutPhase"/> name="logging"> name="OutFlowLogHandler" class= "userguide.loggingmodule.LogHandler"> phase="loggingPhase"/> name="PolicyDetermination"/> name="MessageOut"/> type="INfaultflow"> name="PreDispatch"/> name="Dispatch" class= "org.apache.axis2.engine.DispatchPhase"> name="RequestURIBasedDispatcher" class="org.apache.axis2.engine.RequestURIBasedDispatcher"> phase="Dispatch"/> name="SOAPActionBasedDispatcher" class="org.apache.axis2.engine.SOAPActionBasedDispatcher"> phase="Dispatch"/> name="AddressingBasedD
FW: [Axis2]: Error while starting the server
Hi All, Please ignore the following message. Regards, Syam -Original Message- From: Syam Prasad [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 8:40 AM To: axis-user@ws.apache.org Subject: FW: [Axis2]: Error while starting the server Hi All, Can anybody help me with the following error? Thanks for your help. Regards, Syam -Original Message- From: Syam Prasad [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 3:59 PM To: 'axis-user@ws.apache.org' Subject: [Axis2]: Error while starting the server Hi, Can any body help me with the following error. It is happening while starting the server. ERROR - DeploymentEngine.doDeploy(628) [main] | Invalid service system due to Invalid service META-INF directory not found; nested exception is: org.apache.axis2.deployment.DeploymentException: Invalid service META-INF directory not found org.apache.axis2.deployment.DeploymentException: Invalid service META-INF directory not found; nested exception is: org.apache.axis2.deployment.DeploymentException: Invalid service META-INF directory not found The error message is obvious but I have the directory structure defined like ---webapp \---WEB-INF | web.xml | \---services \---MyService \---META-INF | services.xml Still it is throwing error. Any help is appreciated. Thanks in advance, Syam - 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]
Re: [axis2] NullPointerException with WSDL2Java
oups sorry for the typo !
once fixed I still have my warning:
Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
Aug 25, 2006 2:55:16 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {http://www.mynamespace.net}myStatus_type0 missing!
I can't understand why
any idea?
Olivier
"Anne Thomas Manes"
<[EMAIL PROTECTED]>
25/08/2006 14:55 To: axis-user@ws.apache.org
Please respond to axis-usercc:
bcc:
Subject: Re: [axis2]
NullPointerException with WSDL2Java
Olivier,
You have an extra ">" in your schema declaration that occurs before
you declare the targetNamespace in your schema:
http://www.w3.org/2001/XMLSchema";> <-- error
xmlns="http://www.mynamespace.net";
targetNamespace="http://www.mynamespace.net";>
Anne
On 8/24/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
>
>
> Thanks for your help Anne. As recommended I opened a bug request yesterday.
> It is already fixed, so I tried latest nigthly build (08/24/2006).
> But now I get warnings (see below) at client code generation.
>
> Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {urn:myNamespace}myStatus_type0 missing!
> Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
> WARNING: Type {urn:myNamespace}myStatus_type0 missing!
>
> and here is my new wsdl file:
>
>
> http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://www.mynamespace.net";
> xmlns="http://www.mynamespace.net";>
>
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> xmlns="http://www.mynamespace.net";
> targetNamespace="http://www.mynamespace.net";>
>
>
> type="xsd:int"/>
>
>
>
> type="xsd:string"/>
>
>
> name="myMethod1Response">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
> location="http://localhost:8080/axis2/services/myWebServices"/>
>
>
>
>
> my XMl schema seems valid so I can't understand why
>
> Olivier
>
>
>
> "Anne Thomas Manes"
> <[EMAIL PROTECTED]>
> 23/08/2006 21:02 To: axis-user@ws.apache.org
> Please respond to axis-usercc:
>bcc:
>Subject: Re: [axis2]
> NullPointerException with WSDL2Java
>
>
>
>
>
>
> My guess is that the error is caused by the fact that you use the same
> input message for both operations. Axis (and WS-I Basic Profile)
> requires that each operation have a unique message signature (which is
> the QName of the child element of the ). Both or your
> operations use the same signature: "myNamespace"}myMethod.
>
> The error might also be caused by the fact that "myNamespace" is not a
> valid URI. A namespace must be a valid URI.
>
> To fix your problem:
> 1. Change the target namespace to a valid URI (e.g., "urn: ")
> 2. Define unique input elements for your two operations
>
> Meanwhile, WSDL2Java should not generate an NPE, so please also file a JIRA.
>
> Anne
>
> On 8/23/06, CHAPELLIERE Olivier ORANGE-FT
> <[EMAIL PROTECTED]> wrote:
> >
> > Hi everybody,
> >
> > I have a NullPointerException while generating client
Axis 1.4 sessions with http cookies
Hello everyone,
I've been looking at the axis wiki trying to follow the information
about enabling sessions. I want to use sessions with http cookies but I
cann't seem to get it to work.
Here is two sections of code that I thought would work.
The setup is this;
TestServiceLocator serviceLocator = new TestServiceLocator();
TestBindingStub binding = (TestBindingStub) serviceLocator.getTesting();
binding.setTimeout(6);
binding.setMaintainSession(true);
And, this is what I'm doing to call my test service;
for (int i=0; i < 4; i++) {
System.out.println("Request " + i);
Param_THolder paramHolder = new Param_THolder();
binding.delayMethod(paramHolder);
MessageContext messageContext =
binding._getCall().getMessageContext();
String cookie1 = (String)
messageContext.getProperty(HTTPConstants.HEADER_COOKIE);
String cookie2 = (String)
messageContext.getProperty(HTTPConstants.HEADER_COOKIE2);
System.out.println("cookie1 : '" + cookie1 + "'");
System.out.println("cookie2 : '" + cookie2 + "'");
}
Every time the cookie values are null.
I also have the server logging the session used and each time it's a new
session. So I'm getting a new session with every call.
What am I missing, do I have to create/install a handler to set the
session in the MessageContext for the requests on the server? The only
example I see is for maintaining sessions with the soap headers
(SimpleSessionHandler), which I don't really want to do. Is there one
for http cookies?
Thx
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: MTOM Client
Does this property not work in the 1.0 release? Roshan Punnoose Phone: 301-497-6039 -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 5:23 PM To: axis-user@ws.apache.org Subject: Re: MTOM Client Oops, I meant: options.setProperty(org.apache.axis2.Constants.Configuration.CACHE_ATTAC HMENTS, Boolean.TRUE); On 8/24/06, robert lazarski <[EMAIL PROTECTED]> wrote: > Try: > > options.setProperty(org.apache.axis2.Constants.Configuration.ENABLE_MTOM , >Boolean.TRUE); > > Make sure your using the latest nightlies: > > http://people.apache.org/dist/axis2/nightly/ > > HTH, > Robert > http://www.braziloutsource.com > > On 8/24/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi, > > > > > > > > On the web page for Axis 2/MTOM, I saw that I could use the file system to > > cache large attachments being transferred; however, I only saw the server > > axis config file. How do I setup the client to do the same thing? Do I have > > to set it in the options? > > > > > > > > Server config: > > > > > > > > true > > temp > > directory > > 4000 > > . > > . > > > > > > > > > > > > Thanks! > > > > > > > > Roshan Punnoose > > > > Phone: 301-497-6039 > > > > > > - > > 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] BEGIN:VCARD VERSION:2.1 N:Punnoose;Roshan FN:Punnoose, Roshan ADR;WORK:;2115 LABEL;WORK:2115 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050413T183207Z END:VCARD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WS call redirection
Hi guys, I have the following question. Can Axis in the runtime redirect the call to the web service (e.g. client calls ServiceA which doesn't exist, though Axis is configured in such way, that when it receives the call to ServiceA it atomatically redirects the call to ServiceB).Perhaps with deploy.wsdd?... Best regards, Taras
Re: [axis2] Naming of the Request message by Java2WSDL
If you are using the wrapped convention, then the request message element MUST be the same as the operation name. If you prefer to use unwrapped doc/literal, you can name the request element anything you want, but then you must also provide information to Axis (via the WSDD) as to how to map the incoming QName to the appropriate method. Anne On 8/23/06, William Ferguson <[EMAIL PROTECTED]> wrote: The message elements and wsdl types that Java 2WSDL generates for the request portion of a Service method have the same name as the method itself, while the response portion is of the form Response. IMHO, for clarity it would be better for the the request elements to follow the same pattern as that for the response elments. Eg for a method with signature: public String getMyMethod(String someParam); It would be better to generate an operation element like: Message elements like: And WSDL types of: Doing so makes it much clearer in both the WSDL and in clients using the generated stubs and data bindings (IMHO). Does anyone else concur? If so I'll create an issue for it. William - 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]
Re: StackOverflowError using WSDL2Java
Really bad form in your schema: targetNamespace="http://schemas.xmlsoap.org/wsdl/"; I think you wanted this instead: targetNamespace="http://www.opengis.net/sos/0"; This WSDL is invalid because it cannot resolve the elements referenced from your message parts (sos:GetCapabilities and sos:Capabilities). It's looking for them in a namespace called "http://www.opengis.net/sos/0";, but you've defined them in a namespace called "http://www.opengeospatial.net/sos";. To resolve you problem, please go through your WSDL and schemas to make sure you're using and referencing the proper namespaces and properly importing and including schemas. But regardless, Axis should not be generating a StackOverflowError. Please file a JIRA. Anne On 8/24/06, Christoph Stasch <[EMAIL PROTECTED]> wrote: Hi, I'm using Axis2 1.0 and want to use the WSDL2Java code generator to create java sources from the following wsdl file: http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:sos="http://www.opengis.net/sos/0"; targetNamespace="http://www.opengis.net/sos/0"; xmlns:sml="http://www.geospatial.net/sensorML"; xmlns:om="http://www.geospatial.net/om/0.0"; xmlns:gml="http://www.opengis.net/gml"; xmlns:ows="http://www.opengeospatial.net/ows"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/wsdl/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.opengis.net/sos"; schemaLocation="sosAll.xsd"/> http://schemas.xmlsoap.org/soap/http"/> http://mars.uni-muenster.de/GetCapabilities"/> http://mars.uni-muenster.de:8080/52nSOSv2/SOAP/sos"/> http://mars.uni-muenster.de:8080/52nSOSv2/sos"/> When I try to generate code with the command "wsdl2java -uri sos.wsdl -ss -sd -d xmlbeans", I get the following error: Exception in thread "main" java.lang.StackOverflowError at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393) at java.lang.StringBuilder.append(StringBuilder.java:120) at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:227) at sun.net.www.protocol.file.Handler.parseURL(Handler.java:50) at java.net.URL.(URL.java:596) at java.net.URL.(URL.java:464) at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:881) at sun.misc.URLClassPath$FileLoader.findResource(URLClassPath.java:871) at sun.misc.URLClassPath.findResource(URLClassPath.java:142) at java.net.URLClassLoader$2.run(URLClassLoader.java:362) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findResource(URLClassLoader.java:359) at java.lang.ClassLoader.getResource(ClassLoader.java:977) at java.lang.ClassLoader.getSystemResource(ClassLoader.java:1075) at java.lang.ClassLoader.getSystemResourceAsStream(ClassLoader.java:1181) at javax.xml.parsers.SecuritySupport$4.run(SecuritySupport.java:70) at java.security.AccessController.doPrivileged(Native Method) at javax.xml.parsers.SecuritySupport.getResourceAsStream(SecuritySupport.java:65) at javax.xml.parsers.FactoryFinder.findJarServiceProvider(FactoryFinder.java:218) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:213) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1911) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1708) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:126) I am a newbie to Axis and don't know, whether this is a fault in my wsdl file or the schema files or another pr
Yet another embedded Axis question
Hi all, I am new to Axis, but I know there have been some discussion on this topic before: is there a way to use Axis without an application server? Yes, I have read the FAQ and got to know the SimpleAxisServer (http://wiki.apache.org/ws/SimpleAxisServer), but it is not exactly what I was looking for. I was thinking of something like an Axis API or even an Axis servlet that I could use, for example, together with emebedded Jetty in a standalone java application. My point is that my WebServices shall be very simple and I am not willing to use the whole complexity of SOAP and Axis (WSDL, Tomcat, etc.). Apache XML-RPC fits perfectly for my needs, but SOAP is so widespread that I am in doubt. Does anybody think XML-RPC could be a better choice? PS1.: Yes, I have seen two messages with the same subject in the archives. One had no answer and the other one had a not convincing answer. PS2.: JWS files do not seem a good option. They reduce complexity, but I still need an application server. Thanks in advance, -- DIEGO Moreira da Rosa DATACOM Av França, 735 - Porto Alegre, RS - 90230-220 DDR: 51 3358 0141 Fax: 51 3358 0101 site: www.datacom-telematica.com.br - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: Axis array serialization problem
Based on your WSDL, your response message should look something like this: http://interfazweb.serviciosweb.moduloingenieria.xxx.es";> string string 1 2 1 string 2 string Note that you have a namespace conflict here, and therefore the schema is not valid -- you have two separate qualified elements named . One is the child of the "UsuarioIW" complexType. The other is a child of the "PlantaIW" complexType. If you want both elements to be named "nombre", then you should define a global element named "nombre" and reference that element from the two types. For example: Anne On 8/24/06, HHDirecto. Net <[EMAIL PROTECTED]> wrote: I Forget send globalConfiguration of wsdd file: 2006/8/24, HHDirecto. Net <[EMAIL PROTECTED]>: > > Hi Anne, Here my wsdl and wsdd files: (axis 1.4) > > WSDL > > http://pcacastro:8080/ModuloIngenieria/services/InterfazWeb"; xmlns:apachesoap="http://xml.apache.org/xml-soap " xmlns:impl=" http://pcacastro:8080/ModuloIngenieria/services/InterfazWeb"; xmlns:intf=" http://pcacastro:8080/ModuloIngenieria/services/InterfazWeb"; xmlns:tns1=" http://interfazweb.serviciosweb.moduloingenieria.xxx.es"; xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/ " xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd=" http://www.w3.org/2001/XMLSchema "> > > > http://interfazweb.serviciosweb.moduloingenieria.xxx.es"; xmlns="http://www.w3.org/2001/XMLSchema "> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http "/> > > > > > > > > > > > > > > > > > > > > > > http://pcacastro:8080/ModuloIngenieria/services/InterfazWeb"/> > > > > server-config.wsdd > > C:\Program Files\Apache Software Foundation\apache- tomcat-5.5.16\webapps\ModuloIngenieria\WEB-INF\InterfazWeb.xml > > > > > > http://interfazweb.serviciosweb.moduloingenieria.xxx.es "/> > http://interfazweb.serviciosweb.moduloingenieria.xxx.es"/> > http://interfazweb.serviciosweb.moduloingenieria.xxx.es"/> > > > > Thanks in advance! > > > > > > > - Original Message - > > From: "Anne Thomas Manes" < [EMAIL PROTECTED]> > > To: > > Sent: Wednesday, August 23, 2006 8:46 PM > > Subject: Re: Axis array serialization problem > > > > > > > For some reason you have an extra layer of wrapping in the second > > > array. (and you still have the inner element with the same name as the > > > wrapping element, which is an error). > > > > > > Please post the schema, WSDL, and WSDD. > > > > > > Anne > > > > > > On 8/23/06, HHDirecto. Net < [EMAIL PROTECTED]> wrote: > > >> Axis web service response is ok (I think) but, .net client don't get > > >> "plantas" array it get null (Now It get int array successfull). > > >> > > >> web service response: > > >> > > >> > >> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"; > > >> xmlns:xsd="http://www.w3.org/2001/XMLSchema " xmlns:xsi=" > > >> http://www.w3.org/2001/XMLSchema-instance";> > > >> > >> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"; > > >> xmlns:xsd="http://www.w3.org/2001/XMLSchema " xmlns:xsi=" > > >> > > http://www.w3.org/2001/XMLSchema-instance";> > e > > >> xmlns=" http://interfazweb.serviciosweb.moduloingenieria.xxx.es > > >> "> > > >> [EMAIL PROTECTED]Usuario > > >> > > >> 12 > > >> > > 1planta1 > s> > > >> > > >> > > >> > > >> > > >> Thanks in advance > > >> > > >> 2006/8/23, Anne Thomas Manes < [EMAIL PROTECTED]>: > > >> > How does it fail? > > >> > > > >> > On 8/23/06, HHDirecto. Net <[EMAIL PROTECTED] > wrote: > > >> > > > > >> > > > > >> > > Thanks. I solved it with a array of int. But I have too an array > > of > > >> class > > >> > > and it fails. This is my wsdl: > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > type="xsd:int"/> > > >> > > > >> > > type="tns1:PlantaIW"/> > > >> > > >
Re: Which should I use Axis or Axis2 in a new web service project
I've created a catchall all jira for doc improvements based on some recent comments. http://issues.apache.org/jira/browse/AXIS2-1076 Alot of this stuff seems self-explanatory to those that have been using axis2 for a while, and its hard at least for me to grasp what seems to be vague and what can be improved. We can always improve, but we'll need some help defining what 'scketchy' is, and I ask for some comments inside the jira. I personally will try to find some time to use constructive comments to see if we can get our docs more axis2 newbie friendly in time for the 1.1 release. Robert http://www.braziloutsource.com On 8/25/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Axis2 is the next generation web services platform. It supports all the latest and greatest SOAP and REST capabilities. It's definitely the system you'll be wanting to use a year from now. Unfortunately, it is not yet stable. The developers are planning to release v1.1 next month, and I'm hoping that version will be stable. If you want to use Axis2, you will need to be preprared to use the nightly builds, to help identify bugs, and to perhaps propose fixes. The documentation is also pretty scketchy. Axis is pretty much on life support. It's pretty stable, although a few bugs still exist regarding arrays. If you find a bug, please report it, and it will probably get fixed, but don't expect to see any enhancements going forward. Anne On 8/24/06, Anthony Hong <[EMAIL PROTECTED]> wrote: > Hi all, > > I used to know Axis for developing webservice, > Now I see Axis2, Does it means Axis going to die? Any co-operation > problem when use Axis client and Axis2 endpoint? > Is Axis2 stable now? > > -- > > Anthony Hong > > - > 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]
Re: WSDL2Java Question
Okay, please file a JIRA. On 8/25/06, Marius Hugo <[EMAIL PROTECTED]> wrote: Anne, I've removed the "namespace" attributes and I'm still getting the extra methods; and in the one method, the sessionId is still changed from a long to an int. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 14:07 To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Marius, The only errors that I see in the WSDL is that you need to remove the "namespace" attributes from all the definitions in the binding. (You use the namespace attribute only when using RPC style.) Please make this fix and regenerate (although I doubt this is causing the anomoly). Please let us know what happens. Anne On 8/24/06, Marius Hugo <[EMAIL PROTECTED]> wrote: > Sure, no problem, I've attached the files. > I'm sending the entire files, cause I don't want to go and send what I > think is important and then it ends up that I am missing something > (look for the SessionId). > The extra methods (in the Document) seem to be created for each of the > xs:simpleTypes that are declared in TradeRootMerchantTypes.xsd. > > The types aren't always changed (from long to int for instance), but > the other types are int and string and I don't really see what else > they could change to anyway. > > > Another question: > I am not sure how the restrictions that are placed on a type are > imposed in the generated code. > For instance, in the case of the SessionId type, I don't see any code > that enforces the restrictions that are defined (maxInclusive and > minInclusive). > > If I go look at the following generated code though: > > > > This Additional Data is > provided by the EUA when there exists a requirement to dispatch a > notification instruction. > > > > > base="xs:string"> > value="EMAIL"/> > value="SMS"/> > > > > > > base="xs:string"> > value="120"/> > > > > > > > Then I can see the restriction enforced for notifactionType, but not > for notificationAddress. I haven't worked with xsd and wsdl before, > so I don't really know if I'm just not understanding the concept of > these restrictions or if I'm missing something really obvious, so if > anyone would care to explain it to me in very simple terms...that > would really be appreciated:D > > Thanks, > Marius > > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: 23 August 2006 19:46 > To: axis-user@ws.apache.org > Subject: Re: WSDL2Java Question > > Marius, > > Given that xsd:long is derived from xsd:int restricted by maxInclusive > and minInclusive, it actually makes more sense for you to derive from > xsd:int rather than xsd:long. > > But that's just a nit. This smells like a bug. > xsd:long should map to long, not to int; but since you've derived a > type, the return type should be your value type, SessionId. > > But I don't understand why you have two methods. > > Could you please post the WSDL and XSD? > > Anne > > On 8/23/06, Marius Hugo <[EMAIL PROTECTED]> wrote: > > > > > > This is the first time that I am working with axis and I must now > > migrate someone else's code > > > > from axis to axis2, so I'm a little clueless... > > > > I just have a few simple questions concerning what WSDL2Java > generated: > > > >In ye olden xsd and wsdl: > > - He declared a simple type (xs:long), " SessionId " . > > - He also added restrictions (minInclusive and maxInclusive) to > > that type > > - He also declared that one of the responses that I send, uses > > that type as a field . > > - From what I've learned, all of this looks right and it worked > > on the previous version of axis > > > > - I then used WSDL2Java to generate code: > > it generated > > com.company.product.webservice.types.SessionId > > it also generated the Document that uses > > this type > > > > - In the generated document, the following methods are available > > (well, there are others:): > > > > - int getSessionId(); > > - com.company.product.webservice.types.SessionId > > xgetSessionId(); > > > > > > NOW (these questions apply to both getters and setters) > > > > What is the difference between the two methods? > > > > Are the restrictions imposed on both of them? > > > > Why does the one method r
Re: [axis2] NullPointerException with WSDL2Java
Olivier,
You have an extra ">" in your schema declaration that occurs before
you declare the targetNamespace in your schema:
http://www.w3.org/2001/XMLSchema";> <-- error
xmlns="http://www.mynamespace.net";
targetNamespace="http://www.mynamespace.net";>
Anne
On 8/24/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
Thanks for your help Anne. As recommended I opened a bug request yesterday.
It is already fixed, so I tried latest nigthly build (08/24/2006).
But now I get warnings (see below) at client code generation.
Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {urn:myNamespace}myStatus_type0 missing!
Aug 24, 2006 1:09:10 PM org.apache.axis2.schema.SchemaCompiler findClassName
WARNING: Type {urn:myNamespace}myStatus_type0 missing!
and here is my new wsdl file:
http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
targetNamespace="http://www.mynamespace.net";
xmlns="http://www.mynamespace.net";>
http://www.w3.org/2001/XMLSchema";>
xmlns="http://www.mynamespace.net";
targetNamespace="http://www.mynamespace.net";>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:8080/axis2/services/myWebServices"/>
my XMl schema seems valid so I can't understand why
Olivier
"Anne Thomas Manes"
<[EMAIL PROTECTED]>
23/08/2006 21:02 To: axis-user@ws.apache.org
Please respond to axis-usercc:
bcc:
Subject: Re: [axis2]
NullPointerException with WSDL2Java
My guess is that the error is caused by the fact that you use the same
input message for both operations. Axis (and WS-I Basic Profile)
requires that each operation have a unique message signature (which is
the QName of the child element of the ). Both or your
operations use the same signature: "myNamespace"}myMethod.
The error might also be caused by the fact that "myNamespace" is not a
valid URI. A namespace must be a valid URI.
To fix your problem:
1. Change the target namespace to a valid URI (e.g., "urn: ")
2. Define unique input elements for your two operations
Meanwhile, WSDL2Java should not generate an NPE, so please also file a JIRA.
Anne
On 8/23/06, CHAPELLIERE Olivier ORANGE-FT
<[EMAIL PROTECTED]> wrote:
>
> Hi everybody,
>
> I have a NullPointerException while generating client code for a WSDL.
> I tried axis2 version 1.0 and nightly build of august 22th 2006 and I always
have the exception.
>
> My command line is:
> WSDL2Java.sh -uri bug.wsdl -o gen
>
> My wsdl file is the following:
> 1
> 23xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> 4
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> 5xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> 6targetNamespace="mynamespace">
> 7
> 8
> 9 10 targetNamespace="mynamespace"
> 11 xmlns:mynamespace="mynamespace"
> 12 xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> 13
> 14
> 15
> 16
> 17
> 18
> 19
> 20
> 21
> 22
> 23
> 24
> 25
> 26
> 27
> 28
> 29
> 30
> 31
> 32
> 33
> 34
> 35
> 36
> 37
> 38
> 39
> 40
> 41
> 42
> 43
> 44
> 45
> 46
> 47
> 48
> 49
> 50
> 51
> 52
> 53
> 54
> 55 http://schemas.xmlsoap.org/soap/http"/>
> 56
> 57
> 58
> 59
> 60
> 61
> 62
> 63
> 64
> 65
> 66
> 67
> 68
> 69
> 70 http://localhost:8080/axis2/services/myWebServices"/>
> 71
> 72
> 73
>
> And I get the follow
Re: How could generate *only* deploy.wsdd?
Thanks bell, but i want _generate_ wsdd, no deploy them. I generated wsdl using axis-java2wsdl, but wsdd it's not generated with this task (it's this correct or i'm wrong?). Bell, Douglas wrote: Hi Angel, I'm taking a guess that you are asking how to deploy the services I do it via an ant task. You can also do it via the command line: org.apache.axis.utils.Admin -Dserver=[PATH_TO_YOUR_WSDL] If you use the template below just make sure you have axis-ant.jar on your classpath. ... Hope this helps, Doug -Original Message- From: Angel Cervera Claudio [mailto:[EMAIL PROTECTED] Sent: Thu 8/24/2006 4:07 AM To: axis-user@ws.apache.org Cc: Subject: How could generate *only* deploy.wsdd? Hello people. I'm developing a web service. I have generate wsdl using axis-java2wsdl. Now i need generate a deploy.wsdd to deploy service. If i use axis-wsdl2java, task generate deploy.wsdd and client/server stub. How could generate *only* deploy.wsdd? Thanks and apologies for my poor english. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ángel Cervera Claudio Desarrollos j2ee web: http://www.acervera.com email: [EMAIL PROTECTED] tlf: 984050494 / 985308170 / 670819234 fax: 985308228 Avda. de la Argentina, 132 33213 - Gijón (Asturias) - Spain - Mensajería - msn: [EMAIL PROTECTED] yahoo: angelcervera aol: angelcervera jabber: angelcervera en jabber.org google talk: angelcervera skype: angelcervera Este mensaje y cualquier documento adjunto que lleve consigo es sólo para la persona o compañía a la que va dirigido y puede contener información privilegiada, confidencial o cuya revelación o uso esté prohibido. Si el receptor de esta transmisión no es la persona a quien iba dirigida, o el empleado o agente encargado de hacer llegar dicho material al receptor previsto, se le notifica que cualquier uso, forma de reproducción, difusión, copia, revelación, modificación, distribución y/o publicación de este mensaje o sus documentos adjuntos por cualquier otro que no sea su destinatario previsto está estrictamente prohibido por el remitente. Si ha recibido esto por error, por favor, devuélvalo al remitente y destruya el mensaje y/o las copias que pueda haber en su posesión. This message and any attachments to it is intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorized use. If the recipient of this transmission is not the intended recipient, or the employee or agent responsible for delivering such materials to the intended recipient, you are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by its intended recipient is strictly prohibited by the sender. If you have received it in error, please return it to the sender and destroy the message and/or copies in your possession. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL2Java Question
Anne, I've removed the "namespace" attributes and I'm still getting the extra methods; and in the one method, the sessionId is still changed from a long to an int. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 14:07 To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Marius, The only errors that I see in the WSDL is that you need to remove the "namespace" attributes from all the definitions in the binding. (You use the namespace attribute only when using RPC style.) Please make this fix and regenerate (although I doubt this is causing the anomoly). Please let us know what happens. Anne On 8/24/06, Marius Hugo <[EMAIL PROTECTED]> wrote: > Sure, no problem, I've attached the files. > I'm sending the entire files, cause I don't want to go and send what I > think is important and then it ends up that I am missing something > (look for the SessionId). > The extra methods (in the Document) seem to be created for each of the > xs:simpleTypes that are declared in TradeRootMerchantTypes.xsd. > > The types aren't always changed (from long to int for instance), but > the other types are int and string and I don't really see what else > they could change to anyway. > > > Another question: > I am not sure how the restrictions that are placed on a type are > imposed in the generated code. > For instance, in the case of the SessionId type, I don't see any code > that enforces the restrictions that are defined (maxInclusive and > minInclusive). > > If I go look at the following generated code though: > > > > This Additional Data is > provided by the EUA when there exists a requirement to dispatch a > notification instruction. > > > > > base="xs:string"> > value="EMAIL"/> > value="SMS"/> > > > > > > base="xs:string"> > value="120"/> > > > > > > > Then I can see the restriction enforced for notifactionType, but not > for notificationAddress. I haven't worked with xsd and wsdl before, > so I don't really know if I'm just not understanding the concept of > these restrictions or if I'm missing something really obvious, so if > anyone would care to explain it to me in very simple terms...that > would really be appreciated:D > > Thanks, > Marius > > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: 23 August 2006 19:46 > To: axis-user@ws.apache.org > Subject: Re: WSDL2Java Question > > Marius, > > Given that xsd:long is derived from xsd:int restricted by maxInclusive > and minInclusive, it actually makes more sense for you to derive from > xsd:int rather than xsd:long. > > But that's just a nit. This smells like a bug. > xsd:long should map to long, not to int; but since you've derived a > type, the return type should be your value type, SessionId. > > But I don't understand why you have two methods. > > Could you please post the WSDL and XSD? > > Anne > > On 8/23/06, Marius Hugo <[EMAIL PROTECTED]> wrote: > > > > > > This is the first time that I am working with axis and I must now > > migrate someone else's code > > > > from axis to axis2, so I'm a little clueless... > > > > I just have a few simple questions concerning what WSDL2Java > generated: > > > >In ye olden xsd and wsdl: > > - He declared a simple type (xs:long), " SessionId " . > > - He also added restrictions (minInclusive and maxInclusive) to > > that type > > - He also declared that one of the responses that I send, uses > > that type as a field . > > - From what I've learned, all of this looks right and it worked > > on the previous version of axis > > > > - I then used WSDL2Java to generate code: > > it generated > > com.company.product.webservice.types.SessionId > > it also generated the Document that uses > > this type > > > > - In the generated document, the following methods are available > > (well, there are others:): > > > > - int getSessionId(); > > - com.company.product.webservice.types.SessionId > > xgetSessionId(); > > > > > > NOW (these questions apply to both getters and setters) > > > > What is the difference between the two methods? > > > > Are the restrictions imposed on both of them? > > > > Why does the one method return an int, when SessionId was > > defined as a long? >
Re: WS-routing
You must be dealing with an old service, because WS-Routing was
superceded by WS-Addressing 3 years ago.
In any case, what you need to do is add a handler to add and process
the wsrp header. (Note that the return message is telling you that you
need to include a WS-Routing header in your input message, so it's not
just a matter of ignoring the header.)
Anne
On 8/24/06, Reynir Hubner <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am getting the following error when trying to access a remote service
(that I am not in control of), that uses WS-routing.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
faultSubcode:
faultString: Did not understand "MustUnderstand" header(s):
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
this is because I get this kind of header, with the mustUnderstand flag
set:
http://schemas.xmlsoap.org/soap/actor/next";
soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp";>
http://schemas.xmlsoap.org/soap/fault
uuid:9e6d818f-2b6e-4689-9877-9b855f400b27
701
WS-Routing Header Required
And obviously Axis does not understand the wsrp headres, as it does not
understand WS-routing standard.
Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
Does anyone by any change have implementation for WS-routing ?
Can anyone explain in short how I would implement WS-routing handler (or
show a sample of any simple handler) ?
thank you very much.
- -reynir
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE7c0219KgIQihNwgRAvkGAKDyPV/qLcudDK1NvHVPCQ384+SZPACfQ7Qd
JkxY3I7lKfX4B5GVxyEhqug=
=ViWs
-END PGP SIGNATURE-
-
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]
Re: Multiple parameters
It's always best to avoit exposing Java-specific collection types
through your web service interface. Stick with arrays.
Anne
On 8/24/06, Fu, Glen <[EMAIL PROTECTED]> wrote:
Hi Jay,
Could you give me sample server/client code with ArrayList parameter in
Java on AXIS2?
Can I create a service with below?
public String MyService(String parm0,ArrayList parm1) {
// business logic..
return "return string";
}
Thanks,
Glen
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 9:16 PM
To: axis-user@ws.apache.org
Subject: Re: Multiple parameters
Hi Fu;
None of the message receiver available in Axis2 can not handle this
scenario. I mean if the method take hastable then Axis2 can not handle
that , but arrylist and object[] can handle.
Thanks
Deepal
Fu, Glen wrote:
> Hi,
>
>
> I want to create a service with Hashtable object parameters with
> AXIS2 , could you let me know how to code it at server and client
sides?
>
> The parameters will be like below in Java
> *
>
> public String MyService(String parm0,Hashtable parm1) {
>
> business logic..
>
> }
>
>
>
> Thanks,
> Glen
>
> *
--
Thanks,
Deepal
~Future is Open~
-
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]
Re: [Axis 1.2] Sending SOAP request parameters in BODY instead of HEADER
Please note that in the JIRA, thanks! Anne On 8/24/06, ezwise <[EMAIL PROTECTED]> wrote: I've confirmed that just changing the param list name from "parameters" to something else resolves the issue. -- View this message in context: http://www.nabble.com/-Axis-1.2--Sending-SOAP-request-parameters-in-BODY-instead-of-HEADER-tf2154309.html#a5971548 Sent from the Axis - User forum at Nabble.com. - 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]
Re: SOAP with Attachments (SwA) with Axis2, problem.
Just one addition to this, I am getting this exception while starting my jboss, when jboss tries to deploy the webservice.On 8/25/06, Prasad Chaudhari <
[EMAIL PROTECTED]> wrote:
Hi,
I am trying to get SOAP monitor started on my machine following the tutorial
http://ws.apache.org/axis2/1_0/soapmonitor-module.html
But I get following exception.
2006-08-25 13:04:10,133 INFO
[org.apache.axis2.deployment.WarBasedAxisConfigurator]
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler; nested
exception is:
java.lang.ClassNotFoundException:
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler
2006-08-25 13:04:10,136 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ngaxis2]]
Servlet /ngaxis2 threw load() exception
java.lang.NullPointerException
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.(WarBasedAxisConfigurator.java:81)
To configure soapmonitor module
I have made following changes:-
axis2.xml
i)Added
ii)And appropriate phase element inside all 4 phase order elements.
One example
Services.xml
This is a sample Web Service
com.conject.ng.axis2.ProjectWebService
Copied soapmonitor.mar to the /WEB-INF/modules directory.
Am I missing something or doing wrong. Can anybody help.
Best Regards,
-Prasad
On 8/24/06, robert lazarski <[EMAIL PROTECTED]
> wrote:
Try putting TCPMon or the soapmonitor on the request, post the soapenvelope the axis2 service receives, and maybe we can help.Robert
http://www.braziloutsource.com/
On 8/24/06, Prasad Chaudhari <[EMAIL PROTECTED]> wrote:> Hi All,
>> My client is having axis1.x SOAP client, who sends a file, for which I am
> suppose to write a Webservice. I have decided to use axis 2.0 for this> service.>> To get my axis 1.x SOAP client running with axis 2 SOAP Service, I was> using following tutorial.
> http://ws.apache.org/axis2/1_0/mtom-guide.html>> It says.>
> "Axis2 Handles SwA messages at the inflow only. When Axis2 receives a SwA
> message it extracts the binary attachment parts and puts a reference to> those parts in the Message Context.">> I understood this as following, if I send the SOAP message with attachment
> using axis1.x client to the axis2 webservice. Axis2 will extract the binary> attachment and put an element into the xml like> > xmlns="/>
> and I can retrive this attachment from MessageContext.>> But it does not work. The OMElement which I receive as a parameter to my> serviceMethod do not have this source element into it. If I use following
> code given in tutorial.>> public OMElement echoAttachment(OMElement omEle) {> OMElement child = (OMElement) omEle.getFirstOMChild(); or OMElement child => element.getFirstChildWithName
(new QName("source"));> OMAttribute attr => child.getAttribute(new QName("href"));> String contentID = attr.getAttributeValue();> ..>>> Child element is always null(in case of both statements from the code
> snippet)>> Can somebody help me here. Tutorial says above code has been tested with> axis1.x can somebody send me the test client in axis 1.x.>> Thanks in advance.> -Prasad
>>>
Re: Which should I use Axis or Axis2 in a new web service project
Axis2 is the next generation web services platform. It supports all the latest and greatest SOAP and REST capabilities. It's definitely the system you'll be wanting to use a year from now. Unfortunately, it is not yet stable. The developers are planning to release v1.1 next month, and I'm hoping that version will be stable. If you want to use Axis2, you will need to be preprared to use the nightly builds, to help identify bugs, and to perhaps propose fixes. The documentation is also pretty scketchy. Axis is pretty much on life support. It's pretty stable, although a few bugs still exist regarding arrays. If you find a bug, please report it, and it will probably get fixed, but don't expect to see any enhancements going forward. Anne On 8/24/06, Anthony Hong <[EMAIL PROTECTED]> wrote: Hi all, I used to know Axis for developing webservice, Now I see Axis2, Does it means Axis going to die? Any co-operation problem when use Axis client and Axis2 endpoint? Is Axis2 stable now? -- Anthony Hong - 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]
Re: WSDL2Java Question
Marius, The only errors that I see in the WSDL is that you need to remove the "namespace" attributes from all the definitions in the binding. (You use the namespace attribute only when using RPC style.) Please make this fix and regenerate (although I doubt this is causing the anomoly). Please let us know what happens. Anne On 8/24/06, Marius Hugo <[EMAIL PROTECTED]> wrote: Sure, no problem, I've attached the files. I'm sending the entire files, cause I don't want to go and send what I think is important and then it ends up that I am missing something (look for the SessionId). The extra methods (in the Document) seem to be created for each of the xs:simpleTypes that are declared in TradeRootMerchantTypes.xsd. The types aren't always changed (from long to int for instance), but the other types are int and string and I don't really see what else they could change to anyway. Another question: I am not sure how the restrictions that are placed on a type are imposed in the generated code. For instance, in the case of the SessionId type, I don't see any code that enforces the restrictions that are defined (maxInclusive and minInclusive). If I go look at the following generated code though: This Additional Data is provided by the EUA when there exists a requirement to dispatch a notification instruction. Then I can see the restriction enforced for notifactionType, but not for notificationAddress. I haven't worked with xsd and wsdl before, so I don't really know if I'm just not understanding the concept of these restrictions or if I'm missing something really obvious, so if anyone would care to explain it to me in very simple terms...that would really be appreciated:D Thanks, Marius -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 23 August 2006 19:46 To: axis-user@ws.apache.org Subject: Re: WSDL2Java Question Marius, Given that xsd:long is derived from xsd:int restricted by maxInclusive and minInclusive, it actually makes more sense for you to derive from xsd:int rather than xsd:long. But that's just a nit. This smells like a bug. xsd:long should map to long, not to int; but since you've derived a type, the return type should be your value type, SessionId. But I don't understand why you have two methods. Could you please post the WSDL and XSD? Anne On 8/23/06, Marius Hugo <[EMAIL PROTECTED]> wrote: > > > This is the first time that I am working with axis and I must now > migrate someone else's code > > from axis to axis2, so I'm a little clueless... > > I just have a few simple questions concerning what WSDL2Java generated: > >In ye olden xsd and wsdl: > - He declared a simple type (xs:long), " SessionId " . > - He also added restrictions (minInclusive and maxInclusive) to > that type > - He also declared that one of the responses that I send, uses > that type as a field . > - From what I've learned, all of this looks right and it worked > on the previous version of axis > > - I then used WSDL2Java to generate code: > it generated > com.company.product.webservice.types.SessionId > it also generated the Document that uses this > type > > - In the generated document, the following methods are available > (well, there are others:): > > - int getSessionId(); > - com.company.product.webservice.types.SessionId > xgetSessionId(); > > > NOW (these questions apply to both getters and setters) > > What is the difference between the two methods? > > Are the restrictions imposed on both of them? > > Why does the one method return an int, when SessionId was defined > as a long? > > If I were to go send this Document off as a SOAP message, what will > I be sending? I mean, if I say went and set both values or just the one? > Will I > be sending both values that I set, cause that doesn't really make sense > to me. > > > > Thanks, > Marius - 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]
RE: Can a web service return an XML document as a value?
Ok, so not returning an actual XML _document_, but returning XML content is alright. Thanks very much, Rich. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 12:39 To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Can a web service return an XML document as a value? Returning an XML document as an encoded string is "legal", but it doesn't always work, depending on the content in the nested document. It's always a better idea to strip off the header and just send the root element as a child of the SOAP body. Anne On 8/25/06, Richard Wild <[EMAIL PROTECTED]> wrote: > > > I'm sure this is a really dumb question, but I am completely new to > web services, and my employer suddenly requires me to implement one. > Is it acceptable for a web service to return a text value that is > actually an XML document? This would mean that the SOAP response > would actually comprise an XML document nested within an XML document. Is this legal? > > Thanks, > Rich. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can a web service return an XML document as a value?
Returning an XML document as an encoded string is "legal", but it doesn't always work, depending on the content in the nested document. It's always a better idea to strip off the header and just send the root element as a child of the SOAP body. Anne On 8/25/06, Richard Wild <[EMAIL PROTECTED]> wrote: I'm sure this is a really dumb question, but I am completely new to web services, and my employer suddenly requires me to implement one. Is it acceptable for a web service to return a text value that is actually an XML document? This would mean that the SOAP response would actually comprise an XML document nested within an XML document. Is this legal? Thanks, Rich. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP with Attachments (SwA) with Axis2, problem.
Hi,
I am trying to get SOAP monitor started on my machine following the tutorial
http://ws.apache.org/axis2/1_0/soapmonitor-module.html
But I get following exception.
2006-08-25 13:04:10,133 INFO
[org.apache.axis2.deployment.WarBasedAxisConfigurator]
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler; nested
exception is:
java.lang.ClassNotFoundException:
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler
2006-08-25 13:04:10,136 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ngaxis2]]
Servlet /ngaxis2 threw load() exception
java.lang.NullPointerException
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.(WarBasedAxisConfigurator.java:81)
To configure soapmonitor module
I have made following changes:-
axis2.xml
i)Added
ii)And appropriate phase element inside all 4 phase order elements.
One example
Services.xml
This is a sample Web Service
com.conject.ng.axis2.ProjectWebService
Copied soapmonitor.mar to the /WEB-INF/modules directory.
Am I missing something or doing wrong. Can anybody help.
Best Regards,
-Prasad
On 8/24/06, robert lazarski <[EMAIL PROTECTED]> wrote:
Try putting TCPMon or the soapmonitor on the request, post the soapenvelope the axis2 service receives, and maybe we can help.Roberthttp://www.braziloutsource.com/
On 8/24/06, Prasad Chaudhari <[EMAIL PROTECTED]> wrote:> Hi All,>> My client is having axis1.x SOAP client, who sends a file, for which I am
> suppose to write a Webservice. I have decided to use axis 2.0 for this> service.>> To get my axis 1.x SOAP client running with axis 2 SOAP Service, I was> using following tutorial.
> http://ws.apache.org/axis2/1_0/mtom-guide.html>> It says.>> "Axis2 Handles SwA messages at the inflow only. When Axis2 receives a SwA
> message it extracts the binary attachment parts and puts a reference to> those parts in the Message Context.">> I understood this as following, if I send the SOAP message with attachment
> using axis1.x client to the axis2 webservice. Axis2 will extract the binary> attachment and put an element into the xml like> > xmlns="/>
> and I can retrive this attachment from MessageContext.>> But it does not work. The OMElement which I receive as a parameter to my> serviceMethod do not have this source element into it. If I use following
> code given in tutorial.>> public OMElement echoAttachment(OMElement omEle) {> OMElement child = (OMElement) omEle.getFirstOMChild(); or OMElement child => element.getFirstChildWithName
(new QName("source"));> OMAttribute attr => child.getAttribute(new QName("href"));> String contentID = attr.getAttributeValue();> ..>>> Child element is always null(in case of both statements from the code
> snippet)>> Can somebody help me here. Tutorial says above code has been tested with> axis1.x can somebody send me the test client in axis 1.x.>> Thanks in advance.> -Prasad
>>>
Can a web service return an XML document as a value?
I'm sure this is a really dumb question, but I am completely new to web services, and my employer suddenly requires me to implement one. Is it acceptable for a web service to return a text value that is actually an XML document? This would mean that the SOAP response would actually comprise an XML document nested within an XML document. Is this legal? Thanks, Rich.
Re: How to call the given replyto address from the service?
Hi Santoso,
no, the header looks like ok. What I think is that the problems comes
from the call:
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("c:\\MyJavaStuff\\axis2",
null);
try to use the default constructor for ServiceClient (you'll need the
axis2 libs in the classpath in order to engage the addressing module)
Michele
Santoso Nugroho wrote:
> Hi Michele,
>
> The soapaction is correct, and I got AxisFault : Invalid message addition
> What is meant by "Invalid Message Addition"? is it because of the headers?
>
> here are the sample soap message sent
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
>
>
> http://localhost:8081/axis2/services/AsynchWrappedService
>
>
> http://192.168.1.22:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
>
>
>urn:uuid:C3B147D7E64C6C375111564787858281
>requestData
>
>
>http://www.example.org/AsynchWrappedService";>
> hello, this is the key
>
>
>
>
> here are the exception i got
>
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>
>
>
> soapenv:Client
> Invalid message addition , operation context
> completed
>
>
> org.apache.axis2.AxisFault: Invalid message addition ,
> operation context completed
> at
> org.apache.axis2.description.InOnlyAxisOperation.addMessageContext(InOnlyAxisOperation.java:62)
>
> at
> org.apache.axis2.context.OperationContext.addMessageContext(OperationContext.java:85)
>
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:35)
>
> at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
>
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
>
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
>
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
>
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>
> at java.lang.Thread.run(Unknown Source)
>
>
>
>
>
>
> Thanks,
>
> Santoso
>
> Michele Mazzucco wrote:
>> Hi Santoso,
>>
>> are you sure that the soap action is correct, i.e. the same declared
>> into services.xml? It should look like
>>
>>
>> >
>> class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver" />
>> requestData
>>
>>
>>
>> Are you sure that your service is called? Try to add some logging
>> statements inside your code
>>
>>
>> Hope this helps,
>> Michele
>>
>> On 24 Aug 2006, at 04:30, Santoso Nugroho wrote:
>>
>>> Hi Michele,
>>>
>>> I've change the return type, however the callback is still not called.
>>> Here is my service code :
>>> public OMElement requestData(OMElement element) {
>>>OMElement result = buildResponse(element);
>>>return result;
>>> }
>>>
>>> Here is my client code :
>>> OMElement payload = getPayload();
>>>Options options = new Options();
>>>options.setAction("requestData");
>>>options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>>>options.setUseSeparateListener(true);
>>>EndpointReference epr = new
>>> EndpointReference("http://localhost:8081/axis2/services/AsynchWrappedService";);
>>>
>>>options.setTo(epr);
>>> Callback callback = new Callback() {
>>>public void onComplete(AsyncResult
