3 of 4 imho |Yes. Also there is the choice of |-change attribute value while mbean is "started"
yes |-stop, change attribute value, start yes |-stop, destroy, create(with new values), start no (use below) |-stop, destroy, remove, install, create(with new valuew), start yes |These could all be specified w/model mbean attributes. yes |I think this whole question is also getting into "how will we use mbean |persistence?" and "just what is that replacement for jboss-auto.jcml?" right, you got your JMX book? If only I could get the flacid fin to get out of his hole marcf | |david jencks |> |> > |Why not make more usage of notifications here. Such |> > that jetty could |> > |send a notificatioin when it needs to be redeployed |> > due to config |> > |change. It may know best for some/most config |> > changes. |> > |> > correct, jetty knows best what requires a restart and |> > what does not, all |> > this handling should be done inside the MBean. |> > |> > we will get there, see, you are talking now :) |> > |> > marcf |> > |> > |> > _______________________________________________ |> > Jboss-development mailing list |> > [EMAIL PROTECTED] |> > https://lists.sourceforge.net/lists/listinfo/jboss-dev |> > lopment |> |> |> |> _________________________________________________________ |> View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=9657 |> |> _______________________________________________ |> Jboss-development mailing list |> [EMAIL PROTECTED] |> https://lists.sourceforge.net/lists/listinfo/jboss-development |> |> | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
