Response doesn't match with WSDL . RPC not supported ?

[sudhirkd]

Experts,



We are having very basic problem . Are we doing anything wrong ?



Problem 1:



Ideally we want document style web service. We have created it but response is different than what we expect.



wsdl shows:

<xsd:complexType>

<xsd:sequence>

<xsd:element name="authenticateUserReturn" type="xsd:boolean"/>

</xsd:sequence>

</xsd:complexType>



But response,



<res:authenticateUserResponse xmlns:res="http://soapenc/">

<return>true</return>

</res:authenticateUserResponse>



We tried Java and .NET client generated from this wsdl , it returns null because there is an extra "return" element here ( we believe) . Any clue ? workaround ?



Problem 2:



This is serious than above. To avoid above issue, we changed the style to RPC in the model, WSDL still shows document style (schema/types )etc. I deleted the target directory to make sure it is recreating .



we are using andromda 3.2, axis2. we are only having one service .



Your help is greatly appreciated.

[sudhirkd]

Hi Experts - Any advice ? - Thanks.

[kaeobdetzh]

Sudhirkd,

did you find a solution or workaround to the "return" problem?

I'm seeing the very same problem

-Max

[chad.brandon]

The latest webservice cartridge in CVS (3.3-SNAPSHOT), has a fix for this. Axis2 by default creates messages that don't adhere to the WSDL, so I extended and modified their RPCMessageReceiver (that receives and creates the soap messages) to do that.

[sudhirkd]

Thanks. We had switched to XFire because of this problem. But since Axis2 is still better and next generation, we would try the new fix.



Thank you very Chad for letting us know .



Sudhir

[sudhirkd]

Hi Chad,

Did it mean that both the problems have been fixed mentioned in the beginning. ?

Sudhir

[chad.brandon]

Hi Sudhir,



The style of webservice that its supported with is wrapped (document/literal).

[sudhirkd]

Thanks for the reply, But I was talking about Problem 2 mentioned in the first post. If style in model is changed, no changes on generated code ( we had tried to change from document to RPC style )..



Thanks

[chad.brandon]

My point is that if you want to use RPC you'll have to just deal with whatever axis2 generates (wrapped style is WS-I compliant).

[kaeobdetzh]

I redid my example using the 3.3-SNAPSHOT branch. My example model builds fine, but when I do a request I see a java.lang.NoClassDefFoundError. I was unable so far to figure out which class could be missing.

Code: Select all

SEVERE: StandardWrapper.Throwable
java.lang.NoClassDefFoundError
        at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:555)
        at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:93)
        at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:76)
        at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:640)
        at org.apache.axis2.deployment.WarBasedAxisConfigurator.<init>(WarBasedAxisConfigurator.java:136)
        at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486)
        at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:133)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
        at java.lang.Thread.run(Thread.java:595)
...


My projects webapps/testproject-web-1.0-SNAPSHOT/WEB-INF/lib contains:

Code: Select all

XmlSchema-1.3.1.jar
activation-1.1.jar
activeio-core-3.0.0-incubator.jar
activemq-core-4.1.1.jar
andromda-core-3.3-SNAPSHOT.jar
andromda-metafacades-uml-3.3-SNAPSHOT.jar
andromda-ocl-translation-core-3.3-SNAPSHOT.jar
andromda-ocl-validation-library-3.3-SNAPSHOT.jar
andromda-utils-3.3-SNAPSHOT.jar
annogen-0.1.0.jar
antlr-2.7.6.jar
aopalliance-1.0.jar
asm-1.5.3.jar
asm-attrs-1.5.3.jar
axiom-api-1.2.4.jar
axiom-dom-1.2.4.jar
axiom-impl-1.2.4.jar
axis2-1.2.jar
backport-util-concurrent-2.2.jar
cglib-2.1_3.jar
commons-beanutils-1.7.0.jar
commons-codec-1.3.jar
commons-collections-3.1.jar
commons-digester-1.7.jar
commons-fileupload-1.1.1.jar
commons-httpclient-3.0.1.jar
commons-io-1.1.jar
commons-lang-2.3.jar
commons-logging-1.0.4.jar
commons-pool-1.3.jar
dom4j-1.6.1.jar
ehcache-1.2.3.jar
geronimo-j2ee-management_1.0_spec-1.0.jar
geronimo-jms_1.1_spec-1.0.jar
hibernate-3.2.2.ga.jar
jakarta-httpcore-4.0-alpha4.jar
jaxen-1.1-beta-9.jar
jboss-j2ee-3.2.3.jar
mail-1.4.jar
neethi-2.0.1.jar
spring-2.0.4.jar
stax-api-1.0.1.jar
testproject-common-1.0-SNAPSHOT.jar
testproject-core-1.0-SNAPSHOT.jar
woden-1.0-incubating-M7a.jar
wsdl4j-1.6.2.jar
xercesImpl-2.6.2.jar


-Max

[kaeobdetzh]

After copying these Jars from my webapps/axis2/WEB-INF/lib into

testproject-web-1.0-SNAPSHOT/WEB-INF/lib, the testproject finally

works, i.e. an Axis2-generated client can access the service.

Code: Select all

axis2-adb-1.2.jar
axis2-adb-codegen-1.2.jar
axis2-codegen-1.2.jar
axis2-fastinfoset-1.2.jar
axis2-java2wsdl-1.2.jar
axis2-jaxbri-1.2.jar
axis2-jaxws-1.2.jar
axis2-jaxws-api-1.2.jar
axis2-jibx-1.2.jar
axis2-json-1.2.jar
axis2-kernel-1.2.jar
axis2-metadata-1.2.jar
axis2-saaj-1.2.jar
axis2-saaj-api-1.2.jar
axis2-soapmonitor-1.2.jar
axis2-spring-1.2.jar
axis2-tools-1.2.jar
axis2-xmlbeans-1.2.jar
commons-io-1.2.jar
commons-logging-1.1.jar
geronimo-spec-jms-1.1-rc4.jar
jaxb-api-2.0.2.jar
jaxb-impl-2.0.2.jar
jaxb-xjc-2.0.2.jar
jaxen-1.1-beta-10.jar
jettison-1.0-RC1.jar
jibx-bind-1.1.4.jar
jibx-run-1.1.4.jar
stax-utils-20060915.jar
wstx-asl-3.2.1.jar
xalan-2.7.0.jar
xbean-2.2.0.jar
xercesImpl-2.8.1.jar


-Max

[dbendlin]

Which would be the best way to include all these jars as dependencies in the main pom.xml and in the web pom.xml?



Is there another way to tell maven to include all these jars?

[kaeobdetzh]

After looking closer into which Jars were missing, it turned out that only

wstx-asl-3.2.1.jar was missing. I added the following dependencies:



$PRJ/pom.xml

Code: Select all

<dependency>
    <groupId>woodstox</groupId>
    <artifactId>wstx-asl</artifactId>
    <version>3.2.1</version>
</dependency>


$PRJ/core/pom.xml

Code: Select all

<dependency>
    <groupId>woodstox</groupId>
    <artifactId>wstx-asl</artifactId>
</dependency>


-Max