Re: Axis/.Net interop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Gladish wrote:
In searching the archives I found the following e-mail, but there does
not seem to be a resolution.
http://marc.theaimsgroup.com/?l=axis-userm=106917131020548w=2
http://marc.theaimsgroup.com/?l=axis-userm=106917131020548w=2
I am running into exactly the same situation. After deployment Axis
presents a WSDL which has xsd:byte[][] for a Java byte[][]. I change
the WSDL to use the type soapenc:base64Binary[], change the deployment
descriptor to reference the custom WSDL file and redeploy. At that
point a .NET client is able to pass the data into the method, but is
unable to get the return value, throwing an exception:
Top Exception: System.InvalidOperationException
Inner Exception: Cannot assign object of type System.SByte[][] to an
object of type System.Byte[][]
The Java method is simply:
public byte[][] echoStreams( byte[][] data ) { return data; }
Any help would be greatly appreciated.
Brian J. Gladish
Senior Software Engineer
Raining Data Corporation (http://www.rainingdata.com)
(949) 260-5140
Use SByte, Java uses signed bytes, .NET's byte is unsigned.
- -Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCEp6DoVKKkbjLuUcRAlunAJ9Lbfe2FoK9K9Iedx3WQHSTxa3i1gCfWnqJ
lvI2KFL/Etq4asIAdHM6lT0=
=ITSz
-END PGP SIGNATURE-
RE: Axis/.Net interop
Use SByte, Java uses signed bytes, .NET's byte is unsigned. Yes, or modify the generated .NET client-side proxy class to return a Byte[][], not SByte[][] . -Original Message- From: Jerome Gagner [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 15, 2005 8:15 PM To: [EMAIL PROTECTED] Subject: Re: Axis/.Net interop snip snip Use SByte, Java uses signed bytes, .NET's byte is unsigned. - -Jerome
RE: Axis - .Net Interop Problems
Thanks Brian. Looking through your wsdl and comparing it to mine put me in the right direction. I put together a smaller prototype where business object getters/setters return only typed arrays for 1 - m relationships. .Net wsdl.exe had no problems with the Axis generated wsdl. .Net did not like the element type, soapenc:Array, but had no problems with array types that extend soapenc:Array. John --- Brian Davis [EMAIL PROTECTED] wrote: Yes, I sure am. Here is my wsdl: ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://www.willyloman.com/webservices; ... __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250
RE: Axis - .Net Interop Problems
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 06 January 2005 23:35 To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I too am wrestling with the same issue. I've found more success with wrapped, literal services. This seems to get around the array issue. However, axis seems to still generate broken wsdl, as in .net you will need to go around replacing Unqualified encoding references to Qualified in the .net generated code. You will also need to set up a BeanMapping element for each of your complex types in Axis. At least, that's where I'm heading right now. I don't really know what I'm doing here, just blindly stumbling around trying to find something that works. I'd post my config, but I can't get access to it right now (its at home). This is with Whidbey .net wsdl. Does that help any? James
RE: Axis - .Net Interop Problems
Thanks for the reply. What version Axis are your working with? I understand doc literal is the way to go but I was also under the impression that some people had this working with soap rpc encoding. My goal is to get this working with as little effort as possible. That's why I started with soap rpc encoding. --- James Richardson [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 06 January 2005 23:35 To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I too am wrestling with the same issue. I've found more success with wrapped, literal services. This seems to get around the array issue. However, axis seems to still generate broken wsdl, as in .net you will need to go around replacing Unqualified encoding references to Qualified in the .net generated code. You will also need to set up a BeanMapping element for each of your complex types in Axis. At least, that's where I'm heading right now. I don't really know what I'm doing here, just blindly stumbling around trying to find something that works. I'd post my config, but I can't get access to it right now (its at home). This is with Whidbey .net wsdl. Does that help any? James __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
RE: Axis - .Net Interop Problems
What tool are you using in .Net? I use the command line tool wsdl.exe and it seems to work flawlessly with WSDL generated by Axis. Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 6:35 PM To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I've searched all over the web and found a number of threads indicating the same problem but I haven't seen any definitive solutions to this problem. I looked through postings for Axis 1.2 RC2 and it looks like 1.2 has new and different issues with the same interop scenario. But, some people say they've been able to get this to work in Axis 1.1. How, remains a mystery to me. The source of the problem for .NET appears to be the type, soapenc:Array. Does anyone have a working solution? I've included the .Net wsdl output and Axis wsdl below for reference. .Net wsdl output: = D:\TOSPrototype\SimpleWSClientwsdl http://localhost:8080/jboss-net/services/AgentService?wsdl Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: SimpleType content is missing. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://security.twia.org' is not available to be referenced in this schema. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AgentServiceSoapBinding' from namespace 'http://localhost:8080/jboss-net/services/Agent Service'. - Unable to import operation 'getAgentOfRecordVO'. - The datatype 'Array' is missing. If you would like more help, please type wsdl /?. Axis generated wsdl: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions targetNamespace=http://localhost:8080/jboss-net/services/AgentService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://localhost:8080/jboss-net/services/AgentService; xmlns:intf=http://localhost:8080/jboss-net/services/AgentService; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://contact.twia.org; xmlns:tns2=http://util.twia.org; xmlns:tns3=http://security.twia.org; xmlns:tns4=http://net.jboss.org/jmx; xmlns:tns5=http://agent.twia.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; wsdl:types schema targetNamespace=http://util.twia.org; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://schemas.xmlsoap.org/soap/encoding/; / complexType abstract=true name=TWIAObject sequence element name=key nillable=true type=xsd:anyType / element name=keyAsString nillable=true type=xsd:string / /sequence /complexType complexType abstract=true name=ValueObjectBase sequence element
RE: Axis - .Net Interop Problems
What tool are you using in .Net? I use the command line tool wsdl.exe and it seems to work flawlessly with WSDL generated by Axis. Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 6:35 PM To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I've searched all over the web and found a number of threads indicating the same problem but I haven't seen any definitive solutions to this problem. I looked through postings for Axis 1.2 RC2 and it looks like 1.2 has new and different issues with the same interop scenario. But, some people say they've been able to get this to work in Axis 1.1. How, remains a mystery to me. The source of the problem for .NET appears to be the type, soapenc:Array. Does anyone have a working solution? I've included the .Net wsdl output and Axis wsdl below for reference. .Net wsdl output: = D:\TOSPrototype\SimpleWSClientwsdl http://localhost:8080/jboss-net/services/AgentService?wsdl Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: SimpleType content is missing. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://security.twia.org' is not available to be referenced in this schema. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AgentServiceSoapBinding' from namespace 'http://localhost:8080/jboss-net/services/Agent Service'. - Unable to import operation 'getAgentOfRecordVO'. - The datatype 'Array' is missing. If you would like more help, please type wsdl /?. Axis generated wsdl: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions targetNamespace=http://localhost:8080/jboss-net/services/AgentService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://localhost:8080/jboss-net/services/AgentService; xmlns:intf=http://localhost:8080/jboss-net/services/AgentService; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://contact.twia.org; xmlns:tns2=http://util.twia.org; xmlns:tns3=http://security.twia.org; xmlns:tns4=http://net.jboss.org/jmx; xmlns:tns5=http://agent.twia.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; wsdl:types schema targetNamespace=http://util.twia.org; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://schemas.xmlsoap.org/soap/encoding/; / complexType abstract=true name=TWIAObject sequence element name=key nillable=true type=xsd:anyType / element name=keyAsString nillable=true type=xsd:string / /sequence /complexType complexType abstract=true name=ValueObjectBase sequence element
RE: Axis - .Net Interop Problems
I am using the same tool, wsdl.exe, from .Net 1.1. Do you have complex array types and are you using soap rpc encoding with Axis 1.1? --- Brian Davis [EMAIL PROTECTED] wrote: What tool are you using in .Net? I use the command line tool wsdl.exe and it seems to work flawlessly with WSDL generated by Axis. Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 6:35 PM To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I've searched all over the web and found a number of threads indicating the same problem but I haven't seen any definitive solutions to this problem. I looked through postings for Axis 1.2 RC2 and it looks like 1.2 has new and different issues with the same interop scenario. But, some people say they've been able to get this to work in Axis 1.1. How, remains a mystery to me. The source of the problem for .NET appears to be the type, soapenc:Array. Does anyone have a working solution? I've included the .Net wsdl output and Axis wsdl below for reference. .Net wsdl output: = D:\TOSPrototype\SimpleWSClientwsdl http://localhost:8080/jboss-net/services/AgentService?wsdl Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: SimpleType content is missing. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://security.twia.org' is not available to be referenced in this schema. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AgentServiceSoapBinding' from namespace 'http://localhost:8080/jboss-net/services/Agent Service'. - Unable to import operation 'getAgentOfRecordVO'. - The datatype 'Array' is missing. If you would like more help, please type wsdl /?. Axis generated wsdl: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions targetNamespace=http://localhost:8080/jboss-net/services/AgentService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://localhost:8080/jboss-net/services/AgentService; xmlns:intf=http://localhost:8080/jboss-net/services/AgentService; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://contact.twia.org; xmlns:tns2=http://util.twia.org; xmlns:tns3=http://security.twia.org; xmlns:tns4=http://net.jboss.org/jmx; xmlns:tns5=http://agent.twia.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; wsdl:types schema targetNamespace=http://util.twia.org; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://schemas.xmlsoap.org/soap/encoding/; / complexType abstract=true name=TWIAObject sequence element name=key nillable=true type=xsd:anyType /
RE: Axis - .Net Interop Problems
/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ContactExchangeService wsdl:port name=ContactExchange binding=impl:ContactExchangeSoapBinding wsdlsoap:address location=http://localhost:8080/wl/services/ContactExchange/ /wsdl:port /wsdl:service /wsdl:definitions Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 1:09 PM To: [EMAIL PROTECTED] Subject: RE: Axis - .Net Interop Problems I am using the same tool, wsdl.exe, from .Net 1.1. Do you have complex array types and are you using soap rpc encoding with Axis 1.1? --- Brian Davis [EMAIL PROTECTED] wrote: What tool are you using in .Net? I use the command line tool wsdl.exe and it seems to work flawlessly with WSDL generated by Axis. Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 6:35 PM To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I've searched all over the web and found a number of threads indicating the same problem but I haven't seen any definitive solutions to this problem. I looked through postings for Axis 1.2 RC2 and it looks like 1.2 has new and different issues with the same interop scenario. But, some people say they've been able to get this to work in Axis 1.1. How, remains a mystery to me. The source of the problem for .NET appears to be the type, soapenc:Array. Does anyone have a working solution? I've included the .Net wsdl output and Axis wsdl below for reference. .Net wsdl output: = D:\TOSPrototype\SimpleWSClientwsdl http://localhost:8080/jboss-net/services/AgentService?wsdl Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: SimpleType content is missing. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://security.twia.org' is not available to be referenced in this schema. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AgentServiceSoapBinding' from namespace 'http://localhost:8080/jboss-net/services/Agent Service'. - Unable to import operation 'getAgentOfRecordVO'. - The datatype 'Array' is missing. If you would like more help, please type wsdl /?. Axis generated wsdl: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions targetNamespace=http://localhost:8080/jboss-net/services/AgentService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://localhost:8080/jboss-net/services/AgentService; xmlns:intf=http://localhost:8080/jboss-net/services/AgentService; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://contact.twia.org; xmlns:tns2=http://util.twia.org; xmlns:tns3=http://security.twia.org; xmlns:tns4=http://net.jboss.org/jmx; xmlns:tns5=http://agent.twia.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl
RE: Axis - .Net Interop Problems
/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ContactExchangeService wsdl:port name=ContactExchange binding=impl:ContactExchangeSoapBinding wsdlsoap:address location=http://localhost:8080/wl/services/ContactExchange/ /wsdl:port /wsdl:service /wsdl:definitions Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 1:09 PM To: [EMAIL PROTECTED] Subject: RE: Axis - .Net Interop Problems I am using the same tool, wsdl.exe, from .Net 1.1. Do you have complex array types and are you using soap rpc encoding with Axis 1.1? --- Brian Davis [EMAIL PROTECTED] wrote: What tool are you using in .Net? I use the command line tool wsdl.exe and it seems to work flawlessly with WSDL generated by Axis. Brian Davis Software Developer JMM Ventures -Original Message- From: John Deviney [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 6:35 PM To: [EMAIL PROTECTED] Subject: Axis - .Net Interop Problems Problem: The .Net 1.1 wsdl tool does not like the wsdl generated by Axis 1.1. The datatype 'Array' is missing. Environment: Jboss 3.2.3/Axis 1.1 - .NET 1.1 Hosting services via Axis SOAP RPC Encoding which include complex types and arrays of other complex types. I've searched all over the web and found a number of threads indicating the same problem but I haven't seen any definitive solutions to this problem. I looked through postings for Axis 1.2 RC2 and it looks like 1.2 has new and different issues with the same interop scenario. But, some people say they've been able to get this to work in Axis 1.1. How, remains a mystery to me. The source of the problem for .NET appears to be the type, soapenc:Array. Does anyone have a working solution? I've included the .Net wsdl output and Axis wsdl below for reference. .Net wsdl output: = D:\TOSPrototype\SimpleWSClientwsdl http://localhost:8080/jboss-net/services/AgentService?wsdl Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://localhost:8080/jboss-net/services/AgentService' is not available to be refe renced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://contact.twia.org' is not available to be referenced in this schema. Schema validation warning: SimpleType content is missing. Schema validation warning: Namespace 'http://util.twia.org' is not available to be referenced in this schema. Schema validation warning: Namespace 'http://security.twia.org' is not available to be referenced in this schema. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AgentServiceSoapBinding' from namespace 'http://localhost:8080/jboss-net/services/Agent Service'. - Unable to import operation 'getAgentOfRecordVO'. - The datatype 'Array' is missing. If you would like more help, please type wsdl /?. Axis generated wsdl: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions targetNamespace=http://localhost:8080/jboss-net/services/AgentService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://localhost:8080/jboss-net/services/AgentService; xmlns:intf=http://localhost:8080/jboss-net/services/AgentService; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://contact.twia.org; xmlns:tns2=http://util.twia.org; xmlns:tns3=http://security.twia.org; xmlns:tns4=http://net.jboss.org/jmx; xmlns:tns5=http://agent.twia.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl
Re: Axis - .Net Interop Problems
Brian, In XML Schema, in order to reference an element or type from another schema, you must first import the namespace into the schema. You need to add the following import statement to the second schema: import namespace=http://valueobject.util.app.willyloman.com/ And this import statement to the third schema: import namespace=http://objects.webservice.willyloman.com/ Regards, Anne
RE: Axis - .Net Interop Problems
Thanks. I'm not too sure why Java2WSDL doesn't do that. Well, honestly I'm not sure why it tries to make them have those namespaces at all...I would prefer that they all have the same namespace. Brian Davis Software Developer JMM Ventures -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 5:36 PM To: [EMAIL PROTECTED] Subject: Re: Axis - .Net Interop Problems Brian, In XML Schema, in order to reference an element or type from another schema, you must first import the namespace into the schema. You need to add the following import statement to the second schema: import namespace=http://valueobject.util.app.willyloman.com/ And this import statement to the third schema: import namespace=http://objects.webservice.willyloman.com/ Regards, Anne
RE: Axis - .Net Interop Problems
Thanks. I'm not too sure why Java2WSDL doesn't do that. Well, honestly I'm not sure why it tries to make them have those namespaces at all...I would prefer that they all have the same namespace. Brian Davis Software Developer JMM Ventures -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 5:36 PM To: [EMAIL PROTECTED] Subject: Re: Axis - .Net Interop Problems Brian, In XML Schema, in order to reference an element or type from another schema, you must first import the namespace into the schema. You need to add the following import statement to the second schema: import namespace=http://valueobject.util.app.willyloman.com/ And this import statement to the third schema: import namespace=http://objects.webservice.willyloman.com/ Regards, Anne
RE: Axis/.Net interop
/ s:element name=multipleByteValues type=s:base64Binary / s:element name=multipleDateValues nillable=true type=s1:ArrayOf_xsd_dateTime / s:element name=multipleDoubleValues nillable=true type=s1:ArrayOf_xsd_double / s:element name=multipleFloatValues nillable=true type=s1:ArrayOf_xsd_float / s:element name=multipleIntValues nillable=true type=s1:ArrayOf_xsd_int / s:element name=multipleLongValues nillable=true type=s1:ArrayOf_xsd_long / s:element name=multipleStringValues nillable=true type=s1:ArrayOf_xsd_string / s:element name=multipleValueAttributeDefinition nillable=true type=s2:MultipleValueAttributeDefinition / /s:sequence /s:extension /s:complexContent /s:complexType s:complexType name=MultipleValueAttributeSet s:sequence s:element name=multipleValueAttributes nillable=true type=s1:ArrayOf_tns1_MultipleValueAttribute / /s:sequence /s:complexType s:complexType name=MultipleValueAttributeDefinitionSet s:sequence s:element name=multipleValueAttributeDefinitions nillable=true type=s1:ArrayOf_tns1_MultipleValueAttributeDefinition / /s:sequence /s:complexType /s:schema s:schema targetNamespace=urn:usermanagement.service.framework.webservices.cleverpath.ca.com s:import namespace=http://schemas.xmlsoap.org/soap/encoding/; / s:complexType name=QueryFilter s:sequence s:element name=ascending type=s:boolean / s:element name=constraints nillable=true type=s1:ArrayOf_tns2_WSAttribute / s:element name=resultSetProperties nillable=true type=s1:ArrayOf_xsd_string / s:element name=sortAttributeIDs nillable=true type=s1:ArrayOf_xsd_string / /s:sequence /s:complexType s:complexType name=GroupResultSet s:sequence s:element name=ID nillable=true type=s:string / s:element name=count type=s:int / s:element name=query nillable=true type=s0:Query / s:element name=queryFilter nillable=true type=s3:QueryFilter / /s:sequence /s:complexType s:complexType name=GroupReference s:sequence s:element name=groupAccessKey nillable=true type=s:string / s:element name=serviceReference nillable=true type=s:string / /s:sequence /s:complexType s:complexType name=Group s:sequence s:element name=ID nillable=true type=s3:GroupReference / s:element name=attributeSet nillable=true type=s2:MultipleValueAttributeSet / s:element name=displayName nillable=true type=s:string / /s:sequence /s:complexType s:complexType name=Capability s:sequence s:element name=entityNameCaseSensitive type=s:boolean / s:element name=groupManagerReadOnly type=s:boolean / s:element name=groupMembershipLimit type=s:int / s:element name=membershipManagerReadOnly type=s:boolean / s:element name=supportedGroupContent type=s:int / s:element name=supportsGroupsWithMultipleParents type=s:boolean / s:element name=supportsLightWeightResultSets type=s:boolean / s:element name=supportsOrderedResultSets type=s:boolean / s:element name=userManagerReadOnly type=s:boolean / /s:sequence /s:complexType /s:schema s:schema targetNamespace=http://common.framework.webservices.cleverpath.ca.com; s:import namespace=http://schemas.xmlsoap.org/soap/encoding/; / s:complexType name=WSException s:sequence s:element name=driverID nillable=true type=s:string / s:element name=errorNumber nillable=true type=s:string / s:element name=instanceID nillable=true type=s:string / s:element name=message nillable=true type=s:string / s:element name=serviceID nillable=true type=s:string / s:element name=serviceReference nillable=true type=s:string / s:element name=sessionID nillable=true type=s:string / s:element name=userAccessKey nillable=true type=s:string / /s:sequence /s:complexType /s:schema /types -Original Message- From: chris [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 9:18 PM To: [EMAIL PROTECTED] Subject: RE: Axis/.Net interop Mikhail -I'd definitely expect a Java byte to be converted into an xsd:byte that would then be converted into a .NET System.SByte. A byte is defined in XML schema as: 3.3.19 byte [Definition:] byte is .derived. from short by setting the value of .maxInclusive. to be 127 and .minInclusive. to be -128. The .base type. of byte is short. http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#byte A SByte is defined in .NET as: sbyte -128 to 127 Signed 8-bit integer System http://msdn.microsoft.com/library/default.asp?url=/library/en-us
RE: Axis/.Net interop
Mikhail -I'd definitely expect a Java byte to be converted into an xsd:byte that would then be converted into a .NET System.SByte. A byte is defined in XML schema as: 3.3.19 byte [Definition:] byte is .derived. from short by setting the value of .maxInclusive. to be 127 and .minInclusive. to be -128. The .base type. of byte is short. http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#byte A SByte is defined in .NET as: sbyte -128 to 127 Signed 8-bit integer System http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csref/h tml/vclrfsbyte.asp Therefore, it seems that the conversion of an xsd:byte[][] defined in a WSDL document into a System.SByte[][] is correct. Or maybe I'm missing something about the Java-WSDL-.NET conversion that you are attempting. If you post the bean, wsdl, and C# code, it may help debug the issue. /Chris -Original Message- From: Mikhail Melamud [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 2:32 PM To: [EMAIL PROTECTED] Subject: Axis/.Net interop For the the Java bean having property defined as: private byte[][] multipleByteArrayValues; Axis 1.1 Java2WSDL generates descriptor as follows: complexType name=ArrayOf_xsd_base64Binary complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=xsd:byte[][] / /restriction /complexContent /complexType As I understand this is OK as far as WSDL 1.1 and SOAP 1.1 concerned for rpc/soap encoded web service MS .Net Visual Studio stub generator responds with System.SByte[] to such type definition in wsdl, where the SByte value type represents integers with values ranging from negative 128 to positive 127, which is not exactly what I'd expect. Changing the wsdl to complexType name=ArrayOf_xsd_base64Binary complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=s:base64Binary[] / /restriction /complexContent /complexType where xmlns:s=http://www.w3.org/2001/XMLSchema; produces expected definition in c# stub: System.Byte[][] Has anyone seen this behavior and is there a way to affect Axis's java2Wsdl to generate base64Binary[]as an arraytype or .Net to understand byte[][] and generate proper stub. Thanks Mike __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
