Just as an update, I've got an XMBean deployed, but I'm still having trouble sharing objects between this Bean and the Interceptors/Handlers. I thought I could share a custom static configuration object between them all (since the Interceptors and Handlers already share a static processing core between them), but this hasn't worked for some reason (despite the fact that the JBoss startup sequence suggests that the new static object *is* being shared correctly). Essentially I need a direct means of communicating data from the XMBean when a method is called so that the Interceptors and Handlers are immediately aware of any new data - a data sharing/notification framework would be ideal, but I can't find anything that works. Is there a way of hooking a non-MBean object into the XMBean notification framework? Is there any reason why a static instance of a custom object can't be shared across different classes within the JBoss server?
Again, any help would be appreciated,
Heheh, okay, problem solved! I hadn't configured the shared static object correctly (*it* was static, but its shared internal data structures weren't) ...
So, for anyone else wanting to try this, I developed a means of configuring the behaviour of request interception mechanisms remotely through an XMBean interface, by sharing a static configuration class between the XMBean and any applicable interceptor classes (which in this case are EJB Interceptors and Axis SOAP Handlers), and exposing methods for altering this configuration core through the XMBean.