[
https://jira.jboss.org/jira/browse/JBREM-1054?page=com.atlassian.jira.plu...
]
David Lloyd commented on JBREM-1054:
------------------------------------
Sure, the annotation approach would just be something like this:
interface RemoteOne {
@Transport RemoteTwo createRemoteTwo();
void operateOnRemoteTwo(@Transport RemoteTwo remoteTwo);
}
interface RemoteTwo {
void doSomething();
}
Then if you were to create a Transporter for RemoteOne, sent it to a remote endpoint, and
then called createRemoteTwo() on it, the proxy would create a Transporter for the new
RemoteTwo automatically and send it back.
Likewise, operateOnRemoteTwo() might automatically create a transporter for the RemoteTwo
parameter and send that instead of the original.
Annotation to automatically return new transporters types
---------------------------------------------------------
Key: JBREM-1054
URL:
https://jira.jboss.org/jira/browse/JBREM-1054
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: r3 api
Reporter: David Lloyd
Priority: Optional
Fix For: 3.1.0.Beta1
It would be cool if a transporter interface (or an implementing class of that interface)
could have methods which sport an annotation that indicates that the return value of that
method, if it is an interface, should be automatically wrapped into a transporter (if
invoked via a transporter). This way, complex remote object structures can be easily
created and used.
Also handy would be a simple way of notating such methods when the interface and
implementation are already existent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira