I've created a service broker that lets you separate service declarations from implementations, as we discussed on the commons list a few weeks ago. This broker also handles version numbering at the individual service level (which is the proper place to do this, IMNSHO*).
I'm trying to figure out how to hook in JMX to this mix, and I'd like very much to see what you come up with in that regard. All of what I'm doing requires no modifications to the alpha-4 release. Aside from one exception handling gotcha, which I'll try to submit a patch for, I'd like to see a 1.0 release of this thing soon, or at least get the discussion started. I see all your intended changes below as add-ons rather than changes to the core. They could reasonably go into a 1.1. Luke * To do version checking at the module level, you will need to introduce some notion of importation or other dependency declaration. To do this properly, you would need to require this importation for one module to use another one. I think this would be a good idea, generally, but it does go against your excellent philosophy of starting strict and relaxing as possible, rather than starting loose and tightening as necessary. In any case, version checking at the module level does not obviate the idea of version checking at the service level. L ---- Original message ---- >Date: Wed, 14 Apr 2004 14:53:18 -0400 >From: "Howard M. Lewis Ship" <[EMAIL PROTECTED]> >Subject: Status update >To: <[email protected]> > >So ... what are people doing with HiveMind? It's back, it's free and I've been doing some work on >it. I've also been doing some planning for HiveMind on the Wiki. > >I'm afraid that all the interruptions caused by the IP problem, and then by the infrastructure >delay, have hurt HiveMind. The community is failing to coalesce at the new home ... it's important >that the other HiveMind users and developers check in and start communicating about their needs. > >I have plans for HiveMind in the immediate future: >- Hook into J2EE for declarative security on services via an interceptor >- Create a gateway into Spring, to allow managed Spring beans to appear as HiveMind services >- Interface with JMX: map JMX MBean interfaces to HiveMind services, and add a "performance" >interceptor that records method invocation data into other JMX beans >- Transaction interceptor > >That's my immediate list ... what's your? > >-- >Howard M. Lewis Ship >Independent J2EE / Open-Source Java Consultant >Creator, Tapestry: Java Web Components >Creator, HiveMind >http://howardlewisship.com > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
