The problem I see is having to establish dependcies on every critical service. Naming for instance is used by nearly every bean so we would have to further complicate the correct setup of services. I would rather have fail fast semantics than uncertain running but not working services. There has got to be a valid use case for the fix it on the fly behavior we are moving to.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, June 15, 2002 6:09 PM Subject: Re: [JBoss-dev] Why does one MBean failure cause the entire deployment unit to fail? > I agree with jason that we should always continue deployment as far as > possible and undo as little as possible. We also need to make all problems > extremely visible through jmx and possibly logging. With proper dependency > specifications nothing that depends on a unsuccessfully deployed mbean will > start anyway, including your application, so I don't see the problem in > leaving the state as is, and letting the administrator fiddle with it to > try to fix things through jmx. > > david jencks > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
