The jboss-common.jar dependency still exists. Why would it matter with other app servers? Its only using a few org.jboss classes.
Read this and let me know if it answers your config questions:
For one the packaging becomes lighter. It may not be an issue but have this fear that there might be some conflicts with maybe like xml parsers, etc.
The javabean style attribute setting sort of takes away the generic "property based" configuration that was possible in the previous release. Wonder if I could try to exhibit the same behavior in a roundabout.
Basically I could at run-time construct a bunch of xml based attribute specification and pass it on to the AspectDefinition as an Element and whenever XmlLoadable was called I could cleanly parse and pick out all these name based attributes. These attributes I'd store in a Map and simply retrieve it by name. This is un-structured but gives the flexibility I need for my requirements.
I noticed that even a "Document" could be set as a javabean attribute in RC2. Could you illustrate with an example, I could maybe do the same to achieve what I managed in RC1
See section 4.4.4. You can write your own factory by implementing AspectFactory which accepts an Element.
That helps, thanks a lot.