on 1-06-01 01.18, Peter Fagerlund at [EMAIL PROTECTED] wrote:
> Hey - dont look back - look up *S* - there is JMX - and all
> ClasspathExtension's (on every JBoss node/instance) are MBeans ... if We are
> talking about remote web deployment among JBoss/JMX instances should'ent We
> use the management of instruments then ... ??? ...
Here follows a solution - to a problem We might not have ;-)
*this deployment* - is it to be able to replicate deployments in a cluster
or to dynamically load classes from any (nonJBoss/JMX) source ? ...
URLClassloader can not list remote directories, could be overcome by
extending the ClasspathExtension to subscribe/publish it's "list" of
deployments ... in a JMX agent/monitor notification style ...
JBossHA smart RMI Proxies could be/is the "auto configuration" of nodes ?
Maybe two local deploy folders on each node ?
- LocalDeploy
- LocalAndRemoteDeploy
I am here to understand and learn, so please feel free to educate me ...
/pf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
