Re: axis 1.5 build failed in FC 3
Hi Ken, Well, if you're willing to maintain it then that's great :-) As you've probably seen- the only reason we don't want to maintain it is that we don't have the time/skills. As for documentation - hmm ! Not sure there is much for the GNU system (another one of our reasons for not using it !) I thought there was some on the web pages but couldn't find it just now ! Anyone else seen any docs for the GNU make system? thanks for your help Ken :-) Kenneth F. Krutsch [EMAIL PROTECTED] 29/04/2005 15:34 Please respond to Apache AXIS C User List To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: axis 1.5 build failed in FC 3 Hi, Would you folks like assistance building / maintaining a GNU automake system for this? I have a little experience with this. I know the team really likes Ant, but the reality is that this is a C++ project and I think developers will be expecting a GNU automake -style of build. If the Axis team *is* interested in this, then can someone send me any documentation you have on the build requirements? If not, then sorry for the interruption... Ken Adrian Dick wrote: Hi, You don't mention exactly which version of ANT, etc. you are using. We are using a couple of features that are only present in later versions. The versions I use, and are also used for the nightly build are: Java - v1.4.1 ANT - v.1.6.1 ant-contrib - v0.6 cpptasks - v1.0beta3 These versions _should_ be mentioned in the documentation. Alas, taking a quick look now, I find the levels for ant-contrib and cpptasks are not explicitly mentioned. However, running the command ant -projecthelp on build.xml or package.xml provides some basic setup documentation, which does now include the above information. Could you check which versions you are using, and upgrade if required. Thanks, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Samisa Abeysinghe [EMAIL PROTECTED] wrote on 29/04/2005 05:09:04: I cannot exactly understand what is going wrong with ant based pacaking. Adrian, could you please help ass you are the expert in this space. Thanks, Samisa... -Original Message- From: So Hok Chun, Bill [mailto:[EMAIL PROTECTED]] Sent: Friday, April 29, 2005 12:10 AM To: axis-c-user@ws.apache.org Subject: Re: axis 1.5 build failed in FC 3 Dear Samisa and other folks, Thanks for your suggestion. This is really a problem of header files. I've solved that problem finally. Now, running ant has no problem. But when I run ant -f package.xml, and returns error saying that the symlink type is missing. I am using Ant from www.jpackage.org. Would that causes the problem? I don't know whether that's an extra module in Ant or it's included in the Ant core. (I am no-voice user to ant. Please find the error in the end of this email) Did you have similar error? I tried sh -x ant -f package.xml and look at the classpath. Here it is: ++ exec /usr/lib/jvm/java/bin/java - classpath /usr/share/java/ant.jar:/usr/share/java/ant- launcher.jar:/usr/share/java/ant- contrib.jar:/usr/share/java/cpptasks.jar:/usr/share/java/jaxp_parser_imp l.jar:/usr/share/java/xml-commons-apis.jar:/usr/lib/jvm/java/lib/tools.j ar -Dant.home=/usr/share/ant -Dant.library.dir=/usr/share/ant/lib org.apache.tools.ant.launch.Launcher -lib '' -f package.xml symlink error copyAndLinkLinuxLibraries: BUILD FAILED /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:268: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:247: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:226: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:182: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:146: Could not create task or type of type: symlink. Thanks so much for your help. Bill -- Interface Design Kenneth F. Krutsch President Krutsch Associates, Inc. 14880 Highland Lane Minnetonka, MN 55345 [EMAIL PROTECTED] mobile: (612) 382-8228
RE: axis 1.5 build failed in FC 3
How about GNU Autoconf, Automake and Libtool Vaughan, Elliston, Tromey and Taylor New Riders, 2000 ISBN: 1-57870-190-2 But I think Ken meant axis-specific documentation. Automake support is essential as far as we are concerned, and I'm very grateful to Ken for offering to supply this. Tony Dodd Xaira project at Oxford University Research Technologies From: John Hawkins [mailto:[EMAIL PROTECTED] Sent: 03 May 2005 09:54To: Apache AXIS C User ListSubject: Re: axis 1.5 build failed in FC 3 Hi Ken, Well, if you're willing to maintain it then that's great :-) As you've probably seen- the only reason we don't want to maintain it is that we don't have the time/skills. As for documentation - hmm ! Not sure there is much for the GNU system (another one of our reasons for not using it !) I thought there was some on the web pages but couldn't find it just now ! Anyone else seen any docs for the GNU make system? thanks for your help Ken :-) "Kenneth F. Krutsch" [EMAIL PROTECTED] 29/04/2005 15:34 Please respond to"Apache AXIS C User List" To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: axis 1.5 build failed in FC 3 Hi,Would you folks like assistance building / maintaining a GNU automake system for this? I have a little experience with this. I know the team really likes Ant, but the reality is that this is a C++ project and I think developers will be expecting a GNU automake -style of build.If the Axis team *is* interested in this, then can someone send me any documentation you have on the build requirements? If not, then sorry for the interruption...KenAdrian Dick wrote: Hi,You don't mention exactly which version of ANT, etc. you are using.We are using a couple of features that are only present in later versions.The versions I use, and are also used for the nightly build are:Java - v1.4.1ANT - v.1.6.1ant-contrib - v0.6cpptasks - v1.0beta3These versions _should_ be mentioned in the documentation. Alas, taking aquick look now, I find the levels for ant-contrib and cpptasks are notexplicitly mentioned. However, running the command "ant -projecthelp" onbuild.xml or package.xml provides some basic setup documentation, whichdoes now include the above information.Could you check which versions you are using, and upgrade if required.Thanks,Adrian___Adrian Dick ([EMAIL PROTECTED])"Samisa Abeysinghe" [EMAIL PROTECTED] wrote on 29/04/2005 05:09:04: I cannot exactly understand what is going wrong with ant based pacaking.Adrian, could you please help ass you are the expert in this space.Thanks,Samisa...-Original Message-From: So Hok Chun, Bill [mailto:[EMAIL PROTECTED]]Sent: Friday, April 29, 2005 12:10 AMTo: axis-c-user@ws.apache.orgSubject: Re: axis 1.5 build failed in FC 3Dear Samisa and other folks,Thanks for your suggestion. This is really a problem of header files.I've solved that problem finally. Now, running "ant" has no problem.But when I run "ant -f package.xml", and returns error saying that the"symlink" type is missing. I am using Ant from www.jpackage.org.Would that causes the problem?I don't know whether that's an extra module in Ant or it's included inthe Ant core. (I am no-voice user to ant. Please find the error in theend of this email)Did you have similar error?I tried sh -x ant -f package.xml and look at the classpath. Here it is:++ exec /usr/lib/jvm/java/bin/java -classpath /usr/share/java/ant.jar:/usr/share/java/ant-launcher.jar:/usr/share/java/ant-contrib.jar:/usr/share/java/cpptasks.jar:/usr/share/java/jaxp_parser_impl.jar:/usr/share/java/xml-commons-apis.jar:/usr/lib/jvm/java/lib/tools.jar -Dant.home=/usr/share/ant -Dant.library.dir=/usr/share/ant/liborg.apache.tools.ant.launch.Launcher -lib '' -f package.xml symlink error copyAndLinkLinuxLibraries:BUILD FAILED/home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:268: Thefollowing error occurred while executing this line:/home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:247: Thefollowing error occurred while executing this line:/home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:226: Thefollowing error occurred while executing this line:/home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:182: Thefollowing error occurred while executing this line:/home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:146: Couldnot create task or type of type: symlink.Thanks so much for your
RE: axis 1.5 build failed in FC 3
I too meant the Axis specific information :-) Tony Dodd [EMAIL PROTECTED] 03/05/2005 10:08 Please respond to Apache AXIS C User List To 'Apache AXIS C User List' axis-c-user@ws.apache.org cc Subject RE: axis 1.5 build failed in FC 3 How about GNU Autoconf, Automake and Libtool Vaughan, Elliston, Tromey and Taylor New Riders, 2000 ISBN: 1-57870-190-2 But I think Ken meant axis-specific documentation. Automake support is essential as far as we are concerned, and I'm very grateful to Ken for offering to supply this. Tony Dodd Xaira project at Oxford University Research Technologies From: John Hawkins [mailto:[EMAIL PROTECTED] Sent: 03 May 2005 09:54 To: Apache AXIS C User List Subject: Re: axis 1.5 build failed in FC 3 Hi Ken, Well, if you're willing to maintain it then that's great :-) As you've probably seen- the only reason we don't want to maintain it is that we don't have the time/skills. As for documentation - hmm ! Not sure there is much for the GNU system (another one of our reasons for not using it !) I thought there was some on the web pages but couldn't find it just now ! Anyone else seen any docs for the GNU make system? thanks for your help Ken :-) Kenneth F. Krutsch [EMAIL PROTECTED] 29/04/2005 15:34 Please respond to Apache AXIS C User List To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: axis 1.5 build failed in FC 3 Hi, Would you folks like assistance building / maintaining a GNU automake system for this? I have a little experience with this. I know the team really likes Ant, but the reality is that this is a C++ project and I think developers will be expecting a GNU automake -style of build. If the Axis team *is* interested in this, then can someone send me any documentation you have on the build requirements? If not, then sorry for the interruption... Ken Adrian Dick wrote: Hi, You don't mention exactly which version of ANT, etc. you are using. We are using a couple of features that are only present in later versions. The versions I use, and are also used for the nightly build are: Java - v1.4.1 ANT - v.1.6.1 ant-contrib - v0.6 cpptasks - v1.0beta3 These versions _should_ be mentioned in the documentation. Alas, taking a quick look now, I find the levels for ant-contrib and cpptasks are not explicitly mentioned. However, running the command ant -projecthelp on build.xml or package.xml provides some basic setup documentation, which does now include the above information. Could you check which versions you are using, and upgrade if required. Thanks, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Samisa Abeysinghe [EMAIL PROTECTED] wrote on 29/04/2005 05:09:04: I cannot exactly understand what is going wrong with ant based pacaking. Adrian, could you please help ass you are the expert in this space. Thanks, Samisa... -Original Message- From: So Hok Chun, Bill [mailto:[EMAIL PROTECTED]] Sent: Friday, April 29, 2005 12:10 AM To: axis-c-user@ws.apache.org Subject: Re: axis 1.5 build failed in FC 3 Dear Samisa and other folks, Thanks for your suggestion. This is really a problem of header files. I've solved that problem finally. Now, running ant has no problem. But when I run ant -f package.xml, and returns error saying that the symlink type is missing. I am using Ant from www.jpackage.org. Would that causes the problem? I don't know whether that's an extra module in Ant or it's included in the Ant core. (I am no-voice user to ant. Please find the error in the end of this email) Did you have similar error? I tried sh -x ant -f package.xml and look at the classpath. Here it is: ++ exec /usr/lib/jvm/java/bin/java - classpath /usr/share/java/ant.jar:/usr/share/java/ant- launcher.jar:/usr/share/java/ant- contrib.jar:/usr/share/java/cpptasks.jar:/usr/share/java/jaxp_parser_imp l.jar:/usr/share/java/xml-commons-apis.jar:/usr/lib/jvm/java/lib/tools.j ar -Dant.home=/usr/share/ant -Dant.library.dir=/usr/share/ant/lib org.apache.tools.ant.launch.Launcher -lib '' -f package.xml symlink error copyAndLinkLinuxLibraries: BUILD FAILED /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:268: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:247: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:226: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:182: The following error occurred while executing this line: /home/bill/Desktop/soap/axis-c-1.5.0-linux-src/package.xml:146: Could not create task or type of type: symlink. Thanks so much for your help. Bill -- Interface Design Kenneth F. Krutsch President Krutsch Associates, Inc. 14880 Highland Lane Minnetonka, MN 55345 [EMAIL PROTECTED]
Re: axis 1.5 build failed in FC 3
John Tony: OK, cool. Not having been a contributor to any Apache project before, is there a link that can get me started? Also, should I be on a different mail list, or is the axis-c-user list just fine? Thanks, Ken John Hawkins wrote: I too meant the Axis specific information :-) "Tony Dodd" [EMAIL PROTECTED] 03/05/2005 10:08 Please respond to "Apache AXIS C User List" To "'Apache AXIS C User List'" axis-c-user@ws.apache.org cc Subject RE: axis 1.5 build failed in FC 3 How about GNU Autoconf, Automake and Libtool Vaughan, Elliston, Tromey and Taylor New Riders, 2000 ISBN: 1-57870-190-2 But I think Ken meant axis-specific documentation. Automake support is essential as far as we are concerned, and I'm very grateful to Ken for offering to supply this. Tony Dodd Xaira project at Oxford University Research Technologies From: John Hawkins [mailto:[EMAIL PROTECTED]] Sent: 03 May 2005 09:54 To: Apache AXIS C User List Subject: Re: axis 1.5 build failed in FC 3 Hi Ken, Well, if you're willing to maintain it then that's great :-) As you've probably seen- the only reason we don't want to maintain it is that we don't have the time/skills. As for documentation - hmm ! Not sure there is much for the GNU system (another one of our reasons for not using it !) I thought there was some on the web pages but couldn't find it just now ! Anyone else seen any docs for the GNU make system? thanks for your help Ken :-) "Kenneth F. Krutsch" [EMAIL PROTECTED] 29/04/2005 15:34 Please respond to "Apache AXIS C User List" To Apache AXIS C User List axis-c-user@ws.apache.org cc Subject Re: axis 1.5 build failed in FC 3 Hi, Would you folks like assistance building / maintaining a GNU automake system for this? I have a little experience with this. I know the team really likes Ant, but the reality is that this is a C++ project and I think developers will be expecting a GNU automake -style of build. If the Axis team *is* interested in this, then can someone send me any documentation you have on the build requirements? If not, then sorry for the interruption... Ken Adrian Dick wrote: Hi, You don't mention exactly which version of ANT, etc. you are using. We are using a couple of features that are only present in later versions. The versions I use, and are also used for the nightly build are: Java - v1.4.1 ANT - v.1.6.1 ant-contrib - v0.6 cpptasks - v1.0beta3 These versions _should_ be mentioned in the documentation. Alas, taking a quick look now, I find the levels for ant-contrib and cpptasks are not explicitly mentioned. However, running the command "ant -projecthelp" on build.xml or package.xml provides some basic setup documentation, which does now include the above information. Could you check which versions you are using, and upgrade if required. Thanks, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Samisa Abeysinghe" [EMAIL PROTECTED] wrote on 29/04/2005 05:09:04: I cannot exactly understand what is going wrong with ant based pacaking. Adrian, could you please help ass you are the expert in this space. Thanks, Samisa... -Original Message- From: So Hok Chun, Bill [mailto:[EMAIL PROTECTED]] Sent: Friday, April 29, 2005 12:10 AM To: axis-c-user@ws.apache.org Subject: Re: axis 1.5 build failed in FC 3 Dear Samisa and other folks, Thanks for your suggestion. This is really a problem of header files.
Re: setting ref attribute
Hi All The setSOAPMethodAttribute method in the client side can be used to set attributes.For further details please look at http://marc.theaimsgroup.com/?l=axis-c-devm=108611165220336w=2 Is there a similar method on the server side which could be used to set attributes of values to be returned?? Krishna krishna wrote: Hi All I am currently working with Axis 1.5 Alpha.I want to set the ref attribute - SOAP 1.2 ( href in SOAP 1.1) for a tag in the body of the soap response.I want to do this using a server side handler.Could someone give me pointers on how i can get this done. I have been checking out the API for Message Data and the handlers tutorial.The Handlers tutorial mentions how to get the SOAP Body of an SOAP Request but does not discuss about the SOAP Response. Regards Krishna
Creating ws client within ws server
Operating System: Mandrake Linux 10.0 Axis C++ version 1.5 binary Server service: doc/lit Client service: doc/lit I've been working on a project where a web service is used to perform a number of tasks, including the calling of another web service to verify a user id. When I attempt to create the web service client within the server method, the server method dies, and control jumps right to the fini method. I've tried a number of things including creating the client both statically and dynamically, etc, but no matter what, whenever the client is created the server method it dies. I know the importance of linking in the appropriate libraries when creating the server .so. I've linked libaxis_client.so. Has anyone attempted such a task? I can provide more specifics, but just want to know if this has been done successfully before. Regards, Ian Harder
RE: setting ref attribute
Hi Krishna, This is a Stub API call - meaning that this is available only on the client side. I am not sure on the effort required to get this supported on the server side, but my gut feel is that it should be comparatively easier as the client is already doing this. Please raise a Jira on this. Thanks, Samisa... -Original Message- From: krishna [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 3:27 AM To: Apache AXIS C User List Subject: Re: setting ref attribute Hi All The setSOAPMethodAttribute method in the client side can be used to set attributes.For further details please look at http://marc.theaimsgroup.com/?l=axis-c-devm=108611165220336w=2 Is there a similar method on the server side which could be used to set attributes of values to be returned?? Krishna krishna wrote: Hi All I am currently working with Axis 1.5 Alpha.I want to set the ref attribute - SOAP 1.2 ( href in SOAP 1.1) for a tag in the body of the soap response.I want to do this using a server side handler.Could someone give me pointers on how i can get this done. I have been checking out the API for Message Data and the handlers tutorial.The Handlers tutorial mentions how to get the SOAP Body of an SOAP Request but does not discuss about the SOAP Response. Regards Krishna
Re: Creating ws client within ws server
Hi Ian, Ian Harder [EMAIL PROTECTED] wrote on 04/05/2005 10:47:25: I've been working on a project where a web service is used to perform a number of tasks, including the calling of another web service to verify a user id. When I attempt to create the web service client within the server method, the server method dies, and control jumps right to the fini method. I've tried a number of things including creating the client both statically and dynamically, etc, but no matter what, whenever the client is created the server method it dies. I don't believe this is possible today. Axis C++ can't operate in both client and server mode, or behave as multiple clients or behave have multiple servers. I have previously opened requirements AXISCPP-427 and AXISCPP-426 to help address this (see: http://issues.apache.org/jira/browse/AXISCPP-427 and http://issues.apache.org/jira/browse/AXISCPP-426). The only way I could think of to workaround this today would be to have two (or more) separate instances of Axis (different shared library names, different C++ namespace) and set one up as the server and the other as the client. This would be very painful. Regards, Tim
RE: Creating ws client within ws server
Thanks for the info Tim. I should be able to work around it, although it would be nice not to have that kind of restriction on an Axis process. Ian -Original Message- From: Tim Bartley [mailto:[EMAIL PROTECTED] Sent: May 3, 2005 8:03 PM To: Apache AXIS C User List Subject: Re: Creating ws client within ws server Hi Ian, Ian Harder [EMAIL PROTECTED] wrote on 04/05/2005 10:47:25: I've been working on a project where a web service is used to perform a number of tasks, including the calling of another web service to verify a user id. When I attempt to create the web service client within the server method, the server method dies, and control jumps right to the fini method. I've tried a number of things including creating the client both statically and dynamically, etc, but no matter what, whenever the client is created the server method it dies. I don't believe this is possible today. Axis C++ can't operate in both client and server mode, or behave as multiple clients or behave have multiple servers. I have previously opened requirements AXISCPP-427 and AXISCPP-426 to help address this (see: http://issues.apache.org/jira/browse/AXISCPP-427 and http://issues.apache.org/jira/browse/AXISCPP-426). The only way I could think of to workaround this today would be to have two (or more) separate instances of Axis (different shared library names, different C++ namespace) and set one up as the server and the other as the client. This would be very painful. Regards, Tim
Noooooooobeeeee requires some help
Dear All I wondered whether someone could lead me to a good tuturial or some decent code. I'm trying to write some web services using the eclipse platform and wtp tools. I need the client web service to create a SOAP header - from my server-side web service, when i create the methods and the wsdl file, how do i tell the client it must create a SOAP header. Also, when the client has created the SOAP header my server-side web-service must create a value and send it ot he SOAP header, how to i send a value from the server-side to the client-side web service? Every call the client web-service makes i need to grab the value in the SOAP header and do a check on it to make sure it's still valid. What is the best way to do this? Thanks for any help offered _ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/
sessionID outHeader WSDD
I also have run into a problem using sessionID in soap header. I want the sessionID to be in the soap:header not in the soap:body. My WSDD looks like that: ... requestFlow handler type=java:org.apache.axis.handlers.SimpleSessionHandler/ /requestFlow responseFlow handler type=java:org.apache.axis.handler.SimpleSessionHandler/ /responseFlow The answer of a Request looks like this: soapenv:Header ns1:sessionID soapenv:actor=http://schemas.xmlsoap.org/soap/actor/next; soapenv:mustUnderstand=0 href=#id0/ /soapenv:Header soapenv:Body ... multiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=soapenc:long6713324205952170177/multiRef ... /soapenv:Body ---But I want it to look like that: soapenv:Header ns1:sessionID soapenv:actor=http://schemas.xmlsoap.org/soap/actor/next; soapenv:mustUnderstand=0 xsi:type=soapenc:long6713324205952170177/ns1:sessionID /soapenv:Header Like it is described in the german book of Thomas Bayer/Thilo Frotschner/ Marc Teufel: a href=http://www.entwickler.com/buecher/axis;http://www.entwickler.com/buecher/axis/a on page 244-246 it has perhaps sth to do with the parameter outheader=true but i didn't find any helpful examples about this Problem. thx a lot for your help sorry for my bad english Sebastian
OT: Glue
Hi Im taking up my interest for Axis/Glue/XX doing WebService development in Java, that is. I know this is a Axis forum, but I was looking at Clue does any one know what the price-tag on Clue is 1 developer approx.? Best regards Jan
Re: wrapped vs. document
Because there is no such style as wrapped in WSDL. The only permitted styles in WSDL are rpc and document. Axis WSDD style=wrapped produces WSDL style=document. (wrapped is a programming style rather than a service style -- it presents a programming interface comparable to rpc style, but it produces document/literal services.) See my blog entry for further explanation: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html Anne On 5/2/05, Dave Overbeck [EMAIL PROTECTED] wrote: Hello, I have the following deployment file and resulting wsdl. I can't figure out why the wsdl is coming out with style=document when it should be wrapped. Any ideas? Thanks, Dave deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; service name=ItemInq provider=java:RPC style=wrapped use=literal parameter name=className value=com.turnkey.rtl.jws.ItemInq/ parameter name=allowedMethods value=*/ parameter name=wsdlTargetNamespace value=http://jws.rtl.turnkey.com/ parameter name=wsdlServiceElement value=ItemInqService/ parameter name=wsdlServicePort value=ItemInqService/ parameter name=wsdlPortType value=ItemInqService/ /service /deployment ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://jws.rtl.turnkey.com; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://jws.rtl.turnkey.com; xmlns:intf=http://jws.rtl.turnkey.com; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; !--WSDL created by Apache Axis version: 1.2RC3 Built on Feb 28, 2005 (10:15:14 EST)-- wsdl:types schema elementFormDefault=qualified targetNamespace=http://jws.rtl.turnkey.com; xmlns=http://www.w3.org/2001/XMLSchema; element name=get complexType sequence element name=in0 type=xsd:string/ element name=in1 type=xsd:string/ element name=in2 type=xsd:string/ element name=in3 type=xsd:string/ /sequence /complexType /element element name=getResponse complexType sequence element name=getReturn type=xsd:byte/ /sequence /complexType /element /schema /wsdl:types wsdl:message name=getResponse wsdl:part element=impl:getResponse name=parameters/ /wsdl:message wsdl:message name=getRequest wsdl:part element=impl:get name=parameters/ /wsdl:message wsdl:portType name=ItemInqService wsdl:operation name=get wsdl:input message=impl:getRequest name=getRequest/ wsdl:output message=impl:getResponse name=getResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=ItemInqServiceSoapBinding type=impl:ItemInqService wsdlsoap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=get wsdlsoap:operation soapAction=/ wsdl:input name=getRequest wsdlsoap:body use=literal/ /wsdl:input wsdl:output name=getResponse wsdlsoap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ItemInqService wsdl:port binding=impl:ItemInqServiceSoapBinding name=ItemInqService wsdlsoap:address location=http://192.168.1.6:8080/axis/services/ItemInq/ /wsdl:port /wsdl:service /wsdl:definitions
Re: OT: Glue
I assume you mean webMethods Glue? You have to ask webMethods for pricing. I have to warn you -- webMethods isn't particularly interested in selling you a single developer license. At a minimum, they will sell you a Glue server runtime license, but they want to sell you all of Fabric. You can download an evaluation version of Glue v5 for free. See http://www.webmethods.com/meta/default/folder/007014. It's unsupported, although there's a discussion list available and decent documentation. If you're looking for things like WS-Security, WS-I compliance, and JAX-RPC/SAAJ support, then you'll need to purchase Glue v6. (contact webMethods for pricing) Anne On 5/3/05, Jan Agermose [EMAIL PROTECTED] wrote: Hi I'm taking up my interest for Axis/Glue/XX doing WebService development in Java, that is. I know this is a Axis forum, but I was looking at Clue does any one know what the price-tag on Clue is 1 developer approx.? Best regards Jan
invoke methods wsdl file
Hello
I've got to develop a web service client, but don't know where to start
I have the external wsdl file which exposes the methods i wish to invoke.
Is it something like this
public static void main(String args[])
{
URL url = new
URL(http://thirdpartycallservice/third_party_calling_service.wsdl;);
Service service = new Service();
Call call = (Call)service.createCall();
.
.
.
.
.
.
}
I don't know the next code to continue
Any help much appreciated
_
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
Does this make sense
I'm trying to do the following. Can someone tell me whether it is
OK/possible doing it this way
Is there a better way of doing it
I'm writing server-side web services, exposing methods to clients (these can
be anything).
I need to create a custom soap header. Would it be best for the client to
do this?
I then need to add a value to the SOAP header. Is the below code the right
wya of doing this?
public static String addSOAPHeader(String token) throws Exception
{
URL endpoint = new URL(http://localhost:8080/somwhere;);
Service service = new Service();
Call call = (Call)service.createCall();
SOAPHeaderElement TokenHeader = new
SOAPHeaderElement(http://localhost...,TokenHeader;);
TokenHeader.setObjectValue(stringvalue);
call.addHeader(TokenHeader);
}
With every call the client makes, will this value disappear or will it keep
it. How do i make sure the value is kept, until the client is closed ?
Also i'm ok with setting a vlaue (i think), how do i 'grab' the value?
Many thanks
_
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
Overloaded methods and Wrapped literal
Hi, I use axis 1.1. When I used RPC style, java2wsdl and wsdl2java produced good proxies for classes with overloaded methods. However, they fail to produce good proxies when WRAPPED Style is used. While I know web services do not support overloaded methods, is there an option for ensuring that overloaded methods are handled in a proper manner in wrapped styles? At the moment I see that only one of the methods is produced as many times as the overload. I am able to succeed by deleting or renaming the repeated names in the proxies. But this is not looking like an ideal solution. I would like to know if anyone has successfully used these tools for overloaded methods? Thanks and Regards Sagar
FW: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
From: Cid, Jose Sent: Monday, May 02,
2005 5:24 PMTo: 'axis-user@ws.apache.org'Subject:
SimpleDeserializer encountered a child element, which is NOT expected, in
something it was trying to deserialize.
Can anyone shed some light as to what may be
going on here. I am use axis 1.2RC3. Multiref is
false (server-config.wsdd).
A snippet of my client code is shown
below:
... Service
svc = (Service) serviceMap.get( SERVICE_INSTANCE
); String szServiceAddress = (String)
serviceMap.get( SERVICE_ADDRESS ); String
szNameSpace = (String) serviceMap.get( SERVICE_NAME_SPACE
); String szPortName = (String)
serviceMap.get( SERVICE_PORT_NAME );
Call call = (Call)
svc.createCall( ); call.setProperty(
Call.SESSION_MAINTAIN_PROPERTY, new Boolean( true ) );
call.setTargetEndpointAddress( szServiceAddress
); call.setOperationName( new QName(
szNameSpace, "getUnitDetail" ) );
call.setPortTypeName( new QName( szNameSpace, szPortName ) );
Properties
sessionProperties = getSession( );
if (
sessionProperties != null ) { // Using
previous session
String szCookie = sessionProperties.getProperty( SESSION_COOKIE );
if
( szCookie != null )
{
call.setProperty( HTTPConstants.HEADER_COOKIE, szCookie
);
} }
Object[] aObj =
null;
Object someObj =
call.invoke( aObj );
// = Also
tried to invoke it this way...
//GetUnitDetailResponse gudResponse = (GetUnitDetailResponse) call.invoke( aObj
);...
=== to server:
GET //axis/services/UnitServiceApi?wsdl
HTTP/1.1User-Agent: Java/1.4.2_06Host: localhost:8090Accept:
text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2Connection:
keep-alive
=== from server:
HTTP/1.1 200 OKServer:
Apache-Coyote/1.1Content-Type: text/xml;charset=utf-8Transfer-Encoding:
chunkedDate: Mon, 02 May 2005 20:59:26 GMT
1803?xml version="1.0"
encoding="UTF-8"?wsdl:definitions targetNamespace="http://dsview.avocent.com/server/webservices/units"
xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://dsview.avocent.com/server/webservices/units" xmlns:intf="http://dsview.avocent.com/server/webservices/units"
xmlns:tns1="urn:units:webservices:server:dsview:avocent:com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
!--WSDL created by Apache Axis version:
1.2RC3
Built on Feb 28, 2005 (10:15:14
EST)--
wsdl:types schema
elementFormDefault="qualified"
targetNamespace="urn:units:webservices:server:dsview:avocent:com"
xmlns="http://www.w3.org/2001/XMLSchema"
element
name="getUnitDetail"
complexType
sequence element name="unitId"
type="xsd:unsignedInt"/ element
name="unitType" type="xsd:unsignedInt"/
/sequence /complexType
/element complexType
name="UnitDetail"
sequence element name="UnitId"
nillable="true" type="xsd:string"/ element
name="Name" nillable="true" type="xsd:string"/
element name="Address" nillable="true"
type="xsd:string"/ element name="Type"
nillable="true" type="xsd:string"/
/sequence /complexType
element name="getUnitDetailResponse"
complexType
sequence element name="return"
nillable="true" type="tns1:UnitDetail"/
/sequence /complexType
/element element
name="getUnitList"
complexType
sequence element name="unitType"
type="xsd:unsignedInt"/
/sequence /complexType
/element complexType
name="ArrayOfUnitDetail"
sequence element maxOccurs="unbounded"
minOccurs="0" name="item" type="tns1:UnitDetail"/
/sequence /complexType
element name="getUnitListResponse"
complexType
sequence element name="return"
nillable="true" type="tns1:ArrayOfUnitDetail"/
/sequence /complexType
/element element
name="doAction"
complexType
sequence element name="unitId"
type="xsd:unsignedInt"/ element
name="unitType" type="xsd:unsignedInt"/
element name="actionReq"
type="xsd:unsignedInt"/
/sequence /complexType
/element complexType
name="UnitStatusInfo"
sequence element name="UnitId"
nillable="true" type="xsd:string"/ element
name="Status" nillable="true" type="xsd:string"/
/sequence /complexType
element name="doActionResponse"
complexType
sequence element name="return"
nillable="true" type="tns1:UnitStatusInfo"/
/sequence /complexType
/element
/schema/wsdl:types
wsdl:message
name="getUnitListRequest"
wsdl:part
element="tns1:getUnitList" name="getUnitList"/
/wsdl:message
wsdl:message
name="getUnitDetailRequest"
wsdl:part
element="tns1:getUnitDetail" name="getUnitDetail"/
/wsdl:message
wsdl:message
name="doActionRequest"
wsdl:part
element="tns1:doAction" name="doAction"/
/wsdl:message
wsdl:message
name="getUnitDetailResponse"
wsdl:part
element="tns1:getUnitDetailResponse"
name="getUnitDetailResponse"/
/wsdl:message
wsdl:message
name="doActionResponse"
wsdl:part
element="tns1:doActionResponse" name="doActionResponse"/
/wsdl:message
wsdl:message
name="getUnitListResponse"
wsdl:part
element="tns1:getUnitListResponse" name="getUnitListResponse"/
Re: second parameter is null when using wsdl with wsdlsoap:binding style=document
When using document style, you don't specify parameters in the message definition. Instead you have one message part, and that part points to a wrapped element. The wrapper element should be defined as a sequence of elements -- which are your parameters. If you want to create a parameterized interface, then you want to use the wrapped style. (which is what .NET uses by default) Anne On 5/3/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, in a futher message I read about a similar problem and it's solution. posted solution: change wsdlsoap:binding style=document to wsdlsoap:binding style=rpc But the solution posted there is not applicable to me. My little webservice has to be used in a IIS from MS. And the developer suite of MS has problems with WSDL files that use rpc style. Has anyone a idea to solve this? I am using tomcat 5.5.9 with java 1.5.0_02-b09 on windows xp. My axis release is 1.2 from yesterday evening (02.05.2005 18:12) Thanks Harri __ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201
ANNOUNCE : Axis 1.2 RELEASE
Hi folks: After *much* too long, the Axis team would like to announce the release of Axis 1.2 final. You can get it at: http://www.apache.org/dyn/closer.cgi/ws/axis/1_2/ (if your favorite mirror doesn't have it yet try another, it's propagating now) A few words about this release - * A LOT of things have been cleaned up/fixed since 1.1, but 1.2 is not yet a perfect beast. We know there are still issues that, although they didn't block this release, are important to our user base. We will be working to resolve these in the near term, which brings us to... * This took way too much time. We will (for the remainder of Axis 1.X's lifetime and hopefully all of Axis 2.0's...) be focusing much more aggressively on the release early and often mantra. Expect to see more fixes and more official releases near term. * Thanks to EVERYONE who submitted bug reports, patches, and (especially) good, concise test cases. Without your help we wouldn't have been able to make half the progress we did. * As always, please send questions/comments to axis-user@ws.apache.org, and development-related issues to [EMAIL PROTECTED] Issues may be checked and filed at http://issues.apache.org/jira/browse/AXIS Onwards to 1.Next... Thanks, --Glen on behalf of the Axis team
