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 2007/04/09 21:15:32 UTC
[jira] Created: (TUSCANY-1206) DataBinding support for transform of
Fault DataTypes should account for wrappered FaultBean in JAX-WS style
DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
-----------------------------------------------------------------------------------------------------------
Key: TUSCANY-1206
URL: https://issues.apache.org/jira/browse/TUSCANY-1206
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Kernel
Affects Versions: Java-SCA-Next
Reporter: Scott Kurz
I wonder if the DataBindingJavaInterfaceProcessor should be introspecting the FaultBean rather than the exception type itself in order to
calculate the databinding.
In the code we do:
for ( org.apache.tuscany.spi.model.DataType<?> d : operation.getFaultTypes()) {
dataBindingRegistry.introspectType(d, annotations);
}
Following JAX-WS, say my fault type is a POJO Java class extending Exception with a getFaultInfo() returning an SDO type (this SDO is the FaultBean).
If SDODataBinding.introspect() was called to introspect my FaultBean type, then, you would be able to calculate I wanted SDO databinding (since I load the fault type with <import.sdo>).
But since only my POJO wrapper exc is introspected I end up getting a null DB.
Maybe another solution would be to push the responsibility to check for a FaultBean returned by getFaultInfo() onto an individual DataBindingExtension class, e.g. SDODataBinding.
--
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-1206) DataBinding support for transform
of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng reassigned TUSCANY-1206:
-------------------------------------
Assignee: Raymond Feng
> DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1206
> URL: https://issues.apache.org/jira/browse/TUSCANY-1206
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Data Binding Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Scott Kurz
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
> Attachments: 1206.a.patch
>
>
> I wonder if the DataBindingJavaInterfaceProcessor should be introspecting the FaultBean rather than the exception type itself in order to
> calculate the databinding.
> In the code we do:
> for ( org.apache.tuscany.spi.model.DataType<?> d : operation.getFaultTypes()) {
> dataBindingRegistry.introspectType(d, annotations);
> }
> Following JAX-WS, say my fault type is a POJO Java class extending Exception with a getFaultInfo() returning an SDO type (this SDO is the FaultBean).
> If SDODataBinding.introspect() was called to introspect my FaultBean type, then, you would be able to calculate I wanted SDO databinding (since I load the fault type with <import.sdo>).
> But since only my POJO wrapper exc is introspected I end up getting a null DB.
> Maybe another solution would be to push the responsibility to check for a FaultBean returned by getFaultInfo() onto an individual DataBindingExtension class, e.g. SDODataBinding.
--
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-1206) DataBinding support for transform of
Fault DataTypes should account for wrappered FaultBean in JAX-WS style
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-1206:
--------------------------------
Attachment: 1206.a.patch
This is a patch created against r558780. It is, for a few reasons, not ready to be applied as-is.
At the least, we'd want to port to whatever changes have probably been made (I haven't checked what these might be) and use a real "registry" for the fault pattern handlers instead of the dummy one I made.
But I wanted to help move this discussion along:
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg24973.html
> DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1206
> URL: https://issues.apache.org/jira/browse/TUSCANY-1206
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Scott Kurz
> Fix For: Java-SCA-Next
>
> Attachments: 1206.a.patch
>
>
> I wonder if the DataBindingJavaInterfaceProcessor should be introspecting the FaultBean rather than the exception type itself in order to
> calculate the databinding.
> In the code we do:
> for ( org.apache.tuscany.spi.model.DataType<?> d : operation.getFaultTypes()) {
> dataBindingRegistry.introspectType(d, annotations);
> }
> Following JAX-WS, say my fault type is a POJO Java class extending Exception with a getFaultInfo() returning an SDO type (this SDO is the FaultBean).
> If SDODataBinding.introspect() was called to introspect my FaultBean type, then, you would be able to calculate I wanted SDO databinding (since I load the fault type with <import.sdo>).
> But since only my POJO wrapper exc is introspected I end up getting a null DB.
> Maybe another solution would be to push the responsibility to check for a FaultBean returned by getFaultInfo() onto an individual DataBindingExtension class, e.g. SDODataBinding.
--
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-1206) DataBinding support for transform of
Fault DataTypes should account for wrappered FaultBean in JAX-WS style
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng updated TUSCANY-1206:
----------------------------------
Component/s: (was: Java SCA Core Runtime)
Java SCA Data Binding Runtime
> DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1206
> URL: https://issues.apache.org/jira/browse/TUSCANY-1206
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Data Binding Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Scott Kurz
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
> Attachments: 1206.a.patch
>
>
> I wonder if the DataBindingJavaInterfaceProcessor should be introspecting the FaultBean rather than the exception type itself in order to
> calculate the databinding.
> In the code we do:
> for ( org.apache.tuscany.spi.model.DataType<?> d : operation.getFaultTypes()) {
> dataBindingRegistry.introspectType(d, annotations);
> }
> Following JAX-WS, say my fault type is a POJO Java class extending Exception with a getFaultInfo() returning an SDO type (this SDO is the FaultBean).
> If SDODataBinding.introspect() was called to introspect my FaultBean type, then, you would be able to calculate I wanted SDO databinding (since I load the fault type with <import.sdo>).
> But since only my POJO wrapper exc is introspected I end up getting a null DB.
> Maybe another solution would be to push the responsibility to check for a FaultBean returned by getFaultInfo() onto an individual DataBindingExtension class, e.g. SDODataBinding.
--
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-1206) DataBinding support for transform
of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng resolved TUSCANY-1206.
-----------------------------------
Resolution: Fixed
The fix was checked in under r629687. Some of the ideas are taken from Scott's patch. Thank you for the contribution.
> DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1206
> URL: https://issues.apache.org/jira/browse/TUSCANY-1206
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Data Binding Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Scott Kurz
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
> Attachments: 1206.a.patch
>
>
> I wonder if the DataBindingJavaInterfaceProcessor should be introspecting the FaultBean rather than the exception type itself in order to
> calculate the databinding.
> In the code we do:
> for ( org.apache.tuscany.spi.model.DataType<?> d : operation.getFaultTypes()) {
> dataBindingRegistry.introspectType(d, annotations);
> }
> Following JAX-WS, say my fault type is a POJO Java class extending Exception with a getFaultInfo() returning an SDO type (this SDO is the FaultBean).
> If SDODataBinding.introspect() was called to introspect my FaultBean type, then, you would be able to calculate I wanted SDO databinding (since I load the fault type with <import.sdo>).
> But since only my POJO wrapper exc is introspected I end up getting a null DB.
> Maybe another solution would be to push the responsibility to check for a FaultBean returned by getFaultInfo() onto an individual DataBindingExtension class, e.g. SDODataBinding.
--
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