Bug 778262 (SOA-762) - Need to add ejb3-persistence.jar to CR1 to support the new JON embedded console
Summary: Need to add ejb3-persistence.jar to CR1 to support the new JON embedded console
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-762
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process, Monitoring and Management
Version: 4.3 IR4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 IR5
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-08 19:00 UTC by Len DiMaggio
Modified: 2008-10-03 19:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-03 19:41:14 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-762 0 None None None Never

Description Len DiMaggio 2008-09-08 19:00:17 UTC
Date of First Response: 2008-09-08 15:24:58
project_key: SOA

The ejb3-persistence.jar need to be added to the next (CR1) build for the stand-alone ESB server to support the JON embedded.

Comment 1 Mark Little 2008-09-08 19:24:58 UTC
Tom told me earlier today that this will happen in the next ESB merge.

Comment 2 trev 2008-09-09 14:28:28 UTC
The only ejb3 file included in the standalone is ejb3x.jar, this file will have to be added to the exclude list when building soa esb skeleton

Comment 3 trev 2008-09-10 12:50:16 UTC
find jboss-soa-p-standalone.4.3.0/ -name  ejb3-persistence.jar
jboss-soa-p-standalone.4.3.0/jboss-esb/server/default/lib/ejb3-persistence.jar
jboss-soa-p-standalone.4.3.0/jboss-esb/client/ejb3-persistence.jar


Comment 4 Len DiMaggio 2008-10-03 19:41:14 UTC
[ldimaggi@ldimaggi 43_IR5_oct2]$ find . -name ejb3-persistence.jar  -print | grep standalone
./jboss-soa-p-standalone.4.3.0/jboss-esb/server/default/lib/ejb3-persistence.jar
./jboss-soa-p-standalone.4.3.0/jboss-esb/client/ejb3-persistence.jar

Verified fixed in IR5


Note You need to log in before you can comment on or make changes to this bug.