[
https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy...
]
rajesh k commented on AS7-887:
------------------------------
Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1. I need
your help on couple of thing we came across during migration. I went through many jboss
community forums as well on below issue.
We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's
workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to
make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions
support jars to register commonj jndi in Jboss 6.0.1 EAP.
will we able to use Commonj within EJB in JBoss 6.0.1 EAP as EJB spec prohibits to create
threads within EJB due to vendor licencing issues.
Pl help me in this.
Regards,
Rajesh.
Support legacy ServiceMBeans in SAR deployments
-----------------------------------------------
Key: AS7-887
URL:
https://issues.jboss.org/browse/AS7-887
Project: Application Server 7
Issue Type: Enhancement
Components: JMX
Reporter: Matt Drees
Assignee: Eduardo Martins
Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans
just fine. However, users may expect to be able to deploy older ServiceMBeans from
previous Jboss AS versions. Currently, attempting to do this results in a
ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't
exist anymore.
Ideally this would also involve supporting ServiceMBeans that extend
org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira