[
http://jira.jboss.com/jira/browse/JBCACHE-1283?page=all ]
Mircea Markus resolved JBCACHE-1283.
------------------------------------
Fix Version/s: 3.0.0.ALPHA1
Resolution: Done
all items were resolved but the documentation which cannot be addressed at this moment due
to changes in the doc structure.
http://jira.jboss.com/jira/browse/JBCACHE-1391 was created to capture this and will be
approached asap
Remove MBEAN tag from configuration files
-----------------------------------------
Key: JBCACHE-1283
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1283
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.1.0.GA
Reporter: Manik Surtani
Assigned To: Mircea Markus
Fix For: 3.0.0.ALPHA1, 3.0.0.GA
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Replace the <mbean ... /> container tag in config files with a <jbosscache ...
/> tag.
Would entail:
1) update all sample configs and docs to reflect this "new" element
2) document how the configuration will still accept old <mbean ... /> tags, but
this is deprecated
3) document how the <mbean ... /> tag can cause problems with AS 5 (unintentional
deployment), and how this can be done properly with the MC using the new <jbosscache
... /> tag
Currently the XMLConfigurationParser looks for a <mbean ../> element, under which
it pulls out more specific JBoss Cache elements.
This could easily change so the parser to accept this, or on failing to do so, to pick up
a <jbosscache ... /> container element. And log a deprecation warning when using the
old <mbean ... /> container tag.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira