[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ]
Ilya Buziuk edited comment on JBIDE-19187 at 2/11/15 6:41 AM:
--------------------------------------------------------------
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-18312 and JBIDE-18404
in JBIDE-18404 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
was (Author: ibuziuk):
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-18312 and JBIDE-18404
in JBIDE-18312 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
> CordovaSim + localhost:8080 fail
> --------------------------------
>
> Key: JBIDE-19187
> URL: https://issues.jboss.org/browse/JBIDE-19187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: hybrid4001.zip, localhost_error.png
>
>
> The following logic used to work and now fails:
> $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) {
> $("#contacts").empty();
> var items = [];
> $.each(data, function(key, val) {
> console.log("item: " + key + " " + val.name);
> items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>");
> });
> $("#contacts").append(items);
> $("#contacts").listview("refresh");
> });
> -------
> as seen in this youtube video and comments
> https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment...
> ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools)
> has the following error message:
> https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ]
Ilya Buziuk edited comment on JBIDE-19187 at 2/11/15 6:40 AM:
--------------------------------------------------------------
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-18312 and JBIDE-18404
in JBIDE-18312 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
was (Author: ibuziuk):
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-19187 and JBIDE-18312
in JBIDE-18312 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
> CordovaSim + localhost:8080 fail
> --------------------------------
>
> Key: JBIDE-19187
> URL: https://issues.jboss.org/browse/JBIDE-19187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: hybrid4001.zip, localhost_error.png
>
>
> The following logic used to work and now fails:
> $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) {
> $("#contacts").empty();
> var items = [];
> $.each(data, function(key, val) {
> console.log("item: " + key + " " + val.name);
> items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>");
> });
> $("#contacts").append(items);
> $("#contacts").listview("refresh");
> });
> -------
> as seen in this youtube video and comments
> https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment...
> ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools)
> has the following error message:
> https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19187:
-------------------------------------
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-19187 and JBIDE-18312
in JBIDE-18312 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
> CordovaSim + localhost:8080 fail
> --------------------------------
>
> Key: JBIDE-19187
> URL: https://issues.jboss.org/browse/JBIDE-19187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: hybrid4001.zip, localhost_error.png
>
>
> The following logic used to work and now fails:
> $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) {
> $("#contacts").empty();
> var items = [];
> $.each(data, function(key, val) {
> console.log("item: " + key + " " + val.name);
> items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>");
> });
> $("#contacts").append(items);
> $("#contacts").listview("refresh");
> });
> -------
> as seen in this youtube video and comments
> https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment...
> ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools)
> has the following error message:
> https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19189) NullPointerException in TablePropertiesBlock.doAdd
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19189?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-19189:
-----------------------------------
Yes I will!
> NullPointerException in TablePropertiesBlock.doAdd
> --------------------------------------------------
>
> Key: JBIDE-19189
> URL: https://issues.jboss.org/browse/JBIDE-19189
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.2.Final
> Environment: eclipse.buildId=4.4.1.M20140925-0400
> java.version=1.8.0_31
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
> Command-line arguments: -os win32 -ws win32 -arch x86_64
> Reporter: Michael Kolowicz
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
>
> I want to develop a small prototype of a application. I have create a database on MySQL 5.6 on a remote server. They have only 1 table (It´s like a easy prototype). The table have a Id-column.
> I using the eclipse 4.4.1 (on Windows 7 x64 - german), Hibernate 4.3.8, Hibernate Tools 4.0.0 (Final).
> Installation is a fresh downloaded eclipse with all actual updates. In the application is added the JDBC for MySQL and the Hibernate-Core Files.
> BTW: If i use Eclipse 4.3 with the same database, then the columns can be added an no error come up.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3343) java.lang.IllegalArgumentException: null source after importing WFK Spring projects
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-3343?page=com.atlassian.jira.plugin.... ]
Jiri Peterka updated JBDS-3343:
-------------------------------
CDW qa_ack: + (was: ?)
> java.lang.IllegalArgumentException: null source after importing WFK Spring projects
> -----------------------------------------------------------------------------------
>
> Key: JBDS-3343
> URL: https://issues.jboss.org/browse/JBDS-3343
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.2.GA
> Reporter: Jiri Peterka
> Fix For: 9.0.0.Alpha1
>
>
> {code}
> java.lang.IllegalArgumentException: null source
> at java.util.EventObject.<init>(EventObject.java:56)
> at org.springframework.ide.eclipse.core.model.ModelChangeEvent.<init>(ModelChangeEvent.java:43)
> at org.springframework.ide.eclipse.core.model.AbstractModel.notifyListeners(AbstractModel.java:43)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansModel$ResourceChangeEventHandler.configAdded(BeansModel.java:598)
> at org.springframework.ide.eclipse.beans.core.internal.model.resources.BeansResourceChangeListener$BeansResourceVisitor.resourceAdded(BeansResourceChangeListener.java:97)
> at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener$SpringResourceVisitor.visit(SpringResourceChangeListener.java:145)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener.resourceChanged(SpringResourceChangeListener.java:83)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:364)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:146)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19217?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19217:
--------------------------------------
No, it's 4.3.x related only.
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19217
> URL: https://issues.jboss.org/browse/JBIDE-19217
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS Version: 9.0.0.Alpha1 nightly build
> Build id: Alpha1-v20150204-0904-B2748
> Build date: 20150204-0904
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> While using Hibernate console in maven project
> {code}
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
> at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila
> at java.sql.DriverManager.getConnection(DriverManager.java:689)
> at java.sql.DriverManager.getConnection(DriverManager.java:208)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51)
> ... 26 more
> {code}
> Pom.xml
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.tools.hibernate.ui.bot.test</groupId>
> <artifactId>mvn-hibernate43</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.1-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months