3 Replies Latest reply on Mar 20, 2008 5:51 AM by kconner

    Which files may I write when I write code to a .esb package

    lafbarbosa

      Hi people,

      I've looked at quickstart samples and I saw that we may put some other XML files into. Files like smooks-*.xml, jbm-queue-service.xml, jbmq-queue-service.xml, deployment.xml, jbossesb-gateway.xml, jbossesb-listener.xml, besides jboss-esb.xml.

      Please, which of them are auto-generated and which may be written by the developer?

      Thanks in advance!

      Regards,

      Luiz

        • 1. Re: Which files may I write when I write code to a .esb pack
          lafbarbosa

          Another kind of files are juddi.properties and, when I use JNDI, jndi.properties. Has this last one always the same content (keys, not values)?

          Does anybody know if these files will be always, for any kind of .esb package, in the development directory of a .esb package, as we can see in the samples of quickstart?

          • 2. Re: Which files may I write when I write code to a .esb pack
            kconner

            The files all have different purposes.

            jbm-queue-service.xml and jbmq-queue-service.xml are MBean service definitions and define the local message queues that are associated with the ESB services. These can be deployed internal or external to the esb archive.

            deployment.xml defines the dependencies of the ESB artifact, for example on the queues created above, so that you can order the startup of these artifacts.

            jboss-esb.xml contains the configuration of the ESB.

            jbossesb-gateway.xml and jbossesb-listener.xml are no longer used

            smooks-*.xml contain the configuration for smooks based transformations.

            • 3. Re: Which files may I write when I write code to a .esb pack
              kconner

               

              "lafbarbosa" wrote:
              juddi.properties and, when I use JNDI, jndi.properties.

              These files are only of use if you are running an ESB service/client outside of the standalone ESB server or an AS. If you are deploying an .esb artifact then they are not required.