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

scott.stark@jboss.org do-not-reply at jboss.com
Mon Feb 18 15:26:31 EST 2008


"adrian at jboss.org" wrote : 
  | NOW FOR THE QUESTIONS.
  | 
First, does module name equate to the osgi bundle symbolic name? We would also need additional policy information that equates to the Require-Bundle header parameters. 

"adrian at jboss.org" wrote : 
  | 1) Is the above "Note" about mutual exclusion of exportAll and listing
  | capabilities correct? If not, it could get very messy trying to merge them. ;-)
  | 
I guess, I can't see why one would want to use both syntaxes.

"adrian at jboss.org" wrote : 
  | 2) In the filter case, the packages automatically get the version of the module,
  | but this doesn't happen for listing capabilities explicitly
  | 
  | 
  |   | <classloading xmlns="urn:jboss:classloading:1.0">
  |   |    <capabilities>
  |   |       <module name="export1" version="1.0.0"/>
  |   |       <package name="export2"/>
  |   | 
  | The package export2 has version 0.0.0 if you are explicit.
  | 
Sure, this would be a reason to use the expanded syntax.

"adrian at jboss.org" wrote : 
  | 4) Should I create an included export filter?
  | This would mean all classes are in the classloader, but only
  | the listed packages are exported.
  | While this might seem obvious, it is effectively the same as listing the
  | packages in the capabilities and therefore redundant.
  | It would also mean that "exportAll" doesn't really have that meaning anymore,
  | instead a better name would be something like "autoDiscoverPackages". :-)
  | 
I don't see the difference between this and the export-all="ALL" included="..." notion. What is the difference?

"adrian at jboss.org" wrote : 
  | a) Do you think we should "fixup" the capabilities, i.e.
  | missing module capabilities, missing package versions
  | or should we just do what the user says?
  | 
What would the version be fixed up to? In terms of modules, unless its mapped to something usable like the deployment name, how would the fixed up name be usable?

"adrian at jboss.org" wrote : 
  | b) Is it worth trying to go through the "hard problem" of merging
  | the simple but not very explicit exportAll processing with explicit capabilities?


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

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



More information about the jboss-dev-forums mailing list