[EMAIL PROTECTED] wrote:
1. @Tx tags can only be used on classes but not interfaces (in the case
of MBeans)
a. reason this would be handled by the MBean deployer adding a
transaction interceptor rather than AOP proper.
b. there is no framework within jboss for XMBeans using attribute
tags to specify interception
Use EJBs.
2. There is no way to depend upon the creation of entity managers
(meaning a xxx.par file results in no mbean being created less its
deployment which is created before the entities inside are deployed and
before its EntityManagers.xxx is bound to jndi) which makes it difficult
to use them outside of service beans.
This has been fixed in next release. There is an MBean created for each
persistence unit. You can either depend on it, or...if you are using
EJBs, the dependency will be automatically figured out. <depends> is
now available in jboss.xml for ejbs
3. Service Beans have no way to declare multiple instances (such as
through XML) and must be statically defined on a 1-1 basis with classes
Fixed in next release. jboss.xml will support service bean declaration.
4. Service beans have no way to declare configurable dependency
injection. (AOP does not provide a way to get a services name if it
were to very other than reflection upon attribute tags which leads back
to #3)
<ejb-ref> etc. will work in next release. No <depends
optional-attribute> yet though.
5. unwrapped deployment of par files appears to be non-functional
you mean, exploded pars?
6. dynamic load time weaving appears to be too course grained (on/off
with include/exclude patterns rather than deployable pattern definitions)
Reason I bring this up:
I'm attempting to reorganize JBMS to use the latest JBoss tech, however
service beans are not suited to the task which requires using
traditional xmbeans and mbeans. However, doing this requires looking up
the EntityMangers.xxx and doing a manual injection. However it is
difficult to time startup properly on a coarse deployment (ear/sar/etc
rather than using prefix and seperate deployments) because the depends
tag cannot be used.
Suggestions:
1. XMBean framework should integrate more with the AOP framework at
least in the use of annotations such that interceptors/etc can be used
in the method level intercepts, patterns should be analyzed and proxy
type interceptors deployed for beans with annotations.
In the works for JBoss 5 in conjunction with MC.
2. EJB3 deployer should create an MBean for each entity manager bound to
JNDI and possibly for each entity bean deployed
yes on entity manager (already there) no for each entity bean (doesn't
make sense)
3. A more comprehensive framework with regards to service beans should
emerge which allows base definitions to be described through attributes
and instance/dependency infromation through XML.
done.
4. unwrapped par/ejb3 deployments should be supported.
Bizarre, probably just a simple bug.
Bill
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
