3:20 a.m.
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
The ESB deployer should redeploy the ESB if you modify the jboss-esb.xml, does this work?
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:20 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Lukáš Petrovický commented on JBESB-2912:
-----------------------------------------
When jboss-esb.xml is altered, it is redeployed.
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2912:
--------------------------------------
After removing the archive, the server did not undeploy it. After putting it back, the
server complained that it cannot deploy an already deployed service.
Using a fresh new .esb archive with a new version of jboss-esb.xml does not work for me.
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
Sorry, are you now saying that there is bug in the app server's deployer codebase?
Perhaps a log file would be a good idea, do you have one??
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2912:
--------------------------------------
A service with an http-gateway and a SOAPProxy action (which points to a valid wsdl) does
not publish any endpoint either.
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2912:
--------------------------------------
See the dotNET.esb attachment and try to obtain the wsdl of the published endpoint.
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ý
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2912:
--------------------------------------
Probably the issue should have a different Summary now...
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Martin Vecera updated JBESB-2912:
---------------------------------
Attachment: dotNET.esb
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
I have no idea what is going on now :)
Wait until we release 4.7 and then we can see how it behaves on that.
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
Can anyone add a better description of the problem to this issue?
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner reassigned JBESB-2912:
-----------------------------------
Assignee: (was: Trevor Kirby)
Trevor is chasing up via the SOA issue
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Trevor Kirby reassigned JBESB-2912:
-----------------------------------
Assignee: Trevor Kirby
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: Trevor Kirby
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBESB-2912:
-----------------------------------------
If the .esb archive is deployed in exploded form then even changes to jboss-esb.xml are
ignored. Seems that no changes inside exploded directory could trigger redeployment.
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ý
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:28 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2912:
--------------------------------
Fix Version/s: 4.7 CP1
Dominik, can you add your deployment to this issue in case it is related in some way?
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ý
Fix For: 4.7 CP1
Attachments: dotNET.esb
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:58 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Dominik Pospisil updated JBESB-2912:
------------------------------------
Attachment: FilePollerProject.tgz
Attaching deployment.
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ý
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:39 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Work on JBESB-2912 started by Tom Fennelly.
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:39 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly reassigned JBESB-2912:
-----------------------------------
Assignee: Tom Fennelly
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:35 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
Dominik, I just tried the FilePollerProject attachment... made changes to the esb config
file and it redeployed. Can you verify this again please?
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:14 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBESB-2912:
-----------------------------------------
I have checked this once again, and it still does not redeploy for me.
My environment
Fedora 12, x86_64
Sun JDK 1.6.0_13_x86_64
JBoss [SOA] 5.0.0.ER6_SOA (build: SVNTag=5.0.0.ER6_SOA date=200912181807)
Steps I am doing:
1) start the server
2) copy dir to ${JBOSS_HOME}/server/default/deploy
3) test the service
4) modify jboss-esb.xml inside deployment - message property of PrintLn Action
5) save file
6) test the service again
After saving modified jboss-esb.xml config, nothing happends and the new message is not
reflected until the server is restarted or the archive manually redeployed.
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:09 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Work on JBESB-2912 stopped by Tom Fennelly.
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Emanuel Muckenhuber commented on JBESB-2912:
--------------------------------------------
FYI - by default the hot-deployment checks were limited to certain files, which is
configured in server/${config}/conf/bootstrap/profile.xml. There is a bean called <bean
name="ModificationCheckerFilter" /> listing the deployment descriptors which
can trigger a redeploy of a deployment.
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
Fix For: 4.7 CP1
Attachments: dotNET.esb, FilePollerProject.tgz
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Burr Sutter commented on JBESB-2912:
------------------------------------
Steps to reproduce (not this is a problem for ALL .esb archives, no hot deployment)
1) Start the SOA-P Server
2) Modify the helloworld quickstart build.xml to be "exploded"
<property name="deploy.exploded" value="true"/>
(see attached)
3) "ant deploy" helloworld
look inside your deploy directory, you should see
Quickstart_helloworld.esb as an unzipped archive, a directory
4) "ant runtest" helloworld
see 2 Hello World messages printed to the server console by the 2 actions defined in the
jboss-esb.xml
5) Using a text editor, modify deploy\Quickstart_helloworld.esb\META-INF\jboss-esb.xml
Simply copy action1 and make it action3, the result should be Hello World printing 3 times
now.
(see attached)
But the change to jboss-esb.xml is not detected.
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
Fix For: 4.7 CP1
Attachments: build.xml, dotNET.esb, FilePollerProject.tgz, jboss-esb.xml
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Burr Sutter updated JBESB-2912:
-------------------------------
Attachment: build.xml
Attached build.xml for quickstart helloworld, so it deploys exploded
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
Fix For: 4.7 CP1
Attachments: build.xml, dotNET.esb, FilePollerProject.tgz, jboss-esb.xml
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Burr Sutter updated JBESB-2912:
-------------------------------
Attachment: jboss-esb.xml
attached modified jboss-esb.xml that was edited in the deploy folder.
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
Fix For: 4.7 CP1
Attachments: build.xml, dotNET.esb, FilePollerProject.tgz, jboss-esb.xml
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Burr Sutter commented on JBESB-2912:
------------------------------------
This issue has a very negative impact on the usability of JBoss Developer Studio - by
default it deploys exploded archives for an end-user to "see" changes, they need
to restart the server.
JBIDE-5534
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
Fix For: 4.7 CP1
Attachments: build.xml, dotNET.esb, FilePollerProject.tgz, jboss-esb.xml
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:22 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2912:
--------------------------------
Priority: Blocker (was: Major)
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
OK... I've tried this again on the ESB and it is not an issue there anyway... the
redeploy happens. I'll try with a copy of SOA-P now, but I would have thought it
would be the same.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:57 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
OK... Kev tells me that this is suspected to be an AS5 specific/related issue. I
didn't pick that up from the comments... sorry. Will try it on that now.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:58 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBESB-2912:
--------------------------------------------
Tom, which download (link please ;) and configuration in that download did you use ?
I'll like to compare what I see with yours - also just to know if there is some other
kind of deployment we need to know about in tools.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:01 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
Tested this on AS5 (using the helloworld QS) and it redeployed.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
Tried FilePoller on AS5.
Tried Burr's modified helloworld on AS5.
Tried both of the above together on AS5.
In All cases, the redeploy happened. Need to download and try SOA-P.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
@Max: Which download are you referring to Max? AS5? I'm using AS 5.1.0.GA (Release
ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053).
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:47 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
Tried on Java5 and Java6 (AS5). No difference - redeploy working.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2912:
-----------------------------------
FYI, I tried on:
- Fedora 11 (Linux 2.6.30.9-102.fc11.i686.PAE)
- Sun JDK 1.5.0_22
- JBoss AS 5.1.0
- JBoss ESB 4.7 CP
(https://svn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP)
- default server config
, using Burr's helloworld instructions exactly - and redployment worked fine...
Then, I tried on:
- Fedora 11 (Linux 2.6.30.9-102.fc11.i686.PAE)
- Sun JDK 1.6.0_17
- JBoss SOA-P 5.0.0 ER5
- default server config
, using Burr's helloworld instructions exactly - and redployment did NOT happen.
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
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-2912:
------------------------------
Attachment: profile.diff
diff jboss-soa-p.5.0.0/jboss-as/server/default/conf/bootstrap/profile.xml
jboss-5.1.0.GA/server/default/conf/bootstrap/profile.xml > profile.diff
(regarding the ModificationCheckerFilter)
I've attached profile.diff
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
Okay, so we need to modify that profile.xml file as part of our installation in a similar
manner to the way in which we do for the service bindings.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:42 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBESB-2912:
--------------------------------------------
But you should have this filter already in place if you use EAP5 - or EAP5 it self have a
similar issue still.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
SOA 5 is based on EAP 5, which is why we are now seeing this.
This filter did not exist in AS 5.1.0, as the diff which David has added shows.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBESB-2912:
--------------------------------------------
i'm utterly confused now ;)
The filter is there to make the redeployment *sane*! Without it deployment happens
*constantly*, even when file changes which should *not* trigger a redeploy.
As far as I know, this filter should *not* be removed, it should rather be extended.
It must be an error that it is not in AS 5.1.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
The filter restricts the file list considered for redeploying, a restriction which was not
present in AS 5.1.0.
For servers which include this filter, we need to modify the regexp configuration so that
it also picks up ours.
We are *not* removing this filter, and nobody has ever stated this.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
Max... we'll be checking this filter configuration as part of esb-deploy/soa-build
process (need to see how this is done on SOA-P) and extending it to include the
jboss-esb.xml config, if it's not already part of the filter. As Kev says, it will
not be removed.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2912:
-------------------------------------
Tom, the SOA build just installs us into an EAP server. It is our installation script
that needs to handle this, nothing in SOA.
This comes into the same area as the service bindings.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly closed JBESB-2912.
-------------------------------
Resolution: Done
As per instruction from Kev, I have updated the install script (Ant) to do a search and
replace on the regex pattern, adding jboss-esb.xml as one of the files to be
watched/filtered.
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2912) No re-deployment of an altered package
[
https://jira.jboss.org/jira/browse/JBESB-2912?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2912:
-------------------------------------
branches/JBESB_4_7_CP: 31030
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5255
days inactive
5333
days old
45 comments
10 participants
participants (10)
-
Burr Sutter (JIRA) -
David Ward (JIRA)
-
Dominik Pospisil (JIRA)
-
Emanuel Muckenhuber (JIRA)
-
Kevin Conner (JIRA)
-
Lukáš Petrovický (JIRA)
-
Martin Vecera (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Tom Fennelly (JIRA)
-
Trevor Kirby (JIRA)