]
Max Rydahl Andersen commented on JBESB-2912:
--------------------------------------------
Its good to hear :) Now I just need to understand why AS 5.1 doesn't have that filter
since it means everyone using esb in the community will sure get redeploys, but also get
it when they don't want to.
No re-deployment of an altered package
--------------------------------------
Key: JBESB-2912
URL:
https://jira.jboss.org/jira/browse/JBESB-2912
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 4.7 CP1
Attachments: build.xml, dotNET.esb, FilePollerProject.tgz, jboss-esb.xml,
profile.diff
When deploying an ESB archive of a webservice_consumer1 QS, everything goes well.
However, when I update the ESB archive by deleting WEB-INF/jboss-web.xml in the WAR inside
and then overwrite the already deployed ESB with this new one, the deployer doesn't
pick it up and re-deployment never happens.
I also tried updating the index.jsp inside the WAR inside the ESB archive, and the
re-deployment didn't happen as well. When I delete the whole WAR from inside the ESB,
the re-deployment does happen. (And fails, which is expected.)
From these experiments I conclude that the re-deployment doesn't happen when you only
alter the WAR file inside the ESB archive and nothing else.
If necessary, I can attach both the original and altered ESB archives - didn't do so,
because they're both very easy to create.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: