You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Scott Kurz (JIRA)" <tu...@ws.apache.org> on 2008/03/17 20:04:24 UTC
[jira] Created: (TUSCANY-2094) 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
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
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-2094) 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
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng resolved TUSCANY-2094.
-----------------------------------
Resolution: Fixed
Patch applied under r638511. Thank Scott for the patch.
> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-2094) 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
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-2094:
--------------------------------
Attachment: JAXWSFaultExcMapper.patch
> 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
> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Assigned: (TUSCANY-2094) 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
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org