Bug 779142 (SOA-1540) - Schema tool does not create datasource for messaging
Summary: Schema tool does not create datasource for messaging
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1540
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.0.0 ER1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.0.0 GA,5.0.0 ER2
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-22 07:16 UTC by Jiri Pechanec
Modified: 2009-12-02 17:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-02 17:06:24 UTC
Type: Bug


Attachments (Terms of Use)
build.xml (15.58 KB, text/xml)
2009-10-22 18:16 UTC, Jiri Pechanec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1540 0 None Closed Schema tool does not create datasource for messaging 2012-05-30 10:03:34 UTC

Description Jiri Pechanec 2009-10-22 07:16:02 UTC
Date of First Response: 2009-10-26 10:12:31
project_key: SOA

The schema tool tries to create new datasource for JBoss Mesaging in file jms-ds.xml. This file is already present in EAP 5 so schema tool does not create the datasource and the dependencies will fail.

Comment 1 Jiri Pechanec 2009-10-22 18:16:09 UTC
The attached file contains hotfix for the issue + it also enable jUDDI configuration

Comment 2 Jiri Pechanec 2009-10-22 18:16:09 UTC
Attachment: Added: build.xml


Comment 3 Julian Coleman 2009-10-26 14:12:31 UTC
Fixes from attachment incorporated in revision 3965 of:
  build-tools/resource/schema-tool/build.xml

Commit message:
  SOA-1540
  Rename messaging datasource file.
  Also modify the jUDDI configuration in .../deployers/esb.deployer/.
  From Jiri Pechanec.


Comment 4 Jiri Pechanec 2009-12-02 06:05:35 UTC
Verified in ER4

Comment 5 Julian Coleman 2009-12-02 17:06:24 UTC
Added 5.0.0 GA to fix version.


Note You need to log in before you can comment on or make changes to this bug.