"[EMAIL PROTECTED]" wrote : 
  | What's the relationship between the metadata repository and the bean 
itself? How do the two interact across the beans lifecycle? Will you be able to 
update a beans metadata by using the metadata repository directly or only 
through the beans "management interface"?
  | 

Initial comment:

You are also assuming one QOI (quality of implementation). 
The whole point of the abstraction is that people can pick/choose and plugin 
what 
happens and what is enabled (e.g. maybe deliberately disabling some 
features to provide a stable "lock down").

Back to your questions:

Most of these are a function of the metadata itself. 

The metadata exists independently of the object. 
That is a key feature of the new MC.

Metadata/management and real instance
* You can have a JMX MBean for a bean that is "on-demand" and click "start" on 
the
MBean to actually construct the real service.
* You can "suspend" a service (including removing the classloader) while keeping
the MBean/metadata in place.
* You can have metadata that is crosscutting or overriding lots of services,
e.g. a server level "default datasource"

Lifecycle
* Whether the metadata change leads to a recycling of the lifecycle depends upon
the policy of the metadata.
e.g. changing the transaction timeout of an ejb method does not require a 
redeploy
it just takes affect at the next invocation
e.g. undeploying the ejb's datasource does lead to a temporary removal 
(or at least suspension of service either through valve or cluster failover) of 
the EJB.
* It also depends upon whether the metadata is co-deployed, e.g. that is 
typically
true for ejbs and webapps.

Profile/Deployment/Repository(metadata)/Management Console
* A profile holds the collection of deployments and their top level attributes
* The deployment holds the raw information
* The metadata repository and mangement console is a runtime notion that can
act upon the profile/deployment/repository/object
* Support for cross updates between the different layers are QOI

e.g. 
* If the profile service is static/locked down, changes to it or deployments 
won't affect live data until you restart the server
* If the repository/bean's management decorator have support for persistence
(and the option is configured) that will be able to "marshall" back changes 
into the
deployments/profile

It would also be possible to have a QOI where changes are propogated
across a cluster or federation of servers from a single console.

How much of this is initially available in the open source product is unknown.

Clearly the JBoss Network is well ahead in feature set and it will be able
to provide better QOI than what we can do for JBoss5.

If somebody doesn't want to use the JBoss Network, 
then they can "write their own" profile service or 
management decorator (hopefully contributing back new features to the open
source community).

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910812#3910812

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910812


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to