You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Ramkumar Ramalingam (JIRA)" <tu...@ws.apache.org> on 2008/04/16 16:05:21 UTC

[jira] Commented: (TUSCANY-1881) Remote bidings attached to non-remotable services not reported as a warning in some cases

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

Ramkumar Ramalingam commented on TUSCANY-1881:
----------------------------------------------

This JIRA talks about fixing the databinding issue that crops-up while the interfaces not marked as remotable in case of remote bindings to services. After discussing with Venkat, I understood that the datatransformation interceptor will not be inserted in the invocation chain if the target interface is not marked as remotable. Not having this interceptor will end up with binding specific data transformations not being done.. for example transformation of java object to OMElements in the case of axis2 binding. So if the json-rpc binding does have trouble with the arguments and returntypes because of the absence of transformations... that seems to the expected behaviour in this case.

As a fix we will provide a warning in such scenarios. I'II attach a patch with a fix.

> Remote bidings attached to non-remotable services not reported as a warning in some cases
> -----------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1881
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1881
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model, Java SCA Problem Determination
>    Affects Versions: Java-SCA-1.0
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Ramkumar Ramalingam
>             Fix For: Java-SCA-Next
>
>
> I seem to remember in the past that adding remote bindings to services with interfaces not marked as remotable used to cause and error or a warning.
> This cropped up in the domain manager app which defines the following component.
>     <component name="DomainManagerComponent">
>         <implementation.java class="org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl"/>
>         <service name="DomainManagerInitService">
>             <interface.java interface="org.apache.tuscany.sca.domain.DomainManagerInitService"/>
>             <binding.sca/>
>         </service>
>         <service name="DomainManagerNodeEventService">
>             <interface.java interface="org.apache.tuscany.sca.domain.DomainManagerNodeEventService"/>
>             <binding.ws/>
>         </service>
>         <service name="DomainManagementService">
>             <interface.java interface="org.apache.tuscany.sca.domain.management.DomainManagementService"/>
>             <t:binding.jsonrpc />
>         </service>       
>     </component> 
> Where the DomainManagementService interface was not marked as remotable when it should have been (my mistake) but the interesting effect is that everything works except that no databindings are applied to the wires so parameters/return types are messed up.

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