Re: Oracle V2 parser doesn't like unqualfied 'fault' elements
This error is thrown by the soap client libraries, not the Oracle JAXP implementation. If this is indeed the XML returned by the server: SOAP-ENV:Fault faultcodeSOAP-ENV:Server/faultcode faultstringservice 'urn:test:echo2' unknown/faultstring faultactor/winxml/rpcrouter/faultactor /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope Then this is not parseable because is uses the SOAP-ENV namespace *prefix* without including a matching xmlns:SOAP-ENV=... namespace declaration. I doubt any (XML 1.0 + Namespaces) parser would parse this. __ Steve Muench - Developer, Product Mgr, Evangelist, Author Simplify J2EE and EJB Development with BC4J http://otn.oracle.com/products/jdev/htdocs/j2ee_bc4j.html Building Oracle XML Apps, www.oreilly.com/catalog/orxmlapp - Original Message - From: Robert Quinn [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 00:43 Subject: Oracle V2 parser doesn't like unqualfied 'fault' elements | i'm using the V2 beta which is jaxp compliant. but it | complains about that the faultcode element is not | qualified with a namespace. | | has any one ecountered this before? i saw a reference | in the archive regarding similiar probelm with xerces | 1.3.1, but solution was use a different version of | xerces. (i wish i had that option) | | worst case i'll can update the code to output | qualified names but i hate to do that. (testing, | interop, etc.) | | is it valid xml to have unqualifed name mixed in when | using namespaces? | | thanks for any help | | ** soap message from server | | SOAP-ENV:Fault | faultcodeSOAP-ENV:Server/faultcode | faultstringservice 'urn:test:echo2' | unknown/faultstring | faultactor/winxml/rpcrouter/faultactor | /SOAP-ENV:Fault | /SOAP-ENV:Body | /SOAP-ENV:Envelope | | *** Original Messages | | SOAPException= SOAP-ENV:Client, A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | | | [SOAPException: faultCode=SOAP-ENV:Client; msg=A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element.; | targetException=java.lang.IllegalArgumentException: A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element.] | | | at org.apache.soap.rpc.Call.invoke(Call.java:246) | at | test.client.EchoClient.invokeEchoString(EchoClient.java:200) | at test.client.EchoClient.main(EchoClient.java:25) | Root Cause = A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | java.lang.IllegalArgumentException: A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | at org.apache.soap.Fault.unmarshall(Fault.java:331) | at | org.apache.soap.rpc.RPCMessage.unmarshall(RPCMessage.java:363) | at | org.apache.soap.rpc.RPCMessage.extractFromEnvelope(RPCMessage.java:197) | at | org.apache.soap.rpc.Response.extractFromEnvelope(Response.java:142) | at org.apache.soap.rpc.Call.invoke(Call.java:233) | at | test.client.EchoClient.invokeEchoString(EchoClient.java:200) | at test.client.EchoClient.main(EchoClient.java:25) | | __ | Do You Yahoo!? | Try FREE Yahoo! Mail - the world's greatest free email! | http://mail.yahoo.com/ |
AW: Server Event Notification To Clients
Title: RE: Server Event Notification To Clients Well, I think that's one ofthe points JMS can't do. We are using it in a local network. That'swhySOAP is better. -Ursprüngliche Nachricht-Von: Tony Jeffery [mailto:[EMAIL PROTECTED]]Gesendet: Dienstag, 5. März 2002 16:41An: '[EMAIL PROTECTED]'Betreff: RE: Server Event Notification To Clients Do some of your VB clients access the server through a firewall and if so does JMS still work? -Original Message-From: Harnish, Michael [mailto:[EMAIL PROTECTED]]Sent: 05 March 2002 14:13To: '[EMAIL PROTECTED]'Subject: RE: Server Event Notification To Clients Does Oracle propagate asynchronous messages to the VB client, or does the VB client have to poll the server? -Original Message-From: Beer, Christian [mailto:[EMAIL PROTECTED]]Sent: Tuesday, March 05, 2002 9:08 AMTo: '[EMAIL PROTECTED]'Subject: AW: Server Event Notification To Clients We are using an ORACLE implementation of JMS and it works finest from VB! -Ursprüngliche Nachricht-Von: Tony Jeffery [mailto:[EMAIL PROTECTED]]Gesendet: Dienstag, 5. März 2002 15:05An: '[EMAIL PROTECTED]'Betreff: RE: Server Event Notification To Clients Is this just for Java implementations, in other words can only java clients use this? We will be using VB and C++ clients in the future, running off a java server. -Original Message- From: Harnish, Michael [mailto:[EMAIL PROTECTED]] Sent: 05 March 2002 14:04 To: '[EMAIL PROTECTED]' Subject: RE: Server Event Notification To Clients Have you looked at JMS? -Original Message- From: Tony Jeffery [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 6:42 AM To: '[EMAIL PROTECTED]' Subject: Server Event Notification To Clients Hi all, Can anyone tell me the best way of implementing an event callback from the server to the client, similar to Java RMI callbacks, so that I can notify clients of server events? Would this mean a small SOAP server in the client or is there some other way or am I asking the impossible? I don't want to have to resort to polling the server for updates. Also if this is possible how feasible would it be with many thousands of users connected concurrently to the server/s and notifing them all this way? Any ideas would be very much appreciated. many thanks in advance Tony Jeffery
RE: Soap client threads
Title: Soap client threads Each client thread should create a new instance of the client side SOAPobject...you should have no problems here... (Make sure that you are not using the same SOAP object across threads...that would cause synchronization problems). Java does allow you to have multiple sockets open on multiple threads...(How many depends on how much memory and the OS) -Original Message-From: Beer, Christian [mailto:[EMAIL PROTECTED]]Sent: 06 March 2002 09:43To: '[EMAIL PROTECTED]'Subject: AW: Soap client threads I think for the SOAP toolkit that's no problem. But does Java allow many sockets open from many threads? -Ursprüngliche Nachricht-Von: Michael Weir (Transform Research) [mailto:[EMAIL PROTECTED]]Gesendet: Dienstag, 5. März 2002 22:04An: '[EMAIL PROTECTED]'Betreff: Soap client threads Does the Apache SOAP toolkit allow many client-side threads to concurrently send SOAP messages? I'm trying to build a stress-tester for a server, and want to bash it as hard as possible. Thanks, Michael Weir This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
Re: AW: Soap client threads
I think for the SOAP toolkit that's no problem. But does Java allow many sockets open from many threads? YES.
Re: weblogic6.1 and soap2.2
Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before weblogic.jar in server's classpath.(See attached file: patchCR058220.jar) regards, Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: weblogic6.1 and soap2.2 03/06/2002 02:58 PM Please respond to soap-user I'm trying to deploy a soap2.2 web service on weblogic 6.1, I have soap2.2 as a war file and I can see the jsp's for the admin and I can deploy a web service just fine, but when I try to hit it with a client I get the following null pointer exception error: java.lang.NullPointerException at weblogic.servlet.internal.ChunkOutput.clearBuffer (ChunkOutput.java:231) at weblogic.servlet.internal.ChunkOutput.flush(Chunk Output.java:251) at weblogic.servlet.internal.ChunkOutputWrapper.flus h(ChunkOutputWrapper.java:152) at weblogic.servlet.internal.ServletOutputStreamImpl .flush(ServletOutputStreamImpl.java:119) at org.apache.soap.transport.TransportMessage.writeT o(TransportMessage.java:462) at org.apache.soap.server.http.RPCRouterServlet.doPo st(RPCRouterServlet.java:347) .. .. Now, I checked the mail-archive to see if others have run into the problem, and it seems that they have, but I was not able to find a resolution. Is there one? and if there is what is it? -thanks Gus -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986 patchCR058220.jar Description: Binary data
Re: weblogic6.1 and soap2.2
Ruben, thanks, it work. where can I find some info on this patch? -Gus On Wed, 2002-03-06 at 07:59, [EMAIL PROTECTED] wrote: Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before weblogic.jar in server's classpath.(See attached file: patchCR058220.jar) regards, Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: weblogic6.1 and soap2.2 03/06/2002 02:58 PM Please respond to soap-user I'm trying to deploy a soap2.2 web service on weblogic 6.1, I have soap2.2 as a war file and I can see the jsp's for the admin and I can deploy a web service just fine, but when I try to hit it with a client I get the following null pointer exception error: java.lang.NullPointerException at weblogic.servlet.internal.ChunkOutput.clearBuffer (ChunkOutput.java:231) at weblogic.servlet.internal.ChunkOutput.flush(Chunk Output.java:251) at weblogic.servlet.internal.ChunkOutputWrapper.flus h(ChunkOutputWrapper.java:152) at weblogic.servlet.internal.ServletOutputStreamImpl .flush(ServletOutputStreamImpl.java:119) at org.apache.soap.transport.TransportMessage.writeT o(TransportMessage.java:462) at org.apache.soap.server.http.RPCRouterServlet.doPo st(RPCRouterServlet.java:347) .. .. Now, I checked the mail-archive to see if others have run into the problem, and it seems that they have, but I was not able to find a resolution. Is there one? and if there is what is it? -thanks Gus -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986 -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986
Re: weblogic6.1 and soap2.2
Hi Gus, no idea, I tried to find the Patch from Bea support for a long time but I get no response, just know that it works and I think they solved the problem in sp2. Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: Re: weblogic6.1 and soap2.2 03/06/2002 04:01 PM Please respond to soap-user Ruben, thanks, it work. where can I find some info on this patch? -Gus On Wed, 2002-03-06 at 07:59, [EMAIL PROTECTED] wrote: Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before weblogic.jar in server's classpath.(See attached file: patchCR058220.jar) regards, Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: weblogic6.1 and soap2.2 03/06/2002 02:58 PM Please respond to soap-user I'm trying to deploy a soap2.2 web service on weblogic 6.1, I have soap2.2 as a war file and I can see the jsp's for the admin and I can deploy a web service just fine, but when I try to hit it with a client I get the following null pointer exception error: java.lang.NullPointerException at weblogic.servlet.internal.ChunkOutput.clearBuffer (ChunkOutput.java:231) at weblogic.servlet.internal.ChunkOutput.flush(Chunk Output.java:251) at weblogic.servlet.internal.ChunkOutputWrapper.flus h(ChunkOutputWrapper.java:152) at weblogic.servlet.internal.ServletOutputStreamImpl .flush(ServletOutputStreamImpl.java:119) at org.apache.soap.transport.TransportMessage.writeT o(TransportMessage.java:462) at org.apache.soap.server.http.RPCRouterServlet.doPo st(RPCRouterServlet.java:347) .. .. Now, I checked the mail-archive to see if others have run into the problem, and it seems that they have, but I was not able to find a resolution. Is there one? and if there is what is it? -thanks Gus -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986 -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986
Re: Oracle V2 parser doesn't like unqualfied 'fault' elements
here's the header for that message, should have included in original posting. ?xml version='1.0' encoding='UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:xsd=http://www.w3.org/1999/XMLSchema; SOAP-ENV:Body This happens with oracle parser rather then xerces. Are you not seeing the same thing? I had other symptoms of this problem that led me to swap the parsers and zero in on the fault elements. V2 works fine if the call doesn't generate a fault. I'm looking for a work around, solution and/or confirmation. I'm not beating up the oracle parser. thanks for any help --- Steve Muench [EMAIL PROTECTED] wrote: This error is thrown by the soap client libraries, not the Oracle JAXP implementation. If this is indeed the XML returned by the server: SOAP-ENV:Fault faultcodeSOAP-ENV:Server/faultcode faultstringservice 'urn:test:echo2' unknown/faultstring faultactor/winxml/rpcrouter/faultactor /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope Then this is not parseable because is uses the SOAP-ENV namespace *prefix* without including a matching xmlns:SOAP-ENV=... namespace declaration. I doubt any (XML 1.0 + Namespaces) parser would parse this. __ Steve Muench - Developer, Product Mgr, Evangelist, Author Simplify J2EE and EJB Development with BC4J http://otn.oracle.com/products/jdev/htdocs/j2ee_bc4j.html Building Oracle XML Apps, www.oreilly.com/catalog/orxmlapp - Original Message - From: Robert Quinn [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 00:43 Subject: Oracle V2 parser doesn't like unqualfied 'fault' elements | i'm using the V2 beta which is jaxp compliant. but it | complains about that the faultcode element is not | qualified with a namespace. | | has any one ecountered this before? i saw a reference | in the archive regarding similiar probelm with xerces | 1.3.1, but solution was use a different version of | xerces. (i wish i had that option) | | worst case i'll can update the code to output | qualified names but i hate to do that. (testing, | interop, etc.) | | is it valid xml to have unqualifed name mixed in when | using namespaces? | | thanks for any help | | ** soap message from server | | SOAP-ENV:Fault | faultcodeSOAP-ENV:Server/faultcode | faultstringservice 'urn:test:echo2' | unknown/faultstring | faultactor/winxml/rpcrouter/faultactor | /SOAP-ENV:Fault | /SOAP-ENV:Body | /SOAP-ENV:Envelope | | *** Original Messages | | SOAPException= SOAP-ENV:Client, A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | | | [SOAPException: faultCode=SOAP-ENV:Client; msg=A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element.; | targetException=java.lang.IllegalArgumentException: A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element.] | | | at org.apache.soap.rpc.Call.invoke(Call.java:246) | at | test.client.EchoClient.invokeEchoString(EchoClient.java:200) | at test.client.EchoClient.main(EchoClient.java:25) | Root Cause = A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | java.lang.IllegalArgumentException: A | 'http://schemas.xmlsoap.org/soap/envelope/:Fault' | element must contain a: 'faultcode' element. | at org.apache.soap.Fault.unmarshall(Fault.java:331) | at | org.apache.soap.rpc.RPCMessage.unmarshall(RPCMessage.java:363) | at | org.apache.soap.rpc.RPCMessage.extractFromEnvelope(RPCMessage.java:197) | at | org.apache.soap.rpc.Response.extractFromEnvelope(Response.java:142) | at org.apache.soap.rpc.Call.invoke(Call.java:233) | at | test.client.EchoClient.invokeEchoString(EchoClient.java:200) | at test.client.EchoClient.main(EchoClient.java:25) | | __ | Do You Yahoo!? | Try FREE Yahoo! Mail - the world's greatest free email! | http://mail.yahoo.com/ | __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/
Re: weblogic6.1 and soap2.2
Ruben, Thanks. On Wed, 2002-03-06 at 09:12, [EMAIL PROTECTED] wrote: Hi Gus, no idea, I tried to find the Patch from Bea support for a long time but I get no response, just know that it works and I think they solved the problem in sp2. Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: Re: weblogic6.1 and soap2.2 03/06/2002 04:01 PM Please respond to soap-user Ruben, thanks, it work. where can I find some info on this patch? -Gus On Wed, 2002-03-06 at 07:59, [EMAIL PROTECTED] wrote: Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before weblogic.jar in server's classpath.(See attached file: patchCR058220.jar) regards, Ruben Gus Delgado gus.delgado@netquo To: [EMAIL PROTECTED] tient.comcc: Subject: weblogic6.1 and soap2.2 03/06/2002 02:58 PM Please respond to soap-user I'm trying to deploy a soap2.2 web service on weblogic 6.1, I have soap2.2 as a war file and I can see the jsp's for the admin and I can deploy a web service just fine, but when I try to hit it with a client I get the following null pointer exception error: java.lang.NullPointerException at weblogic.servlet.internal.ChunkOutput.clearBuffer (ChunkOutput.java:231) at weblogic.servlet.internal.ChunkOutput.flush(Chunk Output.java:251) at weblogic.servlet.internal.ChunkOutputWrapper.flus h(ChunkOutputWrapper.java:152) at weblogic.servlet.internal.ServletOutputStreamImpl .flush(ServletOutputStreamImpl.java:119) at org.apache.soap.transport.TransportMessage.writeT o(TransportMessage.java:462) at org.apache.soap.server.http.RPCRouterServlet.doPo st(RPCRouterServlet.java:347) .. .. Now, I checked the mail-archive to see if others have run into the problem, and it seems that they have, but I was not able to find a resolution. Is there one? and if there is what is it? -thanks Gus -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986 -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986 -- Gus Delgado Consultant NetQuotient Consulting Group e-mail: [EMAIL PROTECTED] cell: 512-587-6986
JBoss and SOAP service deployment
I'm stumped trying to get my first service deployed. Can anyone please lend me a hand. I'm trying to rpc the sample interest ejb for JBoss. Soap 2.2, JBoss 2.2.4 and Tomcat 4.0.1... and using the servicemanagerclient for deployment. FullContextFactoryName - I'm using: org.jnp.interfaces.NamingContextFactory but looks like the rpc servlet can't find my EJB Home class. error in the server window is [ERROR,Default] = [ERROR,Default] In TemplateProvider.locate() [ERROR,Default] URI: urn:interestCalc [ERROR,Default] DD.ServiceClass: org.apache.soap.providers.StatelessEJBProvider [ERROR,Default] DD.ProviderClass: null [ERROR,Default] Call.MethodName: calculateCompoundInterest [INFO,Default] Exception caught: javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.docs.interest.InterestHome] and my deployment xml is ?xml version=1.0? isd:service xmlns:isd=http://xml.apache.org/xml-soap/deployment; id=urn:interestCalc isd:provider type=org.apache.soap.providers.StatelessEJBProvider scope=Application methods=create calculateCompoundInterest isd:option key=JNDIName value=interest/Interest/ isd:option key=FullHomeInterfaceName value=InterestHome / isd:option key=ContextProviderURL value=localhost:1099 / isd:option key=FullContextFactoryName value=org.jnp.interfaces.NamingContextFactory / /isd:provider isd:faultListenerorg.apache.soap.server.DOMFaultListener/isd:faultListene r /isd:service Regards, Paul
base64binary
Hello everybody!
I have a problem and hope somebody can help me.
I have .NET client and Java Apache Soap Web Service. One method has an input
parameter byte[]
(public String setArrayByte(byte[] param) and another one - returns byte[]
(public byte[] getArrayByte(String param). When the client calls
getArrayByte() method it works fine my client gets byte[], but when
setArrayByte() is invoked I get an error:
No Deserializer found to deserialize a
'http://www.w3.org/2001/XMLSchema:base64Binary' using encoding style
'http://schemas.xmlsoap.org/soap/encoding/'.
My methods:
public String setArrayByte(byte[] byteArray) {
String str1 = new String(byteArray);
System.out.println(WebService TestArray: string for byte[]= + str1);
return str1;
}
public byte[] getArrayByte(String str) {
System.out.println(WebService TestArray: received string = + str);
byte[] byteArray = str.getBytes();
return byteArray;
}
I generated a client proxy using .NET wsdl.exe
Client proxy in C#:
[System.Web.Services.Protocols.SoapRpcMethodAttribute(urn:testarray-service
, RequestNamespace=urn:testarray-service,
ResponseNamespace=urn:testarray-service)]
[return: System.Xml.Serialization.SoapElementAttribute(meth3_outType)]
public string
setArrayByte([System.Xml.Serialization.SoapElementAttribute(DataType=base64
Binary)] System.Byte[] meth3_inType1) {
object[] results = this.Invoke(setArrayByte, new object[] {
meth3_inType1});
return ((string)(results[0]));
}
[System.Web.Services.Protocols.SoapRpcMethodAttribute(urn:testarray-service
, RequestNamespace=urn:testarray-service,
ResponseNamespace=urn:testarray-service)]
[return: System.Xml.Serialization.SoapElementAttribute(meth2_outType,
DataType=base64Binary)]
public System.Byte[] getArrayByte(string meth2_inType1) {
object[] results = this.Invoke(getArrayByte, new object[] {
meth2_inType1});
return ((System.Byte[])(results[0]));
}
WSDL:
?xml version=1.0 encoding=UTF-8?
definitions name=TestArray_Service
targetNamespace=http://www.testarrayservice.com/TestArray-interface;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=http://www.testarrayservice.com/TestArray-interface;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
message
name=InechoArrayByteRequest
part name=meth1_inType1
type=xsd:base64Binary/
/message
message
name=OutechoArrayByteResponse
part name=meth1_outType
type=xsd:base64Binary/
/message
message
name=IngetArrayByteRequest
part name=meth2_inType1
type=xsd:string/
/message
message
name=OutgetArrayByteResponse
part name=meth2_outType
type=xsd:base64Binary/
/message
message
name=InsetArrayByteRequest
part name=meth3_inType1
type=xsd:base64Binary/
/message
message
name=OutsetArrayByteResponse
part name=meth3_outType
type=xsd:string/
/message
portType
name=TestArray_Service
operation
name=echoArrayByte
input
message=tns:InechoArrayByteRequest/
output
message=tns:OutechoArrayByteResponse/
/operation
operation
name=getArrayByte
input
message=tns:IngetArrayByteRequest/
output
message=tns:OutgetArrayByteResponse/
/operation
operation
name=setArrayByte
input
message=tns:InsetArrayByteRequest/
output
message=tns:OutsetArrayByteResponse/
/operation
/portType
binding
name=TestArray_ServiceBinding
type=tns:TestArray_Service
soap:binding style=rpc
transport=http://schemas.xmlsoap.org/soap/http/
operation
name=echoArrayByte
soap:operation
soapAction=urn:testarray-service/
input
soap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:testarray-service
use=encoded/
/input
output
soap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:testarray-service use=encoded/
/output
/operation
operation
name=setArrayByte
soap:operation
soapAction=urn:testarray-service/
input
soap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:testarray-service
use=encoded/
/input
output
soap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:testarray-service use=encoded/
/output
/operation
operation
name=getArrayByte
soap:operation
soapAction=urn:testarray-service/
input
soap:body
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:testarray-service
use=encoded/
/input
output
soap:body
