[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]