[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1283) Remove MBEAN tag from configuration files

Thu Jun 12 11:40:33 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBCACHE-1283?page=comments#action_12416829 ] 

Manik Surtani commented on JBCACHE-1283:
----------------------------------------

Would also need to provide a tool to transform old-style cfg files to new style ones.

* Tool should be used internally when old-style files are detected.
* Log a WARNing when an internal transformation happens, informing user to use a new-style cfg in future.
* Tool should also be able to be run from the command line, to transform cfg files.
* Provide a shell script and batch file for the above command-line tool.

> 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
>
>   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