# Joinpoint - Accessing a Bean

WARNING: The joinpoint model is subject to change without notice. It is currently under developement as issues with AOP integration and using the Microcontainer in more constrained environments are investigated.

The joinpoint model provides a mechanism to access class operations in a standard way.

## Aims

### Stanardize reflection operations

There are many places that use reflection within JBoss. The joinpoint provides a mechansim to deal with reflection dispatching without having worry about all the standard error handling, etc.

### Overridding Definition

The joinpoint allows the mechanism of dispatch to be overridden either through configuration or implementation. Examples would be not using get/set to define a property either because it is a different method name or it should use direct field access.

## Issues

### javabean versus object

Much of the javabean abstraction has moved the BeanInfo model, it is questionable whether the ability to override on a plain object is still required.

### Alternative implementations

One use of this abstraction would be to precompile reflection objects using javassist for use in environments where dynamic reflection is not supported.

### AOP

Another potential other use is to "optimize away" reflection when already dispatching requests through AOP.