Re: AXIS C++ and AIX
Hi, Our tester just found this very same problem the other day - I'll find out from him what the resolution was. (He's not in until tomorrow UK time). Yes, the version is supposedly 2.2.0 i.e. that's what it says on the can ! Antoine Galataud [EMAIL PROTECTED] 14/03/2006 14:46 Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: AXIS C++ and AIX Hi ! It's me, again ! I didn't have a lot of time to test since my last mail, but now I'm in. I'm facing a strance problem, while running simple_axis_server : there are incorrect symbols referenced in libaxis_xerces.a, which is noramlly linked against xerces 2.2.0 When I run simple_axis_server, I get this in the startup logs : [14/03/2006 15:38:14:466 NFT] 1 AxisConfig getAxisConfProperty @205a2108,@2 /kplustp/thirdparty/axis/c++/1.6a.n/rs6000/axis-c-1.6a.n-AIX-trace-bin /lib/axis/libaxis_xerces.a [14/03/2006 15:38:14:466 NFT] 1 XMLParserFactory loadLib [14/03/2006 15:38:14:958 NFT] 1 AxisEngineException AxisEngineException @2ff209a8, [14/03/2006 15:38:14:958 NFT] 1 - I 29, Failed to load parser within server engine: [14/03/2006 15:38:14:958 NFT] 1 - I Error Message='Exec format error' Error Code='8' [14/03/2006 15:38:14:958 NFT] 1 - I Load lib error=' 0509-130 Symbol resolution failed for /kplustp/thirdparty/axis/c++/1.6a.n/rs6000/axis- c-1.6a.n-AIX-trace-bin/lib/axis/libaxis_xerces.a because: [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setEncoding__Q2_11xercesc_2_211InputSourceFPCUs (number 30) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setPublicId__Q2_11xercesc_2_211InputSourceFPCUs (number 31) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setSystemId__Q2_11xercesc_2_211InputSourceFPCUs (number 32) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol transcode__Q2_11xercesc_2_29XMLStringFPCUs (number 35) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 S 78 /g For example, I will take setEncoding__Q2_11xercesc_2_211InputSourceFPCUs symbol. When I do a dump -t libxerces-c.a, I can found a similar symbol, but not exactly the same : setEncoding__Q2_11xercesc_2_211InputSourceFCPCUs (please note the C missing at the end of first symbol). I'm not sure we built with the same xerces version... Could you precise me the exact one you are using ? 2006/3/13, Antoine Galataud [EMAIL PROTECTED]: Thanks a lot John ! It works ;-) I'll try to give you more feedbacks asap; Thanks again ! 2006/3/13, John Hawkins [EMAIL PROTECTED] : Hi Antoine, can you try changing the build/buildApache13Module.xml file please. There's a line there that currently reads -linker extends=AIXLinker linkerarg value=-r / /linker can you change that to be linker extends=AIXLinker linkerarg value=-G / /linker this makes the compiler link at runtime - but I haven't got a runtime to try it on - but it does give you the load header and makes the file executable for you. Antoine Galataud [EMAIL PROTECTED] 11/03/2006 17:20 Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: AXIS C++ and AIX Sure, I'm not familiar with AIX yet. What's strange is that all others libs built well. I don't think libaxiscpp_mod.so needs particular options, it just needs to be linked against apache libs... When I build all the distribution, every lib is executable (+x), except this one. Each one display a loader section when I execute dump command, except this one. I don't know where to search for this issue. Thanks 2006/3/10, John Hawkins [EMAIL PROTECTED] : no. My only suggestion is that you familiarise yourself more with the AIX compiler options. Antoine Galataud [EMAIL PROTECTED] 09/03/2006 16:59 Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: AXIS C++ and AIX No way, the libaxiscpp_mod.so is still corrupted ! (I tried with -brtl and -c). It's weird... Do you have another idea ? Thanks 2006/3/9, Antoine Galataud [EMAIL PROTECTED] : Thanks a lot ! I'll try that immediatly. 2006/3/9, John Hawkins [EMAIL
Axis C++ 1.6Beta fails to load mod_axis2.dll
Hi, While developing my application, I've had Axis C++ 1.5 and 1.6Beta running on Win2000 Server successfully, and 1.5 running on Win2003 Server successfully too. My final deliverable requires Axis C++ 1.6Beta (due to other issues that were fixed) running on Win2003 Server. This particular configuration has the EXACT same problem as reported by others for different combinations of OS and Axis C++ version: Syntax error on line 957 of C:/Program Files/Apache Group/Apache2/conf/httpd.conf: Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_axis2.dll into server: The specified module could not be found. From Event Viewer: The Apache service named reported the following error: Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_axis2.dll into server: The specified module could not be found. . and The Apache service named reported the following error: Syntax error on line 957 of C:/Program Files/Apache Group/Apache2/conf/httpd.conf: . Line 957 is the first line below: LoadModule axis_module modules/mod_axis2.dll Location /axis SetHandler axis /Location If I comment this line, Apache starts on Win2003, but axis is not available. I've followed all the instructions in wininstall-guide, triple checked it was done correctly, the module is there, in the correct directory ... HELP! Has this problem been seen by others using 1.6Beta? Has there been any solutions for other OS/AxisC++ combinations that I could try? I'm running: Windows Server 2003 R2, Enterprise Edition, SP1 Apache 2.0.55 (apache_2.0.55-win32-x86-nossl.msi) Any suggestions appreciated, Thanks Frank
Re: AXIS C++ and AIX
Hi, I got this same error message when I used the xerces libraries downloaded from the site pointed in the axis installation document. For me this problem occurred because our build machine having a different xerces parser compared to mine. After getting the xerces libraries from the build machine, I could to start the simple_axis_server. 'ls -l' of these libraries gives lrwxrwxrwx 1 axistest usr 14 Mar 10 12:19 libxerces-c.a - libxerces-c.so -rwxr-xr-x 1 axistest usr 5704781 Mar 10 12:19 libxerces-c.so -rwxr-xr-x 1 axistest usr 5704781 Oct 12 2004 libxerces-c22.0.so -rwxr-xr-x 1 axistest usr 5704781 Oct 12 2004 libxerces-c22.so Here the size of the libraries are little higher compared to the one I downloaded. I will try to find out from the build team, from where they got these xerces libraries. Regards James -- James Jose Messaging Clients Team, WMQDDC IBM Software Labs, India Direct: 91-80- 25094331 Ext :2331 E-mail: [EMAIL PROTECTED] Antoine Galataud [EMAIL PROTECTED] 03/14/2006 22:50 Please respond to Apache AXIS C User List To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: AXIS C++ and AIX Thanks for your answer. I stay tuned 2006/3/14, John Hawkins [EMAIL PROTECTED]: Hi, Our tester just found this very same problem the other day - I'll find out from him what the resolution was. (He's not in until tomorrow UK time). Yes, the version is supposedly 2.2.0 i.e. that's what it says on the can ! Antoine Galataud [EMAIL PROTECTED] 14/03/2006 14:46 Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: AXIS C++ and AIX Hi ! It's me, again ! I didn't have a lot of time to test since my last mail, but now I'm in. I'm facing a strance problem, while running simple_axis_server : there are incorrect symbols referenced in libaxis_xerces.a, which is noramlly linked against xerces 2.2.0 When I run simple_axis_server, I get this in the startup logs : [14/03/2006 15:38:14:466 NFT] 1 AxisConfig getAxisConfProperty @205a2108,@2 /kplustp/thirdparty/axis/c++/1.6a.n/rs6000/axis-c-1.6a.n-AIX-trace-bin /lib/axis/libaxis_xerces.a [14/03/2006 15:38:14:466 NFT] 1 XMLParserFactory loadLib [14/03/2006 15:38:14:958 NFT] 1 AxisEngineException AxisEngineException @2ff209a8, [14/03/2006 15:38:14:958 NFT] 1 - I 29, Failed to load parser within server engine: [14/03/2006 15:38:14:958 NFT] 1 - I Error Message='Exec format error' Error Code='8' [14/03/2006 15:38:14:958 NFT] 1 - I Load lib error=' 0509-130 Symbol resolution failed for /kplustp/thirdparty/axis/c++/1.6a.n/rs6000/axis- c-1.6a.n-AIX-trace-bin/lib/axis/libaxis_xerces.a because: [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setEncoding__Q2_11xercesc_2_211InputSourceFPCUs (number 30) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setPublicId__Q2_11xercesc_2_211InputSourceFPCUs (number 31) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol setSystemId__Q2_11xercesc_2_211InputSourceFPCUs (number 32) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 Symbol transcode__Q2_11xercesc_2_29XMLStringFPCUs (number 35) is not exported from [14/03/2006 15:38:14:958 NFT] 1 - I dependent module /kplustp/thirdparty/xml/xerces/c++/2_2_0/rs6000/lib/libxerces- c.a. [14/03/2006 15:38:14:958 NFT] 1 - I 0509-136 S 78 /g For example, I will take setEncoding__Q2_11xercesc_2_211InputSourceFPCUs symbol. When I do a dump -t libxerces-c.a, I can found a similar symbol, but not exactly the same : setEncoding__Q2_11xercesc_2_211InputSourceFCPCUs (please note the C missing at the end of first symbol). I'm not sure we built with the same xerces version... Could you precise me the exact one you are using ? 2006/3/13, Antoine Galataud [EMAIL PROTECTED]: Thanks a lot John ! It works ;-) I'll try to give you more feedbacks asap; Thanks again ! 2006/3/13, John Hawkins [EMAIL PROTECTED] : Hi Antoine, can you try changing the build/buildApache13Module.xml file please. There's a line there that currently reads -linker extends=AIXLinker linkerarg value=-r / /linker can you change that to be linker extends= AIXLinker linkerarg value=-G / /linker this makes the compiler link at runtime - but I haven't got a runtime to try it on - but it does give you the load header and makes
Deploy does nothing
Hi there :O) I was hoping that someone could help me with an axis problem. I have generated a web service with the tools Java2WSDL and WSDL2Java, I have filled in the blanks in the SoapBindingImpl and compiled the files. I have packaged the class files in a jar file and saved it in the WEB-INF\lib dir. Now I have deployed my web service, no problem! The problem is that the deploy.wsdd apparently does absolutely nothing. The server-conf is unchanged and there is no service running. What to do?! Med Venlig Hilsen Christina Wulf E-mail: [EMAIL PROTECTED] Mobil: 51 94 61 04
some axis2 deployment questions
Hi, I'm going to publish a simple service using axis2 war distribution. Now I'm running into some (maybe simple) questions, which I can not solve with the user guide: 1) what's the difference between RawXML and RPC message receivers? With RawXML the methods signature gets OMElement input and output? If I don't want to change my business class I have to use RPCMessageReceiver, right? 2) can I use patterns like: * or multiple operations names like getString getInt to publish a bunch of operations? 3) If I don't specify any operation inside my service element all operations are published. Can I set the messageReceiver to use for all operations? 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this? thx a lot Dominik __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
java.lang.IllegalArgumentException
Hi,
I get the following exception when calling a web service using Axis,
I am calling the Web Service from a JSP page on Tomcat
Any ideas how I can find out what is causing this problem
{http://xml.apache.org/axis/}stackTrace:java.lang.IllegalArgumentExcepti
on
at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeser
ializer.java:176)
at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja
va:502)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1087)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
171)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2448)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
Thanks,
William
Re: [Axis2] EchoNonBlockingDualClient problem
Hi,I have the same problem with Tomcat 5.5 and have two questions:1) Why does my client HTTP server is immediately closed and i get I/O exception when server tries to post the response? 2) Why does it print "waiting" when options.setUseSeparateListener() is passed false? (This is Antony Wilson's question actually) Thanks a lot.Ali Sadik KumlaliFIRST CASE + Original EchoNonBlockingDualClient.java + System.out.println("waiting..."); in while loopClient Log---testEchoNonBlockingDualClient: [java] - Deploying module : addressing [java] - Starting to process SOAP 1.1 message [java] ?xml version='1.0' encoding='utf-8'?soapenv:E
nvelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"soapenv:Headerwsa:To xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"http://10.10.10.103:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__/wsa:Towsa:ReplyTo xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"wsa:Addresshttp://127.0.0.1:8080/axis2/services/MyService/wsa:Address/wsa:Fromwsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"D3C49495E884E3019B11423375911122/wsa:MessageIDwsa:RelatesTo xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
wsa:RelationshipType="wsa:Reply"975BF946D7CFA918C611423375837211/wsa:RelatesTo/soapenv:Headersoapenv:Bodyexample1:echo xmlns:example1="http://example1.org/example1"example1:TextAxis2 Echo String /example1:Text/example1:echo/soapenv:Body/soapenv:Envelope [java] [SimpleHTTPServer] Stop calledServer Log--- Deploying module : addressing- Deploying module : security- Starting to process SOAP 1.1 message- I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught when processing request: The server 10.10.10.103 failed to respond- Retrying requestSECOND CASE: + Original EchoNonBlockingDualClient.java + System.out.println("waiting..."); in while loop
p; +
options.setUseSeparateListener(false); Client Log---testEchoNonBlockingDualClient: [java] - Deploying module : addressing [java] waiting... [java] - Starting to process SOAP 1.1 message [java] ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"soapenv:Headerwsa:To xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Towsa:ReplyTo
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"wsa:Addresshttp://127.0.0.1:8080/axis2/services/MyService/wsa:Address/wsa:Fromwsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"D3C49495E884E3019B11423376489274/wsa:MessageIDwsa:RelatesTo xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" wsa:RelationshipType="wsa:Reply"6439FE16DCA2252A8E11423376486611/wsa:RelatesTo/soapenv:Headersoapenv:Bodyexample1:echo xmlns:example1="http://example1.org/example1"example1:TextAxis2 Echo String /example1:Text/example1:echo/soapenv:Body/soapenv:EnvelopeServer Log--- De
ploying
module : addressing- Deploying module : security- Starting to process SOAP 1.1 messagerobert lazarski [EMAIL PROTECTED] wrote: Could you start another thread with an axis2 prefix mentioning jboss ? I know jboss with web services ok, but it was with either axis 1 or jwsdp - not axis2 . Are you using wsdl and ejb ? Robert http://www.braziloutsource.com/On 3/13/06, Brian Shields [EMAIL PROTECTED] wrote:Tony,Apologies for jumping into this thread on an unr
elated
issue but i notice you have axis2 deployed on JBoss 4.0. I am about to undertakethis task and was wondering if there was any resources on the web tohelp in it. I dont have a lot of experience with JBoss so not looking forward to it!!Regards,BrianAntony Wilson wrote: I have not been able to get the EchonNonBlockingDualClient example to work as described in the documentation.In my setup, I have Axis2 deployed to JBoss 4.0.3 and I have modified the userguide.example1.MyService to delay for about 10 seconds before responding (leaving the 'echo' method).After packaging and deploying the MyService.aar to Axis2, I run EchoNonBlockingDualClient example...slightly modified to add a print statement within the while loop...like sopublic static void main(String[] args)
{try {
Re: some axis2 deployment questions
See my responses inline:On 3/14/06, SOA Work [EMAIL PROTECTED] wrote: Hi,I'm going to publish a simple service using axis2 war distribution.Now I'm running into some (maybe simple) questions, which I can not solve with the user guide:1) what's the difference between RawXML and RPC message receivers? With RawXML the methods signature gets OMElement input and output? If I don't want to change my business class I have to use RPCMessageReceiver, right? I haven't used RPCMessageReceiver - but the version.aar does and it just returns a String - unlike the other recievers that use OMElement. RPCCallTest also works with Strings. 2) can I use patterns like: * or multiple operations names like getString getIntto publish a bunch of operations? I believe just * is supported. 3) If I don't specify any operation inside my service element all operations are published. Can I set the messageReceiver to use for all operations? Not sure. 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this? rpc encoded currently is not supported. thx a lotDominik__ Verschicken Sie romantische, coole und witzige Bilder per SMS!Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
Re: java.lang.IllegalArgumentException
Hello William,
Looks like a tough one.. For starters, use tcpmon to capture the SOAP
message. Checking the SOAP message usually helps to determine whether
the problem is on the sending or receiving end.
Regards,
Dies
William Ward wrote:
Hi,
I get the following exception when calling a web service using Axis,
I am calling the Web Service from a JSP page on Tomcat
Any ideas how I can find out what is causing this problem
{http://xml.apache.org/axis/}stackTrace:java.lang.IllegalArgumentExcepti
on
at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeser
ializer.java:176)
at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja
va:502)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1087)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
171)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2448)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
Re: An RFC example needed!
Hi all,
Thanks for your reply's.
Take a look at the migration guide:
http://ws.apache.org/axis2/0_93/migration.html
Yes I've seen it, I took some time to implement that example, but it isn't
complete. It uses the echo example, look at the the word 'ClientUtil' in
ClientUtil.getEchoOMElement(); while at the same time the Axis1 example
above clearly shows that you can work with the 'String' type right out of
the box (and it's terribly simple to register other types as well!!). On the
other hand, Axis2 introduces an 'OMElement' but nothing clearly shows (at
least for me) how to work with it. I've seen some registering stuff in the
echo example though, but it didn't work out. Really, a simple example which
completely works (like with a class Address { String name,String telephone}
) is needed. Simple examples makes an API good.
Another thing, I don't like a lot of code being added to my data classes.
I've seen what axis2 does to my classes. Is that really needed? In Axis1 I
don't have any generated garbage in my classes (except get and set functions
which are harmless); in fact there's only one _method_ (not even a class)
which calls the service, complete with registering and everything. It looks
like in Axis2 all classes will be filled with generated stuff, before I can
be a client application. Or am I wrong?
http://issues.apache.org/jira/browse/AXIS2-485?page=all
I'll look to it in a moment, thanks! Perhaps I can help?
BTW, the address example in the axis 1.x uses WSDL style 'rpc encoded' .
For
the time being you need to use document / literal with axis2 .
I switched to wrapped/literal right away because I'm talking with .NET
clients too. But I'm not using that example at all, I wrote my own;). I only
looked at it as it is a clear way of how to write my client-method. That was
about two weeks ago.
You're right -- the Apache SOAP page should provide a warning that tells
you to use Axis 1 instead.
Thanks. Is there a place where I should mail it to?
Of course, Axis2 doesn't look complete yet, in the future the main Axis1
page should say that it is depreciated.
After you have refined your WSDL file, then you want to use wsdl2java to
regenerate your service skeleton and WSDD file.
Perhaps if you posted your WSDL and WSDD files we could provide you with a
little more assistance.
Well, in fact, I simply did that, I generated the WSDL, it looked fine, then
I gave it to the .NET service, and they implemented it accordingly. No
wonder: everything works fine (this computer being a server and running the
client code to access this computer). But really, the WSDL or the message is
not the issue at all. I manually wrote a serialiser to get capitals inside
some headers, untill the generated message worked fine (peeking with the
TCPTunneler), while manually sending the message itsself with some a
pure-java code. If I send the captured message with a normal Java socket, it
works perfectly, but if Axis1 does the trick, it simply doesn't work. And
the only difference in the two messages is the \1.0 -- \1.1 number. See for
yourself below! So, how do I force the HTTP\1.1 usage?
Thank you very much!,
Niels
-
Sending with a pure-java client:
POST /axis/services/rpcrouter HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: http://www.voorst.nl/VoorstVariant/getGemeenteInfo;
User-Agent: Java/1.5.0_06
Host: localhost:90
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 1198
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header
ns1:UserCredentials xsi:type=ns1:UserCredentials
xmlns:ns1=http://www.voorst.nl/VoorstVariant/;
ns1:AutorizationKey xsi:nil=true/
ns1:Password xsi:type=xsd:string***/ns1:Password
ns1:UserId xsi:type=xsd:string***/ns1:UserId
/ns1:UserCredentials
/soapenv:Header
soapenv:Body
getGemeenteInfo xmlns=http://www.voorst.nl/VoorstVariant/;
p xsi:type=ns2:Polygoon
xmlns:ns2=http://www.voorst.nl/VoorstVariant/;
ns2:gmlPolygoon
xsi:type=xsd:stringlt;gml:Polygongt;lt;gml:outerBoundaryIsgt;lt;gml:LinearRinggt;lt;gml:coordinatesgt;203000,471000
203600,472000 203700,472000 203700,471900
203600,471900lt;/gml:coordinatesgt;lt;/gml:LinearRinggt;lt;/gml:outerBoundaryIsgt;lt;/gml:Polygongt;/ns2:gmlPolygoon
/p
/getGemeenteInfo
/soapenv:Body
/soapenv:Envelope
Sending with Axis1:
POST /axis/services/rpcrouter 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: localhost:90
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: http://www.voorst.nl/VoorstVariant/getGemeenteInfo;
Content-Length: 1057
?xml version=1.0
RE: java.lang.IllegalArgumentException
Hello Dies, thank you for the reply, I used tcpmon to capture the SOAP message, I believe the problem is at the receiving end as I get the response back from the Web Service no problem, it looks like it has a problem de-serializing the response. The odd thing is if I call the same Web Serice using just a test Java application, I don't see any exception on the Axis side It seems to be just when I use JSP, Tomcat and Axis, I have tried just creating a simple JSP page that has the same code as the test Java Application, but I always get the Axis exception when using JSP Tomcat, even though it is the same code libraries for both applications below is the SOAP request / response that I see using tcpmon : Regards, William == Listen Port: 8081 Target Host: 47.166.106.127 Target Port: 80 Request POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 47.166.106.127:8081 Cache-Control: no-cache Pragma: no-cache SOAPAction: http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContactH istory Content-Length: 423 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ReadCustomerContactHistory xmlns=http://webservices.ci.ccmm.applications.nortel.com; id35/id sessionKey2qrc3E7a00/sessionKey /ReadCustomerContactHistory /soapenv:Body /soapenv:Envelope Response HTTP/1.1 200 OK Connection: close Date: Tue, 14 Mar 2006 13:46:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 1.1.4322 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=utf-8 Content-Length: 4823 ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body ReadCustomerContactHistoryResponse xmlns=http://webservices.ci.ccmm.applications.nortel.com; ReadCustomerContactHistoryResult customerID xmlns=http://datatypes.ci.ccmm.applications.nortel.com;35/customerID contactsList xmlns=http://datatypes.ci.ccmm.applications.nortel.com; CIContactReadType id80/id customerID35/customerID originalSubjectsfs/originalSubject sourceWeb/source statusNew/status skillset id10/id nameOB_Test1/name markAsDeletedfalse/markAsDeleted statusUnspecified/status /skillset priorityUnspecified/priority timezone0/timezone arrivalTime time2006-03-14T10:39:28.000-00:00/time /arrivalTime openDuration0/openDuration contactTypeScheduledCallback/contactType actionList CIActionReadType id203/id contactID80/contactID subjectsfs/subject textdfsdfdf/text callbackTime time2006-03-14T10:39:28.4678080-00:00/time /callbackTime callbackStatusUnspecified/callbackStatus creationTime time2006-03-14T10:39:28.000-00:00/time /creationTime sourceCallback_Request_from_Customer/source timeAllocated0/timeAllocated outboundTalkTime0/outboundTalkTime outboundDispositionCode / actionTypeScheduledCallback/actionType /CIActionReadType /actionList /CIContactReadType CIContactReadType id81/id customerID35/customerID originalSubjectsfsdf/originalSubject sourceWeb/source statusNew/status skillset id2/id nameOB_Default_Skillset/name markAsDeletedfalse/markAsDeleted statusUnspecified/status webDescription / /skillset priorityUnspecified/priority timezone0/timezone arrivalTime time2006-03-14T10:39:34.000-00:00/time
Re: [Axis2] EchoNonBlockingDualClient problem
Hi everybody!
I'm also experiencing the same problem. I run axis2 v0.93 on tomcat
5.5.7. My code is slightly different than the EchoNonBlockingDualClient
but it's basically the same:
public void
startinsertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc,
final
AstrodasPeerCallbackHandler callback)
throws RemoteException {
Call call = new Call(_serviceContext);
call.setClientOptions(_clientOptions);
MessageContext messageContext = getMessageContext();
_clientOptions.setSoapAction(insertMappingAnnotations);
// Uses two separate listeners: dual transport.
call.engageModule(new QName(Constants.MODULE_ADDRESSING));
_clientOptions.setListenerTransportProtocol(Constants.TRANSPORT_HTTP);
_clientOptions.setUseSeparateListener(true);
// Sets the exception throwing status.
_clientOptions.setExceptionToBeThrownOnSOAPFault(true);
// Sets the properties.
SOAPEnvelope envelope = createEnvelope();
setValueDoc(envelope,AstrodasPeerinsertMappingAnnotationsDatabindingSupporter.toOM(requestDoc));
messageContext.setEnvelope(envelope);
call.invokeNonBlocking(operations[0], messageContext,
new Callback() {
public void onComplete(AsyncResult result) {
Object object =
AstrodasPeerinsertMappingAnnotationsDatabindingSupporter
.fromOM(getElement(result.getResponseEnvelope(),doc),
InsertMappingAnnotationsResponseDocument.class);
callback.receiveResultinsertMappingAnnotations((InsertMappingAnnotationsResponseDocument)
object);
}
public void reportError(Exception e) {
callback.receiveErrorinsertMappingAnnotations(e);
}
});
}
I also get the same problem using a dual transport blocking client:
public InsertMappingAnnotationsResponseDocument
insertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc)
throws RemoteException {
MessageContext messageContext = getMessageContext();
Call call = new Call(_serviceContext);
_clientOptions.setSoapAction(insertMappingAnnotations);
call.setClientOptions(_clientOptions);
// Uses two separate listeners: dual transport.
call.engageModule(new QName(Constants.MODULE_ADDRESSING));
_clientOptions.setListenerTransportProtocol(Constants.TRANSPORT_HTTP);
_clientOptions.setUseSeparateListener(true);
// Sets the exception throwing status.
// Sets the properties.
populateModules(call);
SOAPEnvelope envelope = createEnvelope();
// Style is Doc.
setValueDoc(envelope,AstrodasPeerinsertMappingAnnotationsDatabindingSupporter.toOM(requestDoc));
messageContext.setEnvelope(envelope);
MessageContext responseMessageContext =
call.invokeBlocking(operations[0],messageContext);
SOAPEnvelope responseEnvelope = responseMessageContext.getEnvelope();
Object obj = AstrodasPeerinsertMappingAnnotationsDatabindingSupporter
.fromOM(getElement(responseEnvelope,doc),InsertMappingAnnotationsResponseDocument.class);
return (InsertMappingAnnotationsResponseDocument)obj;
}
The request arrives to the client and is executed successfully but the
client doesn't get any response. Actually, the server sends a response
to the client, here it is:
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
soapenv:Fault
faultcodeClient/faultcode
faultstring
For input string: 0:0:0:0:0:0:1:6060; nested exception is:
.java.net.MalformedURLException: For input string:
0:0:0:0:0:0:1:6060; nested exception is:
.org.apache.axis2.AxisFault: For input string:
0:0:0:0:0:0:1:6060; nested exception is:
.java.net.MalformedURLException: For input string:
0:0:0:0:0:0:1:6060
/faultstring
faultactorhttp://myAxisServer/role/default/faultactor
detail
soapenv:Exception
org.apache.axis2.AxisFault: For input string:
0:0:0:0:0:0:1:6060; nested exception is:
.java.net.MalformedURLException: For input string:
0:0:0:0:0:0:1:6060; nested exception is:
.org.apache.axis2.AxisFault: For input string:
0:0:0:0:0:0:1:6060; nested exception is:
.java.net.MalformedURLException: For input string:
0:0:0:0:0:0:1:6060
.at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:265)
.at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:93)
.at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:42)
.at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:158)
.at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:211)
.at
Re: java.lang.IllegalArgumentException
Hello William, We'd need to see the WSDL to see if the SOAP message is right. Unfortunately the SOAP message is rather long and complicated. You might not get any replies. As you seem to use complex structures (array of complex types?) I imagine the Axis engine relies on the Helper classes (or helper code in the generated Javabeans) on the client side. Just checking, but you did not happen to have removed these classes/methods? Regards, Dies William Ward wrote: Hello Dies, thank you for the reply, I used tcpmon to capture the SOAP message, I believe the problem is at the receiving end as I get the response back from the Web Service no problem, it looks like it has a problem de-serializing the response. The odd thing is if I call the same Web Serice using just a test Java application, I don't see any exception on the Axis side It seems to be just when I use JSP, Tomcat and Axis, I have tried just creating a simple JSP page that has the same code as the test Java Application, but I always get the Axis exception when using JSP Tomcat, even though it is the same code libraries for both applications below is the SOAP request / response that I see using tcpmon : Regards, William == Listen Port: 8081 Target Host: 47.166.106.127 Target Port: 80 Request POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 47.166.106.127:8081 Cache-Control: no-cache Pragma: no-cache SOAPAction: http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContactH istory Content-Length: 423 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ReadCustomerContactHistory xmlns=http://webservices.ci.ccmm.applications.nortel.com; id35/id sessionKey2qrc3E7a00/sessionKey /ReadCustomerContactHistory /soapenv:Body /soapenv:Envelope Response HTTP/1.1 200 OK Connection: close Date: Tue, 14 Mar 2006 13:46:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 1.1.4322 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=utf-8 Content-Length: 4823 ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body ReadCustomerContactHistoryResponse xmlns=http://webservices.ci.ccmm.applications.nortel.com; ReadCustomerContactHistoryResult customerID xmlns=http://datatypes.ci.ccmm.applications.nortel.com;35/customerID contactsList xmlns=http://datatypes.ci.ccmm.applications.nortel.com; CIContactReadType id80/id customerID35/customerID originalSubjectsfs/originalSubject sourceWeb/source statusNew/status skillset id10/id nameOB_Test1/name markAsDeletedfalse/markAsDeleted statusUnspecified/status /skillset priorityUnspecified/priority timezone0/timezone arrivalTime time2006-03-14T10:39:28.000-00:00/time /arrivalTime openDuration0/openDuration contactTypeScheduledCallback/contactType actionList CIActionReadType id203/id contactID80/contactID subjectsfs/subject textdfsdfdf/text callbackTime time2006-03-14T10:39:28.4678080-00:00/time /callbackTime callbackStatusUnspecified/callbackStatus creationTime time2006-03-14T10:39:28.000-00:00/time /creationTime sourceCallback_Request_from_Customer/source timeAllocated0/timeAllocated outboundTalkTime0/outboundTalkTime outboundDispositionCode / actionTypeScheduledCallback/actionType /CIActionReadType /actionList /CIContactReadType CIContactReadType id81/id customerID35/customerID originalSubjectsfsdf/originalSubject sourceWeb/source statusNew/status
Re: An RFC example needed! - 2
Hi all, Well, I fixed the problem, by enabling the java.net debug mode, I could easily track down the problem and solve it (reading between the lines of encoded and decoded stuff). Yesterday I ended up with the XML message as I've sended it, without knowing it I was nearly finished. I only had to specify the return type (because it is an array-agr), and voila. Note that I'm not unhappy with Axis, actually I'm quite happy with it. I hope the things I say help improving Axis. Like the suggestion to return the plain HTTP-output when the response serialiser doesn't receive anything it can parse (for example when you are talking to a Microsoft webservice which doesn't use SOAP:FAULT to say things back but only in plain text without any soap headers). I hope Axis2 will end up as good as Axis1. For example, it's a good thing to use a deploy mechanism that looks more like Tomcat. I wondered why you'ld want to introduce another deploy language (the one in Apache SOAP and now the one in Apache Axis1) when already having the services.xml mechanism in Tomcat. Thanks for now, Niels Gorisse _ Don't just search. Find. Check out the new MSN Search! http://search.msn.com/
RE: java.lang.IllegalArgumentException
Hello Dies, I didn't modify any of the classes generated by WSDL2Java, but I don't see any helper methods in the generated client stubs, should I be seeing these ?? Regards, William -Original Message- From: Dies Koper [mailto:[EMAIL PROTECTED] Sent: 14 March 2006 14:02 To: axis-user@ws.apache.org Subject: Re: java.lang.IllegalArgumentException Hello William, We'd need to see the WSDL to see if the SOAP message is right. Unfortunately the SOAP message is rather long and complicated. You might not get any replies. As you seem to use complex structures (array of complex types?) I imagine the Axis engine relies on the Helper classes (or helper code in the generated Javabeans) on the client side. Just checking, but you did not happen to have removed these classes/methods? Regards, Dies William Ward wrote: Hello Dies, thank you for the reply, I used tcpmon to capture the SOAP message, I believe the problem is at the receiving end as I get the response back from the Web Service no problem, it looks like it has a problem de-serializing the response. The odd thing is if I call the same Web Serice using just a test Java application, I don't see any exception on the Axis side It seems to be just when I use JSP, Tomcat and Axis, I have tried just creating a simple JSP page that has the same code as the test Java Application, but I always get the Axis exception when using JSP Tomcat, even though it is the same code libraries for both applications below is the SOAP request / response that I see using tcpmon : Regards, William == Listen Port: 8081 Target Host: 47.166.106.127 Target Port: 80 Request POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 47.166.106.127:8081 Cache-Control: no-cache Pragma: no-cache SOAPAction: http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContac tH istory Content-Length: 423 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ReadCustomerContactHistory xmlns=http://webservices.ci.ccmm.applications.nortel.com; id35/id sessionKey2qrc3E7a00/sessionKey /ReadCustomerContactHistory /soapenv:Body /soapenv:Envelope Response HTTP/1.1 200 OK Connection: close Date: Tue, 14 Mar 2006 13:46:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 1.1.4322 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=utf-8 Content-Length: 4823 ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body ReadCustomerContactHistoryResponse xmlns=http://webservices.ci.ccmm.applications.nortel.com; ReadCustomerContactHistoryResult customerID xmlns=http://datatypes.ci.ccmm.applications.nortel.com;35/customerID contactsList xmlns=http://datatypes.ci.ccmm.applications.nortel.com; CIContactReadType id80/id customerID35/customerID originalSubjectsfs/originalSubject sourceWeb/source statusNew/status skillset id10/id nameOB_Test1/name markAsDeletedfalse/markAsDeleted statusUnspecified/status /skillset priorityUnspecified/priority timezone0/timezone arrivalTime time2006-03-14T10:39:28.000-00:00/time /arrivalTime openDuration0/openDuration contactTypeScheduledCallback/contactType actionList CIActionReadType id203/id contactID80/contactID subjectsfs/subject textdfsdfdf/text callbackTime time2006-03-14T10:39:28.4678080-00:00/time /callbackTime callbackStatusUnspecified/callbackStatus creationTime time2006-03-14T10:39:28.000-00:00/time /creationTime sourceCallback_Request_from_Customer/source timeAllocated0/timeAllocated outboundTalkTime0/outboundTalkTime
RE: org.apache.axis.message.MessageElement.getAsString() not in online JavaDoc
Does anyone have any info on this? Thanks again, Richard A. Neuendorff I spent quite a bit of time researching then including the Xerces libraries to serialize a MessageElement object into a string because I was unaware of getAsString(). I stumbled upon it while trying to do something else and found that it is in my downloaded JavaDoc for 1.2.1 and 1.3.1. Is there a reason it is not in the online JavaDoc? Is it a method that should be avoided for some reason? Thanks, Richard A. Neuendorff
[0.94] How can i shutdown connection after call
Hi all,
in my client class i have function like :
public TFileSendResponse storeFile(int type, String fileName, String
pathToFile) {
TFileSendResponse response = null;
try {
response = FileSend.response(makeCall(FileSend.request(new
TFileSend(,
, type, fileName, pathToFile)), storeFile));
} catch (Exception e) {
e.printStackTrace();
}
return response;
}
it's call function makeCall:
private MessageContext makeCall(MessageContext requestContext, String
action) {
ServiceClient client;
MessageContext result = null;
try {
// creating the Service
AxisService service = new AxisService(IXMLWS2);
// creating the operations
AxisOperation operation = new OutInAxisOperation();
operation.setName(new
javax.xml.namespace.QName(urn:XMLWSIntf-IXMLWS, action));
service.addOperation(operation);
client = new ServiceClient(new
ConfigurationContextFactory().createConfigurationContextFromFileSystem(AXIS2_HOME),
service);
client.getOptions().setTo(targetEPR);
client.getOptions().setSoapAction(urn:XMLWSIntf2-IXMLWS2# +
action);
client.getOptions().setExceptionToBeThrownOnSOAPFault(true);
client.getOptions().setTransportInProtocol(Constants.TRANSPORT_TCP);
client.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.CHUNKED,org.apache.axis2.Constants.VALUE_FALSE);
client.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
OperationClient opClient = client.createClient(new
javax.xml.namespace.QName(urn:XMLWSIntf-IXMLWS, action));
opClient.addMessageContext(requestContext);
opClient.execute(true);
return
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
} catch (AxisFault e) {
e.printStackTrace();
}
return result;
}
after execute, i have open connection to axis server, how can i terminate it ?
thanks in advance!
[Axis2] WSDL2Java client code creation
Hi all, we are playing around with the samples from the tutorial... we have extended the MyService to take a comlpexType (a string, an int and a double) and would like to create the client from the WSDL. Axis has created the attached WSDL from our service, but WSDL2Java fails when called like this: --- axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p org.apache.axis2 - with this error: -- Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:118) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage (WSDLValidatorExtension.java:70) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:80) ... 2 more If we try to enter anything else in the targetNamespace attribute in the WSDL, it gives us a NullPointerException instead. Any clues? Thanks a lot in advance! -- Sebi wsdl:definitions xmlns:ns1=http://org.apache.axis2/xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://org.apache.axis2/; targetNamespace=http://org.apache.axis2/;wsdl:typesxs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ns2=http://www.w3.org/2001/XMLSchema; xmlns:ns0=http://www.w3.org/2001/XMLSchema; xmlns:ns1=http://org.apache.axis2/xsd; ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualified ns2:targetNamespace=http://org.apache.axis2/xsd; xs:element ns0:name=echoRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element xs:element ns0:name=echoResponse xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=return ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element xs:element ns0:name=pingRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element xs:element ns0:name=plingRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param0 ns1:type=xs:string/ xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param1 ns1:type=xs:int/ xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param2 ns1:type=xs:double/ /xs:sequence /xs:complexType /xs:element xs:element ns0:name=plingResponse xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=return ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element xs:element ns0:name=pingFRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element /xs:schema/wsdl:typeswsdl:message name=pingFRequestMessagewsdl:part name=part1 element=ns1:pingFRequest//wsdl:messagewsdl:message name=plingResponseMessagewsdl:part name=part1 element=ns1:plingResponse//wsdl:messagewsdl:message name=echoResponseMessagewsdl:part name=part1 element=ns1:echoResponse//wsdl:messagewsdl:message name=echoRequestMessagewsdl:part name=part1 element=ns1:echoRequest//wsdl:messagewsdl:message name=pingRequestMessagewsdl:part name=part1 element=ns1:pingRequest//wsdl:messagewsdl:message name=plingRequestMessagewsdl:part name=part1 element=ns1:plingRequest//wsdl:messagewsdl:portType name=MyServicePortwsdl:operation name=plingwsdl:input message=tns:plingRequestMessage/wsdl:output message=tns:plingResponseMessage//wsdl:operationwsdl:operation name=pingFwsdl:input message=tns:pingFRequestMessage//wsdl:operationwsdl:operation name=echowsdl:input message= tns:echoRequestMessage/wsdl:output message=tns:echoResponseMessage//wsdl:operationwsdl:operation name=pingwsdl:input message=tns:pingRequestMessage//wsdl:operation/wsdl:portTypewsdl:binding name=MyServiceBinding type=tns:MyServicePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/wsdl:operation name=plingsoap:operation name=operation soapAction=pling style=document/wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2//wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2//wsdl:output/wsdl:operationwsdl:operation name=pingFsoap:operation name=operation soapAction=pingF
Re: Axis2 and JBoss 4.0 and Asynchronous Webservices
I looked more into this out of curiosity: 1) JBoss 4.0.x internally uses a modified version of Axis 1.x. However, they only support their own stacks: http://wiki.jboss.org/wiki/Wiki.jsp?page=WebServiceStacks Any stack not listed above is not supported. This includes Standalone Apache Axis, and the JWSDP Web Services Stack. Only the wscompile tool in the JWSDP is supported. This primarily means EJB - of course nothing is stopping you from using your WAR, handling your transactions via spring, hibernate etc. 2) The modified Axis 1.x stack is being phased out for their own stack, which supports JAXWS-2.0: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWS 3) They have a page Why is Apache Axis not supported http://www.jboss.org/index.html?module=bbop=viewtopicp=3889456#3889456 HTH, Robert http://www.braziloutsource.com/On 3/14/06, robert lazarski [EMAIL PROTECTED] wrote:Just to clarify - what you mention makes sense from a WAR standpoint. I'm unsure, however, how one would wire an EAR or SAR with EJB into an Axis2 Web Service. I've done a lot with EJB, JWSDP and JBoss, and using Axis 1.x would in several ways be similair. Axis2, however, doesn't currently support JAX-RPC which is what the EJB 2.1 spec is based on - and what JBoss is expecting. Now I could be wrong - in which case I would be pleasantly happy to admit. My frame of mind currently is that it'd take a few days to see if it is possible. Just my 2 cents. HTH, Robert http://www.braziloutsource.com/ On 3/14/06, Antony Wilson [EMAIL PROTECTED] wrote:Brian,I really did not do anything special for deploying Axis2 to JBoss 4.0.3.I unzipped the Axis2 war into the JBoss deploy directory and deployedthe Axis2 webservices to the Axis2 services directory (as described inthe Axis2 docs). By default, JBoss 4.0.2+ uses tomcat's classloadingimplementation vice their own unified/flat classloader. This approachisolates the classes/libraries per web application...so you avoid thelibrary/jar conflicts that can sometime arise from using a unified classloader (e.g., the default JBoss classloader). So as I understandit...it is basically like running on Axis2 on standalone Tomcat. If youare using an earlier version of JBoss 4.0.1sp1 or lower...you should modify a few lines in jbosshome\server\default\deploy\jbossweb-tomcat50.sar\META-INF\jboss-service.xmlas follows:!--Get the flag indicating if the normal Java2 parent first classloading model should be used over the servlet 2.3 web container firstmodel.--attribute name=Java2ClassLoadingCompliancefalse/attribute−!--A flag indicating if the JBoss Loader should be used. This loader uses a unified class loader as the class loader rather than the tomcatspecific class loader.The default is false to ensure that wars have isolated class loadingfor duplicate jars and jsp files.-- attribute name=UseJBossWebLoaderfalse/attributeThis will properly isolate the Axis2 classes and has worked for me. Fromthis point on...I just followed the instructions is in the Axis2 docs for deploying webservices.As mentioned in my earlier email...I have had problems with theEchoNonBlockingDualClient example...at this point I'm reasonablyconvinced that it is due to the fact that the webservice is not asynchronous. After reading a few earlier threads, I believe I have toextend the AbstractInOutAsyncMessageReceiver to create an asynchronousservice. Not that much fun:-( I really wish there was an example or default implementation in the Axis2 distro. But I guess it's a smallprice to pay for the power/flexibility of Axis2;-)Hope this helps,TonyBrian Shields wrote: Thats a bit disappointing, maybe i was a bit naive thinking it would be straight forward. I need to have a serious think how i will progress. I am not willing to stop using axis2, ive too much time invested now and everything set up the way i need it for my own research. Unfortunately i also have committments on a project that uses JBoss 4.0. How much of WS-Security is implemented in the most recent stable release of JBoss? How straightforward is it to implement security on existing (Web) SessionBeans? I particularly like the modular approach of axis2 which completely abstracts the security layer from the developer of the endpoint and vice versa. Any other help, pointers etc (maybe a url to a walk thru of deploying axis2 on JBoss 4 ; ) ) greatly appreciated. Regards, Brian. robert lazarski wrote: I haven't mixed JBoss and Axis2 together yet - but I know both reasonably well independently. I've used JBoss and EJB with JWSDP alot. Internally JBoss 4.0.x comes with Axis 1.x - though strangely their docs and examples favor JWSDP. Furthermore, It tends to be more natural to use a Statelful session bean with web services. There are Handlers that are part of Java itself and can be used with Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a lot. However, axis2 does not currently support JAX-RPC. JBoss is pretty wired into JAX-RPC. So to make Web
Re: null namespace generated for qualified elements
Anne,It worked after fixing the error i.e. tns:PutConfigRequest - tns:PutSCIRequest thank you,Vikas+Now, according to your WSDL, the child element of the SOAP Body should be
called cAnneOn 3/13/06, Vikas Singh [EMAIL PROTECTED] wrote:
Anne, Thanks for your help.I tried changes suggested by you but it did not work.WSDL file:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/
xmlns:tns=
http://myns/schemas/2006/02/26/sciwsdl xmlns:wsdl=
http://schemas.xmlsoap.org/wsdl/ xmlns:xsd=
http://www.w3.org/2001/XMLSchema name=NewWSDLFile targetNamespace=
http://myns/schemas/2006/02/26/sciwsdl xmlns:xsd1=
http://myns/schemas/2006/3/3/sci wsdl:types xsd:schema targetNamespace=
http://myns/schemas/2006/02/26/sciwsdl xmlns:scx=
http://myns/schemas/2006/3/3/sci elementFormDefault=qualified xsd:import
namespace=
http://myns/schemas/2006/3/3/scischemaLocation=
http://localhost:8080/jce/sci.xsd / xsd:element name=PutSCIRequest
xsd:complexType xsd:sequence xsd:element ref=scx:SCIConfigRoot / /xsd:sequence/xsd:complexType
/xsd:element xsd:element name=PutSCIResponse
xsd:complexType / /xsd:element /xsd:schema /wsdl:types wsdl:message name=PutSCIResponse
wsdl:part element=tns:PutSCIResponse name=PutSCIResponse /
/wsdl:message wsdl:message name=PutSCIRequest wsdl:part element=tns:PutSCIRequest name=PutSCIRequest /
/wsdl:message wsdl:portType name=SCIConfig
wsdl:operation name=putSCI wsdl:input message=tns:PutSCIRequest / wsdl:output message=tns:PutSCIResponse /
/wsdl:operation /wsdl:portType
wsdl:binding name=sciconfigSoapBinding type=tns:SCIConfig wsdlsoap:binding style=document transport=
http://schemas.xmlsoap.org/soap/http
/ wsdl:operation name=putSCI wsdlsoap:operationsoapAction=
http://myns/schemas/2006/02/26/sciwsdl/putSCI
/ wsdl:inputwsdlsoap:body parts=PutSCIRequest use=literal / /wsdl:input wsdl:outputwsdlsoap:body parts=PutSCIResponse use=literal /
/wsdl:output /wsdl:operation/wsdl:binding wsdl:service name=SCIConfigService
wsdl:port binding=tns:sciconfigSoapBinding name=config
wsdlsoap:addresslocation=http://localhost:8080/jce/services/config /
/wsdl:port /wsdl:service/wsdl:definitions
Pre-serialization request body : mywsdl:PutConfigRequest xmlns:mywsdl=
http://myns/schemas/2006/02/26/sciwsdl
scx:SCIConfigRoot xmlns:scx=http://myns/schemas/2006/3/3/sci/ xmlns:thttp=
http://myns/schemas/2006/3/3/transport/http/ schemaLocation=http://localhost:8080/jce/sci.xsd
serviceGroup=travelDepartment
scx:Policies thttp:TransportPolicy name=default.soap.http.policy thttp:AllowHttp10 false/thttp:AllowHttp10
thttp:KeepAliveConnections true/thttp:KeepAliveConnections
/thttp:TransportPolicy /scx:Policies/scx:SCIConfigRoot/mywsdl:PutConfigRequestPost-serialization request body
(in soapenv:Body) :mywsdl:PutConfigRequest xmlns:mywsdl=
http://myns/schemas/2006/02/26/sciwsdl
scx:SCIConfigRoot
schemaLocation=http://localhost:8080/jce/sci.xsd
serviceGroup=travelDepartment
xmlns:scx=http://myns/schemas/2006/3/3/sci/
xmlns:thttp=http://myns/schemas/2006/3/3/transport/http/
scx:Policies xmlns:scx=
thttp:TransportPolicy name=default.soap.http.policy xmlns:thttp=
thttp:AllowHttp10 xmlns:thttp=
false/thttp:AllowHttp10
thttp:KeepAliveConnections xmlns:thttp=true/thttp:KeepAliveConnections
/thttp:TransportPolicy
/scx:Policies
/scx:SCIConfigRoot
/mywsdl:PutConfigRequest
I get the following exception:org.xml.sax.SAXParseException: The value of the attribute prefix=xmlns,localpart=scx,rawname=xmlns:scx is invalid. Prefixed namespace bindings may not be empty.
When I change the pre-serialization request body to contain explicit namespace defintions for all the elements :mywsdl:PutConfigRequest xmlns:mywsdl=
http://myns/schemas/2006/02/26/sciwsdlscx:SCIConfigRoot xmlns:scx=http://myns/schemas/2006/3/3/sci/
xmlns:thttp=
http://myns/schemas/2006/3/3/transport/http/ schemaLocation=http://localhost:8080/jce/sci.xsd
serviceGroup=travelDepartment
scx:Policies xmlns:scx=http://myns/schemas/2006/3/3/sci/
thttp:TransportPolicy name=default.soap.http.policy xmlns:thttp=
http://myns/schemas/2006/3/3/transport/http/
thttp:AllowHttp10 xmlns:thttp=
http://myns/schemas/2006/3/3/transport/http/ false/thttp:AllowHttp10 thttp:KeepAliveConnections xmlns:thttp=
http://myns/schemas/2006/3/3/transport/http/
true/thttp:KeepAliveConnections /thttp:TransportPolicy /scx:Policies/scx:SCIConfigRoot/mywsdl:PutConfigRequestAxis, post serialization does not insert any empty namespace defintions but the handler method is not found.
Couldn't find an appropriate operation for XML QName {
http://myns/schemas/2006/02/26/sciwsdl}PutConfigRequest
when I tried changing
Re: [Axis2] A question about asynchronous services and message queue
Maybe I should clarify my point here: A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature. It is hard for an asynchronous service to handle long-run service requests without the support of a message queue and more important a persistence layer. I am not sure if they are correct. Any comments? Cheers,DonOn 3/12/06, Dong Liu [EMAIL PROTECTED] wrote: Hi, folks,When trying to deploy some async services to compare their performance to the sync ones, I realize that the async services make no sense with the support of a message queue. What is your idea? Cheers, Don
Re: [Axis2] A question about asynchronous services and message queue
On Tue, 2006-03-14 at 10:59 -0600, Dong Liu wrote: Maybe I should clarify my point here: 1. A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature. 2. It is hard for an asynchronous service to handle long-run service requests without the support of a message queue and more important a persistence layer. I am not sure if they are correct. Any comments? It seems to me that you're looking for WS-Reliable Messaging like features. Have you looked at Sandesha2? That will give behavior you're looking for. I think the core Axis2 platform should continue to have a simple, lightweight async model based purely on threads to cover simple patterns. If you really need reliable, long running async behavior then its time to use WS-RM. Sanjiva.
Axis2 version 1.0
Hey all, Anybody have a general idea when version 1.0 will be released? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
Re: [Axis2] WSDL2Java client code creation
The targetNamespace problem is caused by the fact that you specified:ns2:targetNamespace=http://org.apache.axis2/xsd Rather than:targetNamespace=http://org.apache.axis2/xsdSchema attributes must not be namespace qualified.(I also strongly recommend that you get in the habit of using more descriptive namespaces -- use a name that indicates the nature of the service, and preferably unique to your organization.)Likewise you need to remove the namespace prefix from the following attributes in the schema definition: ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualifiedAs well as all the attributes within the rest of the schema, e.g., this: xs:element ns0:name=echoRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType/xs:elementShould be: xs:element name=echoRequest xs:complexType xs:sequence xs:element name=param0 type=xs:anyType/ /xs:sequence /xs:complexType /xs:elementBy the way, You find things work much better when you use defined types rather than xs:anyType. Based on a quick glance through the rest of the WSDL, I didn't see any glaring errors, except that you must remove the namespace attributes from the soap:body definitions. e.g.; this:soap:body use=literal namespace=http://www.org.apache.axis2/should be this: soap:body use=literal/(You use the namespace attribute only when using rpc style.)AnneOn 3/14/06, robert lazarski [EMAIL PROTECTED] wrote: The attached file is neither vaild xml or valid wsdl. Try using an xml editor - I use kxmleditor on linux - and get the file to at least load. >From there - try getting the wsdl to validate via an wsdl validator (can't recommend one at the moment, sorry). HTH, Robert http://www.braziloutsource.com/ On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:Hi all,we are playing around with the samples from the tutorial... we have extended the MyService to take a comlpexType (a string, an int and a double) and would liketo create the client from the WSDL.Axis has created the attached WSDL from our service, but WSDL2Java fails whencalled like this: ---axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -porg.apache.axis2-with this error:--Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDLTypes Schema does not define a targetNamespace in file:../samples/at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118)at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21)Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL:The WSDL Types Schema does not define a targetNamespace in file:../samples/at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage (WSDLValidatorExtension.java:70)at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)... 2 moreIf we try to enter anything else in the targetNamespace attribute in the WSDL, it gives us a NullPointerException instead.Any clues?Thanks a lot in advance!-- Sebi
[axis2 v0.95] code generation exception
Hi! I have to generate code using org.apache.axis2.wsdl.WSDL2Code having in input a wsdl where some web service return a votable. The votable schema is specified at the following address: http://www.ivoa.net/xml/VOTable/v1.1 I've successfully executed wsdl2code with axis2 up to version 0.93. Now I'm using axis2 v0.94 and I have also checked out and build v0.95. With both these versions I get the following exception: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace 'http://www.ivoa.net/xml/VOTable/v1.1' already contains type 'token at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180) at org.apache.tools.ant.taskdefs.Java.run(Java.java:710) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Thanks for any help! Diego
Re: [Axis2] WSDL2Java client code creation
Hi Anne! Thanks a lot for your comments. We just used the WSDL of our class that was generated by AXIS itself. After uploading the class we downloaded the WSDL and without modifying it in any way we wanted to use it as input for the WSDL2Java client code creation tool. We weren't aware that AXIS creates faulty WSDLs. We'll check out the corrections you suggested and get back tomorrow. Thanks again! -- Sebi Anne Thomas Manes wrote: The targetNamespace problem is caused by the fact that you specified: ns2:targetNamespace=http://org.apache.axis2/xsd; Rather than: targetNamespace=http://org.apache.axis2/xsd; Schema attributes must not be namespace qualified.(I also strongly recommend that you get in the habit of using more descriptive namespaces -- use a name that indicates the nature of the service, and preferably unique to your organization.) Likewise you need to remove the namespace prefix from the following attributes in the schema definition: ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualified As well as all the attributes within the rest of the schema, e.g., this: xs:element ns0:name=echoRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema; ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element Should be: xs:element name=echoRequest xs:complexType xs:sequence xs:element name=param0 type=xs:anyType/ /xs:sequence /xs:complexType /xs:element By the way, You find things work much better when you use defined types rather than xs:anyType. Based on a quick glance through the rest of the WSDL, I didn't see any glaring errors, except that you must remove the namespace attributes from the soap:body definitions. e.g.; this: soap:body use=literal namespace=http://www.org.apache.axis2/ should be this: soap:body use=literal/ (You use the namespace attribute only when using rpc style.) Anne On 3/14/06, robert lazarski [EMAIL PROTECTED] wrote: The attached file is neither vaild xml or valid wsdl. Try using an xml editor - I use kxmleditor on linux - and get the file to at least load. From there - try getting the wsdl to validate via an wsdl validator (can't recommend one at the moment, sorry). HTH, Robert http://www.braziloutsource.com/ On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi all, we are playing around with the samples from the tutorial... we have extended the MyService to take a comlpexType (a string, an int and a double) and would like to create the client from the WSDL. Axis has created the attached WSDL from our service, but WSDL2Java fails when called like this: --- axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p org.apache.axis2 - with this error: -- Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:118) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage (WSDLValidatorExtension.java:70) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:80) ... 2 more If we try to enter anything else in the targetNamespace attribute in the WSDL, it gives us a NullPointerException instead. Any clues? Thanks a lot in advance! -- Sebi
WSDL2Java and Java2WSDL
I have been trying something using 1.1 final and 1.3 WSDL2Java and Java2WSDL produces different types of WSDLs with the Java2WSDL and WSDL2Java produces different java packaging with the different versions. Can anyone tell me why the change and what changed between 1.1 and 1.3? I believe there is no way to generate the same WSDL as the 1.1 final produced with the 1.3 version. Am I wrong with this statement?
Re: [axis2 v0.95] code generation exception
Hi Diego, Post your wsdl and command line options and perhaps we can help. Robert http://www.braziloutsource.com/On 3/14/06, Diego [EMAIL PROTECTED] wrote:Hi!I have to generate code using org.apache.axis2.wsdl.WSDL2Code having ininput a wsdl where some web service return a votable.The votableschema is specified at the following address:http://www.ivoa.net/xml/VOTable/v1.1 I've successfully executed wsdl2code with axis2 up to version 0.93.NowI'm using axis2 v0.94 and I have also checked out and build v0.95.Withboth these versions I get the following exception:org.apache.axis2.wsdl.codegen.CodeGenerationException :java.lang.RuntimeException: java.lang.RuntimeException: Schema fornamespace 'http://www.ivoa.net/xml/VOTable/v1.1' already contains type'token at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180) at org.apache.tools.ant.taskdefs.Java.run(Java.java:710) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute (Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) atorg.apache.tools.ant.helper.SingleCheckExecutor.executeTargets (SingleCheckExecutor.java:37) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382) atorg.apache.tools.ant.taskdefs.CallTarget.execute (CallTarget.java:107) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) atorg.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java :668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)Thanks for any help! Diego
Re: Axis fault question
Hello Dies, Thank you very much for your help. You are correct, I misinterpreted some of my debugging output; I am hitting the server. I took your suggestion and used tcpmon and see that the SOAP request is properly formed but the response is the InvocationTargetException mentioned previously. I cranked the server logging up to 'DEBUG' but see nothing that would indicate a problem (it doesn't even tell me that a SOAP Fault was generated). So, the server receives the request but faults before it's ever sent to my service. Would you have any other suggestions as to things to try or approaches to further debug this problem? (I've pasted the server log and tcpmon request/response below). I'm stumped... Thanks again, Charlton Server log: DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - default constructor DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - default constructor DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - preRegister [EMAIL PROTECTED] Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - preRegister [EMAIL PROTECTED] Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - Getting new thread data DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - Getting new thread data DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Allocating non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Allocating non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Returning non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Returning non-STM instance Request (from TCPMonitor): POST /axis/services/is HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.1 Host: 127.0.0.1 Cache-Control: no-cache Pragma: no-cache SOAPAction: Content-Length: 518 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:retrieve soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=urn:is in0 xsi:type=xsd:stringc=us,o=company,ou=div,cn=principal1/in0 in1 xsi:type=xsd:stringurn:info:resource1/in1 /ns1:retrieve /soapenv:Body /soapenv:Envelope Response (from TCPMonitor): HTTP/1.1 500 Internal Server Error Content-Type: text/xml;charset=utf-8 Date: Tue, 14 Mar 2006 22:06:06 GMT Server: Apache-Coyote/1.1 Connection: close ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body soapenv:Fault faultcodesoapenv:Server.userException/faultcode faultstringjava.lang.reflect.InvocationTargetException/faultstring detail/ /soapenv:Fault /soapenv:Body /soapenv:Envelope From: Dies Koper [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Re: Axis fault question Date: Sat, 11 Mar 2006 13:55:07 +0900 Hello Charlton, Are you sure you are not hitting the server? Judging from the stacktrace the stub send the request and got a response. The response contained a fault: an InvocationTargetException occurred at the server. The server is the _Axis server_, it does not need to be your _service_. In fact, InvocationTargetException probably means the Axis server could not invoke the method on your service. You can use tcpmon to confirm your request was send, SOAP message was correct, and a response (the fault) came from the server, and not happened in your stub. To find out more details about why the InvocationTargetException occurred, you'd have to check the server-side logs. Regards, Dies Charlton Jackson wrote: I'm
WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET server)
Hi All,I am trying to access a .NET service with a Java/Axis client (using WSS4J) and am getting a security-related error. Here are the details:* Web Service: on .NET uses WS-Security UsernameToken (with Password Digest) * Request Messagesoapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd= http://www.w3.org/2001/XMLSchema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance soapenv:Header wsse:Security xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd wsse:UsernameToken xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd wsse:Username xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsdTestDev/wsse:Username wsse:Password Type= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsdR7bh5dDlYgjCurx6Dwq9ki39lQg=/wsse:Password wsse:Nonce xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/tA24bdIc0uwX7euUqvMVQ==/wsse:Nonce wsu:Created xmlns:wsu= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd2006-03-14T22:34:50.971Z/wsu:Created /wsse:UsernameToken /wsse:Security /soapenv:Header soapenv:Body ValidateEmail xmlns=urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2 Email xmlns=urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2 [EMAIL PROTECTED]/Email /ValidateEmail /soapenv:Body /soapenv:Envelope* Response Messagesoapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance soapenv:Body soapenv:Fault faultcodesoapenv:FailedAuthentication/faultcode faultstringThe security token could not be authenticated or authorized/faultstring faultactor http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx/faultactor detail string/ /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope Any inputs towards appropriately troubleshooting and resolving this issue would be appreciated.Regards.
Re: [Axis2] A question about asynchronous services and message queue
I agree that Axis2 should be simple and lightweight, and just for soap processing. WS-RM does cover some of my requirements. However, I have a question in my mind about asynchronous service and client for a long time. As I know, the current implementation of async dual client in axis2 is to listen to a specific port, 6060 by default. That makes problem when running several async dual clients on the same machine at the same time. What I expect is to remove the difference between client and server so that all services can be accessed through the same port for a certain transportation, the http or tcp or JMS transportation components are always there listening, and the correlated service will be triggered based on ws-addressing. Cheers,DonOn 3/14/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Tue, 2006-03-14 at 10:59 -0600, Dong Liu wrote: Maybe I should clarify my point here:1. A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature.2. It is hard for an asynchronous service to handle long-run service requests without the support of a message queue and more important a persistence layer. I am not sure if they are correct. Any comments?It seems to me that you're looking for WS-Reliable Messaging likefeatures. Have you looked at Sandesha2? That will give behavior you're looking for.I think the core Axis2 platform should continue to have a simple,lightweight async model based purely on threads to cover simplepatterns. If you really need reliable, long running async behavior then its time to use WS-RM.Sanjiva.
Re: [Axis2] How to specifiy operation name
You may need to use the tcp monitor or other tools to see the HTTP message. Cheers,DongOn 3/14/06, Michael Robinson
[EMAIL PROTECTED] wrote:
Thanks!!
One question though:
options.setSoapAction("actionName");
options.setAction("actionName");
both fixed the problem. Is there a
difference?
Thanks again for both replies.
Michael
Re: [Axis2] WSDL2Java client code creation
If Axis2 generated that WSDL, then you should log a bug in Jira -- make sure you're using the latest build, though. I recall a bug like this in 0.94, which I'm pretty sure has been fixed now.Anne On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi Anne!Thanks a lot for your comments. We just used the WSDL of our class that wasgenerated by AXIS itself. After uploading the class we downloaded the WSDL andwithout modifying it in any way we wanted to use it as input for the WSDL2Java client code creation tool. We weren't aware that AXIS creates faulty WSDLs.We'll check out the corrections you suggested and get back tomorrow.Thanks again!-- SebiAnne Thomas Manes wrote: The targetNamespace problem is caused by the fact that you specified: ns2:targetNamespace=http://org.apache.axis2/xsd Rather than: targetNamespace=http://org.apache.axis2/xsd Schema attributes must not be namespace qualified.(I also strongly recommend that you get in the habit of using more descriptive namespaces -- use a name that indicates the nature of the service, and preferably unique to your organization.) Likewise you need to remove the namespace prefix from the following attributes in the schema definition: ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualified As well as all the attributes within the rest of the schema, e.g., this: xs:element ns0:name=echoRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element Should be: xs:element name=echoRequest xs:complexType xs:sequence xs:element name=param0 type=xs:anyType/ /xs:sequence /xs:complexType /xs:element By the way, You find things work much better when you use defined types rather than xs:anyType. Based on a quick glance through the rest of the WSDL, I didn't see any glaring errors, except that you must remove the namespace attributes from the soap:body definitions. e.g.; this: soap:body use=literal namespace= http://www.org.apache.axis2/ should be this: soap:body use=literal/ (You use the namespace attribute only when using rpc style.) Anne On 3/14/06, robert lazarski [EMAIL PROTECTED] wrote: The attached file is neither vaild xml or valid wsdl. Try using an xml editor - I use kxmleditor on linux - and get the file to at least load. From there - try getting the wsdl to validate via an wsdl validator (can't recommend one at the moment, sorry). HTH, Robert http://www.braziloutsource.com/ On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi all, we are playing around with the samples from the tutorial... we have extended the MyService to take a comlpexType (a string, an int and a double) and would like to create the client from the WSDL. Axis has created the attached WSDL from our service, but WSDL2Java fails when called like this: --- axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p org.apache.axis2 - with this error: -- Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException : Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:118) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage (WSDLValidatorExtension.java:70) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:80) ... 2 more If we try to enter anything else in the targetNamespace attribute in the WSDL, it gives us a NullPointerException instead. Any clues? Thanks a lot in advance! -- Sebi
Re: WSDL2Java and Java2WSDL
Lots of things have been improved since Axis 1.1. The changes you see could either be because the generated files were improved to follow specifications (JAX-RPC 1.1 in particular), bugs were fixed, but also new bugs that were introduced. Your questions are not easy to answer, as the changes were made over time by many people. Try having a look at release-notes.html and the svn/cvs logs if you are really interested. Regards, Dies Siddhartha Subramanian wrote: I have been trying something using 1.1 final and 1.3 WSDL2Java and Java2WSDL produces different types of WSDLs with the Java2WSDL and WSDL2Java produces different java packaging with the different versions. Can anyone tell me why the change and what changed between 1.1 and 1.3? I believe there is no way to generate the same WSDL as the 1.1 final produced with the 1.3 version. Am I wrong with this statement?
Re: Axis fault question
Hello Charlton, Can you confirm whether your method was actually entered? Just to make sure the exception is not happening within your own code.. I am not familiar with Axis's logging functions, so I'd either use Eclipse in debugging mode and make it stop when an InvocationTargetException is generated, or try harder to figure out what could cause such exception. I believe an InvocationTargetException is generally thrown by the Class.invoke method. This method would be used to either instantiate your impl instance, a Javabean or user exception class, or to call a method on it. You could put something in the default constructor of your impl to check whether instantiation went successfully. Same for your retrieve(String, String) method. If your WSDL uses Doc/lit then we could check the elements in your request are correct (could it be trying to call a non-existing method), maybe compare them with what's in your WSDD. Regards, Dies Charlton Jackson wrote: Hello Dies, Thank you very much for your help. You are correct, I misinterpreted some of my debugging output; I am hitting the server. I took your suggestion and used tcpmon and see that the SOAP request is properly formed but the response is the InvocationTargetException mentioned previously. I cranked the server logging up to 'DEBUG' but see nothing that would indicate a problem (it doesn't even tell me that a SOAP Fault was generated). So, the server receives the request but faults before it's ever sent to my service. Would you have any other suggestions as to things to try or approaches to further debug this problem? (I've pasted the server log and tcpmon request/response below). I'm stumped... Thanks again, Charlton Server log: DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - default constructor DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - default constructor DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - preRegister [EMAIL PROTECTED] Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - preRegister [EMAIL PROTECTED] Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1 DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - Getting new thread data DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - Getting new thread data DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Allocating non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Allocating non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Returning non-STM instance DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - Returning non-STM instance Request (from TCPMonitor): POST /axis/services/is HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.1 Host: 127.0.0.1 Cache-Control: no-cache Pragma: no-cache SOAPAction: Content-Length: 518 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:retrieve soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=urn:is in0 xsi:type=xsd:stringc=us,o=company,ou=div,cn=principal1/in0 in1 xsi:type=xsd:stringurn:info:resource1/in1 /ns1:retrieve /soapenv:Body /soapenv:Envelope Response (from TCPMonitor): HTTP/1.1 500 Internal Server Error Content-Type: text/xml;charset=utf-8 Date: Tue, 14 Mar 2006 22:06:06 GMT Server: Apache-Coyote/1.1 Connection: close ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body soapenv:Fault
Re: java.lang.IllegalArgumentException
Hello William, I do not know the conditions for them to be generated, but generated Javabean classes often get helper methods such as: - getTypeDesc - getSerializer - getDeserializer WSDL2Java has an option to have these methods not inserted in the Javabean classes, but in separate files. Either way, I think they are required in certain circumstances to serialize/deserialize SOAP messages correctly. If you did not modify (overwrite them with your original, etc.) or forget to include them, then I suppose it's okay. When happens if you put the JSP in a different Tomcat instance (different process) from the web service running in Axis? Regards, Dies William Ward wrote: Hello Dies, I didn't modify any of the classes generated by WSDL2Java, but I don't see any helper methods in the generated client stubs, should I be seeing these ?? Regards, William -Original Message- From: Dies Koper [mailto:[EMAIL PROTECTED] Sent: 14 March 2006 14:02 To: axis-user@ws.apache.org Subject: Re: java.lang.IllegalArgumentException Hello William, We'd need to see the WSDL to see if the SOAP message is right. Unfortunately the SOAP message is rather long and complicated. You might not get any replies. As you seem to use complex structures (array of complex types?) I imagine the Axis engine relies on the Helper classes (or helper code in the generated Javabeans) on the client side. Just checking, but you did not happen to have removed these classes/methods? Regards, Dies William Ward wrote: Hello Dies, thank you for the reply, I used tcpmon to capture the SOAP message, I believe the problem is at the receiving end as I get the response back from the Web Service no problem, it looks like it has a problem de-serializing the response. The odd thing is if I call the same Web Serice using just a test Java application, I don't see any exception on the Axis side It seems to be just when I use JSP, Tomcat and Axis, I have tried just creating a simple JSP page that has the same code as the test Java Application, but I always get the Axis exception when using JSP Tomcat, even though it is the same code libraries for both applications below is the SOAP request / response that I see using tcpmon : Regards, William
Re: WSDL2Java and Java2WSDL
One way to ensure that your WSDLs are the same is to generate your code from the WSDL rather than vice versa. But most likely, your Axis 1.1 WSDL will produce interoperability errors. If they contain arrays, they probably have errors. Axis 1.2 and later releases added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically improved support for document/literal. Lots and lots of changes were made in dealing with arrays.Anne On 3/14/06, Siddhartha Subramanian [EMAIL PROTECTED] wrote: I have been trying something using 1.1 final and 1.3 WSDL2Java andJava2WSDL produces different types of WSDLs with the Java2WSDL andWSDL2Java produces different java packaging with the different versions.Can anyone tell me why the change and what changed between 1.1 and 1.3?I believe there is no way to generate the same WSDL as the 1.1 finalproduced with the 1.3 version. Am I wrong with this statement?
Re: [axis2 v0.95] code generation exception
Hi Robert,
thanks a lot for your help!
That's the ant task that I've executed:
target name=wsdl2java-astrodas-peer
java classname=org.apache.axis2.wsdl.WSDL2Code
classpathref=axis2.classpath
arg value=-uri /
arg value=${astrodas-peer.wsdl} /
arg value=-o /
arg value=${src.dir} /
arg value=-p /
arg value=org.astrodas.ws.peer /
/java
/target
and that's the wsdl:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=http://astrodas.org/ws/peer;
xmlns:tns=http://astrodas.org/ws/peer;
xmlns:tns1=http://astrodas.org/ws/model;
xmlns:tns2=http://www.ivoa.net/xml/VOTable/v1.1;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
wsdl:types
xsd:schema elementFormDefault=qualified
targetNamespace=http://astrodas.org/ws/model;
xsd:import namespace=http://www.w3.org/2001/XMLSchema; /
xsd:import namespace=http://www.ivoa.net/xml/VOTable/v1.1;
schemaLocation=http://www.ivoa.net/xml/VOTable/v1.1; /
!-- insertMappingAnnotations --
xsd:complexType name=external-object
xsd:sequence
xsd:element minOccurs=0 maxOccurs=1 name=id
type=xsd:integer /
xsd:element minOccurs=1 maxOccurs=1 name=external-id
type=xsd:integer /
xsd:element minOccurs=1 maxOccurs=1 name=external-db
type=xsd:string /
xsd:element minOccurs=1 maxOccurs=1 name=match
type=xsd:boolean /
/xsd:sequence
/xsd:complexType
xsd:complexType name=annotation
xsd:sequence
xsd:element minOccurs=0 maxOccurs=1 name=id
type=xsd:integer /
xsd:element minOccurs=0 maxOccurs=1 name=type
type=xsd:string /
xsd:element minOccurs=1 maxOccurs=1 name=author
type=xsd:string /
xsd:element minOccurs=0 maxOccurs=1 name=timestamp
type=xsd:string /
/xsd:sequence
/xsd:complexType
xsd:complexType name=mapping-annotation
xsd:complexContent mixed=false
xsd:extension base=tns1:annotation
xsd:sequence
xsd:element minOccurs=1 maxOccurs=unbounded
name=external-object type=tns1:external-object /
xsd:element minOccurs=0 maxOccurs=1 name=text
type=xsd:string /
xsd:element minOccurs=0 maxOccurs=1
name=reliability type=xsd:float /
xsd:element minOccurs=0 maxOccurs=1 name=ra-mean
type=xsd:double /
xsd:element minOccurs=0 maxOccurs=1 name=dec-mean
type=xsd:double /
/xsd:sequence
/xsd:extension
/xsd:complexContent
/xsd:complexType
xsd:element name=insertMappingAnnotations
xsd:complexType
xsd:sequence
xsd:element minOccurs=1 maxOccurs=unbounded
name=mapping-annotation type=tns1:mapping-annotation /
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=insertMappingAnnotationsResponse
xsd:complexType
xsd:sequence
xsd:element minOccurs=1 maxOccurs=1 name=result
type=xsd:int /
/xsd:sequence
/xsd:complexType
/xsd:element
!-- executeGlobalMappingTableQuery --
xsd:element name=executeGlobalMappingTableQuery
xsd:complexType
xsd:sequence
xsd:element minOccurs=1 maxOccurs=1 name=query
type=xsd:string /
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=executeGlobalMappingTableQueryResponse
xsd:complexType
xsd:sequence
xsd:element minOccurs=1 maxOccurs=1 ref=tns2:VOTABLE /
/xsd:sequence
/xsd:complexType
/xsd:element
/xsd:schema
/wsdl:types
!-- insertMappingAnnotations --
wsdl:message name=insertMappingAnnotationsMessage
wsdl:part name=body element=tns1:insertMappingAnnotations /
/wsdl:message
wsdl:message name=insertMappingAnnotationsResponseMessage
wsdl:part name=body element=tns1:insertMappingAnnotationsResponse /
/wsdl:message
!-- executeGlobalMappingTableQuery --
wsdl:message name=executeGlobalMappingTableQueryMessage
wsdl:part name=body element=tns1:executeGlobalMappingTableQuery /
/wsdl:message
wsdl:message name=executeGlobalMappingTableQueryResponseMessage
wsdl:part name=body
element=tns1:executeGlobalMappingTableQueryResponse /
/wsdl:message
wsdl:portType name=AstrodasPeer
wsdl:operation name=insertMappingAnnotations
wsdl:documentationStores an array of annotations in the annotation
backend database/wsdl:documentation
wsdl:input message=tns:insertMappingAnnotationsMessage /
wsdl:output message=tns:insertMappingAnnotationsResponseMessage /
/wsdl:operation
wsdl:operation name=executeGlobalMappingTableQuery
wsdl:documentationExecutes a query on the global mapping table of
the p2p network of annotation/wsdl:documentation
wsdl:input message=tns:executeGlobalMappingTableQueryMessage /
wsdl:output
message=tns:executeGlobalMappingTableQueryResponseMessage /
/wsdl:operation
/wsdl:portType
wsdl:binding name=AstrodasPeerBinding
Re: WSDL2Java and SimpleType doing *strange* things.
Hello Scott, Why not not use the ?wsdl generated wsdl? (i.e. specify the original one in the WSDD instead) Regards, Dies Scott McCoy wrote: When given the declaration... complexType name=keyword simpleContent extension base=xsd:string attribute name=advertisementId type=xsd:int/ attribute name=autoBid type=xsd:boolean/ attribute name=bid type=xsd:decimal/ attribute name=matchType type=impl:match-type/ /extension /simpleContent /complexType WSDL2Java generates a Bean class that has a get_value (named after the internal _value a less complex type declaration has?) and set_value method for accessing the value, but when deployed Axis outputs a wsdl that has an *attribute* named _value for the keyword complexType. When given complexType name=keyword simpleContent/ attribute name=value type=xsd:string/ attribute name=advertisementId type=xsd:int/ attribute name=autoBid type=xsd:boolean/ attribute name=bid type=xsd:decimal/ attribute name=match type=impl:match-type/ /complexType WSDL2Java generates exactly what I expect, but then when deployed axis returns a wsdl that contains: complexType name=keyword simpleContent extension base=xsd:string attribute name=advertisementId type=xsd:int/ attribute name=autoBid type=xsd:boolean/ attribute name=bid type=xsd:decimal/ attribute name=matchType type=impl:match-type/ /extension /simpleContent /complexType How do I get WSDL2Java to do what I want? Heh. I'd prefer to my markup to look like: keyword id=.. advertisement-id=.. auto-bid=.. bid=.. match=..The Keyword/keyword But having an attribute named value containing the keyword is a close runner up in perferred behaviors. Thanks, Scott S. McCoy
Re: failure when trying to build axis2
I am also getting the same error. Any clues?Thanks,SricharanLoreno Oliveira [EMAIL PROTECTED] wrote: Hi,when I try to build the axis source I got the following problem:+| Executing multiproject:install-callback Apache Axis 2.0 - WSDL| Memory: 8M/11M+ Attempting to download XmlSchema-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is not knownWARNING: Failed to download XmlSchema-SNAPSHOT.jar.Attempting to download ws-policy-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is no t known WARNING: Failed to download ws-policy-SNAPSHOT.jar.BUILD FAILEDFile.. C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jellyElement... maven:reactor Line.. 217Column 9The build cannot continue because of the following unsatisfied dependencies:XmlSchema-SNAPSHOT.jarws-policy-SNAPSHOT.jarTotal time: 1 minutes 34 secondsFinished at: Mon Mar 13 15:08:23 BRT 2006 C:\axis2-srcDoes anybody knows why these two jars are not being downloaded??Thanks in advance..Loreno Yahoo! Mail Use Photomail to share photos without annoying attachments.
How to use long for parameter type?
Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
Java2WSDL does not generate the correct method signature in the
*SoapBindingImpl.java file. Here is the scenario.
I have the following method declaration in my Family.java file, which
defines one interface.
public interface Family
{
public int register(String email,
String password,
long birthDate,
String affiliateName)
throws RemoteException;
...
}
I execute:
$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
-lhttp://localhost:8080/axis/services/family-accounts; \
-n urn:family-accounts \
-pfamily-accounts urn:disney.dis.family \
disney.dis.family.Family
to produce the family.wsdl file, which I've attached to this email.
I execute:
$
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
-p disney.dis.family family.wsdl
to produce the auto-generated files. The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:
public int register(java.lang.String in0,
java.lang.String in1,
java.lang.String in2)
throws java.rmi.RemoteException
{
return -3;
}
It should be like this:
public int register(java.lang.String in0,
java.lang.String in1,
long in2,
java.lang.String in3)
throws java.rmi.RemoteException
{
return -3;
}
Can anyone tell me what's wrong? How can I specify long
type parameters?
Many thanks,
Vartan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
family.wsdl
Description: 105362022-family.wsdl
Re: How to use long for parameter type?
Is there a reason why you have to use rpc/encoded?Try generating style=wrapped and see if that fixes the problem.AnneOn 3/14/06, Rhimbo
[EMAIL PROTECTED] wrote:Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4Java2WSDL does not generate the correct method signature in the*SoapBindingImpl.java file.Here is the scenario.I have the following method declaration in my
Family.java file, whichdefines one interface.public interface Family{public int register(String email,String password,long birthDate,String affiliateName)
throws RemoteException;...}I execute:$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \-lhttp://localhost:8080/axis/services/family-accounts
\-n urn:family-accounts \-pfamily-accounts urn:disney.dis.family \disney.dis.family.Familyto produce the family.wsdl file, which I've attached to this email.I execute:
$$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \-p disney.dis.family family.wsdlto produce the auto-generated files.The file that contains theSOAP binding implementation has the following signature
corresponding to the interface method declaration above:public int register(java.lang.String in0,java.lang.String in1, java.lang.String in2) throws
java.rmi.RemoteException{return -3;}It should be like this:public int register(java.lang.String in0,java.lang.String in1,long in2,
java.lang.String in3) throws java.rmi.RemoteException{return -3;}Can anyone tell me what's wrong?How can I specify long
type parameters?Many thanks,Vartan__Do You Yahoo!?Tired of spam?Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
RE: How to use long for parameter type?
Title: RE: How to use long for parameter type?
Hi Vartan,
I have had no problems with long parameters using RPC or Wrapped style.
I did a quick test using my wizard and the Axis 1.3 generated WSDL is ok.
See attached FamilyServer.wsdl
==
package com.acme.service.soap ;
public interface FamilyServerProvider
{
public int register ( String in0, String in1, long in2, String in3 ) ;
}
==
package com.acme.service.soap ;
public class FamilyServerProviderStub implements FamilyServerProvider
{
/*
Service implementation
*/
public final int register ( String in0, String in1, long in2, String in3 )
{
return 0 ;
}
}
==
Create WSDL from source started
java
-classpath
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile
-Djava.ext.dirs=C:\Studio_Beta\lib\ext;
org.apache.axis.wsdl.Java2WSDL
-l
http://www.acme.com/cgi-bin/jsmdirect?myservice
-o
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerService.wsdl
-b
FamilyServerServiceBinding
-S
FamilyServerServiceService
-s
FamilyServerServicePort
-P
FamilyServerServicePortType
-y
RPC
-u
ENCODED
-T
1.2
-A
OPERATION
-i
com.acme.service.soap.FamilyServerProviderStub
com.acme.service.soap.FamilyServerProvider
Create WSDL from source completed
==
-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2006 1:56 PM
To: Axis users
Subject: How to use long for parameter type?
Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
Java2WSDL does not generate the correct method signature in the
*SoapBindingImpl.java file. Here is the scenario.
I have the following method declaration in my Family.java file, which
defines one interface.
public interface Family
{
public int register(String email,
String password,
long birthDate,
String affiliateName)
throws RemoteException;
...
}
I execute:
$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
-lhttp://localhost:8080/axis/services/family-accounts \
-n urn:family-accounts \
-pfamily-accounts urn:disney.dis.family \
disney.dis.family.Family
to produce the family.wsdl file, which I've attached to this email.
I execute:
$
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
-p disney.dis.family family.wsdl
to produce the auto-generated files. The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:
public int register(java.lang.String in0,
java.lang.String in1,
java.lang.String in2)
throws java.rmi.RemoteException
{
return -3;
}
It should be like this:
public int register(java.lang.String in0,
java.lang.String in1,
long in2,
java.lang.String in3)
throws java.rmi.RemoteException
{
return -3;
}
Can anyone tell me what's wrong? How can I specify long
type parameters?
Many thanks,
Vartan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
FamilyServerService.wsdl
Description: Binary data
Wizard.gif
Description: GIF image
RE: WSDL2Java and Java2WSDL
Well I understand the changes and the need for them, but once my WSDL has been published and the clients using it expect the client side to be in a certain way (packaging wise, namespaces etc.) but with 1.3 I cannot say regenerate the WSDL and publish it because what you are suggesting of generating the code from the new WSDL does not produce the same client side stubs expected. So we have to manipulate the WSDL by hand to conform to the namespacing and there by producing the old packaging structure. From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 6:32 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java and Java2WSDL One way to ensure that your WSDLs are the same is to generate your code from the WSDL rather than vice versa. But most likely, your Axis 1.1 WSDL will produce interoperability errors. If they contain arrays, they probably have errors. Axis 1.2 and later releases added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically improved support for document/literal. Lots and lots of changes were made in dealing with arrays. Anne On 3/14/06, Siddhartha Subramanian [EMAIL PROTECTED] wrote: I have been trying something using 1.1 final and 1.3 WSDL2Java and Java2WSDL produces different types of WSDLs with the Java2WSDL and WSDL2Java produces different java packaging with the different versions. Can anyone tell me why the change and what changed between 1.1 and 1.3? I believe there is no way to generate the same WSDL as the 1.1 final produced with the 1.3 version. Am I wrong with this statement?
Re: WSDL2Java and Java2WSDL
If it is just the namespace - Java package mapping you are concerned about, try the following options: -N, --NStoPkg argument=value mapping of namespace to package -p, --PkgtoNS argument=value package=namespace, name value pairs Siddhartha Subramanian wrote: Well I understand the changes and the need for them, but once my WSDL has been published and the clients using it expect the client side to be in a certain way (packaging wise, namespaces etc.) but with 1.3 I cannot say regenerate the WSDL and publish it because what you are suggesting of generating the code from the new WSDL does not produce the same client side stubs expected. So we have to manipulate the WSDL by hand to conform to the namespacing and there by producing the old packaging structure. From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 6:32 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java and Java2WSDL One way to ensure that your WSDLs are the same is to generate your code from the WSDL rather than vice versa. But most likely, your Axis 1.1 WSDL will produce interoperability errors. If they contain arrays, they probably have errors. Axis 1.2 and later releases added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically improved support for document/literal. Lots and lots of changes were made in dealing with arrays. Anne On 3/14/06, Siddhartha Subramanian [EMAIL PROTECTED] wrote: I have been trying something using 1.1 final and 1.3 WSDL2Java and Java2WSDL produces different types of WSDLs with the Java2WSDL and WSDL2Java produces different java packaging with the different versions. Can anyone tell me why the change and what changed between 1.1 and 1.3? I believe there is no way to generate the same WSDL as the 1.1 final produced with the 1.3 version. Am I wrong with this statement? -- Dies KOPER [EMAIL PROTECTED] (changed on 1 July 2005) Fujitsu Ltd - MWPF1 (changed from MWPF3 on 21 Nov 2005) 2-15-16, Shin-Yokohama, Kouhoku-ku, Yokohama, 222-0033, Japan Tel. +81(45)-475-5605 (internal 7181-4217)
Re: [Axis2] WSDL2Java client code creation
Hi all, This prefix in targetNamepace attribute issue was reported to us earlier but we could not recreate it. My guess is that it arises in a particular JDK/OS combination and we need to recreate it so that we can fix it. Details of your environment would be very helpful to us in doing so. BTW thanks Anne for pointing out the issues. We'll fix the WSDL generation bugs soon (if they are still there) and logging a Jira issue would be helpful in keeping track of it. Ajith On 3/15/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: If Axis2 generated that WSDL, then you should log a bug in Jira -- make sure you're using the latest build, though. I recall a bug like this in 0.94, which I'm pretty sure has been fixed now. Anne On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi Anne! Thanks a lot for your comments. We just used the WSDL of our class that was generated by AXIS itself. After uploading the class we downloaded the WSDL and without modifying it in any way we wanted to use it as input for the WSDL2Java client code creation tool. We weren't aware that AXIS creates faulty WSDLs. We'll check out the corrections you suggested and get back tomorrow. Thanks again! -- Sebi Anne Thomas Manes wrote: The targetNamespace problem is caused by the fact that you specified: ns2:targetNamespace=http://org.apache.axis2/xsd; Rather than: targetNamespace=http://org.apache.axis2/xsd; Schema attributes must not be namespace qualified.(I also strongly recommend that you get in the habit of using more descriptive namespaces -- use a name that indicates the nature of the service, and preferably unique to your organization.) Likewise you need to remove the namespace prefix from the following attributes in the schema definition: ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualified As well as all the attributes within the rest of the schema, e.g., this: xs:element ns0:name=echoRequest xs:complexType xs:sequence xs:element xmlns:ns1=http://www.w3.org/2001/XMLSchema ns0:name=param0 ns1:type=xs:anyType/ /xs:sequence /xs:complexType /xs:element Should be: xs:element name=echoRequest xs:complexType xs:sequence xs:element name=param0 type=xs:anyType/ /xs:sequence /xs:complexType /xs:element By the way, You find things work much better when you use defined types rather than xs:anyType. Based on a quick glance through the rest of the WSDL, I didn't see any glaring errors, except that you must remove the namespace attributes from the soap:body definitions. e.g.; this: soap:body use=literal namespace= http://www.org.apache.axis2/ should be this: soap:body use=literal/ (You use the namespace attribute only when using rpc style.) Anne On 3/14/06, robert lazarski [EMAIL PROTECTED] wrote: The attached file is neither vaild xml or valid wsdl. Try using an xml editor - I use kxmleditor on linux - and get the file to at least load. From there - try getting the wsdl to validate via an wsdl validator (can't recommend one at the moment, sorry). HTH, Robert http://www.braziloutsource.com/ On 3/14/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote: Hi all, we are playing around with the samples from the tutorial... we have extended the MyService to take a comlpexType (a string, an int and a double) and would like to create the client from the WSDL. Axis has created the attached WSDL from our service, but WSDL2Java fails when called like this: --- axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p org.apache.axis2 - with this error: -- Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException : Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:118) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL Types Schema does not define a targetNamespace in file:../samples/ at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage (WSDLValidatorExtension.java:70) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGener ationEngine.java:80) ... 2 more If we try to enter anything else in the targetNamespace attribute in the WSDL, it gives us a NullPointerException instead. Any clues?
Re: How to use long for parameter type?
Vartan,
Could you try explicitly setting the classpath (with your classes in front)?
Also, make sure there are no old compiled generated classes in your
classpath.
Can you reproduce it with only that method in your interface? (without
isRegistered and login)?
Regards,
Dies
Rhimbo wrote:
Alick,
Thanks much. It still fails for me. Very strange.
I deleted all of my files except my original interface definition,
Family.java and my FamilyImpl.java, which is the implementation code.
I'm wondering if I have some incompatible libraries in my
Tomcat/AXIS installation for two reasons:
1. You get it to work; I can't.
2. Trying the -y wrapped or --style wrapped makes Java2WSDL die
a dramatic death.
Is there any way to figure out which version of the Java2WSDL
class file I have (something like a -version option)?
Vartan
--- Alick Buckley [EMAIL PROTECTED] wrote:
Hi Vartan,
I have had no problems with long parameters using RPC or Wrapped style.
I did a quick test using my wizard and the Axis 1.3 generated WSDL is
ok.
See attached FamilyServer.wsdl
==
package com.acme.service.soap ;
public interface FamilyServerProvider
{
public int register ( String in0, String in1, long in2, String in3
) ;
}
==
package com.acme.service.soap ;
public class FamilyServerProviderStub implements FamilyServerProvider
{
/*
Service implementation
*/
public final int register ( String in0, String in1, long in2,
String in3
)
{
return 0 ;
}
}
==
Create WSDL from source started
java
-classpath
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile
-Djava.ext.dirs=C:\Studio_Beta\lib\ext;
org.apache.axis.wsdl.Java2WSDL
-l
http://www.acme.com/cgi-bin/jsmdirect?myservice
-o
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerSer
vice.wsdl
-b
FamilyServerServiceBinding
-S
FamilyServerServiceService
-s
FamilyServerServicePort
-P
FamilyServerServicePortType
-y
RPC
-u
ENCODED
-T
1.2
-A
OPERATION
-i
com.acme.service.soap.FamilyServerProviderStub
com.acme.service.soap.FamilyServerProvider
Create WSDL from source completed
==
-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 15 March 2006 1:56 PM
To: Axis users
Subject: How to use long for parameter type?
Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
Java2WSDL does not generate the correct method signature in the
*SoapBindingImpl.java file. Here is the scenario.
I have the following method declaration in my Family.java file, which
defines one interface.
public interface Family
{
public int register(String email,
String password,
long birthDate,
String affiliateName)
throws RemoteException;
...
}
I execute:
$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
-lhttp://localhost:8080/axis/services/family-accounts; \
-n urn:family-accounts \
-pfamily-accounts urn:disney.dis.family \
disney.dis.family.Family
to produce the family.wsdl file, which I've attached to this email.
I execute:
$
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
-p disney.dis.family family.wsdl
to produce the auto-generated files. The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:
public int register(java.lang.String in0,
java.lang.String in1,
java.lang.String in2)
throws java.rmi.RemoteException
{
return -3;
}
It should be like this:
public int register(java.lang.String in0,
java.lang.String in1,
long in2,
java.lang.String in3)
throws java.rmi.RemoteException
{
return -3;
}
Can anyone tell me what's wrong? How can I specify long
type parameters?
Many thanks,
Vartan
RE: How to use long for parameter type?
Title: RE: How to use long for parameter type?
Vartan,
You could look for all axis.jar files ( and other axis jar files - wsdl4j-15.1.jar, etc.. )
org.apache.axis.wsdl.Java2WSDL class is in axis.jar
The classes are dated 5/10/2005 5:23 PM
Also the generated WSDL has the build date.
!--
WSDL created by Apache Axis version: 1.3
Built on Oct 05, 2005 (05:23:37 EDT)
--
-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2006 3:12 PM
To: axis-user@ws.apache.org
Subject: RE: How to use long for parameter type?
Alick,
Thanks much. It still fails for me. Very strange.
I deleted all of my files except my original interface definition,
Family.java and my FamilyImpl.java, which is the implementation code.
I'm wondering if I have some incompatible libraries in my
Tomcat/AXIS installation for two reasons:
1. You get it to work; I can't.
2. Trying the -y wrapped or --style wrapped makes Java2WSDL die
a dramatic death.
Is there any way to figure out which version of the Java2WSDL
class file I have (something like a -version option)?
Vartan
--- Alick Buckley [EMAIL PROTECTED] wrote:
Hi Vartan,
I have had no problems with long parameters using RPC or Wrapped style.
I did a quick test using my wizard and the Axis 1.3 generated WSDL is
ok.
See attached FamilyServer.wsdl
==
package com.acme.service.soap ;
public interface FamilyServerProvider
{
public int register ( String in0, String in1, long in2, String in3
) ;
}
==
package com.acme.service.soap ;
public class FamilyServerProviderStub implements FamilyServerProvider
{
/*
Service implementation
*/
public final int register ( String in0, String in1, long in2,
String in3
)
{
return 0 ;
}
}
==
Create WSDL from source started
java
-classpath
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile
-Djava.ext.dirs=C:\Studio_Beta\lib\ext;
org.apache.axis.wsdl.Java2WSDL
-l
http://www.acme.com/cgi-bin/jsmdirect?myservice
-o
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerSer
vice.wsdl
-b
FamilyServerServiceBinding
-S
FamilyServerServiceService
-s
FamilyServerServicePort
-P
FamilyServerServicePortType
-y
RPC
-u
ENCODED
-T
1.2
-A
OPERATION
-i
com.acme.service.soap.FamilyServerProviderStub
com.acme.service.soap.FamilyServerProvider
Create WSDL from source completed
==
-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2006 1:56 PM
To: Axis users
Subject: How to use long for parameter type?
Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
Java2WSDL does not generate the correct method signature in the
*SoapBindingImpl.java file. Here is the scenario.
I have the following method declaration in my Family.java file, which
defines one interface.
public interface Family
{
public int register(String email,
String password,
long birthDate,
String affiliateName)
throws RemoteException;
...
}
I execute:
$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
-lhttp://localhost:8080/axis/services/family-accounts \
-n urn:family-accounts \
-pfamily-accounts urn:disney.dis.family \
disney.dis.family.Family
to produce the family.wsdl file, which I've attached to this email.
I execute:
$
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
-p disney.dis.family family.wsdl
to produce the auto-generated files. The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:
public int register(java.lang.String in0,
java.lang.String in1,
java.lang.String in2)
throws java.rmi.RemoteException
{
return -3;
}
It should be like this:
public int register(java.lang.String in0,
java.lang.String in1,
long in2,
java.lang.String in3)
throws java.rmi.RemoteException
{
return -3;
}
Can anyone tell me what's wrong? How can I specify long
type parameters?
Many thanks,
Vartan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: failure when trying to build axis2
Hi, Did you guys update the build files. The mentioned jars are not available anymore and the dependencies have been modified. Please get the latest update from SVN. Ajith On 3/15/06, Sricharan Anand [EMAIL PROTECTED] wrote: I am also getting the same error. Any clues? Thanks, Sricharan Loreno Oliveira [EMAIL PROTECTED] wrote: Hi, when I try to build the axis source I got the following problem: + | Executing multiproject:install-callback Apache Axis 2.0 - WSDL | Memory: 8M/11M + Attempting to download XmlSchema-SNAPSHOT.jar. Response content length is not known Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download XmlSchema-SNAPSHOT.jar. Attempting to download ws-policy-SNAPSHOT.jar. Response content length is not known Response content length is not known Response content length is not known Response content length is no t known WARNING: Failed to download ws-policy-SNAPSHOT.jar. BUILD FAILED File.. C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly Element... maven:reactor Line.. 217 Column 9 The build cannot continue because of the following unsatisfied dependencies: XmlSchema-SNAPSHOT.jar ws-policy-SNAPSHOT.jar Total time: 1 minutes 34 seconds Finished at: Mon Mar 13 15:08:23 BRT 2006 C:\axis2-src Does anybody knows why these two jars are not being downloaded?? Thanks in advance.. Loreno Yahoo! Mail Use Photomail to share photos without annoying attachments. -- Ajith Ranabahu
Re: [Axis2][0.94] How can i shutdown connection after call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forwarded with Axis2 prefix;
Filipp Akinfiev wrote:
Hi all,
in my client class i have function like :
public TFileSendResponse storeFile(int type, String fileName, String
pathToFile) {
TFileSendResponse response = null;
try {
response = FileSend.response(makeCall(FileSend.request(new
TFileSend(,
, type, fileName, pathToFile)), storeFile));
} catch (Exception e) {
e.printStackTrace();
}
return response;
}
it's call function makeCall:
private MessageContext makeCall(MessageContext requestContext, String
action) {
ServiceClient client;
MessageContext result = null;
try {
// creating the Service
AxisService service = new AxisService(IXMLWS2);
// creating the operations
AxisOperation operation = new OutInAxisOperation();
operation.setName(new
javax.xml.namespace.QName(urn:XMLWSIntf-IXMLWS, action));
service.addOperation(operation);
client = new ServiceClient(new
ConfigurationContextFactory().createConfigurationContextFromFileSystem(AXIS2_HOME),
service);
client.getOptions().setTo(targetEPR);
client.getOptions().setSoapAction(urn:XMLWSIntf2-IXMLWS2# +
action);
client.getOptions().setExceptionToBeThrownOnSOAPFault(true);
client.getOptions().setTransportInProtocol(Constants.TRANSPORT_TCP);
client.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.CHUNKED,org.apache.axis2.Constants.VALUE_FALSE);
client.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
OperationClient opClient = client.createClient(new
javax.xml.namespace.QName(urn:XMLWSIntf-IXMLWS, action));
opClient.addMessageContext(requestContext);
opClient.execute(true);
return
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
} catch (AxisFault e) {
e.printStackTrace();
}
return result;
}
after execute, i have open connection to axis server, how can i terminate it ?
thanks in advance!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEF6MSYmklbLuW6wYRAlTGAJ4n3SH1JWxetBKHCEKQrrElU6mSDgCfeWfo
dmgUxQMXh+WqSEftnO+OGJ8=
=jW7k
-END PGP SIGNATURE-
