[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Breaking up the MC project and Mavenizing it

[adrian@jboss.org]

"alesj" wrote : 
  |  *** P1 - org.jboss.classloading
  |  **** SPI only
  | 

This was only there for a test that no longer exists.
It should be replaced by whatever underlies the OSGi implementation
in terms of defining a bundle/module (I called it domain) classloader

anonymous wrote : 
  |  **** org.jboss.repository (this one can be dropped; a single interface exists)
  | 

This needs to be left in place unless Kabir verifies that there was no real
AOP release that referenced this class.
IIRC this class is still referenced by AOP's Advisor for backwards
compatibility reasons.

anonymous wrote :  
  |  ** org.jboss.test.kernel.junit
  |  *** TODO - where to put this?
  | 

This is part of the yet to be defined MC api (see below for api vs spi).
In practice, I don't really want an api for the MC since a key idea
behind IOC is to not reference a container api.

But you obviously need some form of api for tests, e.g. the getBean()
supplied by this testcase implementation.

anonymous wrote :  
  |  * managed (org.jboss.managed)
  |  ** API (why not SPI?)
  | 

An API is meant to be used at runtime by an application/user.
It should be 100% stable across releases.

A SPI is for integration issues, which is meant for "super users".
 
anonymous wrote : Don't know what you need to do about Eclipse projects.

Maven can generate eclipse project files from the pom.

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

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