[jboss-dev-forums] [Design of POJO Server] - Re: Hotdeployment is still broken

[adrian@jboss.org]

Ok, Sacha/Scott asked me to look at this
(well actually he asked me to look at something else but this is close enough ;-)

This hasn't moved on much since I first raised this issue:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064180#4064180
and as Charles points out on the JIRA, the touch of deployment descriptors is broken
again
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145508

The basic issue here is that we now have three scanning mechanisms
(one of which isn't currently getting used).

There is 

1) the HDScanner which has some sane rules and a decent abstraction
but it is only used during the initial scan at bootstrap time
2) a MetaDataAwareProfile that knows where deployment descriptors live
3) a SerializableDeploymentRepository that assumes incorrectly that a profile
is made of local directories

Neither (2) or (3) are aware of the "sane" rules that the initial HDScanner
used when determining what is a deployment.

The SerializableDeploymentRepository also doesn't seem to understand
that there should be any number of (sub-)profiles and that they could be activated
"on the fly":
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136492
It doesn't seem to understand (sub-)profiles at all?

There is an APPLICATION_TRANSIENT phase in there but it doesn't look
to be complete or have a notion of whether a (sub-)profile is currently active
when looking for modifications.


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

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