4:48 a.m.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=comments#action_12388767 ]
Kevin Conner commented on JBESB-1359:
-------------------------------------
This part has nothing to do with the ESB, it is controlled by the AS main deployer.
If you need to have a dependency on the war file then you should specify this in the
deployment.xml file.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner closed JBESB-1359.
-------------------------------
Resolution: Rejected
This is a configuration issue.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Martin Vecera reopened JBESB-1359:
----------------------------------
Note from Kevin: It looks as if it is not possible to specify a dependency on a war file.
The AbstractWebContainer creates the service MBean using the hashcode of the URL so you
cannot rely on it for dependencies.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Mark Little updated JBESB-1359:
-------------------------------
Fix Version/s: 4.2.1 CP1
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner reassigned JBESB-1359:
-----------------------------------
Assignee: Kevin Conner
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Work on JBESB-1359 started by Kevin Conner.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=comments#action_12388885 ]
Kevin Conner commented on JBESB-1359:
-------------------------------------
This is really an issue with the AS deployers but we will have to handle this situation.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner closed JBESB-1359.
-------------------------------
Resolution: Done
I have modified the deployer to support <esb-depends> tags within deployment.xml.
This tag takes the name of the war file, which must be an immediate sub deployment of the
esb artifact, and creates a dependency on it.
e.g. <esb-depends>Performance6.war</esb-depends>
Included in revision 16938.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner closed JBESB-1359.
-------------------------------
Fix Version/s: 4.3
Resolution: Done
Trunk fixed in revision 17048.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1, 4.3
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner reopened JBESB-1359:
---------------------------------
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1, 4.3
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6025
days inactive
6038
days old
10 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Mark Little (JIRA)
-
Martin Vecera (JIRA)