[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: ClassLoadingMetaData ease-of-use

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : 
  | The issues would be around contradictory specifications, e.g.
  | 
  |   | <classloader exportAll="ALL" excludeExport="p1">
  |   | <capability>
  |   |    <package name="p1"/>
  |   | ...
  |   | 
  | 
  | So is p1 in the exports or not? ;-)
  | 
  | There's probably other more complicated examples.
  | Especially since I didn't mention that although these filters are shown
  | as lists of packages, I'm potentially allowing any ClassFilter and wildcard
  | capabilities so I don't necessarily know exactly what they mean,
  | although I do know if the Capability implements ExportPackages
  | which is part of the way.

So we have,
exportAll="ALL|NON_EMPTY" - an alias for includedExport="*|NonEmptyPackageFilter"?
included - define what is visible as input to the module itself via inclusion rules.
excluded - define what is visible as input to the module itself via exclusion rules.
includedExport,capability - define what can be exported from module's available content. 

So in the example above, the overlapping p1 specifications could mean an empty p1 package was exported. If it was exportAll="NON_EMPTY", then p1 would not show up as a capability. This leads to the question: what does it mean to resolve a package to a module that only has an empty version of it? Generally this would not be meaningful. The only possible usage would be to obtain package annotations, but then is that really an empty package?

This really seems like a management interface issue where I want to be able to ask, what are the package export filters that apply to the class loader. From that perspective, the includedExport is just an alias for a type of capability (package, custom). However, since you can't use a namespace in an attribute value, how would you specify something other than a package filter? Given that, I would say the includedExport is only used for package filtering, and we can decide if we want better detection of conflicting statements that end up in an empty export set in the management interface.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131424#4131424

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131424