Bug 780116 (SOA-2485)

Summary: ModeShape JDBC driver behavior is not fully logical
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER3   
Target Milestone: ---   
Target Release: 5.1.0.ER4   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2485
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-11 09:26:09 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-10-27 11:32:27 UTC 
project_key: SOA

The JDBC driver behaves illogically in specific situations
1) If connection string does not contain workspace then I can run SQL query but tools does not receive JDBC metadata - is it correct?
2) If connection string contains non-existing workspace then it should be created and provide JDBC metadata - I would expect this behaviour as I have option mode:creatingWorkspacesAllowed="true" but it does not work this way
Comment 1 Van Halbert 2010-10-27 13:45:37 UTC 
#1,  see link.
As to #2,  no, the jdbc driver is considered read only on the initial release and therefore, the jdbc implementation only connects to what's available.     Otherwise, if it allows creating a workspace, there's implied usage of adding data to the workspace, and that is not an option for this release.
Comment 2 Van Halbert 2010-10-27 13:45:54 UTC 
Link: Added: This issue depends MODE-912
Comment 3 Anne-Louise Tangring 2010-10-28 16:13:28 UTC 
Candidate for SOA 5.1.0
Comment 4 Van Halbert 2010-10-29 16:35:57 UTC 
Changes were committed to the 2.2.x product branch and should be in the ER4 release.
Comment 5 Jiri Pechanec 2011-01-11 09:26:09 UTC 
Verified in ER6