Just in case I've misunderstood. Was your reference to composite ClassLoader is
a reference to Bharath's earlier posted link?
http://blog.osgi.org/2008/08/classy-solutions-to-tricky-proxies.html?m=1
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
Thanks Gregg,
I realise that Jini may have been a lot more successful had your experiences
with desktop applications been given greater consideration.
Any thoughts on JavaFX, fxml for serviceui?
Criticism had also in the past, been levelled at the lookup service's inability
to perform boolean
I am a fan of “one jar” because I get real tired of spending time “packaging”
when the class loading mechanisms already provide “segregation”. I understand
how “pretty” packaging is and how everyone can be completely excited about a
clean view of dependencies. However, when I package something
Object based annotations allow creating ClassLoaders - it is not only a
way to download code but to:
1. Make sure only trusted code is executed
2. Resolve any dependencies and create the whole ClassLoader structure
when deserializing objects
So URL handler is not enough - alternative implement
