[jboss-dev-forums] [Design the new POJO MicroContainer] - Reflection and MetaDataRepository refactoring

[adrian@jboss.org]

The devil is always in the detail ;-)

I've found a couple of other wrong dependencies while splitting out this code.

The first is the ArrayInfo using the Signature class from the metadata repository
to determine primitive array class information.
This should clearly be delegating to PrimitiveInfo in both cases.

The second is this horrible method in BeanInfo

  |    /**
  |     * Bean may have additional dependencies
  |     * that the kernel cannot initially resolve. (currently defined by ClassAdapter)
  |     *
  |     * @param metaData the metadata
  |     * @return the list of dependencies
  |     */
  |    List<DependencyBuilderListItem<?>> getDependencies(MetaData metaData);
  | 

This has always bothered me since we first started the aop integration.
It doesn't really belong there. It's really part of the Kernel api.

The original intention isn't even used (instance ClassAdapters for AOP
instance containers).

And the latest rev has some horrible opaque type which is seen here in
the <?> which is actually the KernelControllerContext.

The issue came up again since it causes jboss-reflection to be based
on the metadata repository for no logical reason.

I'm finally going to bite the bullet and move this api to the kernel project
and remove all reference to the DependencyBuilder from the reflection project.

Like I said only aop-mc-int implements it and then only from the MC Pojo lifecycle.

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

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