Application Server 7
  1. Application Server 7
  2. AS7-887

Support legacy ServiceMBeans in SAR deployments

    Details

    • Similar Issues:
      Show 10 results 

      Description

      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.

        Issue Links

          Activity

          Hide
          Guy Kaisin
          added a comment -

          Hi,

          this link should be useful:
          https://ci.jboss.org/hudson/job/WildFly-latest-master/

          Regards,

          Guy

          Show
          Guy Kaisin
          added a comment - Hi, this link should be useful: https://ci.jboss.org/hudson/job/WildFly-latest-master/ Regards, Guy
          Hide
          rajesh k
          added a comment -

          Thank you, I downloaded last successful build (wildfly-8.x.zip) from wildFly-latest-master. Pl kindly share required jars i can apply to EAP 6.0.1 to fix this issue.

          Regards,
          Rajesh.

          Show
          rajesh k
          added a comment - Thank you, I downloaded last successful build (wildfly-8.x.zip) from wildFly-latest-master. Pl kindly share required jars i can apply to EAP 6.0.1 to fix this issue. Regards, Rajesh.
          Hide
          Eduardo Martins
          added a comment -

          Rajesh, if you have eap support please use it, this is a community site, no SLAs here. If you don't have EAP support please start a topic on the community forums.

          Anyway, if you don't have support and want to stick with EAP I would move to the latest release instead, since EAP 6.1 includes all of this. An alternative is Wildfly, which includes latest features/fixes, such as https://issues.jboss.org/browse/WFLY-222

          Show
          Eduardo Martins
          added a comment - Rajesh, if you have eap support please use it, this is a community site, no SLAs here. If you don't have EAP support please start a topic on the community forums. Anyway, if you don't have support and want to stick with EAP I would move to the latest release instead, since EAP 6.1 includes all of this. An alternative is Wildfly, which includes latest features/fixes, such as https://issues.jboss.org/browse/WFLY-222
          Hide
          rajesh k
          added a comment -

          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.

          Show
          rajesh k
          added a comment - 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.
          Hide
          jaikiran pai
          added a comment -

          >> Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1.

          EAP 6.0.1 binary is a paid product and you are entitled to support. Where did you get it from? You might want to check with your team to see who has access to the customer service portal.

          >> 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.

          You already created 2 other JIRAs to ask that question. Please do use the JIRAs for such questions. The user forums are the place where this should be discussed.

          Show
          jaikiran pai
          added a comment - >> Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1. EAP 6.0.1 binary is a paid product and you are entitled to support. Where did you get it from? You might want to check with your team to see who has access to the customer service portal. >> 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. You already created 2 other JIRAs to ask that question. Please do use the JIRAs for such questions. The user forums are the place where this should be discussed.

            People

            • Assignee:
              Eduardo Martins
              Reporter:
              Matt Drees
            • Votes:
              10 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: