Bug 779846 (SOA-2206) - JackRabbit is shipped with SOA-P
Summary: JackRabbit is shipped with SOA-P
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2206
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB, Configuration
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA,5.1.0.ER7
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-06 13:29 UTC by Jiri Pechanec
Modified: 2011-08-11 10:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-11 05:10:15 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779845 0 urgent CLOSED Classloading conflict between ModeShape and JBoss ESB on Lucene 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 780815 0 high CLOSED Remove JcrNodeMatcher from jbpm.varmapping.xml 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2206 0 Major Closed JackRabbit is shipped with SOA-P 2013-07-09 06:19:32 UTC

Internal Links: 779845 780815

Description Jiri Pechanec 2010-08-06 13:29:14 UTC 
project_key: SOA

SOA-P is shipped with JackRabbit and JCR 1.0 API - present in jbossesb.esb/lib dir. Should not it be replaced with ModeShape? Is the use-case for which JackRabbit is used (Message Store) supported? I think it is not.
Should it be supported with ModeShape?
Comment 1 Kevin Conner 2010-08-06 15:01:43 UTC 
This is the same issue as SOA-2205, shipping a JCR implementation for our JCRMessageStoreImpl.
Comment 2 Anne-Louise Tangring 2010-09-22 12:56:42 UTC 
Candidate for SOA 5.1.0
Comment 4 Kevin Conner 2010-09-22 13:19:33 UTC 
Link: Added: This issue related SOA-2205
Comment 5 Jiri Pechanec 2010-09-22 13:41:43 UTC 
It is there since 4.2 coming from JBossESB, it was never supported.
Comment 6 Kevin Conner 2010-09-22 13:47:14 UTC 
The only references within the ESB are direct (but internal) through the JCRMessageStore and indirect through jBPM.

Both uses are as alternatives to providing a JCR implementation via JNDI.

We have never supported JCRMesageStore nor, to my knowledge, the jBPM usage through the platform.
Comment 7 trev 2010-12-06 15:40:31 UTC 
removed as it is not supported
Committed revision 7536.
Comment 9 Dana Mison 2011-01-05 00:14:39 UTC 
Writer: Added: dlesage
Comment 10 Jiri Pechanec 2011-01-06 07:55:15 UTC 
JCR 1.0 API is still present but Modeshape installs JCR 2.0 API in lib dir. Can't this lead to conflicts?
Comment 11 trev 2011-01-12 15:12:03 UTC 
added jcr-1.0.jar to the delete list Committed revision 7889.
Comment 12 Jiri Pechanec 2011-01-25 13:35:00 UTC 
Verified in ER7
Comment 13 David Le Sage 2011-02-11 05:06:46 UTC 
Temporarily reopening to update release note info.
Comment 14 David Le Sage 2011-02-11 05:08:42 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2206

The SOA Platform shipped with JackRabbit and JCR 1.0 API. As these are unsupported, they have been removed.
Comment 15 David Le Sage 2011-02-11 05:10:07 UTC 
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2206

The SOA Platform shipped with JackRabbit and JCR 1.0 API. As these are unsupported, they have been removed. Added: https://issues.jboss.org/browse/SOA-2206

The SOA Platform shipped with JackRabbit and JCR 1.0 API. As these are unsupported on this platform, they have been removed.
Comment 16 Martin Weiler 2011-08-11 10:27:21 UTC 
Link: Added: This issue relates to SOA-3261
Note You need to log in before you can comment on or make changes to this bug.