Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2267

Schema tool moves juddi DatabaseInititalizer into another file which causes riftsaw deployment issue

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 5.1.0.ER1
    • Fix Version/s: 5.1.0.ER2
    • Component/s: Tooling
    • Labels:
      None
    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-2267

      Using the Schema Tool to move org.jboss.internal.soa.esb.dependencies.DatabaseInitializer from deploy/jbossesb-registry.sar/juddi-ds.xml into deploy/jbossesb-registry.sar/META-INF/juddi-service.xml caused an error when the user deployed the BPEL engine. To fix this problem, a new build.xml file has been supplied. This file does not create a separate /deploy/jbossesb-registry.sar/META-INF/juddi-service.xml file but merges the new prototype juddi-service.xml into /deploy/jbossesb-registry.sar/juddi-ds.xml. As a result, uers can now deploy the BPEL engine after having run the Schema Tool.
      Show
      https://issues.jboss.org/browse/SOA-2267 Using the Schema Tool to move org.jboss.internal.soa.esb.dependencies.DatabaseInitializer from deploy/jbossesb-registry.sar/juddi-ds.xml into deploy/jbossesb-registry.sar/META-INF/juddi-service.xml caused an error when the user deployed the BPEL engine. To fix this problem, a new build.xml file has been supplied. This file does not create a separate /deploy/jbossesb-registry.sar/META-INF/juddi-service.xml file but merges the new prototype juddi-service.xml into /deploy/jbossesb-registry.sar/juddi-ds.xml. As a result, uers can now deploy the BPEL engine after having run the Schema Tool.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      Using schema tool moves org.jboss.internal.soa.esb.dependencies.DatabaseInitializer from deploy/jbossesb-registry.sar/juddi-ds.xml into deploy/jbossesb-registry.sar/META-INF/juddi-service.xml which causes deployment error while deploying BPELEngine. If org.jboss.internal.soa.esb.dependencies.DatabaseInitializer is in old place (properly configured for selected db), deployment is ok.

        Gliffy Diagrams

          Attachments

          1. build.xml
            30 kB
          2. juddi-service.xml
            0.4 kB
          3. server.log
            134 kB

            Issue Links

              Activity

                People

                • Assignee:
                  jcoleman Julian Coleman
                  Reporter:
                  jsedlacek Jiri Sedlacek
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: