-----Original Message-----
From: Chad Phillips (JIRA) [mailto:[email protected]] 
Sent: 26 August 2009 17:54
To: [email protected]
Subject: [jira] Created: (TUSCANY-3238) Use of WS binding results in
exception when returning data

Use of WS binding results in exception when returning data
----------------------------------------------------------

                 Key: TUSCANY-3238
                 URL: https://issues.apache.org/jira/browse/TUSCANY-3238
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Axis Binding Extension, Java SCA Misc
Binding Extensions
    Affects Versions: Java-SCA-1.5
         Environment: Microsoft Windows XP SP2 Java JDK 1.5.0_18 Apache
Tuscany SCA Java 1.5 / 1.6 SNAPSHOT (r805992) JAX-WS RI 2.1.7 Ant 1.7.0
            Reporter: Chad Phillips


When the server in attached test program tries to return data to the
client (request was made via a webservice), an exception is being thrown
from the JAXB data binding (see the attached ant_server.log).  I'm not
sure what exactly is causing the issue but it may have to do with the
use of substitution groups in the XSD used to generate the binding
classes for the objects being returned.  This is just speculation on my
part as I have done similar things in the past, without using
substitution groups, and I did not encounter this issue.

Here is how the test program is being used:

Create/run the server:

Open a command prompt and run the following commands (adjust paths as
necessary):
cd <project directory>
set JAXWS_HOME=C:\jaxws-ri-2.1.7
set TUSCANY_HOME=C:\tuscany-sca-1.5
ant clean server

Create/run the client:

Open another command prompt and run the following commands (adjust paths
as necessary):
cd <project directory>
set JAXWS_HOME=C:\jaxws-ri-2.1.7
set TUSCANY_HOME=C:\tuscany-sca-1.5
ant client 

The server and client outputs are attached.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


*****************************************************
This email is issued by a VocaLink group company. It is confidential and 
intended for the exclusive use of the addressee only. You should not disclose 
its contents to any other person. If you are not the addressee (or responsible 
for delivery of the message to the addressee), please notify the originator 
immediately by return message and destroy the original message. The contents of 
this email will have no contractual effect unless it is otherwise agreed 
between a specific VocaLink group company and the recipient.
 
The VocaLink group companies include, among others: VocaLink Limited (Company 
No 06119048, VAT No. 907 9619 87) which is registered in England and Wales at 
registered office Drake House, Homestead Road, Rickmansworth, WD3 1FX. United 
Kingdom, Voca Limited (Company no 1023742, VAT No. 907 9619 87) which is 
registered in England and Wales at registered office Drake House, Three Rivers 
Court, Homestead Road, Rickmansworth, Hertfordshire. WD3 1FX. United Kingdom, 
LINK Interchange Network Limited (Company No 3565766, VAT No. 907 9619 87) 
which is registered in England and Wales at registered office Arundel House, 1 
Liverpool Gardens, Worthing, West Sussex, BN11 1SL and VocaLink Holdings 
Limited (Company No 06119036, VAT No. 907 9619 87) which is registered in 
England and Wales at registered office Drake House, Homestead Road, 
Rickmansworth, WD3 1FX. United Kingdom.
 
The views and opinions expressed in this email may not reflect those of any 
member of the VocaLink group. This message and any attachments have been 
scanned for viruses prior to leaving the VocaLink group network; however, 
VocaLink does not guarantee the security of this message and will not be 
responsible for any damages arising as a result of any virus being passed on or 
arising from any alteration of this message by a third party. The VocaLink 
group may monitor emails sent to and from the VocaLink group network.
 
This message has been checked for all email viruses by MessageLabs.
*************************************************************

Reply via email to