Return-Path: 
 <dev-return-16705-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 71808 invoked from network); 4 Sep 2005 01:49:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 4 Sep 2005 01:49:44 -0000
Received: (qmail 91447 invoked by uid 500); 4 Sep 2005 01:49:32 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 91401 invoked by uid 500); 4 Sep 2005 01:49:32 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 91387 invoked by uid 99); 4 Sep 2005 01:49:32 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_FAIL
X-Spam-Check-By: apache.org
Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2005 18:49:31 -0700
Received: from ajax.apache.org (ajax.apache.org [127.0.0.1])
	by ajax.apache.org (Postfix) with ESMTP id BB56A33E
	for <dev@geronimo.apache.org>; Sun,  4 Sep 2005 03:49:30 +0200 (CEST)
Message-ID: <1736119795.1125798570765.JavaMail.jira@ajax.apache.org>
Date: Sun, 4 Sep 2005 03:49:30 +0200 (CEST)
From: "Stefan Schmidt (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-975) Problems with SOAPArrayType
In-Reply-To: <2117676256.1125797971303.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

     [ http://issues.apache.org/jira/browse/GERONIMO-975?page=all ]

Stefan Schmidt updated GERONIMO-975:
------------------------------------

    Attachment: WSS4JTest.zip

Attaching Ant-based project for testing.

Change paths to G and Axis in the build.xml

There is a JAX-RPC server-side to be deployed to G as a war file: ant deploy-war
There is a Axis client-side which requires a BouncyCastle and Xerces in the classpath. ant tcpmon (start TCP monitor); ant start-J2SEClient (run the Axis client)


> Problems with SOAPArrayType
> ---------------------------
>
>          Key: GERONIMO-975
>          URL: http://issues.apache.org/jira/browse/GERONIMO-975
>      Project: Geronimo
>         Type: Bug
>   Components: webservices
>     Versions: 1.0-M5
>     Reporter: Stefan Schmidt
>  Attachments: WSS4JTest.zip
>
> I am having a number of problems caused by array handling in SOAP. 
> Using sun's jwsdp I generated a simple JAX-RPC Web service which is supposed to return an array of Strings. I used the Java2WSDL approach for a JSE - meaning I generated heavyweight mappings and a wsdl file for my simple WS and deployed it to G. While the WS works in general it shows the following warning:
> 09:21:29,737 WARN  [HeavyweightTypeInfoBuilder] No soap array info for schematype: T=StringArray@http://arrays/java/lang
> This is due to a non-spec conformant wsdl array mapping generated by the jwsdp:
> 	<types>
> 		<schema targetNamespace="http://arrays/java/lang"
> 			xmlns:tns="http://arrays/java/lang"
> 			xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
> 			xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 			xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> 			xmlns="http://www.w3.org/2001/XMLSchema">
> 			<complexType name="StringArray">
> 				<sequence>
> 					<element name="value" type="string" nillable="true"
> 						minOccurs="0" maxOccurs="unbounded" />
> 				</sequence>
> 			</complexType>
> 		</schema>
> 	</types>
> This works for this web service which returns the following response (apart from the warning):
> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>  <soapenv:Body>
>   <getStringArrayResponse xmlns="http://stsmedia.wss4j.test">
>    <result xsi:type="xsd:string" xmlns="">String 1</result>
>    <result xsi:type="xsd:string" xmlns="">String 2</result>
>    <result xsi:type="xsd:string" xmlns="">String 3</result>
>    <result xsi:type="xsd:string" xmlns="">String 4</result>
>   </getStringArrayResponse>
>  </soapenv:Body>
> </soapenv:Envelope>
> However, when I switch on  WSS4J security the response looks quite different (SOAP body only):
>  <soapenv:Body
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
> wsu:Id="id-1197222">
>   <getStringArrayResponse xmlns="http://stsmedia.wss4j.test">
>    <result xmlns="" xmlns:ns1="http://arrays/java/lang"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> soapenc:arrayType="ns1:StringArray[4]" xsi:type="soapenc:Array">
>     <result xsi:type="xsd:string">String 1</result>
>     <result xsi:type="xsd:string">String 2</result>
>     <result xsi:type="xsd:string">String 3</result>
>     <result xsi:type="xsd:string">String 4</result>
>    </result>
>   </getStringArrayResponse>
>  </soapenv:Body>
> So it seems that WSS4J has a different Array serialization methods. I have the feeling that WSS4J actually does it right by adding the correct array encoding. 
> Due to these different array serialization approaches it is currently not possible to sign the SOAP message with WSS4J since G seems to return arrays which lack the appropriate array encoding :-( .
> Regards,
> Stefan Schmidt

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira