I am unclear as to what we are discussing right now, but the MLet supports
the URL loading (it is a URLClassLoader).
Ie you can have configuration and classes live on a central http server.
However for the pure web based installation to work we need to make sure
that a few things are squared away.
1- the fucki*g blabla.properties that some of our modules seems to
desperately cling on... that really fucks us up in the web deployment... we
need to adress these shyness in our modules (web, deployment etc :)
2- the ClasspathExtension... one of our core classes is not really built for
the pure web deployment (suprisingly enough) and fails in URL mode (for
sure)... where is rickard? I will slap his little butt if I catch him at J1,
he sold us on the URL installation but the core classes don't support it.
For Rabbit hole, number 1 on my priority list... (honest)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Peter
|Fagerlund
|Sent: Monday, May 21, 2001 4:48 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] Re: Deployment
|
|
|on 1-05-20 13.09, I wrote:
|
|> It was mentioned a refresh of the code ... does it have bugs or
|just needs
|> massaging ? ...
|
| A total rewrite then ?
|
|> I se an instance of jboss - when deployed on - that could replicate to
|> other nodes of jboss instances ... or to load deployments from other
|> jboss node/s ... local and remote*n deploy folders ...
|
|using a x-tra remote MLet ? per node ?
|
|> Or am I just confusing some of this with the remote loading of
|configuration ?
|
|using a x-tra remote MLet ? per node ?
|
|
|/peter
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
