OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: NEW ISSUE: Remove impact of @WebFault on interface fault name.

Target: CAA Spec CD04 and JCI Spec CD2

Description: The current text in both the CAA and JCI specs indicates that the name attribute of a @WebFault annotation impacts the name of the fault in the SCA interface. Based on some experimentation and a closer reading of the of the JAX-WS spec it appears that the name attribute of the @WebFault annotation really only impacts the local name of the GED used in the part of the fault message, not the name of the fault in the interface.  As an example:
The combination of :


public class Service1WithFaultWFImpl implements Service1WithFaultWF {

        public String operation1(String input) throws BusinessFault3 {





public interface Service1WithFaultWF {

        public String operation1 ( String input ) throws BusinessFault3;



public class BusinessFault3 extends Exception {




public class BusinessFault3Bean {

        private String data;

        public String getData() {

                return data;


        public void setData(String faultData) {

                data = "faultData;


result in a WSDL file of

<?xml version="1.0" encoding="UTF-8"?><!-- Generated by JAX-WS RI at
http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.1 in JDK 6. --><definitions name="Service1WithFaultWFImplService" targetNamespace="http://test/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">


      <xsd:import namespace="
http://test/" schemaLocation="Service1WithFaultWFImplService_schema1.xsd"/>


  <message name="operation1">

    <part element="tns:operation1" name="parameters"/>


  <message name="operation1Response">

    <part element="tns:operation1Response" name="parameters"/>


  <message name="BusinessFault3">

    <part element="tns:BusinessFault" name="fault"/>


  <portType name="Service1WithFaultWFImpl">

    <operation name="operation1">

      <input message="tns:operation1"/>

      <output message="tns:operation1Response"/>

      <fault message="tns:BusinessFault3" name="BusinessFault3"/>



  <binding name="Service1WithFaultWFImplPortBinding" type="tns:Service1WithFaultWFImpl">



  <service name="Service1WithFaultWFImplService">





<?xml version="1.0" encoding="UTF-8"?><xs:schema targetNamespace="
http://test/" version="1.0" xmlns:tns="http://test/" xmlns:xs="http://www.w3.org/2001/XMLSchema">

  <xs:element name="BusinessFault" nillable="true" type="tns:businessFault3Bean"/>

  <xs:element name="operation1" type="tns:operation1"/>

  <xs:element name="operation1Response" type="tns:operation1Response"/>

  <xs:complexType name="operation1">



  <xs:complexType name="operation1Response">



  <xs:complexType name="businessFault3Bean">


      <xs:element minOccurs="0" name="data" type="xs:string"/>




Note that in the operation, the name of the fault s BusinessFault3, not BusinessFault.

Proposal: Change the @WebFault content of table 11.2 of the CAA spec to remove the impact of the name attribute on the interface, removing normative statement JCA100027, and remove section 8.2.6 of the JCI spec

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]