Bug 779934 (SOA-2293) - modeshape-web-jcr-rest-client is not bundled in distribution
Summary: modeshape-web-jcr-rest-client is not bundled in distribution
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2293
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Build Process, Deployment, EDS
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.ER3
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-09 13:05 UTC by Jiri Pechanec
Modified: 2010-10-26 11:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-26 11:10:44 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Jiri Pechanec 2010-09-09 13:05:32 UTC
project_key: SOA

modeshape-web-jcr-rest-client is not bundled in distribution but it is required by Modeshape JDBC  driver of out-of-VM access

Comment 1 Anne-Louise Tangring 2010-09-10 20:51:05 UTC
Candidate for SOA 5.1.0

Comment 2 Van Halbert 2010-09-14 14:05:21 UTC
Link: Added: This issue depends MODE-872


Comment 3 Van Halbert 2010-09-14 14:05:22 UTC
The jdbc driver is inclusive of the rest client.   However,  using the jdbc driver out side the VM to execute queries is not completed.   It currently can only be used in Teiid Designer to import ModeShape metadata to build the physical model and the ModeShape VDB.

Comment 4 Van Halbert 2010-09-14 14:44:05 UTC
After revisiting the ERD, the intended use of the ModeShape jdbc driver was within the VM.   It was to be used in coordination with Teiid, when executing a query thru Teiid to access ModeShape.     The driver, in this release, wasn't meant to be used to outside the VM for executing queries.  It's only purpose was to assist in building the ModeShape VDB by importing the metadata from an existing ModeShape repository.

If this isn't the intention, then this needs to be revisited with Ken.

Comment 5 Jiri Pechanec 2010-09-14 14:48:46 UTC
The driver is going to be used outside VM if we want to use Teiid Designer to import Modeshape repo metadata.

Comment 6 Jiri Pechanec 2010-09-14 14:50:32 UTC
See in ERD
EDS-REPO-3-A
This would involve a JDBC driver on top of ModeShape that can report metadata (and thus imported via Designer) and accept a limited form of

Comment 7 Van Halbert 2010-09-14 15:36:30 UTC
I guess I phrased it wrong above or made it too wordy. 

The importing of metadata using the jdbc driver does work.   I just retested ER1 using the modeshape-jdbc driver.   However, the jdbc driver cannot be used in Designer to perform data preview of the ModeShape model.    You must create the VDB where JNDI name must be set to ModeShapeDS and the translator set to 'modeshape'.  Then manually deploy the vdb to the SOA-P server.   Then you should be able to execute the query:  'select * from <tablename>'   using the Teiid jdbc driver.



Comment 8 Van Halbert 2010-09-16 18:55:03 UTC
In ER2, the rest client interface and jdbc interface will be included in the modeshape-client.jar

Comment 9 Anne-Louise Tangring 2010-09-21 18:14:13 UTC
You can't have fixed version set to both SOA 5.1.0 and Future. If this issue needs to be split into two, then please do so. If not, you need to pick one Fixed Version.


Comment 10 Jiri Pechanec 2010-10-11 12:40:57 UTC
There is no modeshape-client.jar in ER2

Comment 11 Van Halbert 2010-10-11 23:55:07 UTC
There is a modeshape-client.jar  in the eds/modeshape/client directory.  Is there a different place you are expecting it?

Comment 12 Jiri Pechanec 2010-10-12 10:41:18 UTC
It probably slightly philosophical question :-)

But IMHO the logical place for (not only) ModeShape client libs is client dir of application server. The same probably applies to Teiid.


Comment 13 Van Halbert 2010-10-14 15:28:39 UTC
updated installation to copy the modeshape-client.jar  and teiid-client.jar to the client directory.

Comment 14 Jiri Pechanec 2010-10-26 11:10:44 UTC
Verified in ER3


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