5 Replies Latest reply on Jan 28, 2007 11:11 PM by Shah Alam

    Can a .par file be deployed directly.....

    Mike Duffy Novice

      Can a .par file be deployed directly to the sever/default/deply directory or must the .par file be contained in an .ear file?

      When I try to deploy directly, the entity beand are not found. :(

      Is it absolutely necessary to use a .par file for entity beans?

      Thx.

      Mike

        • 1. Re: Can a .par file be deployed directly.....
          Mike Duffy Novice

          If I wrap all the entity beans into a *..ejb3 file and then deploy the file to /server/default/deploy it all seems to work fine.

          However, this forces me to use the system default values (no persistence.xml).

          Is there any way to deploy a *.par file directly without putting it in an *.ear file?

          Thx.

          Mike

          • 2. Re: Can a .par file be deployed directly.....
            Bill Burke Master

            1) You should be able to put a persistence.xml file within a .ejb3 file and deploy EJBs along with persistent entities. This is not spec compliant, but it is what we will support in JBoss.

            2) You should be able to deploy a .par on its own.

            If you are not able to do #1 and #2 then please log a JIRA bug.

            Thanks,

            Bill

            • 3. Re: Can a .par file be deployed directly.....
              Mike Duffy Novice

              Thx.

              I was not able to deploy a seperate *.par for my application. I may have some configuration error.

              As a test I will break apart the *.ear file for TrailBlazer application and see if I can depoly seperate *.par and *.ejb3 files.

              I'll let you know how this goes later tonight.

              Mike

              • 4. Re: Can a .par file be deployed directly.....
                Mike Duffy Novice

                When I break apart the EJB3Trail.ear and place the components in /opt/jboss/server/default/deploy, I get the following error.

                javax.naming.NameNotFoundException: managedEntityFactory.cal not bound
                at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
                at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
                at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
                at org.jnp.server.NamingServer.lookup(NamingServer.java:278)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
                at javax.naming.InitialContext.lookup(InitialContext.java:351)

                I am not sure if this is a bug in JBoss or a configuration error on my part.

                I am placing the application.xml in /opt/jboss/server/default/deploy/EJB3Trail/META-INF

                Should this work?

                Thx.

                Mike

                • 5. Re: Can a .par file be deployed directly.....
                  Shah Alam Newbie

                  I also encouonterd a similer problem while trying to deploy all my entities and session beans in the ejb3, but persistance.xml dosent seems to work. In that case I need to make entries in persistance.properties.