Re: WSDL2Java throws IOException
After I renamed the namespace name to fix the issue, started getting an NPE
in Axis parser code (with both 1.2 and 1.4):
java.lang.NullPointerException
at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.getAsFieldName(JavaB
eanHelperWriter.java:435)
at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeMetaData(JavaBe
anHelperWriter.java:325)
at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeFileBody(JavaBe
anHelperWriter.java:183)
at
org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
at
org.apache.axis.wsdl.toJava.JavaBeanWriter.writeFileBody(JavaBeanWrit
er.java:257)
at
org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
at
org.apache.axis.wsdl.toJava.JavaBeanWriter.generate(JavaBeanWriter.ja
va:1406)
at
org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.ja
va:113)
at
org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(Jav
aGeneratorFactory.java:421)
at org.apache.axis.wsdl.gen.Parser.generateTypes(Parser.java:547)
at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:432)
at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362)
at java.lang.Thread.run(Unknown Source)
Thanks,
Venkatesh.
On Wed, Feb 10, 2010 at 11:33 AM, Venkatesh Audinarayanan <
venkatesh.a...@gmail.com> wrote:
> Hi All,
> Am getting the following error while trying to parse my service wsdl with
> Axis 1.2 wsdl2java:
> Feb 10, 2010 11:28:59 AM org.apache.axis.utils.JavaUtils
> isAttachmentSupported
> WARNING: Unable to find required classes (javax.activation.DataHandler and
> javax
> .mail.internet.MimeMultipart). Attachment support is disabled.
> java.io.IOException: Type {
> http://www.w3.org/2000/09/xmldsig#}SignatureProperty<http://www.w3.org/2000/09/xmldsig#%7DSignatureProperty>
> is referenced but not defined.
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
> Table.java:665)
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545
> )
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
> a:518)
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
> a:495)
> at
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
> at java.lang.Thread.run(Unknown Source)
>
> is it reporting the actual error? is this due to some issue with WSDL?
> Appreciate your help.
> Thanks,
> Venkatesh.
>
WSDL2Java throws IOException
Hi All,
Am getting the following error while trying to parse my service wsdl with
Axis 1.2 wsdl2java:
Feb 10, 2010 11:28:59 AM org.apache.axis.utils.JavaUtils
isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and
javax
.mail.internet.MimeMultipart). Attachment support is disabled.
java.io.IOException: Type {
http://www.w3.org/2000/09/xmldsig#}SignatureProperty
is referenced but not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545
)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
is it reporting the actual error? is this due to some issue with WSDL?
Appreciate your help.
Thanks,
Venkatesh.
RE: wsdl2java -R option
I use the -R option in Axis 1.5.1 and it works ok for me. However, I supply a relative path. If I try to supply an absolute path as you have here, I get a CodeGenerationException. From: rahul yadav [mailto:rahulyada...@gmail.com] Sent: Wednesday, January 27, 2010 5:07 AM To: u...@xmlbeans.apache.org; axis-user@ws.apache.org Subject: wsdl2java -R option Has anybody used -R option in wsdl2java codegeneration with xmlbeans binding, I am using Axis1.5.1 ? here is my command line... wsdl2java -uri d:\test.wsdl -d xmlbeans -o d:\src -p com.axis.test -R d:\resourceTest It throws following exception... org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException running same command without -R flag generates code successfully. Thanks, Rahul Yadav
wsdl2java -R option
Has anybody used -R option in wsdl2java codegeneration with xmlbeans binding, I am using Axis1.5.1 ? here is my command line... wsdl2java -uri d:\test.wsdl -d xmlbeans -o d:\src -p com.axis.test -R d:\resourceTest It throws following exception... org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException running same command without -R flag generates code successfully. Thanks, Rahul Yadav
How to set call properties using code generated from wsdl2java?
Hi all,
I'm using Apache Axis 1.4 (yes, the old one), with wsdl2java to
generate the client code for a webservice. I'd like to set additional
properties on the Call object before calling methods on the generated
stub.
For example, I'd like to set username, password, perhaps add or modify
existing headers, and change the client handlers to use different
implementations.
Currently, I'm doing this by modifying the generated Stub class and
calling the appropriate setters. However, I'd like to achieve this
without touching the generated files. I"m confused, though, because
the Stub class has:
createCall()
which creates the call object and sets some properties. Currently,
this is where I'm modifying the generated source code; then, the Stub
contains:
clientMethod1(){
blahblah
Call _call = createCall();
..
_call.invoke();
}
So I can't see a way that I can use the serviceLocator to get a stub,
modify the properties I want to modify, and then use the stub to call
the methods I want to call, given that the stub methods call
createCall() and then call invoke. There doesn't appear to be a way to
intercept the new Call object before it's invoked.
So: How do you modify properties in the call without modifying the
generated Stub class's source code?
In my code, I can do ((Stub) myImpl).setWhatever(); for properties
that the stub class seems to pass into the Call object (username,
password). But I can't find a way to pass client handlers, for
example, because I can't find how the Stub would pass those into the
call it creates.
Basically, I want to leave the generated files untouched but still
have control over the Call object when I need it.
Thanks for guidance.
wsdl2java generated code failed to parse a response because of a namespaceURI mismatch
Hello everyone,
I have a encountered problem for which I would need some help. The code
generated for a wsdl we wrote works correctly up to the point were the
server's response needs to be parsed. At this point, the element name
"criteria" cannot be properly parsed by xmlbeans apparently because of a
missing namespaceURI. In other words, the xml element named "criteria" is
found but since the namespaceURI is different, xmlbeans ignores it. I am
using Axis2 1.5.1 and I made sure the server side works as expected by
testing it with php's equivalent of axis2 (although it is a lot more basic).
Here is the wsdl:
http://schemas.xmlsoap.org/wsdl/"; targetNamespace="
http://www.broadsign.com/wsdl_ops"; xmlns:bstypes="
http://www.broadsign.com/wsdl_types"; xmlns:tns="
http://www.broadsign.com/wsdl_ops"; xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"; >
http://www.w3.org/2001/XMLSchema"; targetNamespace="
http://www.broadsign.com/wsdl_ops"; xmlns:bstypes="
http://www.broadsign.com/wsdl_types"; xmlns:tns="
http://www.broadsign.com/wsdl_ops"; >
http://www.broadsign.com/wsdl_types";
schemaLocation="types.xsd" />
http://schemas.xmlsoap.org/soap/http";
style="document" />
http://www.broadsign.com/criteria_mgr_list_many_v4"; style="document" />
https://server-test000.broadsign.com:10803"; />
I generated the wsdl using this command: wsdl2java -o gabi_stubs -s -d
xmlbeans -uri criteria_mgr_list_many_v4.wsdl. Here is my code snippet in
main.java:
private static void listCriteria() {
try {
RequestBody body = RequestBody.Factory.newInstance();
WsdlRequest wsdlRequest = WsdlRequest.Factory.newInstance();
RequestDocument requestDocument =
RequestDocument.Factory.newInstance();
ResponseBody response;
body.setIds("12187");
body.setDomainId("12077");
wsdlRequest.setName("criteria_mgr_list_many");
wsdlRequest.setVersion(4);
wsdlRequest.setCriteria(body);
requestDocument.setRequest(wsdlRequest);
requestDocument.documentProperties().setEncoding("utf-16");
System.out.println(requestDocument.xmlText());
try {
ResponseDocument responseDocument;
responseDocument =
m_stub.criteria_mgr_list_many_v4(requestDocument);
System.out.println(responseDocument.xmlText());
// The following line is always 0 even though the response
xml is correct.
// Internally, the xml parsing fails because a QName is
missing its namespaceURI.
System.out.println(responseDocument.getResponse().sizeOfCriteriaArray());
} catch (java.rmi.RemoteException e) {
System.out.println("Got an unkown error while executing the
operation:" + e.toString());
} catch (Criteria_mgr_list_many_v4_error e) {
System.out.println("Failed to list criteria: " +
e.getFaultMessage().getError());
}
} catch (java.lang.Exception e) {
System.out.println("Error:" + e.toString());
}
}
===
Now here is the output I get:
===
http://www.broadsign.com/wsdl_ops";>
http://www.broadsign.com/wsdl_ops"; xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/";>
0
===
The last '0' indicates that the element was not parsed properly.
However, if
Re: WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
Thanks for the update Amila! Amila Suriarachchi wrote: > > On Wed, Dec 30, 2009 at 11:07 AM, fazlan wrote: > >> >> Hi All, >> >> I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java >> ant >> task. >> But I;am having a problem when generating services.xml files. >> >> My requirement is to generate a single services.xml for all the *.wsdl's, >> rather than services.xml files for each *.wsdl file. >> >> Is this possible? >> > no unless you merge your wsdl files into into one by creating multiple > services. > > thanks, > Amila. > >> If so, Pleases provide me with a snippet of ant script how >> to achieve this. >> >> e.g: >> I need something like the following, >> >> >> >>. . . >> >> >> . . . >> >> >> >> but, at present it generates in seperate services.xml files as, >> >> services.xml for WsdlA >> >> >>. . . >> >> >> >> services.xml for WsdlB >> >> >>. . . >> >> >> >> Thanks & Regards, >> Fazlan >> -- >> View this message in context: >> http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > > -- View this message in context: http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26984018.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
On Wed, Dec 30, 2009 at 11:07 AM, fazlan wrote: > > Hi All, > > I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java > ant > task. > But I;am having a problem when generating services.xml files. > > My requirement is to generate a single services.xml for all the *.wsdl's, > rather than services.xml files for each *.wsdl file. > > Is this possible? > no unless you merge your wsdl files into into one by creating multiple services. thanks, Amila. > If so, Pleases provide me with a snippet of ant script how > to achieve this. > > e.g: > I need something like the following, > > > >. . . > > > . . . > > > > but, at present it generates in seperate services.xml files as, > > services.xml for WsdlA > > >. . . > > > > services.xml for WsdlB > > >. . . > > > > Thanks & Regards, > Fazlan > -- > View this message in context: > http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html > Sent from the Axis - User mailing list archive at Nabble.com. > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
Hi All, I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java ant task. But I;am having a problem when generating services.xml files. My requirement is to generate a single services.xml for all the *.wsdl's, rather than services.xml files for each *.wsdl file. Is this possible? If so, Pleases provide me with a snippet of ant script how to achieve this. e.g: I need something like the following, . . . . . . but, at present it generates in seperate services.xml files as, services.xml for WsdlA . . . services.xml for WsdlB . . . Thanks & Regards, Fazlan -- View this message in context: http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2Java
Yep - I guess I answered my own question of how to manage the namespace. Since I am not really interested on using the namespace on the client side other than building local directories to store the stubs, I can simple use the --package option to generate what I need. If there is any other (more efficient and correct method) out there by all means stop me ! ;) Thanks Demetris wrote: Hi all, I intercept and transport the outgoing HTTP GET request to a remote axis container/engine over a p2p overlay. I reissue the GET command using HTTP libraries on the remote side and the URL I sent always has the http://127.0.0.1:8080 in it .. however the WSDL I get back does not always (and I say does not always because it is not consistent over identical reps) contain this local address in its namespace: ex. targetNamespace="http://cypress.ne.uk:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9"; instead of ex. targetNamespace="http://127.0.0.1:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9"; etc. Why is this the case and should I force the namespace to be what I want on the client side by using the --package command as a safeguard? Thanks much Demetris
WSDL2Java
Hi all, I intercept and transport the outgoing HTTP GET request to a remote axis container/engine over a p2p overlay. I reissue the GET command using HTTP libraries on the remote side and the URL I sent always has the http://127.0.0.1:8080 in it .. however the WSDL I get back does not always (and I say does not always because it is not consistent over identical reps) contain this local address in its namespace: ex. targetNamespace="http://cypress.ne.uk:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9"; instead of ex. targetNamespace="http://127.0.0.1:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9"; etc. Why is this the case and should I force the namespace to be what I want on the client side by using the --package command as a safeguard? Thanks much Demetris
Re: axis2 1.5.1 wsdl2java --all-ports
On Thu, Dec 10, 2009 at 12:34 PM, Alex wrote: > hi all, > > as I read on the web, there is no posibility to generate server skeleton > from an wsdl which has multiple ports defined, is this correct? > yes. > > Is there an other possibility to combine all ports in one webService, or is > it better to generate one service for each port. please try using one portType per service. thanks, Amila. > > > here is my ant-task > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > as you can see i use the -ap or --all-ports option but only one port is > generatet. > > I am using axis2 1.5.1 and tomcat 6.0.20 > > > thank you, so long alex > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: axis2 1.5.1 wsdl2java --all-ports
hi all, as I read on the web, there is no posibility to generate server skeleton from an wsdl which has multiple ports defined, is this correct? Is there an other possibility to combine all ports in one webService, or is it better to generate one service for each port. here is my ant-task as you can see i use the -ap or --all-ports option but only one port is generatet. I am using axis2 1.5.1 and tomcat 6.0.20 thank you, so long alex
axis2 1.5.1 wsdl2java --all-ports
hi all, i have a wsdl with 3 ports defined, when I build the service skleton with wsdl2java i only get one port. here is my ant-task as you can see i use the -ap or --all-ports option but only one port is generatet do you have any idea, is it a bug? thank you, so long alex
Re: Problems running wsdl2java, with MathML schema
Hi
Even more info, jaxb handling of this is described here[1], so I guess I can
use jaxb as biniding for this service if adb does not support this tyype of
schema.
Håkon
[1]http://weblogs.java.net/blog/kohsuke/archive/2006/03/simple_and_bett.html
2009/11/26 Håkon Sagehaug
> Hi all,
>
> Just to add more information, I also tried with jixb then I got several
> error messages like the one below, just with different groups involved
>
> ERROR codegen.CodeGen - Error: Referenced group '{
> http://www.w3.org/1998/Math/MathML}:Content-expr.class<http://www.w3.org/1998/Math/MathML%7D%3AContent-expr.class>'
> is not defined for 'group' at (line 104, col 41, in
> http://www.w3.org/Math/XMLSchema/mathml2/content/statistics.xsd)
>
> cheers, Håkon
>
>
> 2009/11/25 Håkon Sagehaug
>
> Hi all,
>>
>> I've developing a service that uses the MathML schema for something, but
>> when I try to run wsdl2java(axis2 1.5) like this
>>
>> wsdl2java.sh -uri SbmlService.wsdl -d adb
>>
>> using I always get this error
>>
>> Caused by: org.apache.axis2.schema.SchemaCompilationException: Can not
>> find the group with the qname{
>> http://www.w3.org/1998/Math/MathML}Presentation-token.class<http://www.w3.org/1998/Math/MathML%7DPresentation-token.class>from
>> the parent schema
>> http://www.w3.org/1998/Math/MathML
>>
>> Is there something with the schema that adb does not support here, the
>> group Presentation-token looks like this in it's schema[1]
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> I know that adb may not support the hole xml schema, but I'd like to use
>> adb instead of xml beans, so was wondering if anyone else had ssen this
>> error before.
>>
>> cheers, Håkon
>>
>> [1] http://www.w3.org/Math/XMLSchema/mathml2/presentation/tokens.xsd
>>
>> --
>> Håkon Sagehaug, Scientific Programmer
>> Parallab, Bergen Center for Computational Science
>> hakon.sageh...@uni.no, phone +47 55584125
>>
>
>
>
> --
> Håkon Sagehaug, Scientific Programmer
> Parallab, Bergen Center for Computational Science(BCCS)
> Uni BCCS/Uni Research
>
> hakon.sageh...@uni.no, phone +47 55584125
>
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
Re: Problems running wsdl2java, with MathML schema
Hi all,
Just to add more information, I also tried with jixb then I got several
error messages like the one below, just with different groups involved
ERROR codegen.CodeGen - Error: Referenced group '{
http://www.w3.org/1998/Math/MathML}:Content-expr.class' is not defined for
'group' at (line 104, col 41, in
http://www.w3.org/Math/XMLSchema/mathml2/content/statistics.xsd)
cheers, Håkon
2009/11/25 Håkon Sagehaug
> Hi all,
>
> I've developing a service that uses the MathML schema for something, but
> when I try to run wsdl2java(axis2 1.5) like this
>
> wsdl2java.sh -uri SbmlService.wsdl -d adb
>
> using I always get this error
>
> Caused by: org.apache.axis2.schema.SchemaCompilationException: Can not find
> the group with the qname{
> http://www.w3.org/1998/Math/MathML}Presentation-token.class<http://www.w3.org/1998/Math/MathML%7DPresentation-token.class>from
> the parent schema
> http://www.w3.org/1998/Math/MathML
>
> Is there something with the schema that adb does not support here, the
> group Presentation-token looks like this in it's schema[1]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I know that adb may not support the hole xml schema, but I'd like to use
> adb instead of xml beans, so was wondering if anyone else had ssen this
> error before.
>
> cheers, Håkon
>
> [1] http://www.w3.org/Math/XMLSchema/mathml2/presentation/tokens.xsd
>
> --
> Håkon Sagehaug, Scientific Programmer
> Parallab, Bergen Center for Computational Science
> hakon.sageh...@uni.no, phone +47 55584125
>
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
Problems running wsdl2java, with MathML schema
Hi all,
I've developing a service that uses the MathML schema for something, but
when I try to run wsdl2java(axis2 1.5) like this
wsdl2java.sh -uri SbmlService.wsdl -d adb
using I always get this error
Caused by: org.apache.axis2.schema.SchemaCompilationException: Can not find
the group with the qname{
http://www.w3.org/1998/Math/MathML}Presentation-token.class from the parent
schema http://www.w3.org/1998/Math/MathML
Is there something with the schema that adb does not support here, the group
Presentation-token looks like this in it's schema[1]
I know that adb may not support the hole xml schema, but I'd like to use
adb instead of xml beans, so was wondering if anyone else had ssen this
error before.
cheers, Håkon
[1] http://www.w3.org/Math/XMLSchema/mathml2/presentation/tokens.xsd
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science
hakon.sageh...@uni.no, phone +47 55584125
Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (wsdl2java)
Hi, we upgrade from Axis2 1.4.1 to 1.5.1. We have successfully upgraded the server side, now we try to upgrade the client. We use wsdl2java to generate the java code. The code to generate the java is as follows: ..org.apache.axis2.wsdl.WSDL2Java -t -p test.services.client.upload -uri http://localhost:8080/test/services/Upload?wsdl We use following code to call the generated code: // Get the service binding ...client.upload.UploadStub stub = new upload.UploadStub(); // Get a handle to the Upload stub - Prepare operation client.upload.UploadStub.Upload operation = (client.upload.UploadStub.Upload) demo_getADBBean(client.upload.UploadStub.Upload.class); // Get document ... // Call the webservice // Note: datdataHandler automatically seritalies the content in Base64 String DataSource dataSource = new ByteArrayDataSource( uploadedfile.toByteArray(), "application/octet-stream"); DataHandler dataHandler = new DataHandler(dataSource); operation.setPdfdocument(dataHandler); ... We noticed that the generated soap is missing its headers: http://www.w3.org/2003/05/soap-envelope";> http://services.test.be";> ...JV...Qo= Does something more needs to be done compared with version 1.4.1 ? Regards, S. -- View this message in context: http://old.nabble.com/Problem-upgrading-from-Axis2-Java-1.4.1-to-1.5.1--%28wsdl2java%29-tp26197986p26197986.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: wsdl2java and Two Similar Elements
When I use Axis2, I get a whole host of other problems. With Axis 1.4 (what I am currently using) I get the behavior described in my original post. Thanks Matthew McKenna mtmckenna...@mac.com On Thursday, October 29, 2009, at 03:09AM, "Amila Suriarachchi" wrote: >
Re: wsdl2java and Two Similar Elements
On Thu, Oct 29, 2009 at 12:28 PM, Matthew McKenna wrote:
> Hello-
>
> I have a WSDL file that imports several XML schemas. One of those schemas
> has the following:
>
>
>
>
>
>
>
>
>
> followed very closely by:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> In order to generate the appropriate Java code, I am using the following in
> my build.xml file:
>
> classname="org.apache.axis.tools.ant.wsdl.Wsdl2javaAntTask">
>
>
>
>
>
>output="generated/src"
>serverSide="false"
>all="true"
> wraparrays="true"
>verbose="true">
> package="${A-package-name}"/>
> package="${services-package-name}"/>
> package="${exchange-package-name}"/>
> package="${types-package-name}"/>
>
>
>
>
> The problem I am running in to is that wsdl2java generates a ITEMID.java
> file, but the class declaration
> and constructor are ItemId. All references to the ITEMID object in other
> generated code 'cannot be resolved'.
>
> My question - Is there some way I can generate the two item id objects?
>
> Thanks very much for any assistance.
>
this seems to be a problem with ADB. please log a jira with your wsdl file.
try with another databinding framework eg -d xmlbeans, -d jaxbri
thanks,
Amila.
>
> Matthew McKenna
> mtmckenna...@mac.com
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
wsdl2java and Two Similar Elements
Hello- I have a WSDL file that imports several XML schemas. One of those schemas has the following: followed very closely by: In order to generate the appropriate Java code, I am using the following in my build.xml file: The problem I am running in to is that wsdl2java generates a ITEMID.java file, but the class declaration and constructor are ItemId. All references to the ITEMID object in other generated code 'cannot be resolved'. My question - Is there some way I can generate the two item id objects? Thanks very much for any assistance. Matthew McKenna mtmckenna...@mac.com
A question about the stub binding class from the WSDL2Java generated code
Hello to whoever cares to answer me to this question,
I recently started to work in a team that is meant to give support to some java
web applications in a production environment. The framework is JAVA2EE with
usage of your axis packages to provide the web services. In the following a
debugging incursion to the code, I found myself looking to the code of the
binding stub class generated by the WSDL2Java tool - version 1.4 - specificaly
the implemented method from the portType interface. In this file
servicemaneSoapBindingStub.java, at lines 104 and 105, I find the following:
94: org.apache.axis.client.Call _call = createCall();
...
try{
104: java.lang.Object _resp = _call.invoke(new
java.lang.Object[] {parameterStringRequest});
105: if (_resp instanceof java.rmi.RemoteException) {
My question is the following:
After examining the code from the class org.apache.axis.client.Call, I've got
under the impression that the method invoke from class
org.apache.axis.client.Call may throw exceptions from class
java.rmi.RemoteException but never returns an object from this Exception
class. Am i right? If so, is this a problem for the stub class code?
Looking forward to hear from you,
---
João Manuel Roseira Borges
Suporte Aplicacional TAP/Megasis
Ed19 - Piso 2 - Sala 24
extensão 36108
RE: wsdl2java issue when parsing wsdl that uses empty namespaces
Hi Sean,
You could change PhoneType to string
You lose the restriction on the possible values, but at least the SOAP agent
will work.
Your application that calls the Axis generated classes could handle the
phone type value check.
You are using the 22 April 2006 version of Axis 1.4, you could look at using
a later over-night build.
I have used 19 November 2006 Axis 1.4 for several years.
http://people.apache.org/dist/axis/nightly/
<http://people.apache.org/dist/axis/nightly/>
axis-bin-1_4.zip 19-Nov-2006 02:33 11M
-Original Message-
From: Sean O'Leary [mailto:razorho...@gmail.com]
Sent: Friday, 16 October 2009 5:00 AM
To: axis-user@ws.apache.org
Subject: wsdl2java issue when parsing wsdl that uses empty namespaces
Hi everyone,
Using: Axis version 1.4 (4/22/2006)
I'm using wsdl2java to compile a wsdl for a service that one of my customers
has provided. Everything is fine except for they have one type that they
have declared in a separate schema in the wsdl with no targetNamespace and
then they refer to that type from another schema without putting anything in
for the namespace prefix. This seems to be "valid" wsdl (using no namespace)
but wsdl2java throws the following exception:
java.io.IOException: Type PhoneType is referenced but not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545
)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Here's the offending WSDL snippet:
http://schemas.xmlsoap.org/wsdl/soap/
<http://schemas.xmlsoap.org/wsdl/soap/> " xmlns:tm="
http://microsoft.com/wsdl/mime/textMatching/
<http://microsoft.com/wsdl/mime/textMatching/> " xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/
<http://schemas.xmlsoap.org/soap/encoding/> " xmlns:mime="
http://schemas.xmlsoap.org/wsdl/mime/
<http://schemas.xmlsoap.org/wsdl/mime/> " xmlns:tns="
http://services.xyzcompany.com <http://services.xyzcompany.com> " xmlns:s="
http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema> "
xmlns:soap12=" http://schemas.xmlsoap.org/wsdl/soap12/
<http://schemas.xmlsoap.org/wsdl/soap12/> " xmlns:http="
http://schemas.xmlsoap.org/wsdl/http/
<http://schemas.xmlsoap.org/wsdl/http/> " targetNamespace="
http://services.xyzcompany.com <http://services.xyzcompany.com> "
xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/
<http://schemas.xmlsoap.org/wsdl/> ">
http://services.xyzcompany.com <http://services.xyzcompany.com> ">
If I add targetNamespace=" http://services.xyzcompany.com
<http://services.xyzcompany.com> " to the 2nd schema and then prefix the
type="PhoneType" so it is type="tns:PhoneType", wsdl2java is able to compile
the wsdl. Then the problem is of course as soon as I use the generated code
to connect to the service it errors out as axis complains about the same
issue with the service's wsdl.
Any help you can provide is very much appreciated.
Thanks!
Sean
wsdl2java issue when parsing wsdl that uses empty namespaces
Hi everyone, Using: Axis version 1.4 (4/22/2006) I'm using wsdl2java to compile a wsdl for a service that one of my customers has provided. Everything is fine except for they have one type that they have declared in a separate schema in the wsdl with no targetNamespace and then they refer to that type from another schema without putting anything in for the namespace prefix. This seems to be "valid" wsdl (using no namespace) but wsdl2java throws the following exception: java.io.IOException: Type PhoneType is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol Table.java:665) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545 ) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Unknown Source) Here's the offending WSDL snippet: http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime=" http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:tns=" http://services.xyzcompany.com"; xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:http=" http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace=" http://services.xyzcompany.com"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/ "> http://services.xyzcompany.com";> If I add targetNamespace="http://services.xyzcompany.com"; to the 2nd schema and then prefix the type="PhoneType" so it is type="tns:PhoneType", wsdl2java is able to compile the wsdl. Then the problem is of course as soon as I use the generated code to connect to the service it errors out as axis complains about the same issue with the service's wsdl. Any help you can provide is very much appreciated. Thanks! Sean
Re: wsdl2java and wsdl problem
Dear Anne, I need to expose java web services. I am using Axis1.4, Java 1.5 and Tomcat 5.0 for exposing services. SOAP request and SOAP response have 'authentication' tag in SOAP header. SOAP Request - UserName Password ... -- SOAP response - XXUserName XXPassword 2007B By seeing the SOAP message structure, we have decided to add SOAP header explicitly in WSDL. We are NOT able to differentiate between SOAP request and SOAP response 'authentication' tag in WSDL. We have attempted to solve the above problem by creating 2 different type of WSDL. Please have look into these wsdl. WSDL-1 : http://test.com"; xmlns:tns="http://test.com"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://test.com";> http://schemas.xmlsoap.org/soap/http"; /> http://localhost:8080/hello-service/hello-service"/> WSDL-2 : http://test.com"; xmlns:tns="http://test.com"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://test.com";> http://schemas.xmlsoap.org/soap/http"; /> http://localhost:8080/hello-service/hello-service"/> Please advise. Regards, Santosh Anne Thomas Manes wrote: > > The type declaration is valid. > > indicates that the element may contain one of the elements > listed in the choice group. The minOccurs="0" attribute indicates that > the element is optional. It is not intended to be an array; therefore, > it would be inappropriate to say maxOccurs="unbounded". > > Anne > > > On Fri, Sep 12, 2008 at 12:04 AM, Shehan Simen > wrote: >> Hi, >> >> I have a question about wsdl. The wsdl2java fails in following case. But >> I >> feel the wsdl is wrong. >> >> I got the following element in a complex type. >> >> >> >> >> >> >> >> >> >> >> >> >> >> > type="tns:IndividualName" minOccurs="0"/> >> >> > type="
Re: Axis2 wsdl2java jibx: No mapping defined for element
Hi, you need to check the binding.xml file and verify there is a correct
mapping defined for ElementName. There should be an entry like this:
http://sample/types"/>
The element name and namespace in the binding file needs to match the WSDL
definition.
Anshuk Pal Chaudhuri-2 wrote:
>
> Hello,
>
> Mentioned an incorrect subject line in my earlier mail. My applogies.
>
> I am trying to integrate axis2 1.5 with jibx 1.2.1.
> I am not sure that is a problem with axis2 or jibx.
> I have the wsdl file and the schema with me.
> I have used the jibx org.jibx.schema.codegen.CodeGen to generate the
> objects & the binding file from the schema.
> I then enhance the classes using the jibx binding compiler way.Uptil now
> all fine.
>
> Then when am trying to generate server side skeletons using:
>
> org.apache.axis2.wsdl.WSDL2Java -uri Service.wsdl -d jibx -Ebindingfile
> binding.xml -s -ss -sd -scn ServiceName
> referring
> http://ws.apache.org/axis2/1_1_1/jibx/jibx-codegen-integration.html#wsdl
> I am getting errors.
>
> The stacktrace:
>
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen..CodeGenerationException
>> java.lang.RuntimeException: No mapping defined for element
>> {http://sample/types
> }ElementName
>
> I am not sure where I went wrong, also I did find it being mentioned in
> quite a few number of places such as,
> http://marc.info/?l=axis-user&m=117028406518758&w=2
>
> But I really did not find any solution, I think somebody has got some
> workaround for this.
> If I use jaxb instead of jibx, it works fine, there is not binding file in
> such a case, is the generated the binding file in correct, I am not really
> sure so hinting at different things.
> Can anyone help in some workaround.
>
>
> Regards,
> Anshuk
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/Axis2-wsdl2java-jibx%3A-No-mapping-defined-for-element-tp25603967p25668398.html
Sent from the Axis - User mailing list archive at Nabble.com.
Axis2 wsdl2java jibx: No mapping defined for element
Hello,
Mentioned an incorrect subject line in my earlier mail. My applogies.
I am trying to integrate axis2 1.5 with jibx 1.2.1.
I am not sure that is a problem with axis2 or jibx.
I have the wsdl file and the schema with me.
I have used the jibx org.jibx.schema.codegen.CodeGen to generate the objects &
the binding file from the schema.
I then enhance the classes using the jibx binding compiler way.Uptil now all
fine.
Then when am trying to generate server side skeletons using:
org.apache.axis2.wsdl.WSDL2Java -uri Service.wsdl -d jibx -Ebindingfile
binding.xml -s -ss -sd -scn ServiceName
referring
http://ws.apache.org/axis2/1_1_1/jibx/jibx-codegen-integration.html#wsdl
I am getting errors.
The stacktrace:
Exception in thread "main"
org.apache.axis2.wsdl.codegen..CodeGenerationException
> java.lang.RuntimeException: No mapping defined for element
> {http://sample/types
}ElementName
I am not sure where I went wrong, also I did find it being mentioned in quite a
few number of places such as,
http://marc.info/?l=axis-user&m=117028406518758&w=2
But I really did not find any solution, I think somebody has got some
workaround for this.
If I use jaxb instead of jibx, it works fine, there is not binding file in such
a case, is the generated the binding file in correct, I am not really sure so
hinting at different things.
Can anyone help in some workaround.
Regards,
Anshuk
Re: HTTP Authentication with Axis 1.4 (using wsdl2java ADB)
On Fri, Sep 11, 2009 at 1:19 PM, Nicolas Raoul < nicolas.raoul.li...@gmail.com> wrote: > Thank you Prabath! > But this sample is not what a wsdl2java user would do, right? > > This sample is doing AXIOM stuff manually, which I should not do since > wsdl2java generated me some convenient object-oriented classes to use. > And the classes wsdl2java generated do not seem to have any method > that I could use to feed them an Authenticator or Properties object. > even with the generated stub you can get the service client object and set the properties. thanks, Amila. > > Thanks anyway, > Nicolas Raoul. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: HTTP Authentication with Axis 1.4 (using wsdl2java ADB)
Thank you Prabath! But this sample is not what a wsdl2java user would do, right? This sample is doing AXIOM stuff manually, which I should not do since wsdl2java generated me some convenient object-oriented classes to use. And the classes wsdl2java generated do not seem to have any method that I could use to feed them an Authenticator or Properties object. Thanks anyway, Nicolas Raoul.
Re: WSDL2Java tool generating invalid package name
> > Hi, > Am using Axis 1.4 version. Have attached the WSDL file. > I use the following command to generate proxy and stub classes > java org.apache.axis.wsdl.WSDL2Java -o > C:\ddrive\10.3\soap_test\axis14_latest\axis-1_4\sigan c:\Sigan.wsdl > > If you look at the attached WSDL (Rename file extension to zip and unzip) > , the namespace is not an URL. It's like relative directory path > "br/com/vivo/sigan/integracao/schema/interface8/pesquisa/PesquisaMSISDNXMLEntrada". > > > If you look at the package declarations/package member references in the > generated classes, you will find that, it uses "/" as package name separator > i.e., package > br/com/vivo/sigan/integracao/schema/interface8/PesquisaEntradaMSISDN; > due to this, the classes don't get compiled.. > I don't want to explicitly specify package name using "-p" option as this > leads to other issues. > is there any solution for this issue? > Please advise. > Appreciate your quick reply. > Thanks, > Venkatesh. > > Sigan.zap Description: Binary data
WSDL2Java tool generating invalid package name
Hi, Am using Axis 1.4 version. Have attached the WSDL file. I use the following command to generate proxy and stub classes java org.apache.axis.wsdl.WSDL2Java -o C:\ddrive\10.3\soap_test\axis14_latest\axis-1_4\sigan c:\Sigan.wsdl If you look at the attached WSDL (Rename file extension to zip and unzip) , the namespace is not an URL. It's like relative directory path "br/com/vivo/sigan/integracao/schema/interface8/pesquisa/PesquisaMSISDNXMLEntrada". If you look at the package declarations/package member references in the generated classes, you will find that, it uses "/" as package name separator i.e., package br/com/vivo/sigan/integracao/schema/interface8/PesquisaEntradaMSISDN; due to this, the classes don't get compiled.. I don't want to explicitly specify package name using "-p" option as this leads to other issues. is there any solution for this issue? Please advise. Appreciate your quick reply. Thanks, Venkatesh. Sigan.zap Description: Binary data
Re: [axis2] posisble to set namespace prefixes in wsdl2java?
Odd but understandable request (it's much easier to read a file if the ns's are human-readable). If you're using wsdl2java, you probably already have a wsdl, so you can use that! You can simply go into your META-INF/services.xml and set useOriginalwsdl to true (note the odd capitlization). Make sure that whatever wsdl you are using for deployment is named the same as the .aar file (or maybe that should be - make sure your .aar file has the same name as the wsdl). Also make sure to put the WSDL and any related XSDs in the META-INF folder. Charles Koppelman DrFirst.com On Fri, Aug 28, 2009 at 2:20 PM, Hegerich, Robert L, JR (Bob) < heger...@alcatel-lucent.com> wrote: > Is there a way to invoke wsdl2java so that instead of the default namespace > prefixes (ns1, ns2, etc.) you can specify the namespace prefix for a > namespace? We're replacing a gSOAP server with Apache Axis (2.1.3) and the > client insists that the namespace prefixes be kept the same for some unknown > reason. > > I see the Qname() constructor does allow for prefix selection but nothing > in command line seems to invoke it. Perhaps something in -E? > > K.R. >Bob H.=
[axis2] posisble to set namespace prefixes in wsdl2java?
Is there a way to invoke wsdl2java so that instead of the default namespace prefixes (ns1, ns2, etc.) you can specify the namespace prefix for a namespace? We're replacing a gSOAP server with Apache Axis (2.1.3) and the client insists that the namespace prefixes be kept the same for some unknown reason. I see the Qname() constructor does allow for prefix selection but nothing in command line seems to invoke it. Perhaps something in -E? K.R. Bob H.=
wsdl2java ant task timeout problem
Hello, I have a problem about ant-wdsl2java task parameter "timeout". I have set timeout while wsdl2java convert. My client connect to server, send to data but server doesn't send data (to be occur timeout) but, there is nothing to happen. Client wait forever. When I set timeout parameter from java code _stub.setTimeout(1); client throw exception after 10 seconds. Is there a problem about ant-wsdl2java task timeout parameter or I missunderstand to timeout parameter. Thanks.. My ant task is below .
Re: WSDL2Java header creation issues
Hi Swapna,
Thanks for you response.
**I am doing something like this:
WebServiceLocator service = new WebServiceLocator();
WebServiceSoap_PortType portType = null;
try {
portType = service.getWebServiceSoap();
service.setWebServiceSoapEndpointAddress(address);
((Stub)portType).setUsername("java");
((Stub)portType).setPassword("sun");
ConsumptionHistoryDetails chd = new
ConsumptionHistoryDetails(1234);
ConsumptionHistoryDetailsResponse response =
portType.getConsumptionHistoryDetails(chd);
System.out.println("request :
"+service.getCall().getMessageContext().getRequestMessage().getSOAPPartAsString());
}catch(Exception e){
e.printStackTrace();
}
looks like I am not able to connect to the service. Could you please let me
know if I am missing something?
Thanks,
Samanth.
On Wed, Aug 12, 2009 at 2:56 PM, sksalver wrote:
>
> add the following where it says "_resp = _call.invoke" in your stub class
>
>
>
> //*
>
>inputXML =
> _call.getMessageContext().getRequestMessage().getSOAPPartAsString();
>outputXML =
> _call.getMessageContext().getResponseMessage().getSOAPPartAsString();
>
>
>
> //*
>
> samanth marisetty wrote:
> >
> > Hi,
> >
> > I tried to do this.
> >
> > header.addChildElement("userID").addTextNode("java");
> > header.addChildElement("userPwd").addTextNode("sun");
> > ((Stub) portType).setHeader(header);
> >
> > but the problem is, I get a null response back from the service. I used a
> > tool called SoapUI to call the service, I was getting back the response.
> > Is
> > there a way to see what SOAP xml request is being sent? I mean a way to
> > log
> > or do a standard out?
> >
> > Thanks,
> > Samanth.
> >
> > On Wed, Aug 12, 2009 at 1:51 PM, sksalver wrote:
> >
> >>
> >> You can use axis client stub class methos set header to do this.
> >>
> >> Thanks,
> >> Swapna
> >>
> >> samanth marisetty wrote:
> >> >
> >> > Hi,
> >> >
> >> >I am using WSDL2Java to create java stubs and want to write a
> >> client.
> >> I
> >> > wanted to know if there is any argument that I need to use, to
> generate
> >> > the
> >> > headers.
> >> >
> >> > Thanks,
> >> > Samanth.
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24941612.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24942634.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
Re: WSDL2Java header creation issues
add the following where it says "_resp = _call.invoke" in your stub class
//*
inputXML =
_call.getMessageContext().getRequestMessage().getSOAPPartAsString();
outputXML =
_call.getMessageContext().getResponseMessage().getSOAPPartAsString();
//*
samanth marisetty wrote:
>
> Hi,
>
> I tried to do this.
>
> header.addChildElement("userID").addTextNode("java");
> header.addChildElement("userPwd").addTextNode("sun");
> ((Stub) portType).setHeader(header);
>
> but the problem is, I get a null response back from the service. I used a
> tool called SoapUI to call the service, I was getting back the response.
> Is
> there a way to see what SOAP xml request is being sent? I mean a way to
> log
> or do a standard out?
>
> Thanks,
> Samanth.
>
> On Wed, Aug 12, 2009 at 1:51 PM, sksalver wrote:
>
>>
>> You can use axis client stub class methos set header to do this.
>>
>> Thanks,
>> Swapna
>>
>> samanth marisetty wrote:
>> >
>> > Hi,
>> >
>> >I am using WSDL2Java to create java stubs and want to write a
>> client.
>> I
>> > wanted to know if there is any argument that I need to use, to generate
>> > the
>> > headers.
>> >
>> > Thanks,
>> > Samanth.
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24941612.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24942634.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2Java header creation issues
Hi,
I tried to do this.
header.addChildElement("userID").addTextNode("java");
header.addChildElement("userPwd").addTextNode("sun");
((Stub) portType).setHeader(header);
but the problem is, I get a null response back from the service. I used a
tool called SoapUI to call the service, I was getting back the response. Is
there a way to see what SOAP xml request is being sent? I mean a way to log
or do a standard out?
Thanks,
Samanth.
On Wed, Aug 12, 2009 at 1:51 PM, sksalver wrote:
>
> You can use axis client stub class methos set header to do this.
>
> Thanks,
> Swapna
>
> samanth marisetty wrote:
> >
> > Hi,
> >
> >I am using WSDL2Java to create java stubs and want to write a client.
> I
> > wanted to know if there is any argument that I need to use, to generate
> > the
> > headers.
> >
> > Thanks,
> > Samanth.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24941612.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
Re: WSDL2Java header creation issues
You can use axis client stub class methos set header to do this. Thanks, Swapna samanth marisetty wrote: > > Hi, > > I am using WSDL2Java to create java stubs and want to write a client. I > wanted to know if there is any argument that I need to use, to generate > the > headers. > > Thanks, > Samanth. > > -- View this message in context: http://www.nabble.com/WSDL2Java-header-creation-issues-tp24940347p24941612.html Sent from the Axis - User mailing list archive at Nabble.com.
WSDL2Java header creation issues
Hi, I am using WSDL2Java to create java stubs and want to write a client. I wanted to know if there is any argument that I need to use, to generate the headers. Thanks, Samanth.
Calling WSDL2Java from Java class inside eclipse plugin
Hi,
I'm currently working on an eclipse plugin allowing me to right-click a
WSDL file in a project and following, to generate the WS stubs by
selecting a menu item which triggers the code generation (actually, the
same as wsdl2java on the command line).
I'm facing no errors are any similar stuff, but every time I want to
generate some code, only the needed build.xml file is generated, no
errors or exceptions are thrown.
For the ease of understanding I will post party of the source:
Map optionsMap =
initializeGeneratorProperties();
AxisService service = WSAdapterGeneratorUtil
.getAxisService(WSDLFile);
CodeGenConfiguration codegenConfig = new
CodeGenConfiguration(
optionsMap);
codegenConfig.setAxisService(service);
WSDLReader reader = WSDLFactory.newInstance()
.newWSDLReader();
codegenConfig.setWsdlDefinition(reader.readWSDL(WSDLFile));
codegenConfig.setBaseURI(WSAdapterGeneratorUtil
.getBaseUri(WSDLFile));
new CodeGenerationEngine(codegenConfig).generate();
The above excerpt shows from my point of view the proper way of doing so
(generating code). Below is the source of the
initializeGeneratorProperties(); method, maybe I'm forgetting about some
options in the optionsMap:
Map optionsMap = new HashMap();
optionsMap.put("uri", new CommandLineOption("uri",
new String[] { WSDLFile }));
optionsMap.put("p", new CommandLineOption("p",
new String[] { "at.sample.path" }));
optionsMap
.put("l", new CommandLineOption("l", new String[] {
"java" }));
optionsMap
.put("o", new CommandLineOption("o", new String[] {
genDir }));
optionsMap.put("d", new CommandLineOption("d",
new String[] { "xmlbeans" }));
optionsMap.put("pn", new CommandLineOption("pn",
new String[] { "Soap" }));
Well, as this code is error free (in case of exceptions and errors, I
hope to get some useful help quite soon, as for me, I can't figure out
the small bug or misconfiguration or what else leads to this strange
behaviour, that I won't get any classes to be generated.
Thanks a lot in advance,
Philipp
wsdl2java generates generic OMElement MessageReceiverInOut
When I run wsdl2java, I get a MessageReceiverInOut generated with one toEnvelope() method and one toOM(). This toOM method returns a OMElement and the receiver method that calls it uses OMElement.class as the "cast this to" parameter for all messages. This will only allow me to parse the first data point in my message. I have seen other code that seems to autogenerate a separate toOM method for each message type, a separate toEnvelope for each request, and uses different classes in the "cast this to" parameter. My current plan is to do this all by hand, but there must be a better way. How do I get wsdl2java to do that for me? Thank you so much, Charles
wsdl2java - targetNamespace becomes "default package" (no package) in eclipse
Hi, I currently try to generate server code for a wsdl-File I got from another person. In this wsdl-File it seems that all the defined elements without explicit NS-Prefixes (those which maps to the target namespace then?) are getting no package definition in java after code generation. Is there a way to avoid this? I don't like Java-Classes without package definition. Regards, Martin
Re: WSDL2Java: Different class mappings of nested complex types with identical names with JDKs of different vendors.
Norman, Can you open a JIRA for this issue? Thanks. Andreas On Fri, Jul 31, 2009 at 11:32, Norman Kubicek wrote: > Hi, > > > > we run in to some problems developing an Axis2 v1.5 Web service client with > SUN JDK 6 (different platforms) and IBM JDK 6 (PowerPC Linux) in parallel. > > The WSDL of the Web service contains following nested type definitions with > identical names: > > > > … > > > > > > > > > > > > name="key" type="xsd:string"/> > > name="value" type="xsd:string"/> > > > > > > > > > > > > > > > > > > > > > > > > name="key" type="xsd:anyType"/> > > name="value" type="xsd:anyType"/> > > > > > > > > > > > > … > > > > As result the WSDL2Java tool generates inner or separate classes (depends on > –u command line option) for the “entry” type definitions with the following > names: > > > > Entry_type0.java > > Entry_type1.java > > > > The problem is the order the Entry_type*.java classes are created, i.e. > Entry_type0.java belongs to the string2stringMap class in the SUN JDK, but > to the anyType2anyTypeMap class in the IBM JDK. As result source code that > accesses these classes is affected and has to be adapted for the JDKs of > both vendors. > > > > Is there any fix or workaround for this issue? > > > > Regards, > > Norman Kubicek > > > > > > > > > >
WSDL2Java: Different class mappings of nested complex types with identical names with JDKs of different vendors.
Hi, we run in to some problems developing an Axis2 v1.5 Web service client with SUN JDK 6 (different platforms) and IBM JDK 6 (PowerPC Linux) in parallel. The WSDL of the Web service contains following nested type definitions with identical names: ... ... As result the WSDL2Java tool generates inner or separate classes (depends on -u command line option) for the "entry" type definitions with the following names: Entry_type0.java Entry_type1.java The problem is the order the Entry_type*.java classes are created, i.e. Entry_type0.java belongs to the string2stringMap class in the SUN JDK, but to the anyType2anyTypeMap class in the IBM JDK. As result source code that accesses these classes is affected and has to be adapted for the JDKs of both vendors. Is there any fix or workaround for this issue? Regards, Norman Kubicek
Re: WSDL2Java StringIndexOutOfBoundException
Ok, I've found the cause of the problem. It seems to be a problem with Axis2 1.5 itself. I've tried to build a service out of different wsdl files and got the same error every time - also with a file originally generated by Axis2 once. I've switched to version 1.4.1 and everything is fine now. Greetings, Tina Hi everyone, I try to generate a service out of my wsdl file. Unfortunately, I get a exception I can't interpret. Does anyone have an idea what could be the cause? Greetings, Tina Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:159) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1938) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.getBaseURI(CodeGenerationEngine.java:341) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:151) ... 2 more
WSDL2Java StringIndexOutOfBoundException
Hi everyone, I try to generate a service out of my wsdl file. Unfortunately, I get a exception I can't interpret. Does anyone have an idea what could be the cause? Greetings, Tina Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:159) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1938) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.getBaseURI(CodeGenerationEngine.java:341) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:151) ... 2 more
RE: Axis2 1.5 WSDL2Java errors
My portType tag will now work but only if I leave the default one in as well --> It does give me the error again though when I put in the wsdl:port tag under wsdl:service. Does anyone see anything wrong with this? -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24380646.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
I'm getting all of these errors running WSDL2Java from the 1.5 bin. -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24373563.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
that is a AXIS-1_4 artifact you need to run WSDL2JAVA from %Axis2_1.5%/bin and not %AXIS-1_4/bin% Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Mon, 6 Jul 2009 11:54:24 -0700 > From: leftoverlingu...@gmail.com > To: axis-user@ws.apache.org > Subject: RE: Axis2 1.5 WSDL2Java errors > > > I'm able to generate code up until I change the wsdl:porttype tag. > > > jcaristi wrote: > > > > Your command is OK. Are you importing a WSDL 2 document? I not sure you > > can import WSDL 2.0 from within WSDL 1.1. Try removing this import. If > > this doesn't work, you could try a very small simple WSDL (sample > > attached) and see if you can generate code. If it works, you could start > > from there, adding one feature at a time. > > > > -- > View this message in context: > http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24360939.html > Sent from the Axis - User mailing list archive at Nabble.com. > _ Windows Live™ SkyDrive™: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009
RE: Axis2 1.5 WSDL2Java errors
I'm able to generate code up until I change the wsdl:porttype tag. jcaristi wrote: > > Your command is OK. Are you importing a WSDL 2 document? I not sure you > can import WSDL 2.0 from within WSDL 1.1. Try removing this import. If > this doesn't work, you could try a very small simple WSDL (sample > attached) and see if you can generate code. If it works, you could start > from there, adding one feature at a time. > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24360939.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
Your command is OK. Are you importing a WSDL 2 document? I not sure you can import WSDL 2.0 from within WSDL 1.1. Try removing this import. If this doesn't work, you could try a very small simple WSDL (sample attached) and see if you can generate code. If it works, you could start from there, adding one feature at a time. -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Monday, July 06, 2009 12:10 PM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors C:\>wsdl2java -uri ss.wsdl http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:wsa10="http://www.w3.org/2005/08/addressing"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:i2="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:tns="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:i1="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:i0="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl0"; /> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl1"; /> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl2"; /> - http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/Imports";> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd6"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd7"; namespace="http://schemas.microsoft.com/2003/10/Serialization/"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd0"; namespace="http://schemas.mimeo.com/dom/3.0/Utilities.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd1"; namespace="http://schemas.mimeo.com/dom/3.0/Configurations.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd2"; namespace="http://schemas.mimeo.com/dom/3.0/ImpressionSources.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd3"; namespace="http://schemas.mimeo.com/dom/3.0/Document.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd4"; namespace="http://schemas.mimeo.com/PrintFile2.0.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd5"; namespace="http://schemas.mimeo.com/VariableDataTemplate1.0.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd8"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/Common/Search"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd9"; namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"; /> http://services.dev.mimeo.com/EnterpriseServ
RE: Axis2 1.5 WSDL2Java errors
C:\>wsdl2java -uri ss.wsdl http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:wsa10="http://www.w3.org/2005/08/addressing"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:i2="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:tns="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:i1="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:i0="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl0"; /> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl1"; /> http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; location="http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl=wsdl2"; /> - http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/Imports";> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd6"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd7"; namespace="http://schemas.microsoft.com/2003/10/Serialization/"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd0"; namespace="http://schemas.mimeo.com/dom/3.0/Utilities.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd1"; namespace="http://schemas.mimeo.com/dom/3.0/Configurations.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd2"; namespace="http://schemas.mimeo.com/dom/3.0/ImpressionSources.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd3"; namespace="http://schemas.mimeo.com/dom/3.0/Document.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd4"; namespace="http://schemas.mimeo.com/PrintFile2.0.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd5"; namespace="http://schemas.mimeo.com/VariableDataTemplate1.0.xsd"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd8"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/Common/Search"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd9"; namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd10"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/Common/Security/"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd12"; namespace="http://schemas.mimeo.com/EnterpriseServices/2008/09/Common/Faults"; /> http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?xsd=xsd11"; namespace="http://schemas.microsoft.com/Message"; /> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
RE: Axis2 1.5 WSDL2Java errors
Could you post your entire WSDL document and the command that you are using to run WSDL2Java? -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Monday, July 06, 2009 11:44 AM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors I'm still getting the same error after trying both of those changes. Now it just says "Cannot find the declaration of element 'wsdl:definitions'." jcaristi wrote: > > If you define the WSDL namespace with a prefix, you will need to use it: > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > Try using or (easier) switch your declaration to this: > > xmlns="http://schemas.xmlsoap.org/wsdl/";> > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24357862.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
RE: Axis2 1.5 WSDL2Java errors
I'm still getting the same error after trying both of those changes. Now it just says "Cannot find the declaration of element 'wsdl:definitions'." jcaristi wrote: > > If you define the WSDL namespace with a prefix, you will need to use it: > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > Try using or (easier) switch your declaration to this: > > xmlns="http://schemas.xmlsoap.org/wsdl/";> > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24357862.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
If you define the WSDL namespace with a prefix, you will need to use it: xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; Try using or (easier) switch your declaration to this: xmlns="http://schemas.xmlsoap.org/wsdl/";> -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Monday, July 06, 2009 11:08 AM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors When I use a local validation tool I get an error on the second line saying "cvc-elt.1: 9Cannot find the declaration of element 'definitions'." The definition element seems to have everything it needs so I'm not really sure what the problem with it is. Here's the line that I'm getting the error on: http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:wsa10="http://www.w3.org/2005/08/addressing"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:i2="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:tns="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:i1="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:i0="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> jcaristi wrote: > > This server does not seem to be available on the Internet. I get: > > "Firefox can't find the server at services.dev.mimeo.com." > > You may be able to get to it because it's on your Intranet. You may want > to try a locally installed WSDL validation tool. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24356817.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
RE: Axis2 1.5 WSDL2Java errors
When I use a local validation tool I get an error on the second line saying "cvc-elt.1: 9Cannot find the declaration of element 'definitions'." The definition element seems to have everything it needs so I'm not really sure what the problem with it is. Here's the line that I'm getting the error on: http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:wsa10="http://www.w3.org/2005/08/addressing"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:i2="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMtomBinding"; xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:tns="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:i1="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsMSWSEBinding"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:i0="http://schemas.mimeo.com/EnterpriseServices/2008/09/StorageService/HttpsBinding"; xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> jcaristi wrote: > > This server does not seem to be available on the Internet. I get: > > "Firefox can't find the server at services.dev.mimeo.com." > > You may be able to get to it because it's on your Intranet. You may want > to try a locally installed WSDL validation tool. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24356817.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
This server does not seem to be available on the Internet. I get: "Firefox can't find the server at services.dev.mimeo.com." You may be able to get to it because it's on your Intranet. You may want to try a locally installed WSDL validation tool. -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Thursday, July 02, 2009 3:00 PM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl This is the WSDL file . When I put it in my browser it shows up fine. jcaristi wrote: > > In order to use this tool, your WSDL would need to be available on the > Internet. For example, if you point to an Amazon WSDL, it works. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24312273.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
RE: Axis2 1.5 WSDL2Java errors
http://services.dev.mimeo.com/EnterpriseServices/2008/09/StorageService.svc?wsdl This is the WSDL file . When I put it in my browser it shows up fine. jcaristi wrote: > > In order to use this tool, your WSDL would need to be available on the > Internet. For example, if you point to an Amazon WSDL, it works. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24312273.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
In order to use this tool, your WSDL would need to be available on the Internet. For example, if you point to an Amazon WSDL, it works. -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Wednesday, July 01, 2009 5:01 PM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors I used http://xmethods.net/ve2/Tools.po to validate it. I gave it a URL and the URL is available when I try it in a web browser. jcaristi wrote: > > What validation tool are you using? It seems like it can't retrieve your > WSDL. Did you provide a URL? Is the WSDL available at that URL? (You can > check with a browser) > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24297044.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
RE: Axis2 1.5 WSDL2Java errors
I used http://xmethods.net/ve2/Tools.po to validate it. I gave it a URL and the URL is available when I try it in a web browser. jcaristi wrote: > > What validation tool are you using? It seems like it can't retrieve your > WSDL. Did you provide a URL? Is the WSDL available at that URL? (You can > check with a browser) > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24297044.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
What validation tool are you using? It seems like it can't retrieve your WSDL. Did you provide a URL? Is the WSDL available at that URL? (You can check with a browser) -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Wednesday, July 01, 2009 4:48 PM To: axis-user@ws.apache.org Subject: RE: Axis2 1.5 WSDL2Java errors When I attempt to validate it I get "WSDLException: faultCode=WSDL Retrieval error: Could not obtain data from connection". I think this may be because I need to specify a username/password, but is it possible for me to do that through WSDL2Java? jcaristi wrote: > > This is likely to be an error in your WSDL. Try running it through a > validation tool or loading it into SoapUI. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24296885.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
RE: Axis2 1.5 WSDL2Java errors
When I attempt to validate it I get "WSDLException: faultCode=WSDL Retrieval error: Could not obtain data from connection". I think this may be because I need to specify a username/password but is it possible for me to do that through WSDL2Java? jcaristi wrote: > > This is likely to be an error in your WSDL. Try running it through a > validation tool or loading it into SoapUI. > > -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24296885.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
This is likely to be an error in your WSDL. Try running it through a validation tool or loading it into SoapUI. -Original Message- From: LeftoverLinguine [mailto:leftoverlingu...@gmail.com] Sent: Wednesday, July 01, 2009 3:31 PM To: axis-user@ws.apache.org Subject: Axis2 1.5 WSDL2Java errors I'm getting the following errors when I run WSDL2Java: [ERROR] Cannot Determine the MEP org.apache.axis2.AxisFault: Cannot Determine the MEP at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getMEP(WSDL11 ToAxisServiceBuilder.java:2745) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOpera tions(WSDL11ToAxisServiceBuilder.java:1287) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortT ype(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo ints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi ce(WSDL11ToAxisServiceBuilder.java:362) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA llServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException : Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:153) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: org.apache.axis2.AxisFault: Cannot Determine the MEP at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getMEP(WSDL11 ToAxisServiceBuilder.java:2745) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOpera tions(WSDL11ToAxisServiceBuilder.java:1287) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortT ype(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo ints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi ce(WSDL11ToAxisServiceBuilder.java:362) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA llServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:147) ... 2 more Does anyone have any idea what could be causing the errors? -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24295840.html Sent from the Axis - User mailing list archive at Nabble.com. STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
Axis2 1.5 WSDL2Java errors
I'm getting the following errors when I run WSDL2Java: [ERROR] Cannot Determine the MEP org.apache.axis2.AxisFault: Cannot Determine the MEP at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getMEP(WSDL11 ToAxisServiceBuilder.java:2745) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOpera tions(WSDL11ToAxisServiceBuilder.java:1287) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortT ype(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo ints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi ce(WSDL11ToAxisServiceBuilder.java:362) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA llServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException : Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:153) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: org.apache.axis2.AxisFault: Cannot Determine the MEP at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getMEP(WSDL11 ToAxisServiceBuilder.java:2745) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOpera tions(WSDL11ToAxisServiceBuilder.java:1287) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortT ype(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo ints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi ce(WSDL11ToAxisServiceBuilder.java:362) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA llServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:147) ... 2 more Does anyone have any idea what could be causing the errors? -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24295840.html Sent from the Axis - User mailing list archive at Nabble.com.
wsdl2java -d jaxbri -uw does not unwrap and returns void
Basically, with jaxbri as data binding option AND -uw ( for unwrap ), the wsdl2java process generates the return type as "void". Upon searching around I found that there is a JIRA *AXIS2*-3681 already open. Is there is workaround ? or a timeline when this JIRA could be resolved ? Any response appreciated as this is a showstopper for us to move forward with jaxb. Currently only ADB seems to unwrap properly, not even xmlbeans. Is that correct ? Thanks John
Re: problem with wsdl2java in 1.5
It looks like your Java runtime environment (GCJ/GNU classpath?) is
incomplete. I would recommend to install Sun's JRE for Linux.
Andreas
On Thu, Jun 25, 2009 at 02:12, Vadim
Letitchevski wrote:
> wsdl2java in axis2-1.5 did not work for me reporting exceptions like these:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org.apache.axis2.description.AxisDescription
> at java.lang.Class.initializeClass(libgcj.so.7rh)
> at java.lang.Class.initializeClass(libgcj.so.7rh)
> at
> org.apache.axis2.description.WSDLToAxisServiceBuilder.(WSDLToAxisServiceBuilder.java:101)
> at
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.(WSDL11ToAxisServiceBuilder.java:215)
> at
> org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.(WSDL11ToAllAxisServicesBuilder.java:63)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:144)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: java.lang.ClassNotFoundException:
> java.util.concurrent.ConcurrentHashMap not found in
> gnu.gcj.runtime.SystemClassLoader{urls=[file:NED615Soap.wsdl,file:/home/Ned/axis2-1.5/,file:./,file:/home/Ned/axis2-1.5//lib/activation-1.1.jar,file:/home/Ned/axis2-1.5//lib/axiom-api-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-dom-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-impl-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-ant-plugin-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-clustering-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-corba-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-fastinfoset-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-java2wsdl-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxbri-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxws-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jibx-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-json-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-kernel-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-metadata-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-mtompolicy-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-saaj-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-spring-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-http-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-local-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-xmlbeans-1.5.jar,file:/home/Ned/axis2-1.5//lib/bcel-5.1.jar,file:/home/Ned/axis2-1.5//lib/commons-codec-1.3.jar,file:/home/Ned/axis2-1.5//lib/commons-fileupload-1.2.jar,file:/home/Ned/axis2-1.5//lib/commons-httpclient-3.1.jar,file:/home/Ned/axis2-1.5//lib/commons-io-1.4.jar,file:/home/Ned/axis2-1.5//lib/commons-lang-2.3.jar,file:/home/Ned/axis2-1.5//lib/commons-logging-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-annotation_1.0_spec-1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-jaxws_2.1_spec-1.0.jar,file:/home/Ned/axis2-1.5//lib/geronimo-saaj_1.3_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-stax-api_1.0_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-ws-metadata_2.0_spec-1.1.2.jar,file:/home/Ned/axis2-1.5//lib/httpcore-4.0.jar,file:/home/Ned/axis2-1.5//lib/jalopy-1.5rc3.jar,file:/home/Ned/axis2-1.5//lib/jaxb-api-2.1.jar,file:/home/Ned/axis2-1.5//lib/jaxb-impl-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxb-xjc-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxen-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/jettison-1.0-RC2.jar,file:/home/Ned/axis2-1.5//lib/jibx-bind-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/jibx-run-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/log4j-1.2.15.jar,file:/home/Ned/axis2-1.5//lib/mail-1.4.jar,file:/home/Ned/axis2-1.5//lib/mex-1.5.jar,file:/home/Ned/axis2-1.5//lib/neethi-2.0.4.jar,file:/home/Ned/axis2-1.5//lib/smack-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/smackx-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/soapmonitor-1.5.jar,file:/home/Ned/axis2-1.5//lib/woden-api-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/woden-impl-dom-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/wsdl4j-1.6.2.jar,file:/home/Ned/axis2-1.5//lib/wstx-asl-3.2.4.jar,file:/home/Ned/axis2-1.5//lib/xalan-2.7.0.jar,file:/home/Ned/axis2-1.5//lib/xercesImpl-2.6.2.jar,file:/home/Ned/axis2-1.5//lib/xml-apis-1.3.02.jar,file:/home/Ned/axis2-1.5//lib/xmlbeans-2.3.0.jar,file:/home/Ned/axis2-1.5//lib/xml-resolver-1.2.jar,file:/home/Ned/axis2-1.5//lib/XmlSchema-1.4.3.jar,file:./],
> parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
> at java.net.URLClassLoader.findClass(libgcj.so.7rh)
> at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.7rh)
> at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
> at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
> at java.lang.Class.forName(libgcj.so.7rh)
> at java.lang.Class.initializeClass(libgcj.so.7rh)
> ...7 more
> QUESTIONS:
> When I did all
problem with wsdl2java in 1.5
wsdl2java in axis2-1.5 did not work for me reporting exceptions like these:
Exception in thread "main" java.lang.NoClassDefFoundError:
org.apache.axis2.description.AxisDescription
at java.lang.Class.initializeClass(libgcj.so.7rh)
at java.lang.Class.initializeClass(libgcj.so.7rh)
at
org.apache.axis2.description.WSDLToAxisServiceBuilder.(WSDLToAxisServiceBuilder.java:101)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.(WSDL11ToAxisServiceBuilder.java:215)
at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.(WSDL11ToAllAxisServicesBuilder.java:63)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:144)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.ClassNotFoundException:
java.util.concurrent.ConcurrentHashMap not found in
gnu.gcj.runtime.SystemClassLoader{urls=[file:NED615Soap.wsdl,file:/home/Ned/axis2-1.5/,file:./,file:/home/Ned/axis2-1.5//lib/activation-1.1.jar,file:/home/Ned/axis2-1.5//lib/axiom-api-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-dom-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-impl-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-ant-plugin-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-clustering-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-corba-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-fastinfoset-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-java2wsdl-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxbri-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxws-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jibx-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-json-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-kernel-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-metadata-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-mtompolicy-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-saaj-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-spring-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-http-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-local-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-xmlbeans-1.5.jar,file:/home/Ned/axis2-1.5//lib/bcel-5.1.jar,file:/home/Ned/axis2-1.5//lib/commons-codec-1.3.jar,file:/home/Ned/axis2-1.5//lib/commons-fileupload-1.2.jar,file:/home/Ned/axis2-1.5//lib/commons-httpclient-3.1.jar,file:/home/Ned/axis2-1.5//lib/commons-io-1.4.jar,file:/home/Ned/axis2-1.5//lib/commons-lang-2.3.jar,file:/home/Ned/axis2-1.5//lib/commons-logging-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-annotation_1.0_spec-1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-jaxws_2.1_spec-1.0.jar,file:/home/Ned/axis2-1.5//lib/geronimo-saaj_1.3_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-stax-api_1.0_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-ws-metadata_2.0_spec-1.1.2.jar,file:/home/Ned/axis2-1.5//lib/httpcore-4.0.jar,file:/home/Ned/axis2-1.5//lib/jalopy-1.5rc3.jar,file:/home/Ned/axis2-1.5//lib/jaxb-api-2.1.jar,file:/home/Ned/axis2-1.5//lib/jaxb-impl-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxb-xjc-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxen-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/jettison-1.0-RC2.jar,file:/home/Ned/axis2-1.5//lib/jibx-bind-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/jibx-run-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/log4j-1.2.15.jar,file:/home/Ned/axis2-1.5//lib/mail-1.4.jar,file:/home/Ned/axis2-1.5//lib/mex-1.5.jar,file:/home/Ned/axis2-1.5//lib/neethi-2.0.4.jar,file:/home/Ned/axis2-1.5//lib/smack-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/smackx-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/soapmonitor-1.5.jar,file:/home/Ned/axis2-1.5//lib/woden-api-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/woden-impl-dom-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/wsdl4j-1.6.2.jar,file:/home/Ned/axis2-1.5//lib/wstx-asl-3.2.4.jar,file:/home/Ned/axis2-1.5//lib/xalan-2.7.0.jar,file:/home/Ned/axis2-1.5//lib/xercesImpl-2.6.2.jar,file:/home/Ned/axis2-1.5//lib/xml-apis-1.3.02.jar,file:/home/Ned/axis2-1.5//lib/xmlbeans-2.3.0.jar,file:/home/Ned/axis2-1.5//lib/xml-resolver-1.2.jar,file:/home/Ned/axis2-1.5//lib/XmlSchema-1.4.3.jar,file:./],
parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
at java.net.URLClassLoader.findClass(libgcj.so.7rh)
at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.7rh)
at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
at java.lang.Class.forName(libgcj.so.7rh)
at java.lang.Class.initializeClass(libgcj.so.7rh)
...7 more
QUESTIONS:
When I did all the same but with axis2-1.4 it seems to generate the code. I
don't know if it is working yet, but I am wondering if I should just rely on
axis2-1.4 or fix my problem for axis2-1.5?
I am new to axis2 and java programming in whole. Unfortunately axis2c does not
support SOAP 1.1 attachments (pure MIME) , only MTOM (am I right?).
Re: WSDL2Java generates uncompilable code
Hello Again , Do i need to put in some more details Please let me know. This is a major issue. --- On Wed, 10/6/09, sri ram wrote: From: sri ram Subject: WSDL2Java generates uncompilable code To: axis-user@ws.apache.org Date: Wednesday, 10 June, 2009, 4:29 PM Hi axis 1.4 Users, I have an issue while using axis 1.4 engine . While I run wsdl2java WSDL2Java generates uncompilable code Issue is : (java.lang.String) super(_value); ^ 1 error Because the code invokes a superconstructor but doesn't extend any other class. I'm assuming that the problem is in the use of the "extension" element. For this scenario I have found the probable solution given from one of the users in this link https://issues.apache.org/jira/browse/AXIS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505768 He modified the JavaBeanWriter.java file . Is that the right fix should I follow it. Can anyone confirm or give an alternate fix for this . Can anyone give a solution... Thanks Sriram Explore and discover exciting holidays and getaways with Yahoo! India Travel Click here! Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/
Re: WSDL2Java generates uncompilable code
resending . This issue should have been addressed before, can anyone guide me its important. --- On Wed, 10/6/09, sri ram wrote: From: sri ram Subject: WSDL2Java generates uncompilable code To: axis-user@ws.apache.org Date: Wednesday, 10 June, 2009, 4:29 PM Hi axis 1.4 Users, I have an issue while using axis 1.4 engine . While I run wsdl2java WSDL2Java generates uncompilable code Issue is : (java.lang.String) super(_value); ^ 1 error Because the code invokes a superconstructor but doesn't extend any other class. I'm assuming that the problem is in the use of the "extension" element. For this scenario I have found the probable solution given from one of the users in this link https://issues.apache.org/jira/browse/AXIS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505768 He modified the JavaBeanWriter.java file . Is that the right fix should I follow it. Can anyone confirm or give an alternate fix for this . Can anyone give a solution... Thanks Sriram Explore and discover exciting holidays and getaways with Yahoo! India Travel Click here! Cricket on your mind? Visit the ultimate cricket website. Enter http://beta.cricket.yahoo.com
WSDL2Java generates uncompilable code
Hi axis 1.4 Users, I have an issue while using axis 1.4 engine . While I run wsdl2java WSDL2Java generates uncompilable code Issue is : (java.lang.String) super(_value); ^ 1 error Because the code invokes a superconstructor but doesn't extend any other class. I'm assuming that the problem is in the use of the "extension" element. For this scenario I have found the probable solution given from one of the users in this link https://issues.apache.org/jira/browse/AXIS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505768 He modified the JavaBeanWriter.java file . Is that the right fix should I follow it. Can anyone confirm or give an alternate fix for this . Can anyone give a solution... Thanks Sriram Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/
How to add JSESSIONID to the following requests' header in java rpc client using Axis2 1.4 stub classes generated by WSDL2JAVA
hi, I'm using Axis2 1.4 to call a WS. I generated the stub classes using the WSDL2Java tool. The java rpc client using stub classes to send requests to WS. After the client sends the first request to WS, it can get JSESSIONID in the first response's header (Set-Cookie). I want to add the JSESSIONID to the following requests' header (Cookie). Could someone give me a sample about this? I just need a code snippet like: MyServiceStub stub = new MyServiceStub(MyServiceUrl); ServiceClient sender = _stub._getServiceClient(); sender.getOptions().setManageSession(true); sender.getOptions().setProperty(HTTPConstants.HEADER_COOKIE, "JSESSIONID=**"); // *** is the JSESSIONID in the first response's header (I use these code, but can't find the "Cookie: JSESSIONID=" part in the following requests' header using TCPMon.) Note: 1. The client is a java rpc client using stub classes but not jsp or other http request. 2. The container of the WS may be Tomcat, JBoss, WebLogic or similar ones. Thanks Kevin
Axis2/wsdl2java - different source code generated when using different JRE versions!
Hello, We have a WSDL centric solution and therefor uses wsd2java to generate the server side skeletons (and client code to test our solution). The actual real clients are using a variety of differnt WS implementations (gSOAP etc) A long time (big) problem is that the generated code does not honor the order of the WSDL tags defined in the WSDL file. But since we "own" the server interface, the clients have simply made sure that the tags are sent in the order that the Axis2 server expects them. Now to my last finding: I accidently noticed that wsdl2java generates source code that expects the order of the tags *differently* if I run wsd2ljava with a Sun JRE 1.5 or a Sun JRE 1.6 Actually when using 1.6 the code generated validates the tags in a more correct way (e.g. closer to the WSDL defintion) I'm actually a bit surprised over my finding and perhaps there is some simple explanation. I realize that differences in java seralization can be involved. Using WinXP, Axis2 1.3 BR Niels _ Vi vet vem du passar ihop med! Klicka här för att få veta! http://dejting.se.msn.com/channel/index.aspx?trackingid=1002952
Re: jaxb issues with Axis2 - while using the wsdl2java tool
Sebastin I thought so too...in the very beginning. But it is there in AXIS_HOME directory (activation-1.1.jar). Also...if that was the case wouldnt it be failing for all cases. Why is it specifically for the chain-import scenario I described. Thanks Preetham 2009/5/29 Sebastian Just - RÖPERWEISE Systems > Hi! > > Caused by: java.lang.NoClassDefFoundError: javax/activation/DataHandler > > I guess you're missing the activation framework in your classpath. > > > Best regards, > Sebastian >
Re: jaxb issues with Axis2 - while using the wsdl2java tool
Hi! > Caused by: java.lang.NoClassDefFoundError: javax/activation/DataHandler I guess you're missing the activation framework in your classpath. Best regards, Sebastian
jaxb issues with Axis2 - while using the wsdl2java tool
All, We were previously using adb with Axis2 and all was working fine. Recently we have been prototyping jaxb with Axis2. We have a complex wsdl which imports several schemas and in turn the schema has additional schema imports. In this scenario...errors are thrown. When we researched into it...we figured out the code generation tool of Axis (JAxB) is not able to handle a chain of schema imports based on the scenario described above. I get the following error: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:112) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:101) ... 3 more Caused by: java.lang.NoClassDefFoundError: javax/activation/DataHandler at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.(RuntimeBuiltinLeafInfoImpl.java:224) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.(RuntimeTypeInfoSetImpl.java:61) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:127) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:79) at com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:152) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.(RuntimeModelBuilder.java:87) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286) at com.sun.tools.xjc.reader.xmlschema.bindinfo.BindInfo.getJAXBContext(BindInfo.java:332) at com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1.(AnnotationParserFactoryImpl.java:80) at com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl.create(AnnotationParserFactoryImpl.java:79) at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.createAnnotationParser(NGCCRuntimeEx.java:323) at com.sun.xml.xsom.impl.parser.state.annotation.action0(annotation.java:48) at com.sun.xml.xsom.impl.parser.state.annotation.enterElement(annotation.java:73) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:294) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.revertToParentFromEnterElement(NGCCHandler.java:111) at com.sun.xml.xsom.impl.parser.state.foreignAttributes.enterElement(foreignAttributes.java:50) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:200) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:246) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:238) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:226) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:262) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:270) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.startElement(NGCCRuntime.java:219)
Interop problem / wsdl2java - ignoring the order of the elements in WSDL
Hi, I have created Axis2 server side skeletons and client stubs using wsdl2java. Works fine. But it seems like the codegenerator ignores the order in the elements was listed in the WSDL Much like described in <https://teras.tietoenator.com/exchweb/bin/,DanaInfo=.aenclpEzpm2ypzn737Qu76 +redir.asp?URL=https://cwiki.apache.org/jira/browse/AXIS-2677> https://cwiki.apache.org/jira/browse/AXIS-2677. This is OKwhen the client is under our control (since our client uses Axis2), but a customer uses another WS implementation: gSOAP. The same WSDL was used to generate the service parts (by Axis2) and the client stubs was generated by the corresponing gSOAP tooling support. But the gSOAP client stub seems to send the elements in the order specified in the WSDL, but the Axis2 service requires the elements to be received according to its internal sorted list very hard to maintin interopt giving us unexpected subelements errors. Any suggestions/ideas/tips/tricks on how to solve this? (Either in Axis2 or gSOAP) BR L
RE: wsdl2java
The answer may be contained in the rest of the Exception stack trace. You could look there for clues and if you still can't figure it out, post the entire trace. -Original Message- From: TomazM [mailto:tomaz.majerh...@arnes.si] Sent: Thursday, May 21, 2009 10:34 AM To: axis Subject: wsdl2java I have error when using jbix %AXIS2_HOME%\bin\wsdl2java -uri jibx\META-INF\IPIS_JIBX.wsdl -Ebindingfile jibx\META-INF\binding.xml -p service.jibx -d jibx -s -ss -sd -ssi -uw -o build_jibx Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL Is there any way to determine in which line of wsdl is error. wsdl: http://aris.ipis/"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="http://arnes.ipis/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> IPISOZ http://arnes.ipis/"; targetNamespace="http://arnes.ipis/";> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://jalovec.arnes.si:8080/axis2/services/IPISOZ"/> STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
wsdl2java
I have error when using jbix %AXIS2_HOME%\bin\wsdl2java -uri jibx\META-INF\IPIS_JIBX.wsdl -Ebindingfile jibx\META-INF\binding.xml -p service.jibx -d jibx -s -ss -sd -ssi -uw -o build_jibx Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL Is there any way to determine in which line of wsdl is error. wsdl: http://aris.ipis/"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="http://arnes.ipis/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> IPISOZ http://arnes.ipis/"; targetNamespace="http://arnes.ipis/";> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://jalovec.arnes.si:8080/axis2/services/IPISOZ"/> begin:vcard fn:Tomaz Majerhold n:Majerhold;Tomaz org:ARNES, Slovenian NREN;Development team adr:;;Jamova 39;Ljubljana;Ljubljana;1000;Slovenia title:Developer tel;work:+386 14798930 tel;fax:+386 1 479 88 99 tel;home:+386 1425 38 01 tel;cell:+386 40757229 x-mozilla-html:FALSE url:http://www.arnes.si/ version:2.1 end:vcard
RE: using Axis2 wsdl2java to generate Axis1 client stubs
Good Morning Edward could you explain the schema/namespace which defines DotNet tree element? could you explain what is the purpose of DotNet tree element? attaching your DotNet generated wsdl would be helpful Thank You, Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. To: axis-user@ws.apache.org Subject: using Axis2 wsdl2java to generate Axis1 client stubs From: edward.thomp...@wachovia.com Date: Mon, 11 May 2009 09:18:08 -0400 I am using the Axis2 wsdl2java utility to generate client side java code for Axis1. The reason is that the Axis1 wsdl2java utility can't seme to handle "tree wsdl" generated by out .NET applications. The wdl2java utility for Axis2 indicates a backward compatability option, (-b). However, the code generated a) still references axis2 packages, and b) still has a dependency on the Stubs generated for Axis2 use (i.e. it doesn't seem to generate standalone code that is free from Axis2 dependencies.) So I am wondering what the purpose of the backward compatability option is. I am assuming that I have misunderstood its purpose. _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009
using Axis2 wsdl2java to generate Axis1 client stubs
I am using the Axis2 wsdl2java utility to generate client side java code for Axis1. The reason is that the Axis1 wsdl2java utility can't seme to handle "tree wsdl" generated by out .NET applications. The wdl2java utility for Axis2 indicates a backward compatability option, (-b). However, the code generated a) still references axis2 packages, and b) still has a dependency on the Stubs generated for Axis2 use (i.e. it doesn't seem to generate standalone code that is free from Axis2 dependencies.) So I am wondering what the purpose of the backward compatability option is. I am assuming that I have misunderstood its purpose.
WSDL2Java and manual soap calls not working
Hi Guys,
I'm a newbie, and I'm using axis-1.4. I have a web service that I am
connecting to, which I did not write, which was written using axis-1.4. I am
having problems using the WSDL2Java generated files, as well as using the soap
call api. Neither appear to work as expected.
I'm almost at my wits end, and feel like doing a manual call using
HttpsURLConnection. But boy would it be nice to be able to use the WSDL2Java
generated classes, or at the very least, use the axis-SOAP api to make the call.
In both cases, I am getting proper XML responses. I can tell, because I step
through the code, and the soap response has the same XML that I would get if I
did the request manually.
1. WSDL2Java does not generate code that is able to access the soap service I
am accessing; I get an error that says...
org.xml.sax.SAXException: Invalid element in
DataTypes.APASProxy._2007._04.ReceivedTranscript - ReceivedTranscript
The code was generated from the wsdl from the service directly. i.e.
http://localhost/axis/service/ServiceName?wsdl
I have no idea where to start. Simple requests that take no parameters, and
return strings, work just fine. But when it's a complex return value, such as
an array, it doesn't appear to work, AT ALL. Here's an example of one that
fails for me; which I do manually here to show that it works fine without the
WSDL generated classes.
openssl s_client -connect hostname:443
POST /axis/services/APASQueueService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: apasproxy.athabascau.ca
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
"http://APASProxy.ServiceContracts/2007/04/GetRegisteredEducationalInstitutions";
Content-Length: 351
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/200
1/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04"/>
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04";>http://APASProxy.DataTypes/2007/04";>48024000
..blah, blah, blah, yada, yada, yada.
closed
2. I am unable to make an axis Call connection either; I keep getting an error
that says
org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which
is NOT expected, in something it was trying to deserialize.
The above one, is the "simple" request I mentioned earlier. Just a string
retrieval.
Here's an example of the java code...
Service soapService = new Service();
Call call = (Call) soapService.createCall();
call.setTargetEndpointAddress(
new java.net.URL
("https://hostname/axis/services/APASQueueService";));
call.setOperationName(
new QName("", "GetHostInstitution"));
call.setReturnType(XMLType.XSD_STRING); // this is not working
try {
System.out.println(call.invoke(
new Object[] { }));
} catch (java.rmi.RemoteException re) {
re.printStackTrace();
}
Here's an example from doing it manually. If I step through the code, it is
getting the same response, but is unable to handle it. Try to ignore any
wrapping that occurs, as I'm sure my mail client will wrap some of it.
openssl s_client -connect hostname:443
POST /axis/services/APASQueueService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: hostname
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://APASProxy.ServiceContracts/2007/04/GetHostInstitution";
Content-Length: 333
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/200
1/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04"/>
HTTP/1.1 200 OK
Date: Fri, 08 May 2009 15:40:34 GMT
Content-Type: text/xml;charset=utf-8
Connection: close
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04";>http://APASProxy.DataTypes/2007/04";>48002000Athabasca
Universityclosed
Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
Problem with wsdl2java
Hi all, I'm trying to consume a secure Axis Web service from a Globus Toolkit 4 service. I generated stubs with standard Axis' wsdl2java from a wsdl (glite-security-voms-admin-2.0.2.wsdl)where all wsdl:operation are described this way: http://schemas.xmlsoap.org/soap/encoding/"; namespace=" http://glite.org/wsdl/services/org.glite.security.voms.service.admin"; use="encoded"/> http://schemas.xmlsoap.org/soap/encoding/"; namespace=" http://glite.org/wsdl/services/org.glite.security.voms.service.admin"; use="encoded"/> http://schemas.xmlsoap.org/soap/encoding/"; name="VOMSException" namespace=" http://glite.org/wsdl/services/org.glite.security.voms.service.admin"; use="encoded"/> Let me underline the soapAction="". As far as I understood, in Globus Toolkit environment, stubs should be generated from a wsdl that "expect soapAction to be populated". So for test, I've tried to specify, in a given operation of that wsdl, the correct soapAction. Then I've re-generated the stubs and everything works! After this long explaination (sorry) my question is: could it be possible (using some option in wsdl2java command) to inject the correct soapAction at stub creation time, in order to have GT4 compliant stubs? Or could you suggest me another workaround? Thank you very much, Andrea
Re: problem with AXis2 Wsdl2java ADB Code generator
I think I need to reword my question. Basically I have a webservice with operation TrygetByKeyTenant, the respnse of this has two message parts defined in wsdl as: As the name specify this will return the TenantValue if one is there with the given key else the second part i.e (http://www.syndesis.com/ys/intf"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> But the generated ADB Java class for TryGetByKeyTenantResponse throws exception in serialise method if entity is null. I have just modified this to return the xsi:nul="true" instead of throwing null it works fine. can some one let me know how to get around this. Is there any option to specify nil=true for the message parts? Regards, Krishna krishna.arani wrote: > > Hi, > The last message was not getting posted to mailing list so I again posting > again. sorry If it causes any problem. > In my rpc/literal style webservice, I have a element with > multiple parts in it. One of the part can be nullable. The problem is the > generated ADB from wsdl2java throws an exception if the part is null while > serialising to xml. > > > > > > > here the "entity" can be null. so it is expected that the soap response to > have > > http://www.syndesis.com/ys/intf"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> > > But the generated ADB class throws an exception if entity is null. > > If have moved these two element parts under another type and use that as > part it works by defining nillable="true" for the second element. But I > dont want to do this or change the message structure as other parties will > have to chage too. This was working fine with axis1. > > any advice on how to go with this issue. > Thanks in advance. > > -Krishna Arani > -- View this message in context: http://www.nabble.com/problem-with-AXis2-Wsdl2java-ADB-Code-generator-tp23175797p23212701.html Sent from the Axis - User mailing list archive at Nabble.com.
problem with AXis2 Wsdl2java ADB Code generator
Hi, The last message was not getting posted to mailing list so I again posting again. sorry If it causes any problem. In my rpc/literal style webservice, I have a element with multiple parts in it. One of the part can be nullable. The problem is the generated ADB from wsdl2java throws an exception if the part is null while serialising to xml. here the "entity" can be null. so it is expected that the soap response to have http://www.syndesis.com/ys/intf"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> But the generated ADB class throws an exception if entity is null. If have moved these two element parts under another type and use that as part it works by defining nillable="true" for the second element. But I dont want to do this or change the message structure as other parties will have to chage too. This was working fine with axis1. any advice on how to go with this issue. Thanks in advance. -Krishna Arani -- View this message in context: http://www.nabble.com/problem-with-AXis2-Wsdl2java-ADB-Code-generator-tp23175797p23175797.html Sent from the Axis - User mailing list archive at Nabble.com.
Problem Axis2 Wsdl2java generated message
Hi, In my rpc/literal style webservice, I have a element with multiple parts in it. One of the part can be nullable. The problem is the generated ADB from wsdl2java throws an exception if the part is null while serialising to xml. here the "entity" can be null. so it is expected that the soap response to have http://www.syndesis.com/ys/intf"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> But the generated ADB class throws an exception if entity is null. If have moved these two element parts under another type and use that as part it works by defining nillable="true" for the second element. But I dont want to do this or change the message structure as other parties will have to chage too. This was working fine with axis1. any advice on how to go with this issue. Thanks in advance. -Krishna Arani -- View this message in context: http://www.nabble.com/Problem-Axis2-Wsdl2java-generated-message-tp23175455p23175455.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2JAVA created uncompilable Stub
Hi Pricilla,
I'll answer you to the best of my knowledge, which is limited to how I've
used Axis so far.
The file with the word "Skeleton" in it is the only file that you should
have to modify. The java class that you created in the first steps (to come
up with the WSDL file) probably only contained the signatures of your web
service methods. The Skeleton file is pretty much the equivalent of your
.java file, e.g. it only contains method signatures, but it uses SOAP object
types instead of the types that you used.
Look for your method names in the skeleton file. There should be a comment
for each of them telling you that you need to implement them (along with a
thrown exception). In other words, for each of your methods, remove
everything between the opening and closing braces, and start coding.
The WSDL2Java process should have also created a build.xml file. Once your
Skeleton is coded, you can right-click this build file, and choose "Run
as...", and then "Ant Build". This will compile your classes (skeleton
included), and create the .class files and a .aar file in the "build"
sub-directory of your project (which it will create).
The .aar file is the archive that you need to deploy to a container.
Personnally, I use Tomcat, and so that's what I'll talk to you about.
First, you need to download and install Tomcat. Once tomcat is installed,
you need to download and install the Axis2 War Archive FOR THE SAME VERSION
OF AXIS2 THAT YOU USED TO CREATE YOUR WEB SERVICE.
To install the .war file, you have two options : copy it to the
/webapps directory (and restart tomcat just to make sure), or
use the "Tomcat Manager" application that comes with Tomcat. I'll let you
search a bit for that...
Once Axis2 is installed, you can access it by going to
http://:8080/axis2. Three options will be offered there : Services,
Validate, and Admin. You can validate your Axis2 installation with the
Validate option.
To deploy your service, again, you have two options. 1- drop your .aar file
in the /webapps/axis2/WEB-INF/services directory, or use the
deployment tool in the Admin section of axis2 (user/pass is admin/axis2).
The deployment tool is the first option in the Admin section.
For development, I also recommend editing the
/webapps/axis2/WEB-INF/conf/axis2.xml configuration file. The
line to edit is has "hotupdate" in it, you should set this parameter to
true. This will make Axis re-deploy your web service every time you
overwrite the .aar file with a new one.
As for the stub, don't touch it. It was created by WSDL2Java to match the
method signatures of your web service. What you need to do in your client
is instantiate it, and call its methods. It will take care of communicating
with your web service and returning you the result.
Here's a sample of my code that uses my stub. This is the more complex
asynchronous call, for which you need to create a callback object. The more
direct synchronous call is more intuitive... :
Dispatch request = new Dispatch();
DispatcherStub stub = new DispatcherStub("http://"; + dispatcherHost +
":8080/axis2/services/Dispatcher");
Callback callback = new Callback();
callback.setId(obj.getId());
request.setId(obj.getId());
stub.startdispatch(request, callback);
I'm sure I forgot a detail or two, but that's the essence of it.
pricilla p wrote:
>
> Hi Jacques,
>
> I am new to axis.
>
> I have to develop an web service
>
> I have followed the steps you mentioned and created a wsdl, skeleton and
> stubs.
>
> Could you pls tell me what changes i need to make it in skeleton and stub
> files
>
> Also pls tell me how to deploy this web service.
>
>
> Thanks,
> Pricilla.
>
>
>
--
View this message in context:
http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22927751.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2JAVA created uncompilable Stub
On Tue, Apr 7, 2009 at 9:15 AM, pricilla p wrote: > Hi Jacques, > > I am new to axis. > > I have to develop an web service > > I have followed the steps you mentioned and created a wsdl, skeleton and > stubs. > > Could you pls tell me what changes i need to make it in skeleton and stub > files > > Also pls tell me how to deploy this web service. > you have to implement your business logic at the skelton. you need to create a .aar file to deploy it as an axis2 service. Please refer to user guide. thanks, Amila. > > > Thanks, > Pricilla. > > > On Fri, Apr 3, 2009 at 11:43 AM, Jacques46 wrote: > >> >> Just putting in my 2 cents, because a week ago I knew nothing about Axis, >> and >> I had to overcome some of the hurdles that have been encountered by other >> posters in the past... I hope I can avoid other people the same wasted >> time >> that I experienced... >> >> My environment is Eclipse 3.2.2, with the Codegen Wizard plugin. >> >> I have used the wizard in both directions (wsdl2java and java2wsdl) in >> versions 1.3 and 1.4.1 of Axis2. >> >> About the wizard : when you go to the Axis website, you can download the >> Codegen Wizard plugin for any version of Axis. What's misleading is that >> when you unzip each version (1.3 and 1.4.1), they both are contained in >> the >> "Axis2_Codegen_Wizard_1.3.0" directory. Having successfully created my >> stubs with version 1.3 of the wizard and Axis libraries, I now wanted to >> compile them with Axis2 1.4.1. My first reaction when I downloaded the >> 1.4.1 wizard was to say "hmmm... seems the wizard hasn't changed since >> version 1.3, because it's in the same directory name". WRONG ! Upon >> further inspection, I clearly saw that the libraries in the /lib directory >> of the plugin were indeed different. >> >> So, here are the steps I would recommend for a successful compile : >> >> - If you're in Eclipse, EXIT ! >> - If you have not done so yet, download the Axis2 standard distribution >> binary for the version you want, unzip it to some directory, and then >> create >> an environment variable "AXIS2_HOME" that points to that directory. >> - Download the Codegen Wizard for the Axis version you're shooting for >> (the >> same version as the standard distribution). Unzip it into your Eclipse's >> plugins directory. Note that if you had a previous version of the plugin >> there, you're gonna have to overwrite it with this new one if they both >> have >> the same name. >> - Copy the geronimo-stax-api_1.0_spec-1.0.1.jar and >> backport-util-concurrent-3.1.jar from the AXIS2_HOME/lib directory to the >> Wizard's /lib directory. >> - Edit the plugin.xml file of the Wizard. You'll see in there a bunch of >> nodes, add 2 nodes pointing to the jars you just copied. >> - Start Eclipse >> - Create a new project >> - In that project, import the jars from the AXIS2_HOME/lib directory >> (import >> them in a new folder you'll call lib) >> - Refresh the project >> - Project properties : Add all the jars to the build path >> - Create some java class that will have the methods you want your web >> service to have. Save it. >> - Right-click on the project, New->, Other... >> - Select Axis2 Wizards -> Axis2 Code Generator, Next. >> - Select Java2WSDL >> - Type the fully qualified class name, and then add the path for the class >> file. For example, if you class is com.xyz.TheClass, and your java source >> is in /src/com/xyz/TheClass.java, and the corresponding class >> file >> is in /bin/com/xyz/TheClass.class, then you'd enter >> "/bin. >> - Click Test Class Loading... If it doesn't work, review previous step. >> - Click Next, and you can change the options if you want, and then click >> next again. >> - Select to send the output to a project in the workspace, and browse to >> that project. Then give your wsdl a name, and click Finish. >> - Hopefully, all went well, and if you refresh your project, you'll see >> the >> WSDL. >> >> Now, if you want to create client and server code for this new WSDL: >> >> - Go in the codegen wizard again, this time select WSDL2Java, click Next. >> - Select the WSDL file you've just created. Next. >> - In Codegen Option, select Custom. Check "Generate both..." (last >> checkbox). Next. >> - Browse to the project location, and Click Finish. >> >> You should have the client and server code generated, along with a nice >> ant >> build file. >> >> The class you'll want to modify is Skeleton.java for the >> server-side. For a client to use that service, you'd instantiate >> Stub.java. >> >> I really hope this helps someone in the future. It's been a frustrating >> week. >> >> Jacques. >> -- >> View this message in context: >> http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22872262.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL2JAVA created uncompilable Stub
Hi Jacques, I am new to axis. I have to develop an web service I have followed the steps you mentioned and created a wsdl, skeleton and stubs. Could you pls tell me what changes i need to make it in skeleton and stub files Also pls tell me how to deploy this web service. Thanks, Pricilla. On Fri, Apr 3, 2009 at 11:43 AM, Jacques46 wrote: > > Just putting in my 2 cents, because a week ago I knew nothing about Axis, > and > I had to overcome some of the hurdles that have been encountered by other > posters in the past... I hope I can avoid other people the same wasted > time > that I experienced... > > My environment is Eclipse 3.2.2, with the Codegen Wizard plugin. > > I have used the wizard in both directions (wsdl2java and java2wsdl) in > versions 1.3 and 1.4.1 of Axis2. > > About the wizard : when you go to the Axis website, you can download the > Codegen Wizard plugin for any version of Axis. What's misleading is that > when you unzip each version (1.3 and 1.4.1), they both are contained in the > "Axis2_Codegen_Wizard_1.3.0" directory. Having successfully created my > stubs with version 1.3 of the wizard and Axis libraries, I now wanted to > compile them with Axis2 1.4.1. My first reaction when I downloaded the > 1.4.1 wizard was to say "hmmm... seems the wizard hasn't changed since > version 1.3, because it's in the same directory name". WRONG ! Upon > further inspection, I clearly saw that the libraries in the /lib directory > of the plugin were indeed different. > > So, here are the steps I would recommend for a successful compile : > > - If you're in Eclipse, EXIT ! > - If you have not done so yet, download the Axis2 standard distribution > binary for the version you want, unzip it to some directory, and then > create > an environment variable "AXIS2_HOME" that points to that directory. > - Download the Codegen Wizard for the Axis version you're shooting for (the > same version as the standard distribution). Unzip it into your Eclipse's > plugins directory. Note that if you had a previous version of the plugin > there, you're gonna have to overwrite it with this new one if they both > have > the same name. > - Copy the geronimo-stax-api_1.0_spec-1.0.1.jar and > backport-util-concurrent-3.1.jar from the AXIS2_HOME/lib directory to the > Wizard's /lib directory. > - Edit the plugin.xml file of the Wizard. You'll see in there a bunch of > nodes, add 2 nodes pointing to the jars you just copied. > - Start Eclipse > - Create a new project > - In that project, import the jars from the AXIS2_HOME/lib directory > (import > them in a new folder you'll call lib) > - Refresh the project > - Project properties : Add all the jars to the build path > - Create some java class that will have the methods you want your web > service to have. Save it. > - Right-click on the project, New->, Other... > - Select Axis2 Wizards -> Axis2 Code Generator, Next. > - Select Java2WSDL > - Type the fully qualified class name, and then add the path for the class > file. For example, if you class is com.xyz.TheClass, and your java source > is in /src/com/xyz/TheClass.java, and the corresponding class file > is in /bin/com/xyz/TheClass.class, then you'd enter > "/bin. > - Click Test Class Loading... If it doesn't work, review previous step. > - Click Next, and you can change the options if you want, and then click > next again. > - Select to send the output to a project in the workspace, and browse to > that project. Then give your wsdl a name, and click Finish. > - Hopefully, all went well, and if you refresh your project, you'll see the > WSDL. > > Now, if you want to create client and server code for this new WSDL: > > - Go in the codegen wizard again, this time select WSDL2Java, click Next. > - Select the WSDL file you've just created. Next. > - In Codegen Option, select Custom. Check "Generate both..." (last > checkbox). Next. > - Browse to the project location, and Click Finish. > > You should have the client and server code generated, along with a nice ant > build file. > > The class you'll want to modify is Skeleton.java for the > server-side. For a client to use that service, you'd instantiate > Stub.java. > > I really hope this helps someone in the future. It's been a frustrating > week. > > Jacques. > -- > View this message in context: > http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22872262.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
Re: WSDL2JAVA created uncompilable Stub
Just putting in my 2 cents, because a week ago I knew nothing about Axis, and I had to overcome some of the hurdles that have been encountered by other posters in the past... I hope I can avoid other people the same wasted time that I experienced... My environment is Eclipse 3.2.2, with the Codegen Wizard plugin. I have used the wizard in both directions (wsdl2java and java2wsdl) in versions 1.3 and 1.4.1 of Axis2. About the wizard : when you go to the Axis website, you can download the Codegen Wizard plugin for any version of Axis. What's misleading is that when you unzip each version (1.3 and 1.4.1), they both are contained in the "Axis2_Codegen_Wizard_1.3.0" directory. Having successfully created my stubs with version 1.3 of the wizard and Axis libraries, I now wanted to compile them with Axis2 1.4.1. My first reaction when I downloaded the 1.4.1 wizard was to say "hmmm... seems the wizard hasn't changed since version 1.3, because it's in the same directory name". WRONG ! Upon further inspection, I clearly saw that the libraries in the /lib directory of the plugin were indeed different. So, here are the steps I would recommend for a successful compile : - If you're in Eclipse, EXIT ! - If you have not done so yet, download the Axis2 standard distribution binary for the version you want, unzip it to some directory, and then create an environment variable "AXIS2_HOME" that points to that directory. - Download the Codegen Wizard for the Axis version you're shooting for (the same version as the standard distribution). Unzip it into your Eclipse's plugins directory. Note that if you had a previous version of the plugin there, you're gonna have to overwrite it with this new one if they both have the same name. - Copy the geronimo-stax-api_1.0_spec-1.0.1.jar and backport-util-concurrent-3.1.jar from the AXIS2_HOME/lib directory to the Wizard's /lib directory. - Edit the plugin.xml file of the Wizard. You'll see in there a bunch of nodes, add 2 nodes pointing to the jars you just copied. - Start Eclipse - Create a new project - In that project, import the jars from the AXIS2_HOME/lib directory (import them in a new folder you'll call lib) - Refresh the project - Project properties : Add all the jars to the build path - Create some java class that will have the methods you want your web service to have. Save it. - Right-click on the project, New->, Other... - Select Axis2 Wizards -> Axis2 Code Generator, Next. - Select Java2WSDL - Type the fully qualified class name, and then add the path for the class file. For example, if you class is com.xyz.TheClass, and your java source is in /src/com/xyz/TheClass.java, and the corresponding class file is in /bin/com/xyz/TheClass.class, then you'd enter "/bin. - Click Test Class Loading... If it doesn't work, review previous step. - Click Next, and you can change the options if you want, and then click next again. - Select to send the output to a project in the workspace, and browse to that project. Then give your wsdl a name, and click Finish. - Hopefully, all went well, and if you refresh your project, you'll see the WSDL. Now, if you want to create client and server code for this new WSDL: - Go in the codegen wizard again, this time select WSDL2Java, click Next. - Select the WSDL file you've just created. Next. - In Codegen Option, select Custom. Check "Generate both..." (last checkbox). Next. - Browse to the project location, and Click Finish. You should have the client and server code generated, along with a nice ant build file. The class you'll want to modify is Skeleton.java for the server-side. For a client to use that service, you'd instantiate Stub.java. I really hope this helps someone in the future. It's been a frustrating week. Jacques. -- View this message in context: http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22872262.html Sent from the Axis - User mailing list archive at Nabble.com.
wsdl2java and javadoc (AXIS2-3371)
Are there any news about this improvement? https://issues.apache.org/jira/browse/AXIS2-3371 Would be really handy to have javadoc generated if using contract first...
wsdl2java
OK, looking for something definitive here. I am running Axis 1.4 (Implementation-Version: 1.4 1855 April 22 2006) Trying to convert some wsdl generated from Microsoft WCF to java stubs using wsdl2java, and running into some problems. The WCF side of my team says java has trouble with tree wsdl (wdl:import, xsd:import). I have trouble believing this is true, and assume that wcf is generating non standard wsdl. So, can wsdl2java under Axis 1.4 support tree wsdl? Or am I barking up the wrong... Ed
Re: Help with wsdl2java
On 31/03/2009 09:48, "Andreas Veithen" wrote:
> Frank,
>
> MTOM is a _transparent_ way of optimizing messages. Why does the WSDL
> explicitly reference xop:Include?
That is a very good question... And not one I can answer immediatly.
I am 'new' to MTOM, that is, I learned it about 2 months ago, and I learned
it through gSOAP. At the level of gSOAP (in C++), it is not transparent... I
think I see at that level the 'processed' message with it's attachments.
What you are saying is that the WSDL should in fact contain a binary blob
there, with mime type attribute, instead of the xop:Include object.
Makes sense, but then I have to investigate how I can make such a setup with
gSAOP (where I start from C++ classes...)
Thanks for the input
Frank
>
> Andreas
>
> On Mon, Mar 30, 2009 at 18:18, Frank Vyncke wrote:
>> I,
>>
>> Am starting to develop a 'client' for a gSOAP based server, using MTOM
>> attachments.
>>
>> I have a wsdl file, but when I try to compile the wsdl file, I get an
>> exception with the following message:
>>
>> Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
>> the element {http://www.w3.org/2004/08/xop/include}Include from the parent
>> schema http://www.genivia.com/schemas/mtom_stream_test.xsd
>>
>> Can anyone tell me where this error comes from, because the wsdl file does
>> import the http://www.w3.org/2004/08/xop/include schema correctly (I think,
>> there is no way I can check if it really imported the schema or not).
>>
>> Thanks
>> Frank
>>
>>
Re: Help with wsdl2java
Frank,
MTOM is a _transparent_ way of optimizing messages. Why does the WSDL
explicitly reference xop:Include?
Andreas
On Mon, Mar 30, 2009 at 18:18, Frank Vyncke wrote:
> I,
>
> Am starting to develop a 'client' for a gSOAP based server, using MTOM
> attachments.
>
> I have a wsdl file, but when I try to compile the wsdl file, I get an
> exception with the following message:
>
> Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
> the element {http://www.w3.org/2004/08/xop/include}Include from the parent
> schema http://www.genivia.com/schemas/mtom_stream_test.xsd
>
> Can anyone tell me where this error comes from, because the wsdl file does
> import the http://www.w3.org/2004/08/xop/include schema correctly (I think,
> there is no way I can check if it really imported the schema or not).
>
> Thanks
> Frank
>
>
Re: wsdl2java issue in upgrading from axis 1.2 to 1.4
Is there any workaround for this problem? What i was thinking was to use wsdl2java of axis1.2 and use axis 1.4 for actual SOAP requests. But when i tried it by replacing the jars, it seems not working :( On Mon, Mar 30, 2009 at 8:56 PM, Jean-christophe cazeaux < jccazeau...@gmail.com> wrote: > Hello, > > I got exactly the same issue. This occurs with axis 1.3 and axis 1.4. > If you add a "foo" attribute in your wsdl like this : > > > > maxOccurs="49" nillable="true"/> > > > > The java Class ItemList will be correctly generated. So it appears to > be a regression in axis from 1.3... Maybe someone has an other > explanation and/or solution? > > JC > > 2009/3/30 Rishi Renjith : > > Hello, > > In my project, we are planning to upgrade from axis 1.2 to axis 1.4. But > > when we tested, we noticed that wsdl2java is not generating some java > > classes which it used to generate in axis 1.2 > > For eg, with the wsdl structure as below, > > > > > > > > > nillable="true"/> > > > > > > > > > > > maxOccurs="49" nillable="true"/> > > > > > > > > > > > maxOccurs="1" nillable="true"/> > > > > > > wsdl2java is not generating a class for ItemList in axis 1.4, but it used > to > > generate a class for ItemList in axis1.2. > > Is wsdl2java in 1.4 backward compatible with 1.2 ? > > > > > > Thanks, > > Rishi >
Re: Help with wsdl2java
On Mon, Mar 30, 2009 at 1:18 PM, Frank Vyncke wrote:
> I,
>
> Am starting to develop a 'client' for a gSOAP based server, using MTOM
> attachments.
>
> I have a wsdl file, but when I try to compile the wsdl file, I get an
> exception with the following message:
>
> Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
> the element {http://www.w3.org/2004/08/xop/include}Include from the parent
> schema http://www.genivia.com/schemas/mtom_stream_test.xsd
>
> Can anyone tell me where this error comes from, because the wsdl file does
> import the http://www.w3.org/2004/08/xop/include schema correctly (I think,
> there is no way I can check if it really imported the schema or not).
>
> Thanks
> Frank
>
>
I'd try validating the wsdl with an outside tool like Eclipse WTP, so
you can determine whether its really a valid wsdl or not. Please
excuse if you've already done that.
- R
Re: wsdl2java issue in upgrading from axis 1.2 to 1.4
Hello, I got exactly the same issue. This occurs with axis 1.3 and axis 1.4. If you add a "foo" attribute in your wsdl like this : The java Class ItemList will be correctly generated. So it appears to be a regression in axis from 1.3... Maybe someone has an other explanation and/or solution? JC 2009/3/30 Rishi Renjith : > Hello, > In my project, we are planning to upgrade from axis 1.2 to axis 1.4. But > when we tested, we noticed that wsdl2java is not generating some java > classes which it used to generate in axis 1.2 > For eg, with the wsdl structure as below, > > > > nillable="true"/> > > > > > maxOccurs="49" nillable="true"/> > > > > > maxOccurs="1" nillable="true"/> > > > wsdl2java is not generating a class for ItemList in axis 1.4, but it used to > generate a class for ItemList in axis1.2. > Is wsdl2java in 1.4 backward compatible with 1.2 ? > > > Thanks, > Rishi
Help with wsdl2java
I,
Am starting to develop a 'client' for a gSOAP based server, using MTOM
attachments.
I have a wsdl file, but when I try to compile the wsdl file, I get an
exception with the following message:
Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
the element {http://www.w3.org/2004/08/xop/include}Include from the parent
schema http://www.genivia.com/schemas/mtom_stream_test.xsd
Can anyone tell me where this error comes from, because the wsdl file does
import the http://www.w3.org/2004/08/xop/include schema correctly (I think,
there is no way I can check if it really imported the schema or not).
Thanks
Frank
wsdl2java issue in upgrading from axis 1.2 to 1.4
Hello, In my project, we are planning to upgrade from axis 1.2 to axis 1.4. But when we tested, we noticed that wsdl2java is not generating some java classes which it used to generate in axis 1.2 For eg, with the wsdl structure as below, wsdl2java is not generating a class for ItemList in axis 1.4, but it used to generate a class for ItemList in axis1.2. Is wsdl2java in 1.4 backward compatible with 1.2 ? Thanks, Rishi
RE: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility
this discussion was initiated by WS-Policy embedded in WSDL from Dennis S If memory serves he mentioned something about various transports not being handled? Is this still the case? Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. > Date: Wed, 25 Mar 2009 16:01:18 -0500 > From: se...@ittc.ku.edu > To: axis-user@ws.apache.org > CC: k...@ittc.ku.edu > Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java > utility > > Hi Pradeep, > > That time frame is fantastic and works great for us! I look forward to > hearing from you or seeing the JIRA status change. > > Thank you very much. > > leon > > - Original Message - > From: "Pradeep Fernando" > To: axis-user@ws.apache.org > Sent: Wednesday, March 25, 2009 8:46:21 AM GMT -06:00 US/Canada Central > Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java > utility > > Hi leon, > > I'm bit bussy with my GSOC & hopefully i would be able to fix this within > this week itself. I have gathered required info to > work on this issue & looks good. Sagara gave me some valuable info on woden > parser. > > thanks , > pradeep fernando. > > -- > Leon S. Searl, Software/Hardware Research Engineer > Information and Telecommunication Technology Center, University of Kansas > Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612 > Ph: 785-864-7820 Fax: 785-864-0387 > http://www.ittc.ku.edu > _ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009
Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility
Hi Pradeep, That time frame is fantastic and works great for us! I look forward to hearing from you or seeing the JIRA status change. Thank you very much. leon - Original Message - From: "Pradeep Fernando" To: axis-user@ws.apache.org Sent: Wednesday, March 25, 2009 8:46:21 AM GMT -06:00 US/Canada Central Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility Hi leon, I'm bit bussy with my GSOC & hopefully i would be able to fix this within this week itself. I have gathered required info to work on this issue & looks good. Sagara gave me some valuable info on woden parser. thanks , pradeep fernando. -- Leon S. Searl, Software/Hardware Research Engineer Information and Telecommunication Technology Center, University of Kansas Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612 Ph: 785-864-7820 Fax: 785-864-0387 http://www.ittc.ku.edu
