3 Replies Latest reply on Aug 9, 2011 12:03 PM by Bernd Eckenfels

    Deployment of (ordinary) JAR files

    Bernd Eckenfels Novice

      Hello,

       

      while trying to deploy an EJB-JAR, which contained only a Message Driven Bean (with EJB3 Annotion) I noticed that AS7.0.0 Stand Alone (via deployment folder) did not do anything with that JAR (at least it logged nothing). As I see in the documentation different deployers should analyse the files. In case of a JAR it can be a EJB-JAR or maybe an JDBC driver (recognized by the META-INF/service/ entry).

       

      However I wonder what JBoss AS7 is supposed to do with a JAR which does not contain deployable content (or as in my case it contains content which it does not recognize as deployable).Is AS7 adding the pain jar to a classpath or ignoring it?

       

      If it is ignoring it, I would strongly recommend to add code which can detect an "unknown" deployment artifact and issue a warning, or maybe even geenrate a ".failed" marker file.

       

      Can somebody hint me, where I could see what that deployment artifact's role is in the running AS? I havent found a entry in the management console telling me that.

       

      Greetings

      Bernd

        • 1. Re: Deployment of (ordinary) JAR files
          Bernd Eckenfels Novice

          Minor update, the deployed EJB-JAR does show up in the JNDI, but with no beans or ressources (which is expected):

           

          [standalone@localhost:9999 /] /subsystem=naming:jndi-view
          {
              "outcome" => "success",
              "result" => {
          ...

                  "applications" => {
                      "net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT.jar" => {
                          "java:app" => {"AppName" => {
                              "class-name" => "org.jboss.as.naming.context.ModularReference",
                              "value" => "net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT"
                          }},
                          "modules" => {"net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT" => {"java:module" => {"ModuleName" => {
                              "class-name" => "org.jboss.as.naming.context.ModularReference",
                              "value" => "net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT"
                          }}}}
                      },


          ...
          • 2. Re: Deployment of (ordinary) JAR files
            jaikiran pai Master

            1) AS 7.0.0.Final did not have support for MDBs

            2) MDBs aren't bound in JNDI. That's why you don't see the JNDI names

             

            Try latest AS7 nightly build which has MDB support.

            1 of 1 people found this helpful
            • 3. Re: Deployment of (ordinary) JAR files
              Bernd Eckenfels Novice

              jaikiran pai wrote:

              1) AS 7.0.0.Final did not have support for MDBs

              Yes, I know (now). However my question was more about the case when you drop a normal JAR, since I would expect the deployer to reject it on verification if it does not contain any deployable/managed ressource.

               

              Thats why I asked, if a "normal" JAR is actually considered deployable for some reasons, because otherwise I would add a JIRA for missing warning/error about "empty deployments".

              2) MDBs aren't bound in JNDI. That's why you don't see the JNDI names

              Where in the management I can find more about the content (modules) of a deployed artifact. In the old JMX console all the objects have been listed. Is there a similiar view in the new tree?

               

              Thans for your help

              Bernd