December 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1288) Delete projects gives NPE in new "auto scanning for src code"

by Max Andersen (JIRA)

Delete projects gives NPE in new "auto scanning for src code" ------------------------------------------------------------- Key: JBIDE-1288 URL: http://jira.jboss.com/jira/browse/JBIDE-1288 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Assigned To: Viacheslav Kabanovich Priority: Critical Fix For: 2.0.0.CR1 Create some projects, delete them and you get a couple of these: java.lang.NullPointerException at org.jboss.tools.common.model.util.EclipseResourceUtil.getJavaProjectSrcLocations(EclipseResourceUtil.java:409) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.updateSrcs(FileSystemsLoader.java:212) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.update(FileSystemsLoader.java:63) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.doUpdate(FileSystemsImpl.java:287) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.access$4(FileSystemsImpl.java:281) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl$UpdateRunnable.run(FileSystemsImpl.java:265) at org.jboss.tools.common.model.XJob.run(XJob.java:125) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1610) hibernate reverce engeniering - Table & Columns tab - delete/remove button

by Vitali Yemialyanchyk (JIRA)

hibernate reverce engeniering - Table & Columns tab - delete/remove button -------------------------------------------------------------------------- Key: JBIDE-1610 URL: http://jira.jboss.com/jira/browse/JBIDE-1610 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Fix For: LATER possible add but not possible to remove items -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-3330) Seam generate-entities wizard doesn't generate anything when "Reverse engineer from database" checkbox is checked.

by Anton Klimkovich (JIRA)

Seam generate-entities wizard doesn't generate anything when "Reverse engineer from database" checkbox is checked. ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-3330 URL: https://jira.jboss.org/jira/browse/JBIDE-3330 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.cr1 Reporter: Anton Klimkovich EXECUTE: Create sean web project EXECUTE: Create hibernate.xml and relate it with any DB (in my example it was related with Test HSQL DB) EXECUTE: New -> Seam Generate Entities EXECUTE: Check the "Reverse engineer from database" checkbox EXECUTE: Press Next button EXECUTE: Include some tables and press Finish button FAILURE: Seam generate-entities wizard doesn't generate anything If you create entity and then use Generate entities with "Reverse engineer from database" checkbox it will generate Entities like with "Use Existing entities " checkbox. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1285) Datasources not found during testng run

by Max Andersen (JIRA)

Datasources not found during testng run --------------------------------------- Key: JBIDE-1285 URL: http://jira.jboss.com/jira/browse/JBIDE-1285 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Assigned To: Denis Golovin Priority: Blocker Fix For: 2.0.0.CR1 EXECUTE: New Seam Web Project (Seam 1.2) EXECUTE: New Action EXECUTE: Run the generated test xml with testng ASSERT: Green bar I get: [Parser] Running: C:\Users\max\workspace\floppy-test\test-src\org\domain\floppy\test\PingTest.xml 20:51:17,219 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.LocalOnlyContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} 20:51:17,233 ERROR [NamingHelper] Could not obtain initial context javax.naming.NamingException: Local server is not initialized at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at org.hibernate.util.NamingHelper.getInitialContext(NamingHelper.java:28) at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124) at org.hibernate.ejb.InjectionSettingsFactory.createConnectionProvider(InjectionSettingsFactory.java:29) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:61) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1928) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:631) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:760) at org.hibernate.ejb.Ejb3Configuration.createFactory(Ejb3Configuration.java:151) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:205) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:114) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:37) at org.jboss.seam.core.EntityManagerFactory.startup(EntityManagerFactory.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123) at org.jboss.seam.Component.callComponentMethod(Component.java:1842) at org.jboss.seam.Component.callCreateMethod(Component.java:1757) at org.jboss.seam.Component.newInstance(Component.java:1746) at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175) at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:145) at org.jboss.seam.init.Initialization.init(Initialization.java:504) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:701) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:166) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) at org.testng.TestRunner.runWorkers(TestRunner.java:689) at org.testng.TestRunner.privateRun(TestRunner.java:566) at org.testng.TestRunner.run(TestRunner.java:466) at org.testng.SuiteRunner.runTest(SuiteRunner.java:301) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:296) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:276) at org.testng.SuiteRunner.run(SuiteRunner.java:191) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:808) at org.testng.TestNG.runSuitesLocally(TestNG.java:776) at org.testng.TestNG.run(TestNG.java:701) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) 20:51:17,234 FATAL [DatasourceConnectionProvider] Could not find datasource: java:/floppyTestDatasource javax.naming.NamingException: Local server is not initialized at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at org.hibernate.util.NamingHelper.getInitialContext(NamingHelper.java:28) at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124) at org.hibernate.ejb.InjectionSettingsFactory.createConnectionProvider(InjectionSettingsFactory.java:29) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:61) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1928) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:631) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:760) at org.hibernate.ejb.Ejb3Configuration.createFactory(Ejb3Configuration.java:151) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:205) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:114) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:37) at org.jboss.seam.core.EntityManagerFactory.startup(EntityManagerFactory.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123) at org.jboss.seam.Component.callComponentMethod(Component.java:1842) at org.jboss.seam.Component.callCreateMethod(Component.java:1757) at org.jboss.seam.Component.newInstance(Component.java:1746) at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175) at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:145) at org.jboss.seam.init.Initialization.init(Initialization.java:504) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:701) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:166) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) at org.testng.TestRunner.runWorkers(TestRunner.java:689) at org.testng.TestRunner.privateRun(TestRunner.java:566) at org.testng.TestRunner.run(TestRunner.java:466) at org.testng.SuiteRunner.runTest(SuiteRunner.java:301) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:296) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:276) at org.testng.SuiteRunner.run(SuiteRunner.java:191) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:808) at org.testng.TestNG.runSuitesLocally(TestNG.java:776) at org.testng.TestNG.run(TestNG.java:701) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) FAILED CONFIGURATION: @BeforeClass init javax.persistence.PersistenceException: org.hibernate.HibernateException: Could not find datasource at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:217) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:114) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:37) at org.jboss.seam.core.EntityManagerFactory.startup(EntityManagerFactory.java:74) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123) at org.jboss.seam.Component.callComponentMethod(Component.java:1842) at org.jboss.seam.Component.callCreateMethod(Component.java:1757) at org.jboss.seam.Component.newInstance(Component.java:1746) at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175) at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:145) at org.jboss.seam.init.Initialization.init(Initialization.java:504) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:701) Caused by: org.hibernate.HibernateException: Could not find datasource at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:56) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124) at org.hibernate.ejb.InjectionSettingsFactory.createConnectionProvider(InjectionSettingsFactory.java:29) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:61) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1928) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:631) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:760) at org.hibernate.ejb.Ejb3Configuration.createFactory(Ejb3Configuration.java:151) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:205) ... 38 more Caused by: javax.naming.NamingException: Local server is not initialized at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at org.hibernate.util.NamingHelper.getInitialContext(NamingHelper.java:28) at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52) ... 47 more ... Removed 26 stack frames -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
18
0 / 0

