Bug 778430 (SOA-912)

Summary: verify difference in deployed services between 4.2 and 4.3
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Aleksandar Kostadinov <akostadinov>
Component: ConfigurationAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 IR1, 4.3 IR2, 4.3 IR3, 4.3 IR4, 4.3 IR5   
Target Milestone: ---   
Target Release: 4.3 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-912
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-28 14:45:40 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Aleksandar Kostadinov 2008-10-04 12:01:34 UTC 
Date of First Response: 2008-10-14 11:36:58
project_key: SOA

Please look at the additional services present in 4.3 IR5 compared to 4.2 CP02 and verify these are expected:

Embedded:
jboss.jca:service=RARDeployment,name='mail-ra.rar'
jboss.esb:deployment=slsb.esb

Standalone:
jboss.esb:deployment=slsb.esb
jboss.jca:service=RARDeployment,name='mail-ra.rar'
jboss:service=juddi
2 x jboss.web.deployment:war=juddi.war,id=##### (two of them instead of one as in the prev version)

For full listing, see artifacts:
http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-unix-scripts/55/
http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-unix-scripts/56/
Comment 1 Julian Coleman 2008-10-14 15:36:58 UTC 
slsb.esb is new in SOA-P 4.3
juddi-service.sar is now shipped with the standalone version.
Comment 2 Julian Coleman 2008-10-16 15:05:21 UTC 
mail-ra.rar was not shipped as part of EAP 4.3.0 CP01 (which was the base
for SOA 4.2.0 CP02).  (Note, that it was shipped as part of the SEAM component,
but not in the AS part).
Comment 3 Julian Coleman 2008-10-16 15:20:52 UTC 
juddi.war is found at:

  server/default/deploy/jbossesb.sar/juddi.war
  server/default/deploy/juddi-service.sar/juddi.war

This is why there are two instances in jboss.web.deployment.

As an extension to the earlier comment - These are additions because we now
ship the juddi-service.sar from the EAP in standalone SOA-P 4.3.0 (see SOA-880).