November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-830) Spaces in project path causes JTA exception

by Ondrej Skutka (JIRA)

Spaces in project path causes JTA exception ------------------------------------------- Key: JBDS-830 URL: https://jira.jboss.org/jira/browse/JBDS-830 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Ondrej Skutka Priority: Critical Fix For: 2.1.0 Steps to reproduce: 1) Create a new Seam project with database 2) Go to Hibernate Configurations view 3) Unfold the configuration following exception is thrown: 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: java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes Furturemore you cannot generate seam entities, because of "Couldn't connect to Database". -- 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

16 years, 2 months

5
19
0 / 0

[JBoss JIRA] Created: (JBDS-832) Some titles are not correct in Welcome screen.

by Alexey Kazakov (JIRA)

Some titles are not correct in Welcome screen. ---------------------------------------------- Key: JBDS-832 URL: https://jira.jboss.org/jira/browse/JBDS-832 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M2 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.0.0.M2 See sreenshot. -- 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

16 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-682) Make Seam Runtimes 1.2.AP and 2.0.FP as default in spite of user's additional platform selection.

by Anton Klimkovich (JIRA)

Make Seam Runtimes 1.2.AP and 2.0.FP as default in spite of user's additional platform selection. -------------------------------------------------------------------------------------------------- Key: JBDS-682 URL: https://jira.jboss.org/jira/browse/JBDS-682 Project: Developer Studio Issue Type: Feature Request Components: installer Affects Versions: 2.1.0 Reporter: Anton Klimkovich EXECUTE: On step 5 of installation select Yes chechbox to install JBoss Enterprise Application Platform EXECUTE: On step 5 add SOA-P EXECUTE: Window - JBoss tools -> Web -> Seam ASSERT: Seam Runtime 1.2.AP and 2.0.FP should be default runtimes Seam Runtimes are checked as default now depending on user's additional platform selection. Since Soa-P doesn't contain seamGen for seam 1.2 I think Seam Runtimes 1.2.AP and 2.0.FP as default will be better. -- 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

16 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-366) Welcome screen: view of Create New is incorrectly, and there is strange behavior

by Tatyana Romanovich (JIRA)

Welcome screen: view of Create New is incorrectly, and there is strange behavior -------------------------------------------------------------------------------- Key: JBDS-366 URL: http://jira.jboss.com/jira/browse/JBDS-366 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.CR1 Environment: JBoss Developer Studio Version: 1.1.0 Build id: 200806161541-nightly Build date: 06/16/2008 15:46 Reporter: Tatyana Romanovich Assigned To: Maxim Areshkau Priority: Trivial EXECUTE: Open JBDS with empty workspace EXECUTE: select Getting Started on the Welcome screen EXECUTE: move mouse over the each links 1. FAILURE: green badge on the icon appears only for "Viewlets and Tutorials" point (see Welcome1.png) EXECUTE: select any item (click on the right of link) EXECUTE: move mouse over another items icon 2. FAILURE: both icons have green badge at the same time (see Welcome2.png) EXECUTE: Select "Create New..." 3. FAILURE: "Create jBPM Process Project" is subitem of "Create Seam Project". Is it right? (see Welcome3.png) EXECUTE: Select "Perspectives" EXECUTE: Select any item -> Welcome window gets smaller EXECUTE: Verify Welcome window 4. FAILURE: Welcome to JBDS appears (Is it right? ) EXECUTE: Try to select Perspectives link 5. FAILURE: Perspectives can't be displayed -- 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

16 years, 2 months

4
20
0 / 0

[JBoss JIRA] Created: (JBDS-340) Intro/Welcome screen cleanup

by Max Rydahl Andersen (JIRA)

Intro/Welcome screen cleanup ---------------------------- Key: JBDS-340 URL: http://jira.jboss.com/jira/browse/JBDS-340 Project: Developer Studio Issue Type: Task Components: ui/branding Reporter: Max Rydahl Andersen Assigned To: Max Rydahl Andersen Fix For: 2.0.0.alpha Splashscreen support has improved in Ganymede, same has the intro and welcome screen setup. SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there. If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism and hopefully create a JBDS branded version. -- 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

16 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (JBDS-695) Translation of JBoss Developer Studio (L10n)

by Sean Flanigan (JIRA)