[JBoss JIRA] Created: (JBDS-269) Seam 2 project "explode" ant-task endlessly loops

by Samuel Mendenhall (JIRA)

Seam 2 project "explode" ant-task endlessly loops ------------------------------------------------- Key: JBDS-269 URL: http://jira.jboss.com/jira/browse/JBDS-269 Project: Developer Studio Issue Type: Bug Reporter: Samuel Mendenhall Assigned To: Max Andersen Priority: Minor This case is from a customer issue in the Support Portal. When the customer makes a change to a file the build.xml "explode" ant-task starts in a forever loop. The customer must unckeck the Project--> Build Automatically option to make it stop. This issue came about when the the customer removed the deployed module in "JBoss Server View". He added then removed the JSF capabilities to solve a problem with the nagivation.xml, and this was the result. Please see the private attachment for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

5
10
0 / 0

[JBoss JIRA] Created: (JBDS-416) Page Design Options wizard

by Svetlana mukhina (JIRA)

Page Design Options wizard -------------------------- Key: JBDS-416 URL: https://jira.jboss.org/jira/browse/JBDS-416 Project: Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Michael Sorokin Fix For: 2.0.0.alpha check the wizard screens in guide, make sure they are not out-of-date -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3336) Seam validator is called too often

by Adrian Mitev (JIRA)

Seam validator is called too often ---------------------------------- Key: JBIDE-3336 URL: https://jira.jboss.org/jira/browse/JBIDE-3336 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.beta1 Environment: Windows XP, eclipse 3.4.1, wtp 3.0.3, jboss tools nightly build N200812020037 Reporter: Adrian Mitev The Seam validator is called even if i save a build.xml file and it scans all pages. Quite heavy, i have over 50 pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
20
0 / 0

[JBoss JIRA] Created: (JBIDE-1786) Support for Seam 2.1

by Norman Richards (JIRA)

Support for Seam 2.1 -------------------- Key: JBIDE-1786 URL: http://jira.jboss.com/jira/browse/JBIDE-1786 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Norman Richards The tools don't support adding a 2.1 Seam runtime. The "New Seam Runtime" dialog reports "The selected seam appears to be of an incompatible version '2.1.0.A1'". The Finish button is not active to allow the runtime to be selected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

8
17
0 / 0

[JBoss JIRA] Created: (JBIDE-3402) Drools features should not have "Feature" in their names

by Nick Boldt (JIRA)

Drools features should not have "Feature" in their names -------------------------------------------------------- Key: JBIDE-3402 URL: https://jira.jboss.org/jira/browse/JBIDE-3402 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.0.0.beta1 Reporter: Nick Boldt As with JBIDE-3317, we should be consistent w/ the feature names. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-367) describe in guide seam project property validation

by Svetlana mukhina (JIRA)

describe in guide seam project property validation -------------------------------------------------- Key: JBDS-367 URL: http://jira.jboss.com/jira/browse/JBDS-367 Project: Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 2.0.0.alpha Describe new functionality in guide corresponding to the linked task -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2008