What? How does JBoss.NET get in there? Really, I don't get how you come up with these things sometimes.
JBoss.NET is not accessable from this component... since JBoss.NET is itself deployed here. I would have to be a JMX notification, which you could then install an JBoss.NET adapter or whatever if you like, but the core system can not make use of it directly. --jason Quoting Peter Fagerlund <[EMAIL PROTECTED]>: > on 15-04-2 02.10, David Jencks at [EMAIL PROTECTED] wrote: > > > On 2002.04.14 19:44:06 -0400 Peter Fagerlund wrote: > >> on 15-04-2 01.24, Larry Sanderson at [EMAIL PROTECTED] wrote: > >> > >>> I don't know... perhaps someone would like to add a custom layer of > >> security > >>> on all deployments. Perhaps they would like to get an email when new > >>> deployments occur. Who knows? The point is I can see no down-side to > >>> making this pluggable, and it is a very easy patch. More important, > >> though, > >>> is to prevent SubDeployers from accessing MainDeployer specific > >>> functionality. That is just bad design. > >> > >> It is of interest to have a "notification" of deploys when the thought > >> frame is agent centric. > > > > The farm service runs off of such notifications today. Possibly they > could > > be finer grained or at a different time. > > maybe as a jboss.net "notification" then since in in a agent frame no > config > nor geo boundery should prevent ? ... > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
