Hide Forgot
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
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.
The differences between the jboss-service.xml files is probably related to SOA-495.
I was wrong about the client/jbossall-client.jar file, it is indeed the version from FP01.
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.
moved to CR1 as we still need to check out juddi/scout and why the client jar needs updating
Link: Added: This issue is related to SOA-880
Link: Added: This issue is related to SOA-881
Link: Added: This issue related SOA-880
Link: Removed: This issue related SOA-880
Verified in CR1