Hello all,
I developed a first version of NXRuntime remoting service.
What was done:
1. the remoting infrastructure - enable nxruntime hosts to
inter-communicate.
2. Enable components to contribute extensions on remote hosts.
This is also working when extensions contains references to local
classes or resources
A remote class loader is used to remotely load resources when not found
on the host that
received remote contributions.
The remoting service is implemented using jboss-remoting. The last
version of jboss-remoting.jar is used (2.0.0.GA).
NXRuntime is replacing the current jboss-remoting.jar from JBoss when it
is deployed.
Some have experienced problems when replacing this library so if you are
not able to start jboss
after updating from svn simply restore the original jboss-rempoting.jar
in jboss/servers/default/lib/jboss-remoting.jar
I will fix this soon.
The remoting infrastructure is enabling NXRuntime based applications (I
will call them network nodes) to detect other nxruntime nodes that are
part of the same network group.
Once a nxruntime node is joining the group it will be synchronized with
other nodes in the group.
This enable nxrutnime nodes to contribute extensions on remote nodes
when the target component is not found on the local nxruntime.
Using the remoting infrastructure NXRuntime components will be able to
define remote interfaces and thus to use remote components. But for now
only contributing extensions remotely is implemented.
The network detection is done using a plugable module. By default a
simple detection mechanism (using a master node that needs to be online
when other nodes are started)
In future support will be provided for jgroups.
The remoting is disbaled by default. You need to edit
NXRuntime.jar/OSGI-INF/RemotingService.xml file to enable it
Regards,
Bogdan
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
