You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2006/08/25 13:09:25 UTC
[jira] Closed: (TUSCANY-611) RMI Binding
[ http://issues.apache.org/jira/browse/TUSCANY-611?page=all ]
ant elder closed TUSCANY-611.
-----------------------------
Resolution: Fixed
All these patches applied now, thanks for all the patches Venkat.
I'm going to close this JIRA now and new work can go in new JIRAs
> RMI Binding
> -----------
>
> Key: TUSCANY-611
> URL: http://issues.apache.org/jira/browse/TUSCANY-611
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-M2
> Reporter: Venkatakrishnan
> Assigned To: ant elder
> Fix For: Java-M2
>
> Attachments: binding_rmi.zip, Tuscany-RMI-Binding-Aug-10-Updated.diff, Tuscany-RMI-Binding-Aug-10.diff, Tuscany-RMI-Binding-Formatted-Aug-15-1.diff, Tuscany-RMI-Binding-Reference-Sample-Aug-10.diff, Tuscany-RMI-Binding-Service-Sample-Aug-10.diff, Tuscany-RMI-Binding-Updated-Aug-15-2.diff, Tuscany-SCA-SPI-Aug-15.diff
>
>
> SCA RMI Binding with samples for SCA Reference and SCA Service using RMI Binding.
> Here is a first cut implementation for this. Could somebody please review and apply? Also I have had the following issues un-resolved: -
> - The samples can be tested thro the Testcases in them. These testcases work from eclipse as long as I have added the RMI-Binding Eclipse project to the classpath. Otherwise the binding does get picked up. The same is the issue when trying to execute the testcases from maven. Could somebody please help in fixing this? Thanks.
> Note :-
> --------
> I shall be working further with this binding to address the following : -
> - there is single attribute called 'uri' for the binding. I shall be splitting this to host, port and service name with defaults to each when not specified.
> - it is now required the that SCA Service require a component to implement the interface Remote. I imagine this to be intrusive. All that a developer should do is pick up an existing component with a 'non remote' interface and simply deploy it exposing the service as RMI. The binding should dynamically be able to generate a remote interface and a proxy and host it as a facade to this implementation.
> - will be glad to take forward any other inputs from the community as well.
> Thanks
> - Venkat
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org