Bug 777997 (SOA-524)

Summary: SOA-P jboss-soa-p.4.2.0/jboss-as/tools missing "console" directory
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: tcunning
Component: Release ProcessAssignee: Mike Brock <cbrock>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: ldimaggi, rruss
Target Milestone: ---   
Target Release: 4.2 CP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-524
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-10 13:21:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 777906    
Bug Blocks: 777998, 778000, 778001, 778002, 778374    

Description tcunning 2008-04-24 22:29:06 UTC
Date of First Response: 2008-04-24 20:05:48
project_key: SOA

The soa-4.2.0.GA.zip GA build had a directory that contained the alternative database files for the ESB management console :

jboss-soa-p.4.2.0/jboss-as/tools/console

That directory is missing in the CP01 GA build I downloaded off of porkchop, and the early release CP01 that was provided to Toronto Hydro :

jboss-soa-p.4.2.0/jboss-as/tools

Comment 1 Len DiMaggio 2008-04-24 23:24:56 UTC
Link: Added: This issue depends SOA-434


Comment 2 Len DiMaggio 2008-04-24 23:32:20 UTC
Link: Added: This issue depends SOA-427


Comment 4 tcunning 2008-04-25 00:21:14 UTC
I don't think should block GA or require another build - the workaround we can present is that the files to be able to do this are present in the source distribution (soa-4.2.0.GA_CP01.src.zip).     I don't see anything in the db schema change scripts that will cause a problem here.

Comment 5 Len DiMaggio 2008-04-25 02:02:55 UTC
The files are here (in the src .zip):

soa-4.2.0-cp01/soa-work/esb/checkout/product/tools/console


Comment 6 Mark Little 2008-04-25 12:21:19 UTC
We'll fix this in the next CP. It can't go into the TP-FP since that is for new features only and not bug fixes.

Comment 7 Len DiMaggio 2008-04-25 16:21:18 UTC
Link: Removed: This issue depends SOA-427 


Comment 8 Len DiMaggio 2008-04-25 16:25:21 UTC
Link: Added: This issue is a dependency of SOA-525


Comment 9 Len DiMaggio 2008-04-25 20:07:22 UTC
Link: Added: This issue is a dependency of SOA-527


Comment 10 Len DiMaggio 2008-04-25 20:08:52 UTC
Link: Added: This issue is a dependency of SOA-528


Comment 11 Len DiMaggio 2008-04-25 20:13:00 UTC
Link: Added: This issue is a dependency of SOA-529


Comment 12 Len DiMaggio 2008-04-28 18:31:08 UTC
It's not as simple as we thought.

Part of the ESB console that we wanted to remove in SOA-434 is in (in the GA build):

/opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/tools/console

And part is in:

/opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/tools/console/console



Comment 13 tcunning 2008-04-28 19:50:29 UTC
I think what we need from the ESB project is 

tools/console/management/*
tools/console/management-esb/*
tools/console/management-web/*
MANAGEMENT-README.txt

Once these are laid down, we need to copy the JSP files from the SOA-P project into management-web.

Comment 14 tcunning 2008-04-28 22:46:38 UTC
Link: Added: This issue is related to SOA-526


Comment 15 Mike Brock 2008-06-02 07:53:17 UTC
Fixed

Comment 16 Jiri Pechanec 2008-06-10 13:21:31 UTC
Verified in CR1

Comment 17 nwallace 2008-09-25 19:46:30 UTC
Link: Added: This issue is a dependency of SOA-857