Remy Maucherat wrote: > Costin Manolache wrote: >> Remy Maucherat wrote: > >> Cast the notification to MBeanServerNotification :-) > > Ok, it sort of works now. > > The remaining problems: > - some attributes need to send JMX notifications (welcome files, > mappings, etc) so the mapper can be updated > - the Host handling is not dynamic > - some operations need also be propagated (removal of a component)
What if we simplify this by exposing the mappings, welcome files, etc as JMX attributes of context ? Of course, we won't save the web.xml if someone adds a mapping ( yet :-), but you'll only need to listen for context add/remove notifications. And the jmx console would provide more usefull informations. The methods and info is already there - we just need to expose them. BTW - I assume you read the discussion on authorization - the problem is the same ( mapping requests URIs to constraints ), it would be good if we can reuse some code. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
