Bug 778394 (SOA-878)

Summary:	Unexpected differences in IR5 build
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	Build Process	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified
Target Milestone:	---
Target Release:	4.3 CR1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-878
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-20 11:36:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Pechanec 2008-09-26 07:46:47 UTC

Date of First Response: 2008-09-26 05:03:10
project_key: SOA

There were unexpected differences found in the IR5 build, please explain them to accept IR5 build

Standalone build
Not present in 4.2 but are present in 4.3
deploy/juddi-service.sar 
client/ejb3-persistence.jar
lib/ejb3-persistence.jar
Can be the last one related to new console?

Differences to EAP
lib/hibernate-commons-annotations.jar
lib/hibernate-annotations.jar
lib/hibernate-entitymanager.jar
lib/hibernate-validator.jar
client/hibernate-commons-annotations.jar
client/hibernate-annotations.jar
client/jbossall-client.jar
client/hibernate-validator.jar
Can this be related to Seam FP?

all/conf/jboss-service.xml - Unified invoker is used for UserTransaction
production/conf/jboss-service.xml - JRMP invoker is used for UserTransaction
In EAP both configurations are using unified

Comment 1 Julian Coleman 2008-09-26 09:03:10 UTC

In the standalone build, client/ejb3-persistence.jar and lib/ejb3-persistence.jar
were added to support the embedded console.  deploy/juddi-service.sar  was
added to remove differences between embedded default and standalone.

The differences between SOA-P IR5 and EAP CP02 are because SOA-P is based
upon EAP FP01 (i.e. SEAM FP).  However, the different client/jbossall-client.jar
comes from the ESB build.

Comment 2 Julian Coleman 2008-09-26 09:11:57 UTC

The differences between the jboss-service.xml files is probably related to
SOA-495.

Comment 3 Julian Coleman 2008-09-26 09:30:55 UTC

I was wrong about the client/jbossall-client.jar file, it is indeed the version from FP01.

Comment 4 Julian Coleman 2008-09-26 09:32:57 UTC

Issue resolved as not a blocker for IR5 testing.

Separate issues for deploy/juddi-service.sar and jboss-service.xml
will be created and linked here.

Comment 5 trev 2008-09-26 09:38:25 UTC

moved to CR1 as we still need to check out juddi/scout and why the client jar needs updating

Comment 6 Julian Coleman 2008-09-26 09:48:09 UTC

Link: Added: This issue is related to SOA-880

Comment 7 Julian Coleman 2008-09-26 09:48:09 UTC

Link: Added: This issue is related to SOA-881

Comment 8 Julian Coleman 2008-09-26 09:48:55 UTC

Link: Added: This issue related SOA-880

Comment 9 Julian Coleman 2008-09-26 09:50:34 UTC

Link: Removed: This issue related SOA-880

Comment 10 Jiri Pechanec 2008-10-20 11:36:05 UTC

Verified in CR1