Bug 779907 (SOA-2267) - Schema tool moves juddi DatabaseInititalizer into another file which causes riftsaw deployment issue
Summary: Schema tool moves juddi DatabaseInititalizer into another file which causes r...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2267
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER2
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-07 10:55 UTC by Jiri Sedlacek
Modified: 2015-08-02 23:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-01 03:21:41 UTC
Type: Bug

Attachments (Terms of Use)
server.log (133.52 KB, text/x-log)
2010-09-07 10:56 UTC, Jiri Sedlacek 		no flags Details
build.xml (30.09 KB, text/xml)
2010-09-09 09:11 UTC, Julian Coleman 		no flags Details
juddi-service.xml (457 bytes, text/xml)
2010-09-09 09:11 UTC, Julian Coleman 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779852 0 high CLOSED schema tool missing mbean and producing invalid configuration Persistence 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2267 0 None None None Never

Internal Links: 779852

Description Jiri Sedlacek 2010-09-07 10:55:04 UTC 
project_key: SOA

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.
Comment 1 Jiri Sedlacek 2010-09-07 10:56:05 UTC 
Attachment: Added: server.log
Comment 2 Julian Coleman 2010-09-09 08:56:25 UTC 
Link: Added: This issue is related to SOA-2212
Comment 3 Julian Coleman 2010-09-09 09:11:30 UTC 
Updated schema tool build.xml and juddi-service.xml attached.
Please replace the files in .../tools/schema with these.

The attached build.xml does not create a separate
.../deploy/jbossesb-registry.sar/META-INF/juddi-service.xml
but merges the new prototype juddi-service.xml into
.../deploy/jbossesb-registry.sar/juddi-ds.xml

Having the separate file may be causing problems similar to those
in JBESB-3395 and  JBAS-7438.
Comment 4 Julian Coleman 2010-09-09 09:11:30 UTC 
Attachment: Added: build.xml
Attachment: Added: juddi-service.xml
Comment 5 Jiri Sedlacek 2010-09-09 10:06:36 UTC 
Tested and working properly.
Comment 6 Julian Coleman 2010-09-09 11:06:27 UTC 
Resolved with revision 6486 of:
  build-tools/schema-tool/juddi-service.xml
  build-tools/schema-tool/build.xml

Commit message:
  SOA-2212
  SOA-2267
  In build.xml, do not create a separate:
    .../deploy/jbossesb-registry.sar/META-INF/juddi-service.xml
  file but merge in the contents of the schema tool juddi-service.xml to:
    .../deploy/jbossesb-registry.sar/juddi-ds.xml 
  
  The schema tool juddi-service.xml now only contains the mbean template and is
  no longer a complete XML file.

  Tested by Jiri Sedlacek.
Comment 7 Jiri Sedlacek 2010-10-26 08:16:35 UTC 
verified in 5.1.0.ER3
Comment 8 David Le Sage 2011-03-01 03:18:25 UTC 
Temporarily reopening to update release note info.
Comment 9 David Le Sage 2011-03-01 03:21:33 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: 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.
Note You need to log in before you can comment on or make changes to this bug.