Bug 779156 (SOA-1551) - No re-deployment of an altered package
Summary: No re-deployment of an altered package
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1551
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.0 GA,5.0.0 ER8
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-26 08:20 UTC by Lukáš Petrovický
Modified: 2010-02-05 08:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-05 08:44:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1551 0 None None None Never

Description Lukáš Petrovický 2009-10-26 08:20:15 UTC 
Date of First Response: 2009-12-09 05:41:41
project_key: SOA

See JBESB-2912
Comment 1 Lukáš Petrovický 2009-10-26 08:20:31 UTC 
Link: Added: This issue depends JBESB-2912
Comment 2 trev 2009-12-09 10:41:41 UTC 
Trev to get more info for Kev
Comment 3 Burr Sutter 2009-12-22 02:23:52 UTC 
If the .esb archive is deployed zipped then it "sees" updates to jboss-esb.xml file
if the .esb archive is deployed exploded then changes to jboss-esb.xml are ignored
The IDE uses the exploded variation and those changes are not seen.
Comment 4 Kevin Conner 2010-01-06 09:16:26 UTC 
Link: Added: This issue is a dependency of JBIDE-5534
Comment 5 Max Rydahl Andersen 2010-01-08 12:45:14 UTC 
Just to be clear, the IDE can use both exploded and non-exploded deployment - we just default to exploded since that is (normally) more efficient (i.e. copying  a few bytes vs MB's of jar)
Comment 6 Tom Fennelly 2010-01-12 13:05:17 UTC 
ESB install scripts updated to mod the profile.xml and include jboss-esb.xml in the mod filter bean's regex for AS5 based targets (which includes SOA-5).  Changes committed.
Comment 7 Tom Fennelly 2010-01-12 13:06:22 UTC 
Ooops... typo in last comment.  Should have said "which includes SOA-P".
Comment 8 Kevin Conner 2010-01-14 09:57:43 UTC 
This should be present in ER7
Comment 9 Kevin Conner 2010-01-15 14:59:00 UTC 
Sorry, I thought you were installing ESB directly into the server but have just found out that there is a copy stage inbetween.

You will need to add the profile.xml to your copy stage in order to pick up Tom's fix.
Comment 10 trev 2010-01-18 12:07:05 UTC 
committed builders/eap/post-patch/patch_bootstrap_profile.xml Rev 4801

If we change the build to use the esb install process to install directly into esb, this needs removing
Comment 11 Lukáš Petrovický 2010-02-05 08:44:21 UTC 
Re-deployment works as expected in ER8.
Note You need to log in before you can comment on or make changes to this bug.