JDK-5031385 : m-let file format should be XML
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2004-04-14
  • Updated: 2008-09-17
  • Resolved: 2008-09-17
Related Reports
Relates :  
Relates :  
Relates :  
The m-let service (javax.management.loading.MLet) defines a text file format that describes MBeans to be loaded.  That format looks like XML, but is not quite.  Here's an example:
  CODE = com.example.mlets.MyMLet
  CODEBASE = http://codehost/mlets
  ARCHIVE = "MyMLet.jar"
  NAME = MyMLet>

There's no XML header that would declare a namespace and character encoding.  There's no defined syntax for comments.  Tools that can handle XML files can't handle this.

Plainly, now that XML is part of the core Java platform, it would make sense to use a real XML format here.  Rather than trying to allow both the old format and the new with the same API, the proposal would be to deprecate the existing MLet.getMBeansFromURL methods and add new methods that expect an XML file.  The exact schema for this file is yet to be defined but it would lead to files very similar to the example above.

EVALUATION Although vaguely desirable, MLets are not widely used enough to justify this change, especially since by default it would be incompatible with existing MLet files.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang

PUBLIC COMMENTS The current m-let file format looks like XML but isn't. It should be deprecated in favour of a real XML format.

EVALUATION Cannot fix for Tiger because of required J2EE 1.4 compatibility. Should address in Mustang. ###@###.### 2004-04-14