[JBoss JIRA] Created: (JBIDE-9724) The home directory does not exist or is missing a required file or folder: modules\org\jboss\as\server\main setting up AS 7 runtime in eclipse indigo
by David Norris (JIRA)
The home directory does not exist or is missing a required file or folder: modules\org\jboss\as\server\main setting up AS 7 runtime in eclipse indigo
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-9724
URL: https://issues.jboss.org/browse/JBIDE-9724
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Windows XP Professional Service Pack 3
Jboss Tools 3.3.x + Eclipse 3.7(indigo) + Jboss AS 7.x
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Oracle JRockit(R) (build R28.1.4-7-144370-1.6.0_26-20110617-2131-windows-ia32, compiled mode)
maven 3.0.3
Reporter: David Norris
Assignee: Rob Stryker
Error when setting up a Server Runtime Environment for jboss-as-7 in eclipse (or netbeans for that matter).
It makes no difference if you put the jboss server in the default location (c:/program files/jboss-7.0.x).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10731) org.jboss.tools.seam.ui.test.jbide.JBide3989Test failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10731:
--------------------------------------
Summary: org.jboss.tools.seam.ui.test.jbide.JBide3989Test failure
Key: JBIDE-10731
URL: https://issues.jboss.org/browse/JBIDE-10731
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.3.0.Beta1
{code}
testJBide3989(org.jboss.tools.seam.ui.test.jbide.JBide3989Test) Time elapsed: 2.391 sec <<< FAILURE!
junit.framework.AssertionFailedError: The quickfix "Set Seam Properties" doesn't exist.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.tools.seam.ui.test.jbide.JBide3989Test.testJBide3989(JBide3989Test.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
{code}
--
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-10606) Seam Generate Entities wizard problem
by Tomas Remes (Created) (JIRA)
Seam Generate Entities wizard problem
-------------------------------------
Key: JBIDE-10606
URL: https://issues.jboss.org/browse/JBIDE-10606
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Environment: JBDS 4.1.0.GA
Reporter: Tomas Remes
Assignee: Alexey Kazakov
Steps to reproduce:
1. Import existing Seam 2.2 project into workspace
2. Add valid Seam runtime to the project (in Seam Settings)
3. No project is selected in package explorer!!!
4. File -> New -> Seam Generate Entities
5. Fill in imported project name (or try to select project using Browse button)
6. Following error occurs: Selected seam project has some invalid settings. Please press "Settings..." and correct them.
In settings is everything fine, project has valid Seam runtime and this error still occurs.
--
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-10470) Hibernate configuration is not able to use Hibernate Configuration File referenced in persistence.xml
by Jiri Peterka (Created) (JIRA)
Hibernate configuration is not able to use Hibernate Configuration File referenced in persistence.xml
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10470
URL: https://issues.jboss.org/browse/JBIDE-10470
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M4
Environment: JBSD 5.0.M5 H55
Reporter: Jiri Peterka
Assignee: Dmitry Geraskov
Fix For: 3.3.0.Beta1
1. Create JPA Project
2. Add JPA/Hibernate(4.0) libs
3. Open persitence.xml
4. On Hibernate page use Configuration file, create it
5. Try to use Hibernate Console
ERROR: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
Could not create JPA based Configuration
<No message>
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: <no message>
java.lang.reflect.InvocationTargetException
javax.persistence.PersistenceException: [PersistenceUnit: jpahibernate40] Unable to configure EntityManagerFactory
[PersistenceUnit: jpahibernate40] Unable to configure EntityManagerFactory
org.hibernate.HibernateException: /jpahibernate40/src/hibernate.cfg.xml not found
/jpahibernate40/src/hibernate.cfg.xml not found
In persistence.xml is:
<property name="hibernate.ejb.cfgfile" value="/jpahibernate40/src/hibernate.cfg.xml"/>
--
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