In my PoC there is actually only one implementation based on RMI code
downloading ( IOW RmiAnnotation has a list of URLs ). But even that
enables us to get rid of httmd url handler since RmiAnnotation is
verified by ProxyTrustVerifier - one thing less to remember when
configuring the client :-D
Regards,
Michal
W dniu 2014-02-25 21:31, Michal Kleczek pisze:
Of course it is annotated :-)
There needs to be a common "bootstrap" implementation available. I've
called it RmiAnnotation that just uses a default
PreferredClassProvider logic (the devil's in the details - but all is
in my PoC :-) )
Regards,
Michal
W dniu 2014-02-25 21:27, Greg Trasuk pisze:
How do you get the code that implements that object?
Greg Trasuk
On Feb 25, 2014, at 3:09 PM, Michal Kleczek <michal.klec...@xpro.biz>
wrote:
This. I like this. How would this work, would it be an Entry, an
attribute
of the service (perhaps similar to the ServiceUI factory?).
My PoC is attached to one of the issues in Jira (I'll try to find it
tomorrow once I have some more time). It was discussed some time ago
on this list mainly with Peter.
Basically the idea is to change codebase annotation from
java.lang.String which needs to be interpreted by the client to an
object implementing an interface.
This object can be verified in exactly the same way as normal
proxies are verified ( by a TrustVerifier - in particular the
ProxyTrustVerifier ). All that happens during deserialization.
It does not have anything to do with Entries since it is implemented
at the layer below that - hence is available for _all_ downoladed
code (for RemoteEventListeners as well :-) )
Regards,
Michal
--
Michał Kłeczek
XPro Quality Matters
http://www.xpro.biz
--
Michał Kłeczek
XPro Quality Matters
http://www.xpro.biz
