[jboss-dev-forums] [Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

[adrian@jboss.org]

"bill.burke at jboss.com" wrote : anonymous wrote : 
  |   | But what I will say is that components are an implementation detail.
  |   | The profile service should not be interested in the components directly,
  |   | it is not going to touch their attachments. 
  |   | 
  | 
  | Don't know about this....I had an idea to be able to serialize an EJB Container so that redeployment is super fast.

That's not what I'm talking about.

I'm saying that the users should modify the -ds.xml,
they shouldn't be allowed to modifed the underlying MBean definitions
and expect the modified version to work across releases.

I don't have a problem with advanced features in the profile service
that cache the components (either metadata or resulting objects)
as long as the cache is flushed when a new version of JBoss is released
or some significant global config changes.

In fact, it would be a useful debugging feature in the admin console
to be able to click on an "Advanced" button and see the underlying
MC/JMX configurations generated.

But, I'd imagine the feature you are talking about is incredibly difficult to
implement anyway.

The basics are pretty simple, you could replace the "InstantiateAction"
in the MC/JMX with a "DeserializeAction" but then it has still got to go through
configure/create/start to get up-to-date references and do things
like binding its entry point into jndi.

"No man is and island" and references to things like the 
TransactionManager singleton cannot be serialized, they must be
reinjected.

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

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