Red Hat Bugzilla – Bug 779156
No re-deployment of an altered package
Last modified: 2010-02-05 03:44:21 EST
Date of First Response: 2009-12-09 05:41:41
Link: Added: This issue depends JBESB-2912
Trev to get more info for Kev
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.
Link: Added: This issue is a dependency of JBIDE-5534
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)
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.
Ooops... typo in last comment. Should have said "which includes SOA-P".
This should be present in ER7
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.
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
Re-deployment works as expected in ER8.