| Summary: | modeshape-web-jcr-rest-client is not bundled in distribution | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Build Process, Deployment, EDS | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER1 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.1.0.ER3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2293 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-26 11:10:44 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
2010-09-09 13:05:32 UTC
Candidate for SOA 5.1.0 Link: Added: This issue depends MODE-872 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. 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. The driver is going to be used outside VM if we want to use Teiid Designer to import Modeshape repo metadata. 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 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. In ER2, the rest client interface and jdbc interface will be included in the modeshape-client.jar 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. There is no modeshape-client.jar in ER2 There is a modeshape-client.jar in the eds/modeshape/client directory. Is there a different place you are expecting it? 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. updated installation to copy the modeshape-client.jar and teiid-client.jar to the client directory. Verified in ER3 |