[ 
https://issues.apache.org/jira/browse/TUSCANY-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2094:
-------------------------------------

    Assignee: Raymond Feng

> Would like to keep track of element name during fault/exception mapping at 
> introspect time and invocation time so I can use FaultException matching 
> helpfully
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2094
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2094
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Data Binding Runtime
>    Affects Versions: Java-SCA-1.1
>            Reporter: Scott Kurz
>            Assignee: Raymond Feng
>             Fix For: Java-SCA-1.2
>
>         Attachments: JAXWSFaultExcMapper.patch
>
>
> In the JAXWSFaultExceptionMapper, we look at the @WebFault to capture the 
> fault element name.   
> It would be nice to capture during introspect this so it could be set into 
> the FaultException at wrap time for use in matching. 
> I'll attach a patch which has does:
> 1) During introspect, save the @WebFault element and set it in as the fault 
> DT's XMLType logical's element name
> 2) During wrapFaultInfo(), if we have a FaultException let's grab the element 
> name from the fault logical and do a setFaultName()
> The reason I had to do 1) in addition to 2) is that the instrospection of the 
> fault itself was, in my case, creating an XMLType with Type but no Element.
> (This happened since the JAXBDataBinding only sets up an Element on the 
> XMLType if it finds an @XMLRootElement).    
> I wasn't sure in 1) if I should always set the @WebFault as the fault's 
> logical's element name or if I should only do so in the introspect of the 
> fault did not itself set this field to non-null.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to