This is a feature request, not a bug...
It would be great if the mofcompiler could be a bit more
flexible in generating beans/classes with regards to
packages/imports/exceptions. Currently there appears
to be no way to generate the entire set of classes from
an entire CIM Schema release into anything other than
one monolithic package. It would be nice if you could
instruct the mofcompiler to segregate the various
classes into appropriate sub-packages by way of an
input mapping file, or some other logical filename-based
pattern matching.
For example, one of the CIM schema 2.7 mof files is:
Device27_Sensors.mof. With a file pattern matching
approach (possible by a regexp passed in as an arg to
mofcomp), one could specify that package for classes
defined in this file should be in a package named
something like: "org.dmtf.cim27.device.sensors".
mofcomp could keep track of the package to class
mappings and generate the appropriate import
statements as well.
Log in to post a comment.