[ 
https://issues.apache.org/jira/browse/TUSCANY-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573922#action_12573922
 ] 

Raymond Feng commented on TUSCANY-1711:
---------------------------------------

The business interfaces and data types are defined by application developers. 
So they should have the flexibility to choose their styles. For the java2wsdl 
mapping, the SCA spec says we follow the JAXWS rules. 

I guess in your case, the data is POJO and it uses interfaces to represent 
data. Are you suggesting that we use proxies to instantiate the data modeled by 
interfaces? Please clarify.

Thanks,
Raymond

> Reference a ws with complex data type...
> ----------------------------------------
>
>                 Key: TUSCANY-1711
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1711
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-Next
>         Environment: win jdk1.6 svn 575578 eclipse
>            Reporter: gengshaoguang
>             Fix For: Java-SCA-Next
>
>
> Hi every one:
> I have a suggestion:
> When a Tuscany domain references a WS provided by another (or a WS from any 
> where). If the data type is not primitive, the consumer side must declare 
> classes according to the data structure (or ask for stubs from the provider 
> side).
> This is quite usual BUT, if we could improve a little: declare interface 
> instead of class (respond type only), will it be more "decouple mannered".
> Current scenario: the complex type transformation is done by:
> org.apache.tuscany.sca.databinding.javabeans.XML2JavaBeanTransformer
> it must instantiate the corresponding java type class and set values, I would 
> suggest if the type is a interface, create a proxy.
> (now it gives a instantiation exception).
> Is this worth doing?

-- 
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