james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <aok...@bellsouth.net>
Subject RE: Monitoring
Date Fri, 05 Dec 2003 19:48:37 GMT
Yes this is the next critical step.  I think everyone at
Avalon would be in favor of this since it has surprisingly 
become the basis for IoC in the J2EE container world.

Yes, I'm all for it as Noel says! Once the repo release is
complete is suspect this is the next priority concern.  What
do you say Steve?


> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Friday, December 05, 2003 1:53 PM
> To: dev@avalon.apache.org
> Cc: geronimo-dev@incubator.apache.org; James Developers List
> Subject: RE: Monitoring
> Stephen J. McConnell wrote:
> > Right now I'm in the process of pulling together the next release of
> > Merlin.  The main *feature* of the new release will be a much cleaning
> > embedding strategy based on a bunch of improvements from Alex (Apache
> > Directory Project).
> > If you or other have thoughts on this I'm real interested in getting
> > feedback, suggestions, options, etc.
> Alex, myself, and (AIUI) James Strachan are all of the mind that it would
> be
> very useful, indeed important, for the Avalon container (e.g., Merlin) to
> support JSR 77/88 directly.
>   http://www.jcp.org/en/jsr/detail?id=77
>   http://www.jcp.org/en/jsr/detail?id=88
> Like them or not, those are the standard Java specifications for
> management
> and deployment.  Enabling components written to use those specifications
> to
> be directly supported by in Avalon container would make such a container
> far
> more attractive, and would allow the Avalon container to leverage work
> being
> done for those JSRs.  There is code in the Geronimo CVS that does this (as
> explained by James, the actual Geronimo kernel *is* a JSR 77/88
> container),
> so you would not be starting from scratch.
> 	--- Noel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message