[JBoss JIRA] (JBIDE-10649) Command execution interrupted: Execution context is null
by Dmitry Geraskov (JIRA)
Dmitry Geraskov created JBIDE-10649:
---------------------------------------
Summary: Command execution interrupted: Execution context is null
Key: JBIDE-10649
URL: https://issues.jboss.org/browse/JBIDE-10649
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M5
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.3.0.Beta1
Steps to reproduce:
1) Open HQL Editor for existing console configuration
2) restart ide
3) type some query and call code completion
4) finish the query and execute it
Observe the exception
org.hibernate.console.HibernateConsoleRuntimeException: Command execution interrupted: Execution context is null, 'Hibernate3.6' console configuration is closed.
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:110)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:263)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10323) NPE in Central software/update page
by Max Rydahl Andersen (Created) (JIRA)
NPE in Central software/update page
-----------------------------------
Key: JBIDE-10323
URL: https://issues.jboss.org/browse/JBIDE-10323
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M5
I'm getting NPE on refreshing central:
java.lang.NullPointerException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.stream(P2TransportService.java:93)
at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.stream(WebUtil.java:161)
at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.readResource(WebUtil.java:95)
at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:107)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1500)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10467) Run Schema Export from Hibernate Console Configuration error
by Jiri Peterka (Created) (JIRA)
Run Schema Export from Hibernate Console Configuration error
------------------------------------------------------------
Key: JBIDE-10467
URL: https://issues.jboss.org/browse/JBIDE-10467
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M5
Reporter: Jiri Peterka
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.3.0.M5
Hibernate Configuration Run SchemaExport action gives me:
java.sql.SQLException: S1000 General error java.lang.RuntimeException: database alias does not exist
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at org.hibernate.eclipse.libs.FakeDelegatingDriver.connect(FakeDelegatingDriver.java:40)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10330) CDI model doesn't load beans from indirectly dependent projects
by Alexey Kazakov (Created) (JIRA)
CDI model doesn't load beans from indirectly dependent projects
---------------------------------------------------------------
Key: JBIDE-10330
URL: https://issues.jboss.org/browse/JBIDE-10330
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M5
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.Beta1
EXECUTE: Create three CDI projects:
Project1
Project2 (depends on/exports Project1)
Project3 (depends on Project2)
EXECUTE: Create a @Named bean in Project1: @Named("bean1").
EXECUTE: Create a @Named bean in Project2: @Named("bean2").
EXECUTE: Create a @Named bean in Project3: @Named("bean3").
EXECUTE: Perform full build for all the projects.
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project1.
ASSERT: There is the only bean "bean1" available. It's good.
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project2.
ASSERT: There are bean "bean1" and "bean2" available. It's good too.
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project3.
ASSERT: There are bean "bean1" and "bean2" and "bean3" available. Everything is fine so far.
EXECUTE: Restart your Eclipse.
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project3.
{color:red}FAILURE: There is the only bean "bean3" available! It's a bug.{color}
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project2.
ASSERT: There are bean "bean1" and "bean2" available. Ok.
EXECUTE: Try Ctrl+Space in a EL like #{bean|} in any page of Project3.
ASSERT: There are bean "bean1" and "bean2" and "bean3" available again. So it's working now!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month