Translation of JBoss Developer Studio (L10n) -------------------------------------------- Key: JBDS-695 URL: https://jira.jboss.org/jira/browse/JBDS-695 Project: Developer Studio Issue Type: Feature Request Reporter: Sean Flanigan Fix For: 2.1.0 This feature request is for the overall localization of JBoss Developer Studio. To start with, we need at least the following locales/languages: - Japanese (ja_JA) - Simplified Chinese (zh_CN) - Brazilian Portuguese (pt_BR) - Spanish (es_ES) - French (fr_FR) - German (de_DE) We can add sub-tasks and/or dependencies as appropriate. -- 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

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-637) use jbds builder instead of richfaces so product feature is set to 2.0 instead of 3.0

by Denis Golovin (JIRA)

use jbds builder instead of richfaces so product feature is set to 2.0 instead of 3.0 ------------------------------------------------------------------------------------- Key: JBDS-637 URL: https://jira.jboss.org/jira/browse/JBDS-637 Project: Developer Studio Issue Type: Bug Components: Build Affects Versions: 2.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 2.0.0.GA -- 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

16 years, 2 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4194) NPE with Hibernate Tools

by Murat HAZER (JIRA)

NPE with Hibernate Tools ------------------------ Key: JBIDE-4194 URL: https://jira.jboss.org/jira/browse/JBIDE-4194 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.GA Environment: Eclipse Platform, Version: 3.4.2, Build id: M20090211-1700 JBoss Tools RichFaces for Eclipse, Version: 3.0.0.GA-R200903141626-H5 Reporter: Murat HAZER if you create hibernate-cfg.xml with annotations driven mapping classes hibernate tools gives following error; !ENTRY org.hibernate.eclipse.console 4 2 2009-04-16 16:14:58.008 !MESSAGE java.lang.NullPointerException !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2009-04-16 16:14:58.008 !MESSAGE <No message> !STACK 0 java.lang.NullPointerException at org.hibernate.cfg.annotations.CollectionBinder.buildOrderByClauseFromHql(CollectionBinder.java:851) at org.hibernate.cfg.annotations.CollectionBinder.bindOneToManySecondPass(CollectionBinder.java:608) at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:563) at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:517) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter$1.execute(ConsoleConfigurationWorkbenchAdapter.java:45) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:94) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:41) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:99) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:105) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) solution: upgrade hibernate-annotations.jar to 3.3.1.GA and hibernate-entitymanager.jar to 3.3.2.GA -- 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

16 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5288) AssertionFailedException: IFile parameter can not be null

by Yura Zhishko (JIRA)

AssertionFailedException: IFile parameter can not be null --------------------------------------------------------- Key: JBIDE-5288 URL: https://jira.jboss.org/jira/browse/JBIDE-5288 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor Open any xhtml page from jar file (you may use https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js...). RESULT: org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getModelForRead(ModelManagerImpl.java:1437) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:261) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:165) at org.jboss.tools.jst.jsp.contentassist.XmlContentAssistProcessor.createContext(XmlContentAssistProcessor.java:43) at org.jboss.tools.jst.jsp.contentassist.AbstractXMLContentAssistProcessor.createContext(AbstractXMLContentAssistProcessor.java:260) at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.setTarget(JSPPropertySourceAdapter.java:126) at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.<init>(JSPPropertySourceAdapter.java:103) at org.jboss.tools.jst.jsp.outline.JSPPropertySheetConfiguration$JSPPropertySourceProvider0.getPropertySource(JSPPropertySheetConfiguration.java:56) at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470) at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:752) at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973) at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510) at org.eclipse.wst.sse.ui.internal.properties.ConfigurablePropertySheetPage.selectionChanged(ConfigurablePropertySheetPage.java:174) at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:344) at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156) at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:60) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3531) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:614) at org.eclipse.ui.internal.WorkbenchPage.showEditor(WorkbenchPage.java:2943) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2843) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:374) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:178) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:229) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:208) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:373) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:526) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1101) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1205) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-963) JBT project configuration dialogs copied/moved to Project->Configure menu

by Svetlana mukhina (JIRA)

JBT project configuration dialogs copied/moved to Project->Configure menu -------------------------------------------------------------------------- Key: JBDS-963 URL: https://jira.jboss.org/jira/browse/JBDS-963 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc Check all guides, update sections where the menu is shown, update info on project configure menu -- 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

16 years, 2 months

2
19
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 November 2009