Re: wsdl exploder
I think WSDL4J [1] will do what you want. Simply read in the WSDL and then serialize it out. AFAIK, WSDL will serialize to a single file. John Kaputin should know for sure whether WSDL4J will suit your purpose. [1] http://sourceforge.net/projects/wsdl4j Lawrence From: Jon Seymour [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: 09/12/2008 07:47 AM Subject: wsdl exploder Has anyone ever come across a WSDL-exploder that converts a logical WSDL entity that spans multiple files (via the WSDL and XML schema import mechanisms) into a single entity that contains all the referenced entities inline? I need such a beast to help support a client whose ability to properly keep track of schema locations in a multi-file entity is somewhat suspect. jon seymour. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 osgi bundle on Tomcat+servletbridge
Did you start the Axis2 bundle? In WEB-INF/eclipse/configuration/config.ini add the Axis2 bundle to the list of osgi.bundles [EMAIL PROTECTED],... Lawrence techi_amol [EMAIL PROTECTED] 07/02/2008 01:57 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Axis2 osgi bundle on Tomcat+servletbridge Hi All, i followed the instructions given in axis2_osgi_integration.pdf, and instead of using equinox standalone with embedded Jetty, I tried to do the same thing on Tomcat, with servletbridge.war hosting the equinox osgi env. (For more details please refer http://www.nabble.com/-Axis2--Axis2-OSGi-bundle.-Phase-1-td18046920.html) However, when i try to start org.apache.axis2.osgi_1.0.0.SNAPSHOT bundle, i get the following exception org.osgi.framework.BundleException: Exception in org.apache.axis2.osgi.internal.Activator.start() of bundle org.apache.axis2.osgi. at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1018) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:252) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:145) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:294) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:279) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:214) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoClassDefFoundError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:596) at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:581) at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:97) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:90) at org.apache.axis2.osgi.deployment.OSGiServerConfigurator.populateAxisConfiguration(OSGiServerConfigurator.java:80) at org.apache.axis2.osgi.deployment.OSGiServerConfigurator.getAxisConfiguration(OSGiServerConfigurator.java:61) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:68) at org.apache.axis2.osgi.deployment.OSGiConfigurationContextFactory.createConfigurationContext(OSGiConfigurationContextFac tory.java:51) at org.apache.axis2.osgi.InitServlet.init(InitServlet.java:45) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.init(ServletRegistration.java:65) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.registerServlet(ProxyServlet.java:141) at org.eclipse.equinox.http.servlet.internal.HttpServiceImpl.registerServlet(HttpServiceImpl.java:50) at org.apache.axis2.osgi.internal.Activator$HttpServiceTracker.addingService(Activator.java:76) at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064) at org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:926) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:330) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:274) at org.apache.axis2.osgi.internal.Activator.start(Activator.java:45) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993) ... 14 more Nested Exception: java.lang.NoClassDefFoundError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:596) at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:581) at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:97) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:90) at org.apache.axis2.osgi.deployment.OSGiServerConfigurator.populateAxisConfiguration(OSGiServerConfigurator.java:80) at
Re: WSDL2.0 endpoint problem
Hi Yassou, As you've got an Axis2 specific question I think you'll get a better response posting to the Axis2 user list [EMAIL PROTECTED] You can subscribe to the list at [1]. [1] http://ws.apache.org/axis2/mail-lists.html Lawrence Yassou [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 06/06/2008 06:38 AM To [EMAIL PROTECTED] cc Subject WSDL2.0 endpoint problem Hi ! My probleme is that the WSDL2.0 description after deployement in axis2 is not the same WSDL2.0 description provided in the begining I provide this: ?xml version=1.0 encoding=UTF-8? wsdl2:description xmlns:wsdl2=http://www.w3.org/ns/wsdl; xmlns:tns= http://wsdl2package; xmlns:wsoap=http://www.w3.org/ns/wsdl/soap; xmlns:wrpc=http://www.w3.org/ns/wsdl/rpc; xmlns:ns1= http://org.apache.axis2/xsd; xmlns:wsaw= http://www.w3.org/2006/05/addressing/wsdl; xmlns:wsdlx= http://www.w3.org/ns/wsdl-extensions; xmlns:ns=http://wsdl2package; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:whttp= http://www.w3.org/ns/wsdl/http; targetNamespace=http://wsdl2package; wsdl2:documentation Please Type your service description here /wsdl2:documentation wsdl2:types xs:schema attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://wsdl2package; xs:element name=add xs:complexType xs:sequence xs:element minOccurs=0 name=a type=xs:int / xs:element minOccurs=0 name=b type=xs:int / /xs:sequence /xs:complexType /xs:element xs:element name=addResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return type=xs:int / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl2:types wsdl2:interface name=ServiceInterface wsdl2:operation name=add style=http://www.w3.org/ns/wsdl/style/rpc; wrpc:signature=a #in b #in return #return pattern= http://www.w3.org/ns/wsdl/in-out; wsdl2:input element=ns:add wsaw:Action=urn:add /wsdl2:output element=ns:addResponse wsaw:Action=urn:addResponse / /wsdl2:operation /wsdl2:interface wsdl2:binding name=Wsdl2classHttpBinding interface=tns:ServiceInterface whttp:methodDefault=POST type= http://www.w3.org/ns/wsdl/http;wsdl2:operation ref=tns:add whttp:location=Wsdl2class/add / /wsdl2:binding wsdl2:service name=Wsdl2class interface=tns:ServiceInterface wsdl2:endpoint name=Wsdl2classHttpEndpoint binding=tns:Wsdl2classHttpBinding address= http://127..0.0.1:8080/axis2/services/Wsdl2class.Wsdl2classHttpEndpoint; / /wsdl2:service /wsdl2:description with this service.xml : ?xml version=1.0 encoding=UTF-8? !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.3 Built on : Aug 10, 2007 (04:45:47 LKT) -- serviceGroup service name=Wsdl2class messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=org.apache.axis2.axis2userguide.Wsdl2ClassMessageReceiverInOut/ /messageReceivers parameter name=ServiceClassorg.apache.axis2.axis2userguide.Wsdl2ClassSkeleton/parameter parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter operation name=add mep=http://www.w3.org/ns/wsdl/in-out; actionMapping\\/actionMapping outputActionMappingurn:addResponse/outputActionMapping /operation /service /serviceGroup I execute ant jar.server and I copy build/lib/*.aar file to G:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axis2\WEB-INF\services then when I check the WSDL2.0 description axis2 shows when I write this address in address bar : http://localhost:8080/axis2/services/Wsdl2class?wsdl2 - wsdl2:description xmlns:wsdl2=http://www.w3.org/ns/wsdl; xmlns:tns= http://ws..apache.org/axis2; xmlns:wsoap=http://www.w3.org/ns/wsdl/soap; xmlns:wrpc=http://www.w3.org/ns/wsdl/rpc; xmlns:wsaw= http://www.w3.org/2006/05/addressing/wsdl; xmlns:wsdlx= http://www.w3.org/ns/wsdl-extensions; xmlns:whttp= http://www.w3.org/ns/wsdl/http; targetNamespace= http://ws.apache.org/axis2; wsdl2:documentationWsdl2class/wsdl2:documentation wsdl2:types / - wsdl2:interface name=ServiceInterface - wsdl2:operation name=add pattern=http://www.w3.org/ns/wsdl/in-out; wsdl2:input element=#none / wsdl2:output element=#none wsaw:Action=urn:addResponse / /wsdl2:operation /wsdl2:interface - wsdl2:binding name=Wsdl2classSoap11Binding interface= tns:ServiceInterface type=http://www.w3.org/ns/wsdl/soap; wsoap:version =1.1 wsdl2:operation ref=tns:add / /wsdl2:binding - wsdl2:binding name=Wsdl2classHttpBinding interface= tns:ServiceInterface whttp:methodDefault=POST type= http://www.w3.org/ns/wsdl/http; wsdl2:operation ref=tns:add whttp:location=Wsdl2class/add / /wsdl2:binding - wsdl2:binding name=Wsdl2classSoap12Binding interface= tns:ServiceInterface type=http://www.w3.org/ns/wsdl/soap; wsoap:version =1.2 wsdl2:operation ref=tns:add / /wsdl2:binding - wsdl2:service name=Wsdl2class interface=tns:ServiceInterface wsdl2:endpoint name=Wsdl2classHttpSoap12Endpoint binding=
WSDL 2.0 and REST article
I've just published an article entitled Describe REST Web services with WSDL 2.0 [1] on developerWorks. I think this will be useful to the Web services community so I thought I'd share the link. [1] http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/ Lawrence Mandel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-I Basic profile error
I think you're seeing these errors because you haven't specified the name attribute on your binding input and output elements. For example, wsdl:portType name=imageViewPortType ... wsdl:operation name=imageCheck wsdl:input name=availableRequest message=tns:availableRequestMsg / wsdl:output name=availableResponse message=tns:availableResponseMsg / wsdl:fault name=generalErrorMessage message=tns:generalErrorMsg / wsdl:fault name=schemaErrorMessage message=tns:schemaErrorMsg / /wsdl:operation ... wsdl:binding name=imageViewBinding type=tns:imageViewPortType ... wsdl:operation name=imageCheck soap:operation soapAction=http://ws.myco.com/imagecheck; style=document / wsdl:input name=availableRequest soap:header message=tns:authenticationMsg part=authentication use=literal / soap:body parts=availableRequest use=literal / /wsdl:input wsdl:output name=availableResponse soap:body parts=availableResponse use=literal / /wsdl:output wsdl:fault name=generalErrorMessage soap:fault name=generalErrorMessage use=literal / /wsdl:fault wsdl:fault name=schemaErrorMessage soap:fault name=schemaErrorMessage use=literal / /wsdl:fault /wsdl:operation Lawrence T. Allen [EMAIL PROTECTED] 04/08/2008 11:01 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: WS-I Basic profile error Below is the output. Warning: This web reference does not conform to WS-I Basic Profile v1.1. R2718: A wsdl:binding in a DESCRIPTION MUST have the same set of wsdl:operations as the wsdl:portType to which it refers. - Operation 'imageCheck' on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview' has no matching binding. - Operation 'imageView' on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview' has no matching binding. - Operation 'imageCheck' on binding 'imageViewBinding' from namespace 'http://ws.myco.com/imageview' has no matching operation on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview'. - Operation 'imageCheck' on binding 'imageViewBinding' from namespace 'http://ws.myco.com/imageview' has no matching operation on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview'. - Operation 'imageView' on binding 'imageViewBinding' from namespace 'http://ws.myco.com/imageview' has no matching operation on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview'. - Operation 'imageView' on binding 'imageViewBinding' from namespace 'http://ws.myco.com/imageview' has no matching operation on portType 'imageViewPortType' from namespace 'http://ws.myco.com/imageview'. Thanks very much for any help. T Anne Thomas Manes wrote: Please provide the specific error(s). Anne On Mon, Apr 7, 2008 at 1:17 PM, Jack Sprat [EMAIL PROTECTED] wrote: I have a WSDL that passes WS-I basic profile validation when run from the latest version of soapUI. I have a partner using .Net to consume the service that gets an error when trying to create a Web Reference to it. I'm trying to debug the problem for him and found that the Microsoft wsdl.exe tool is complaining that the WSDL does not conform to the WS-I Basic Profile 1.1. The errors indicate the operations have no matching binding but I cannot see the errors. Can someone lend a hand? This has me stumped. The WSDL is below. ?xml version=1.0 encoding=UTF-8? wsdl:definitions name=imageViewService targetNamespace=http://ws.myco.com/imageview; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://ws.myco.com/imageview; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; wsdl:types xsd:schema attributeFormDefault=unqualified elementFormDefault=qualified xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://ws.myco.com/imageview; targetNamespace=http://ws.myco.com/imageview; !-- Reference all the schemas -- xsd:include schemaLocation=availableImagesRequest.xsd/ xsd:include schemaLocation=availableImagesResponse.xsd/ xsd:include schemaLocation=imagesRequest.xsd/ xsd:include schemaLocation=imagesResponse.xsd/ !-- Define simple types used in SOAP request/response here. -- xsd:complexType name=AuthenticationType xsd:sequence xsd:element name=user type=tns:UserType / xsd:element name=password type=tns:PasswordType / /xsd:sequence /xsd:complexType xsd:simpleType name=EchoRequestType xsd:restriction base=xsd:string xsd:maxLength value=100 / /xsd:restriction /xsd:simpleType xsd:simpleType name=PasswordType
Re: [Axis2] [1.4] Zero Blockers / RC4 this weekend / Plan for 1.4 Final
Dims, Releasing Woden by next Friday should be doable. Axis2 and Woden are continuously integrated and Woden is still at M8 so I think it's safe for Woden to forgo the RC process (which we haven't used to this point) and simply vote on the release. Let's aim for a vote starting Monday with the goal or releasing Wed. Will that work with your schedule? Lawrence Davanum Srinivas [EMAIL PROTECTED] 04/01/2008 11:00 PM Please respond to axis-user@ws.apache.org To Axis developer list [EMAIL PROTECTED], axis-user@ws.apache.org, [EMAIL PROTECTED], [EMAIL PROTECTED] cc Subject [Axis2] [1.4] Zero Blockers / RC4 this weekend / Plan for 1.4 Final -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, Looks like there are no blockers on the JIRA marked for 1.4 https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hiderequestId=12312460 So, I'll try to cut RC4 this friday and we can roll out the RC's for axiom/xmlschema/neethi early next week. If all's well (cross my fingers) we can shoot for 1.4 Final next friday. One issue though...Can we get a woden release by next friday? thanks, dims -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH8vbWgNg6eWEDv1kRAiSMAJ9tiV1artrFtpP/uC8IEVoT3+WKbQCfUfM8 +CzhMg3v0wkFZ1agNi+zjfg= =gLeB -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: eclipse and axis2
Hi Michael, As Matthias said, by default the Eclipse Web Tools Platform (WTP) creates it's own webapps directory in WORKSPACE/.metadata/.plugins/org.eclipse.wst.server.core/tmp0. You should find your exploded war there. Also of note, the WTP 2.x Web service tools can generate Axis2 services. I don't know all of the specifics but you may be interested in these tools. Lawrence [EMAIL PROTECTED] 03/07/2008 03:06 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject AW: eclipse and axis2 Hi Michael, I am not using Axis2 for a long time, but I'm using eclipse for quite a while. So all other users, please correct me if I'm wrong. What version of eclipse do you have installed? I assume it is a current version with Web Tools plugin. I installed the eclipse Version for Java EE Developers. The easiest way I encountered to setup an axis2 eclipse project is first telling eclipse where your Axis2 distribution is. Therefore set the Axis2 Runtime location to your axis2 installation directory (in eclipse: Window - Preferences - Web Services - Axis2 Preferences). Now you can create a new dynamic web project with an axis2 nature which arranges all necessary libraries for you. The other problem why eclipse does not deploy your axis2.war is probably the feature of eclipse that it does not modify your tomcat installation in standard mode. Therefore it does not deploy your webapps installed to this tomcat. You can change this setting when you doubleclick on your server and change the Server Locations to Use Tomcat Installation. That way your axis2.war should be deployed. HTH, Matthias. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Michael Potter Gesendet: Donnerstag, 6. März 2008 23:10 An: axis-user@ws.apache.org Betreff: eclipse and axis2 Axis2 Crew, I am trying to use Eclipse to edit existing webservices that are in the form of .aar files. At this point I have tomcat successfully installed and working with Eclipse. The problem I am having is getting Axis2 installed and working with Eclipse. I downloaded Axis2 and built the axis2.war file. I moved the axis2.war into webapps directory. I expected the .war file to expand when I started tomcat. I start tomcat using the context sensitive menu in Eclipse. Is there something special about the way Eclipse starts tomcat where it does not expand a .war file? Can anyone give me some hints about other things I may run into when using axis2 with Eclipse? -- Michael Potter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 and OSGi
Hi Demetris, Dims has kicked off an effort to create an Axis2 OSGi bundle. He posted to the axis-dev list last week [1]. [1] http://marc.info/?l=axis-devm=120308686726732w=2 Lawrence Demetris G [EMAIL PROTECTED] 02/28/2008 11:02 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Axis2 and OSGi Hi all, has anyone tried to execute Axis2 in the OSGi containers? I know Axis1.x was imported as a bundle in OSGi but no idea about Axis2. I am wondering if it can be deployed in a similar manner as in Tomcat although I think it may still need an Activator to control the rest of its implementation. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Moving Axis2 code base into JDK 1.5
+1 Woden has also discussed a move to Java 5 and the dev team was in favour of this move. As Axis2 depends on Woden we cannot consider this move unless Axis2 also moves. Lawrence Deepal Jayasinghe [EMAIL PROTECTED] 02/26/2008 11:15 PM Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] [EMAIL PROTECTED], axis-user@ws.apache.org axis-user@ws.apache.org cc Subject [Axis2] Moving Axis2 code base into JDK 1.5 Hi all , As you might remember few months back Glen asked the list about moving to JDK 1.5 and I think we got very positive feedback. So I thought of asking again and change the code to work with JDK 1.5 . The main reason behind sending this mail is due the dependency we have for annogen. As I can see that project is dead one and there is no development happening so I do not think it is a good idea to depend on such a project. In the meantime we have few issues with annogen as well ,first inner class problem (I have locally fixed that both in Axis2 and Annogen will commit soon) , second is the final class problem. I request a release from annogen after the changes that Dims did , but we did not get any reply so far. We all know that we get better annotation support from JDK 1.5 so if we move to JDK 1.5 we can get rid of the annogen dependency and we can just use JDK for annotation processing. Other problem is generic support , if we move to JDK 1.5 we can have generic support in our POJOs. In addition to POJO we can get better concurrent support in JDK 1.5 as well. So if we move to JDK 1.5 we can get better support , and I do not think any advantage of staying in 1.4 . If some user want to use Axis2 in JDK 1.4 they can happily use Axis2 1.3 , which is very stable version and working fine in 1.4 and 1.5. If any user or developers have any concern on moving to JDK 1.5 please come forward and reply to this mail that will be very helpful for all of us. Here is my +1 for moving to JDK 1.5 to and release Axis2 1.4 in JDK 1.5 Thank you, Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: WSDL problem 'Didn't find specified return QName' error
Hi Rushikesh,
Can you please attach your entire WSDL document, including the definitions
element. This type of error is typically a problem with namespace
declarations or usage.
Here's a shot at the problem without all of the information. In your WSDL
snippet you reference the XML schema element impl:getServerStatus but this
element is not defined in your XML schema snippets.
BTW, you'll generally get more responses if you request them nicely. The
following came across (to me at least) as pretty demanding.
Please spend some time reading this fully. I am tired of trying to solve
this problem for more than a week now.
Remember, Apache is an Open Source community comprised of many people who
donate their time. There are no support contracts here.
Lawrence
Rushikesh Thakkar [EMAIL PROTECTED]
01/11/2008 02:50 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Fwd: WSDL problem 'Didn't find specified return QName' error
Hi folks,
Please spend some time reading this fully. I am tired of trying to solve
this problem for more than a week now.
I have to write a webservice client using Axis 1.4. The webservice is very
old, written using servlets and apache-soap. I do not even have the WSDL
for it. So I wrote WSDL by myself, by analyzing request and response soap
messages. I am using the types and stubs generated for this service by
WSDL2Java tool, in my client application.
GetServerStatusResponse response = mappService .getServerStatus
(getServerStatusRequest);
System. out.println(response.getCode ());
System. out.println(response.getDescription ());
System. out.println(response.getTrackingCode ());
The above code executes normally without any exceptions, but its prints
only null values.
Can anybody tell me what the problem with my WSDL is?
Following is the Response soap-message that the webservice sends.
?xml version=1.0 encoding=ISO-8859-1?
SOAP-ENV:Envelope xmlns:SOAP-ENV=
http://schemas.xmlsoap.org/soap/envelope/
SOAP-ENV:Body
getServerStatus xmlns=urn:sampleURN
serviceStatus
code0/code
descriptiongetServerStatus OK!/description
trackingCodeAABBMMCOEED/trackingCode
/serviceStatus
statusServer xyz alive at Thu Jan 10 11:33:35 CET
2008%BUILDTAG%Build date amp; time: %DEPLOYDATE%/status
/getServerStatus
/SOAP-ENV:Body
/SOAP-ENV:Envelope
Here is the WSDL definition I've written for above message:
xsd:element name=getServerStatusResponse
xsd:complexType
xsd:sequence
xsd:element name=getServerStatusReturn
type=impl:GetServerStatusResponse/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:complexType name=GetServerStatusResponse
xsd:complexContent
xsd:extension base=impl:ServiceStatus
xsd:sequence
xsd:element name=status type=xsd:string/
/xsd:sequence
/xsd:extension
/xsd:complexContent
/xsd:complexType
xsd:complexType name=ServiceStatus
xsd:sequence
xsd:element name=code nillable=true type=xsd:string/
xsd:element name=description nillable=true type=xsd:string/
xsd:element name=trackingCode nillable=true type=xsd:string/
/xsd:sequence
/xsd:complexType
wsdl:message name=getServerStatusRequest
wsdl:part element=impl:getServerStatus name=parameters/
/wsdl:message
wsdl:message name=getServerStatusResponse
wsdl:part element=impl:getServerStatusResponse name=parameters/
/wsdl:message
wsdl:portType name=samplePortName
wsdl:operation name=getServerStatus
wsdl:input message=impl:getServerStatusRequest
name=getServerStatusRequest/
wsdl:output message=impl:getServerStatusResponse
name=getServerStatusResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=sampleBindingName type=impl:samplePortName
wsdlsoap:binding style=document transport=
http://schemas.xmlsoap.org/soap/http /
wsdl:operation name=getServerStatus
wsdlsoap:operation soapAction=/
wsdl:input name=getServerStatusRequest
wsdlsoap:body use=literal/
/wsdl:input
wsdl:output name=getServerStatusResponse
wsdlsoap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
If I add the following 4 lines in _initOperationsDesc1() method of the
WebService Stub, then I get the following error .
Error: Didn't find specified return QName {
http://aaa.ccc.com}getServerStatus!;
param = new org.apache.axis.description.ParameterDesc(new
javax.xml.namespace.QName( urn:sampleURN, serviceStatus ),
org.apache.axis.description.ParameterDesc. OUT, new
javax.xml.namespace.QName ( http://bbb.dummycomp.com; , ServiceStatus
),
com.dummycomp.bbb.webservice.ServiceStatus. class , false, false);
oper.addParameter(param);
param = new org.apache.axis.description.ParameterDesc(new
Re: wsdl version
The WSDL 2.0 specification [1] became a W3C recommendation in June 2007. While WSDL 2.0 is the future it has not yet seen widespread adoption (although adoption is increasing, in part because of Axis2). For now I think your best bet is to use WSDL 1.1 and, if you'd like to future proof your app and be on the cutting edge, implement WSDL 2.0 as well. You might be interested in WSDL 1.1 - 2.0 converters. Apache Woden [2] has one in SVN that's a bit out of date. There is also one available from the W3C [3] but it too looks to be out of date. [1] http://www.w3.org/2002/ws/desc/ [2] http://incubator.apache.org/woden/ [3] http://www.w3.org/2006/02/WSDLConvert.html Lawrence Mauro Molinari [EMAIL PROTECTED] 11/20/2007 03:36 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: wsdl version Simon Steinacker ha scritto: Hello, I have a general question: Which version of WSDL (1.1/2.0) is recommended to be used? Is WSDL 2.0 already stable and applicable in a critical business applications? Thanks, Lg Simon It may depend on the level of interoperability you want to have. I might be wrong, but I think .NET 1.1 is not compatible with WSDL 2.0. -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimum Library Requirement?
There have been many such discussions on the user and dev lists. (I
started one as well [1].) There was a good discussion a few weeks ago on
the Axis dev list (for the record I'm not an Axis committer) and the
agreed outcome was that Axis2 should be repackaged into server, client,
and optional packages to help users better understand what they need. The
conversation also helped trim the fat identifying some packages that can
be removed. See [2] for a post somewhere in the middle of the
conversation.
[1] http://marc.info/?l=axis-userm=119213917321134w=2
[2] http://marc.info/?l=axis-devm=119237705617226w=2
Lawrence
Michael Bernagou [EMAIL PROTECTED]
11/20/2007 05:47 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Minimum Library Requirement?
Hi everybody,
I have a question about the libraries. I have a little number of services
using AXIOM but there so many libraries that my application is huge
compare with the little ko for the code.
In fact I develop a Client (GUI Swing application) that use axis2 to call
some services to a server.
My method is quite simple :
public static MainUser getAuthenticatedUser(String login, char[] password)
throws PapoException {
EndpointReference targetEPR = new EndpointReference(baseUrl +
CoreVariables.USER_WEBSERVICE);
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(
http://webservices.papo/xsd;, tns);
OMElement method = fac.createOMElement(getAuthenticatedUser,
omNs);
OMElement loginElement = fac.createOMElement(login, omNs);
loginElement.addChild(fac.createOMText(loginElement, login));
method.addChild(loginElement);
OMElement passwordElement = fac.createOMElement(password, omNs);
passwordElement.addChild (fac.createOMText(passwordElement, new
String(password)));
method.addChild(passwordElement);
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol (Constants.TRANSPORT_HTTP);
try {
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(method);
OMElement firstElement = result.getFirstElement();
if(firstElement.getLocalName().equals(message)) {
throw new PapoException(firstElement.getText());
}
else {
loginElement = firstElement;
login = loginElement.getText();
OMElement firstNameElement =
(OMElement)loginElement
.getNextOMSibling();
String firstName = firstNameElement.getText ();
OMElement lastNameElement =
(OMElement)firstElement.getNextOMSibling();
String lastName = lastNameElement.getText();
OMElement emailElement =
(OMElement)lastNameElement.getNextOMSibling();
String email = emailElement.getText();
MainUser user = new MainUser(login);
user.setFirstName(firstName);
user.setLastName(lastName);
user.setEmail(email);
return user;
}
}
catch (AxisFault af) {
af.printStackTrace();
throw new PapoException(The call to the service has failed
!!,
af);
}
}
What are the minimal list of library to make this run. At the moment I put
all the libraries, and try to delete one by one the jar to see what is
needed, but, I still have something like 15 jars... just for this piece of
code :(
At the server side, it is less important but still huge compare with the
code...
--
Michael Bernagou
Java Developper
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimum Library Requirement?
I think you're right about the optional repository. The key really is the
good description. I got the feeling from the axis-dev conversation that
there are very few people who understand all of Axis2's dependencies.
Lawrence
Michael Bernagou [EMAIL PROTECTED]
11/20/2007 01:01 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: Minimum Library Requirement?
Thanks!
So I just have to wait for the repackaging :)
Personnaly I would prefer 2 light packages (client and server) and a
repository for optional libs with a good description. The
axis-optional.jar will still contain many jars not needed, especially if I
just need one of them ;)
Anyway, let's wait and see!
M.
2007/11/20, Lawrence Mandel [EMAIL PROTECTED]:
There have been many such discussions on the user and dev lists. (I
started one as well [1].) There was a good discussion a few weeks ago on
the Axis dev list (for the record I'm not an Axis committer) and the
agreed outcome was that Axis2 should be repackaged into server, client,
and optional packages to help users better understand what they need. The
conversation also helped trim the fat identifying some packages that can
be removed. See [2] for a post somewhere in the middle of the
conversation.
[1] http://marc.info/?l=axis-userm=119213917321134w=2
[2] http://marc.info/?l=axis-devm=119237705617226w=2
Lawrence
Michael Bernagou [EMAIL PROTECTED]
11/20/2007 05:47 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Minimum Library Requirement?
Hi everybody,
I have a question about the libraries. I have a little number of services
using AXIOM but there so many libraries that my application is huge
compare with the little ko for the code.
In fact I develop a Client (GUI Swing application) that use axis2 to call
some services to a server.
My method is quite simple :
public static MainUser getAuthenticatedUser(String login, char[] password)
throws PapoException {
EndpointReference targetEPR = new EndpointReference(baseUrl +
CoreVariables.USER_WEBSERVICE);
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(
http://webservices.papo/xsd;, tns);
OMElement method = fac.createOMElement(getAuthenticatedUser,
omNs);
OMElement loginElement = fac.createOMElement(login, omNs);
loginElement.addChild(fac.createOMText(loginElement, login));
method.addChild(loginElement);
OMElement passwordElement = fac.createOMElement(password, omNs);
passwordElement.addChild (fac.createOMText(passwordElement, new
String(password)));
method.addChild(passwordElement);
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol (Constants.TRANSPORT_HTTP);
try {
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(method);
OMElement firstElement = result.getFirstElement();
if(firstElement.getLocalName().equals(message)) {
throw new PapoException( firstElement.getText());
}
else {
loginElement = firstElement;
login = loginElement.getText();
OMElement firstNameElement =
(OMElement)loginElement
.getNextOMSibling();
String firstName = firstNameElement.getText ();
OMElement lastNameElement =
(OMElement)firstElement.getNextOMSibling();
String lastName = lastNameElement.getText();
OMElement emailElement =
(OMElement)lastNameElement.getNextOMSibling();
String email = emailElement.getText();
MainUser user = new MainUser(login);
user.setFirstName(firstName);
user.setLastName(lastName);
user.setEmail(email);
return user;
}
}
catch (AxisFault af) {
af.printStackTrace();
throw new PapoException(The call to the service has failed
!!,
af);
}
}
What are the minimal list of library to make this run. At the moment I put
all the libraries, and try to delete one by one the jar to see what is
needed, but, I still have something like 15 jars... just for this piece of
code :(
At the server side, it is less important but still huge compare with the
code...
--
Michael Bernagou
Java Developper
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Bernagou
Java Developper
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] 2 Instances of Axis2 running by default in Axis2 WAR?
Hi David,
I just confirmed your comment with HEAD. I've been working off the latest
release (1.3) and it looks like this was fixed 9 days after that release.
Thanks,
Lawrence
David Illsley [EMAIL PROTECTED]
10/12/2007 03:54 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: [Axis2] 2 Instances of Axis2 running by default in Axis2 WAR?
Lawrence,
This isn't my area of expertise, but looking at AxisAdminServlet and
AxisServlet, it looks like the init(ServletConfig) methods
store/retrieve the first created configuration context from an
attribute on the ServletContext, so only one should be created:
Extract:
this.configContext =
(ConfigurationContext)
servletContext.getAttribute(CONFIGURATION_CONTEXT);
if(configContext == null){
configContext = initConfigContext(config);
config.getServletContext().setAttribute(CONFIGURATION_CONTEXT,
configContext);
}
Does that make sense?
David
On 11/10/2007, Lawrence Mandel [EMAIL PROTECTED] wrote:
I'm trying to understand how Axis2 is initialized. When deploying Axis2
in
a Servlet container (like Tomcat) there are two Servlets that get
invoked:
AxisServlet and AxisAdminServlet. Both of these Servlets seem to go
through the same initialization routine setting up Axis2 configurations.
In this way it appears that both Servlets contain their own instance of
Axis2 and therefore their own copies of the running services and modules
and both will probe for new services and modules. It seems to me that
Axis2 should only be configured once and this configuration should be
shared between AxisServlet and AxisAdminServlet.
Am I correct in my assessment above and if so are two instances of Axis2
created intentionally?
Thanks,
Lawrence
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Axis2 jars and dependencies
The Axis2 download includes 19 Axis2 jars and 39 third party jars. I'm trying to understand: 1. Why Axis2 has to be broken up into 19 separate jars. Can any of these be amalgamated to produce less jars? (I find it confusing that there are so many and I think most people just put them all on the classpath instead of thinking about it.) 2. Why Axis2 has so many dependencies. Are some of these dependencies optional or can they be made optional? I'd appreciate any help in understanding the requirement, even if just a pointer to an existing document that I've missed. I did find one wiki page [1] that started this discussion about a year ago but it's out of date. [1] http://wiki.apache.org/ws/FrontPage/Axis2/axis2_std_build_list Here are lists of the Axis2 jars and the third party jars. Axis2 axis2-adb-1.3.jar Used by Java2WSDL and WSDL2Java? axis2-adb-codegen-1.3.jarUsed by Java2WSDL and WSDL2Java? axis2-clustering-1.3.jar ? axis2-codegen-1.3.jar WSDL2Java? axis2-fastinfoset-1.3.jar ? axis2-java2wsdl-1.3.jar Used by the Axis2 kernel to general WSDL on the fly - Am I correct that this is also used for the standalone tool? axis2-jaxbri-1.3.jar ? axis2-jaxws-1.3.jar Used by kernel? Anything else make use of this? axis2-jaxws-api-1.3.jar Used by kernel? Anything else make use of this? axis2-jibx-1.3.jar Optional? axis2-json-1.3.jar Optional? Do I need this if I don't want JSON support? axis2-jws-api-1.3.jarJava Web Services API? Is this used by multiple tools/runtimes? axis2-kernel-1.3.jar Core Axis2 axis2-metadata-1.3.jar? axis2-mtompolicy-1.3.jar Optional? axis2-saaj-1.3.jar SOAP attachments - optional? axis2-saaj-api-1.3.jar SOAP attachments - optional? axis2-spring-1.3.jar Optional? axis2-xmlbeans-1.3.jar Optional? Third Party activation-1.1.jarMIME support annogen-0.1.0.jar Annotation support axiom-api-1.2.5.jarXML pull parsing axiom-dom-1.2.5.jar XML pull parsing axiom-impl-1.2.5.jar XML pull parsing backport-util-concurrent-2.2.jar ? commons-codec-1.3.jar URL encoding? commons-fileupload-1.1.1.jar Used for uploading new service files in the admin client? commons-httpclient-3.0.1.jar Used by the Axis2 kernel? commons-io-1.2.jar ? commons-logging-1.1.jar Is this related to Log4J? geronimo-annotation_1.0_spec-1.1.jar More annotation support? geronimo-jms_1.1_spec-1.1.jar JMS bindings? httpcore-4.0-alpha5.jarUsed by the Axis2 kernel? httpcore-nio-4.0-alpha5.jar Used by the Axis2 kernel? httpcore-niossl-4.0-alpha5.jar Used by the Axis2 kernel? jaxb-api-2.0.jar Used by the Axis2 kernel? jaxb-impl-2.0.5.jar Used by the Axis2 kernel? jaxb-xjc-2.0.5.jar Used by the Axis2 kernel? jaxen-1.1.1.jar XPath engine - where is this used? jettison-1.0-RC1.jarJSON StAX parser jibx-bind-1.1.5.jar Related to JAXB? jibx-run-1.1.5.jar Related to JAXB? juli-6.0.10.jar ? log4j-1.2.14.jar Logging - Is this optional? I don't always want to use Log4J - for example, when working with Eclipse. mail-1.4.jar MIME support? mex-impl-1.3.jar ? neethi-2.0.2.jar WS Policy - Is this optional? soapmonitor-1.3.jarIs this part of Axis2 or another project? Is this just used by the Axis2 runtime or is it just the standalone SOAP monitor tool? stax-api-1.0.1.jar XML pull parsing - I think this should be replaced in the next version with Geronimo's API as Axiom has made the change tribes-6.0.10.jar ? woden-1.0-incubating-M7b.jarWSDL 2.0 support wsdl4j-1.6.2.jar WSDL 1.1 support wstx-asl-3.2.1.jar XML pull parsing xalan-2.7.0.jar XSLT - Where is this used? xbean-2.2.0.jar Looks like a competitor to OSGi - where is this used?
[Axis2] 2 Instances of Axis2 running by default in Axis2 WAR?
I'm trying to understand how Axis2 is initialized. When deploying Axis2 in a Servlet container (like Tomcat) there are two Servlets that get invoked: AxisServlet and AxisAdminServlet. Both of these Servlets seem to go through the same initialization routine setting up Axis2 configurations. In this way it appears that both Servlets contain their own instance of Axis2 and therefore their own copies of the running services and modules and both will probe for new services and modules. It seems to me that Axis2 should only be configured once and this configuration should be shared between AxisServlet and AxisAdminServlet. Am I correct in my assessment above and if so are two instances of Axis2 created intentionally? Thanks, Lawrence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 jars and dependencies
*I cleaned up the lists below as they were difficult to read.* The Axis2 download includes 19 Axis2 jars and 39 third party jars. I'm trying to understand: 1. Why Axis2 has to be broken up into 19 separate jars. Can any of these be amalgamated to produce less jars? (I find it confusing that there are so many and I think most people just put them all on the classpath instead of thinking about it.) 2. Why Axis2 has so many dependencies. Are some of these dependencies optional or can they be made optional? I'd appreciate any help in understanding the requirement, even if just a pointer to an existing document that I've missed. I did find one wiki page [1] that started this discussion about a year ago but it's out of date. [1] http://wiki.apache.org/ws/FrontPage/Axis2/axis2_std_build_list Here are lists of the Axis2 jars and the third party jars. Axis2 axis2-adb-1.3.jarUsed by Java2WSDL and WSDL2Java? axis2-adb-codegen-1.3.jarUsed by Java2WSDL and WSDL2Java? axis2-clustering-1.3.jar ? axis2-codegen-1.3.jarWSDL2Java? axis2-fastinfoset-1.3.jar? axis2-java2wsdl-1.3.jar Used by the Axis2 kernel to general WSDL on the fly - Am I correct that this is also used for the standalone tool? axis2-jaxbri-1.3.jar ? axis2-jaxws-1.3.jar Used by kernel? Anything else make use of this? axis2-jaxws-api-1.3.jar Used by kernel? Anything else make use of this? axis2-jibx-1.3.jar Optional? axis2-json-1.3.jar Optional? Do I need this if I don't want JSON support? axis2-jws-api-1.3.jarJava Web Services API? Is this used by multiple tools/runtimes? axis2-kernel-1.3.jar Core Axis2 axis2-metadata-1.3.jar ? axis2-mtompolicy-1.3.jar Optional? axis2-saaj-1.3.jar SOAP attachments - optional? axis2-saaj-api-1.3.jar SOAP attachments - optional? axis2-spring-1.3.jar Optional? axis2-xmlbeans-1.3.jar Optional? Third Party activation-1.1.jarMIME support annogen-0.1.0.jar Annotation support axiom-api-1.2.5.jar XML pull parsing axiom-dom-1.2.5.jar XML pull parsing axiom-impl-1.2.5.jar XML pull parsing backport-util-concurrent-2.2.jar ? commons-codec-1.3.jar URL encoding? commons-fileupload-1.1.1.jar Used for uploading new service files in the admin client? commons-httpclient-3.0.1.jar Used by the Axis2 kernel? commons-io-1.2.jar? commons-logging-1.1.jar Is this related to Log4J? geronimo-annotation_1.0_spec-1.1.jar More annotation support? geronimo-jms_1.1_spec-1.1.jar JMS bindings? httpcore-4.0-alpha5.jar Used by the Axis2 kernel? httpcore-nio-4.0-alpha5.jar Used by the Axis2 kernel? httpcore-niossl-4.0-alpha5.jarUsed by the Axis2 kernel? jaxb-api-2.0.jar Used by the Axis2 kernel? jaxb-impl-2.0.5.jar Used by the Axis2 kernel? jaxb-xjc-2.0.5.jarUsed by the Axis2 kernel? jaxen-1.1.1.jar XPath engine - where is this used? jettison-1.0-RC1.jar JSON StAX parser jibx-bind-1.1.5.jar Related to JAXB? jibx-run-1.1.5.jarRelated to JAXB? juli-6.0.10.jar ? log4j-1.2.14.jar Logging - Is this optional? I don't always want to use Log4J - for example, when working with Eclipse. mail-1.4.jar MIME support? mex-impl-1.3.jar ? neethi-2.0.2.jar WS Policy - Is this optional? soapmonitor-1.3.jar Is this part of Axis2 or another project? Is this just used by the Axis2 runtime or is it just the standalone SOAP monitor tool? stax-api-1.0.1.jarXML pull parsing - I think this should be replaced in the next version with Geronimo's API as Axiom has made the change tribes-6.0.10.jar ? woden-1.0-incubating-M7b.jar WSDL 2.0 support wsdl4j-1.6.2.jar WSDL 1.1 support wstx-asl-3.2.1.jarXML pull parsing xalan-2.7.0.jar XSLT - Where is this used? xbean-2.2.0.jar Looks like a competitor to OSGi - where is this used? xercesImpl-2.8.1.jar DOM parser - Does Axis2 actually need a DOM
[Axis2] JSON service
Hi all, A few days ago I asked about some trouble I'm having getting a JSON response from an Axis2 service. (See below.) I didn't get any responses so thought I'd try a different approach. Does anyone have an example of an Axis2 service that returns JSON? Thanks, Lawrence Lawrence Mandel/Toronto/[EMAIL PROTECTED] 04/25/2007 06:23 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject [Axis2] Trouble getting JSON response I've just picked up the latest Axis2 build (from 20070425) and am having trouble getting JSON and SOAP responses from the sample Version service. Really I think the problem is I just don't understand if Axis2 can do what I'd like it to do. The online documentation and googling for an answer (which revealed an interesting doc at WSO2) hasn't resulted in an answer. I'd like to return one of the following depending on the content type specified on the request: 1. Plain XML 2. XML wrapped in a SOAP envelope 3. JSON I specified messageformatters and messagebuilders as follows: messageFormatters messageFormatter contentType=application/x-www-form-urlencoded class= org.apache.axis2.transport.http.XFormURLEncodedFormatter/ messageFormatter contentType=multipart/form-data class= org.apache.axis2.transport.http.MultipartFormDataFormatter/ messageFormatter contentType=application/xml class= org.apache.axis2.transport.http.ApplicationXMLFormatter/ messageFormatter contentType=text/javascript class=org.apache.axis2.json.JSONMessageFormatter/ /messageFormatters messageBuilders messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/x-www-form-urlencoded class=org.apache.axis2.builder.XFormURLEncodedBuilder / messageBuilder contentType=multipart/form-data class= org.apache.axis2.builder.MultipartFormDataBuilder/ messageBuilder contentType=text/javascript class=org.apache.axis2.json.JSONOMBuilder/ /messageBuilders The rest of my axis2.xml file has not been modified. When I make a request to http://localhost:8080/axis2/services/Version/getVersion I get the following response: ns:getVersionResponse xmlns:ns=http://axisversion.sample/xsd; ns:returnHello I am Axis2 version service , My version is 1.2-SNAPSHOT/ns:return /ns:getVersionResponse Good. When I change the content type in the header to text/javascript (Content-Type: text/javascript) I get the following error (formatted for readability here): type: Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.apache.axis2.json.JSONOMBuilder.processDocument(JSONOMBuilder.java:49) org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:130) org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:98) org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest(AxisServlet.java:767) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs. As for SOAP, I'm not sure what exactly I have to do to get a SOAP response. I tried setting the SOAPAction header (I read this somewhere) but that didn't help. Suggestions? Pointers to docs? Have I configured Axis2 correctly? Is this type of configuration known to work? Thanks, Lawrence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Trouble getting JSON response
I've just picked up the latest Axis2 build (from 20070425) and am having trouble getting JSON and SOAP responses from the sample Version service. Really I think the problem is I just don't understand if Axis2 can do what I'd like it to do. The online documentation and googling for an answer (which revealed an interesting doc at WSO2) hasn't resulted in an answer. I'd like to return one of the following depending on the content type specified on the request: 1. Plain XML 2. XML wrapped in a SOAP envelope 3. JSON I specified messageformatters and messagebuilders as follows: messageFormatters messageFormatter contentType=application/x-www-form-urlencoded class= org.apache.axis2.transport.http.XFormURLEncodedFormatter/ messageFormatter contentType=multipart/form-data class= org.apache.axis2.transport.http.MultipartFormDataFormatter/ messageFormatter contentType=application/xml class= org.apache.axis2.transport.http.ApplicationXMLFormatter/ messageFormatter contentType=text/javascript class=org.apache.axis2.json.JSONMessageFormatter/ /messageFormatters messageBuilders messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/x-www-form-urlencoded class=org.apache.axis2.builder.XFormURLEncodedBuilder / messageBuilder contentType=multipart/form-data class= org.apache.axis2.builder.MultipartFormDataBuilder/ messageBuilder contentType=text/javascript class=org.apache.axis2.json.JSONOMBuilder/ /messageBuilders The rest of my axis2.xml file has not been modified. When I make a request to http://localhost:8080/axis2/services/Version/getVersion I get the following response: ns:getVersionResponse xmlns:ns=http://axisversion.sample/xsd; ns:returnHello I am Axis2 version service , My version is 1.2-SNAPSHOT/ns:return /ns:getVersionResponse Good. When I change the content type in the header to text/javascript (Content-Type: text/javascript) I get the following error (formatted for readability here): type: Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.apache.axis2.json.JSONOMBuilder.processDocument(JSONOMBuilder.java:49) org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:130) org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:98) org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest(AxisServlet.java:767) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs. As for SOAP, I'm not sure what exactly I have to do to get a SOAP response. I tried setting the SOAPAction header (I read this somewhere) but that didn't help. Suggestions? Pointers to docs? Have I configured Axis2 correctly? Is this type of configuration known to work? Thanks, Lawrence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
