Ok.. i buy into that. I think running a JMX server on the client side should be a piece of cake. The hard part is figuring out how the client-side deployment system going to work.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:jboss-development-admin@;lists.sourceforge.net]On Behalf Of David > Jencks > Sent: Monday, November 11, 2002 12:45 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] JMX on the client side? > > > Let me give you my example of why I want it. > > I worked over the trunk invoker so it would do distributed transactions. > This requires at least a source of xid's on the calling side, and > preferably a TransactionManager. Well, they are already there if the > calling side is a jboss instance. If it's a client, the only way you will > be propagating a transaction is if you have a UserTransaction. So, I'd > like to implement the client-side UserTransaction to use the same > mechanism, based on at least an XidFactory and perhaps a > TransactionManager. These are pretty much dependent on the jmx > framework. > If the jmx framework is on the client, I just register the mbeans and I'm > done. If not, I have to rewrite a bunch of the code to be independent of > the jmx framework. Incidently, I think the client end of the > trunk invoker > would also be simpler if it were an mbean: in fact I think there > could be a > lot more code sharing between the two ends. > > david jencks > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
