JBoss.NET and .NET Interop

[rajd]

Hi,

I'm working on the JBoss.NET and .NET Interop.

When I create the proxy using axis it works fine. But when I try it with
.NET wsdl command it throws up the error listed below:

Schema validation warning: SimpleType content is missing.

Warning: Schema could not be validated. Class generation may fail or may produce
incorrect results.

Error: Unable to import binding 'BusinessContactServiceSoapBinding' from namespa
ce 'http://localhost:8080/jboss-net/services/BusinessContactService'.
- Unable to import operation 'get'.
- Schema with targetNamespace='http://net.jboss.org/jmx' has invalid syntax.
- SimpleType content is missing.


The WSDL is pasted below:
<?xml version="1.0" encoding="utf-8"?>
<definitions xmlns:s1="http://net.jboss.org/jmx" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://bupa/BusinessContact" xmlns:s2="http://localhost:8080/jboss-net/services/BusinessContactService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://localhost:8080/jboss-net/services/BusinessContactService" xmlns="http://schemas.xmlsoap.org/wsdl/">

<s:schema targetNamespace="http://bupa/BusinessContact">
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<s:complexType name="BaseEntityData">
<s:sequence>
<s:element name="inErrorState" type="s:boolean" />
<s:element name="message" nillable="true" type="s:string" />
</s:sequence>
</s:complexType>
<s:complexType name="ContactData">
<s:complexContent mixed="false">
<s:extension base="s0:BaseEntityData">
<s:sequence>
<s:element name="address" nillable="true" type="s:string" />
<s:element name="contactId" type="s:int" />
<s:element name="dname" nillable="true" type="s:string" />
<s:element name="fname" nillable="true" type="s:string" />
<s:element name="lname" nillable="true" type="s:string" />
<s:element name="mname" nillable="true" type="s:string" />
<s:element name="nname" nillable="true" type="s:string" />
<s:element name="title" nillable="true" type="s:string" />
<s:element name="type" nillable="true" type="s:string" />
<s:element name="userId" type="s:int" />
</s:sequence>
</s:extension>
</s:complexContent>
</s:complexType>
</s:schema>
<s:schema targetNamespace="http://net.jboss.org/jmx">
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<s:simpleType name="ObjectNameType" />
</s:schema>
<s:schema targetNamespace="http://localhost:8080/jboss-net/services/BusinessContactService">
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<s:complexType name="ArrayOf_xsd_anyType">
<s:complexContent mixed="false">
<s:restriction base="soapenc:Array">
<s:attribute d7p1:arrayType="s:anyType[]" ref="soapenc:arrayType" xmlns:d7p1="http://schemas.xmlsoap.org/wsdl/" />
</s:restriction>
</s:complexContent>
</s:complexType>
</s:schema>


































































<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />

<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />



<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />



<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />



<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />



<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />



<soap:operation soapAction="BusinessContactService" />

<soap:body use="encoded" namespace="http://contact.appservice.web.bupa.com" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />


<soap:body use="encoded" namespace="http://localhost:8080/jboss-net/services/BusinessContactService" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />





<soap:address location="http://bupal1v8111j/jboss-net/services/BusinessContactService" />




I don't know if its because I'm using rpc binding style or JBoss.NET usage.
Any leads on this would be helpful

Cheers,
Raj

[efrinmn]

It may have to do with the fact that .NET uses document/literal wrapped style of WSDL whereas JBOSS by and large uses RPC/encoded. You may have some problems if you are taking the WSDL generated in JBOSS and attempting to use it in .NET. http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/ may help.

[rajd]

I have tried to use the Java2WSDL tool to create a WSDL for me from a very simple interface. Can't get that to work. I used the example6 of Axis1.1 for the same. No luck.
Any sample interface with a successful creation of a DOCUMENT style and WRAPPED style would do the trick.

Thanks in advance.

[takenori]

Hi,

Doc/Lit is not a problem.
Rpc/Enc works fine.

That's still a really big problem
in the near future.

Be sure to use valid data types or its arrays
(refere to axis user guide 1,5,1,1)
as parameters and return types.
And any complex types and its array
consists from valid data types.

Takenori,

[jason.greene]

This is a bug with the JMX wsdl genertor that has been fixed in cvs. If you are not exposing JMX MBeans as web services, you can work around this problem by deleting the jmx-net.wsr folder in the jboss-net.sar directory.