[ https://jira.jboss.org/browse/JBDS-1364?page=com.atlassian.jira.plugin.sy... ] Max Andersen updated JBDS-1364: ------------------------------- Fix Version/s: 4.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1364?page=com.atlassian.jira.plugin.sy... ] John Doyle commented on JBDS-1364: ---------------------------------- The only reason this ConnectionProfile exists is to used by the Teiid JDBC Importer. As currently implemented (because of limitations of the ModeShape JDBC Driver) this connection profile is only usable to view the JDBC metadata of a ModeShape Repository. You cannot execute queries unless the driver is in the same process space as ModeShape, and that's not the case in eclipse. While it is true that ModeShape in EDS will have a /repository/eds repository, I don't think there's any reason to assume that that's the repository a user wants to import metadata from. It's certainly a valid use case, but I don't know why it would be the default url other than that it would work as the default (work being defined as 'will connect'). I'm pretty sure BRMS is supporting ModeShape in this release as well. I recommend an obviously bad URL that will not work, but guides the user, and forces them to do the right thing. jdbc:jcr:http://localhost:8080/modeshape-rest/repository/<target-repository> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1364?page=com.atlassian.jira.plugin.sy... ] John Doyle edited comment on JBDS-1364 at 10/21/10 10:36 AM: ------------------------------------------------------------- The only reason this ConnectionProfile exists is to used by the Teiid JDBC Importer. As currently implemented (because of limitations of the ModeShape JDBC Driver) this connection profile is only usable to view the JDBC metadata of a ModeShape Repository. You cannot execute queries unless the driver is in the same process space as ModeShape, and that's not the case in eclipse. While it is true that ModeShape in EDS will have a /repository/eds repository, I don't think there's any reason to assume that that's the repository a user wants to import metadata from. It's certainly a valid use case, but I don't know why it would be the default url other than that it would work as the default (work being defined as 'will connect'). I'm pretty sure BRMS is supporting ModeShape in this release as well. I recommend an obviously bad URL that will not work, but guides the user, and forces them to do the right thing. jdbc:jcr:http://localhost:8080/modeshape-rest/repository/\<target-repository> was (Author: jdoyle): The only reason this ConnectionProfile exists is to used by the Teiid JDBC Importer. As currently implemented (because of limitations of the ModeShape JDBC Driver) this connection profile is only usable to view the JDBC metadata of a ModeShape Repository. You cannot execute queries unless the driver is in the same process space as ModeShape, and that's not the case in eclipse. While it is true that ModeShape in EDS will have a /repository/eds repository, I don't think there's any reason to assume that that's the repository a user wants to import metadata from. It's certainly a valid use case, but I don't know why it would be the default url other than that it would work as the default (work being defined as 'will connect'). I'm pretty sure BRMS is supporting ModeShape in this release as well. I recommend an obviously bad URL that will not work, but guides the user, and forces them to do the right thing. jdbc:jcr:http://localhost:8080/modeshape-rest/repository//<target-repository> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1364?page=com.atlassian.jira.plugin.sy... ] Randall Hauch commented on JBDS-1364: ------------------------------------- I'd suggest using the REST API to discover the repositories and workspaces. For details, see http://docs.jboss.org/modeshape/latest/manuals/reference/html_single/refe.... But basically, an HTTP GET against http://localhost:8080/modeshape-rest/ will return a JSON response containing (among other things) the names of the repositories. Similarly, once a repository is selected, an HTTP GET against http://localhost:8080/modeshape-rest/{repositoryName} will return a JSON response containing information about the repository, including the available workspaces that are visible to the user. Hopefully this information can be used by the ConnectionProfile to give the user a choice list for the repository names and, when one is selected, the workspace names. But it would also be nice if the user could paste (or type) in a URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1364?page=com.atlassian.jira.plugin.sy... ] John Doyle resolved JBDS-1364. ------------------------------ Resolution: Done Profile Editor now provides the user with the ability to connect to ModeShape and get a list or repositories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira