|Depends on your definition of a system.
|
|What is your definition of System?
see below
|What is your definition of Application?
see below
|> The system as in JMX server is
|> outside this scope,
|
|What does the JMX server have to do with anything!?!?? *sigh* This is
|getting ridiculous...
The base server and JMX loaded services are part of the System, the server.
I.e the "jboss2.0 started" with no applications
|> the application as a collection of modules is the
|
|In my terminology that would be "system as a collection of
|applications". Same thing AFAICT.
no not the same thing.... application is what a user of the server will
deploy.
The administrator of the System is aware of the server, the jms server, the
datapools (i.e. all JMX loaded modules) the administrator of the Application
is only aware of his particular application.
They are very different roles.
|> it, it is meant as a externalizable object.
|
|No it is not. Why do you want to externalize the metadata? When is that
|useful?
...? all XML files for metadata are externalizations of it.
|
|> |2) Whenever you want to update *a part* of the System, you call
|> |SystemDeployer.redeploy(appname). The SD knows what URL the appname
|> |refers to, and determines the dependency chain (with respect to other
|> |applications), and correctly undeploy and deploy the applications (=the
|> |desired one plus all dependent apps) in the right order (which is
|> |trivial since we have all the info we need).
|>
|> right this is the Application Manager we want to write. (all
|this noise to
|> essentially say what we were saying 3 days ago :)
|
|SystemDeployer==Application Manager
right, so we will deploy the JBoss System and server with an "application
manager" and we will deploy the applications with a SystemDeployer... right,
makes oodles of sense :)
|The one inch you have to move sooner or later is to remove the thought
|that the metadata structure needs to be externalizable. It does not (we
|never do that anyway) so there's absolutely no problem with adding
|runtime data such as classloaders to it.
Yes but it's silly rickard :)).
2 points:
1- the name SYstem when you mean application is misleading and we should
fight over it since we agree on what it does.
2- Putting the CL in metadata is irrelevant (we are not further) you mix XML
externalizable information and runtime information for no gain... to keep
the information at the ContainerFactory level (or equivalent supra service)
is another way and at least we know what was static and what not... non
important == repackagitis.
Let's drop it...
like you say "by jove, let's code it" :)))
marc
|
|/Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|
|
