The point is that the current integration is too heavy for something that is at best experimental and I should be able to configure a deployment that runs without it. I would like to see a looser integration that allows for this.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Andreas Schaefer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Scott M Stark" <[EMAIL PROTECTED]> Sent: Friday, May 24, 2002 3:05 PM Subject: Re: [JBoss-dev] How about integrating JSR77 via notifications > Hi Scott > > > The source of the problem is management setup such as this from > > SARDeployer where over 60% of the code is JSR77 setup with > > implicit dependencies on the org.jboss.management.* pkgs that > > if it fails, prevents the service from being created. Why can't these > > steps be performed based on an event generated from here rather > > than embedding all of this here? Its not a question of breaking this > > code now, its maintainability and mixing of functionality. > > NOTE: this is an experiment because JSR-77 does not know anything > about SAR,services etc. I wanted to extrapolate and see what we > can gain from. Therefore the implementation is everyting that stable. > We could wrap the whole thing in a try-catch block or we can check > if the classes are available before going on any further. > What is the best way to do so ? > > If all else fails we can take the part around ServiceModule and > management-MBean out. > > As I mentioned JSR-77 is not what it claims it would be. One of > the big missing parts is that you cannot create or destroy any part. > Therefore you cannot create a new DataSource, JCA, Queue, > Topic etc. which is an important part of J2EE management, isn't it? > > Like the ServiceModule/MBean I would like to add this as a > vendor-specific feature (one feature more than the competition). > > Have fun - Andy > > BTW the intrusive stuff is coming with the performance statistics > integration because then we need to track the statistics in each > service (JMS, JCA, EJBs, etc.) and on demand provide these > values to the client (of course massaged when it is running in > a cluster). > > > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
