October 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-603) seam wizards should allow user to point to DTP database connection

by Max Andersen (JIRA)

seam wizards should allow user to point to DTP database connection ------------------------------------------------------------------ Key: JBIDE-603 URL: http://jira.jboss.com/jira/browse/JBIDE-603 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Max Andersen instead of specifying connection properties again and again ;) -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2675) template attribute causes NullPointerException

by Tim Evers (JIRA)

template attribute causes NullPointerException ---------------------------------------------- Key: JBIDE-2675 URL: https://jira.jboss.org/jira/browse/JBIDE-2675 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Environment: This bug only appears on 3.0.0 Reporter: Tim Evers I have an xhtml file with the following declaration <?xml version="1.0" encoding="UTF-8"?> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="https://ajax4jsf.dev.java.net/ajax" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:gekko="http://gekkoTagLibs.com" template="/layout/template.xhtml"> With jbossTools 3.0.0 I get the following exception when trying to open it in the xhtml editor. java.lang.NullPointerException at org.jboss.tools.vpe.editor.util.DocTypeUtil.getDoctype(DocTypeUtil.java:153) at org.jboss.tools.vpe.editor.util.DocTypeUtil.getDoctype(DocTypeUtil.java:71) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:281) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:754) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:223) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:421) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:318) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:160) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:228) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:207) 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:363) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:603) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) 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:818) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297) 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:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:382) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) If I remove the template everything seems to work ok. Also if I change the template to be a relative location such as ../template.xhtml then I don't get the exception either. -- 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, 5 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-2203) Hibernate Reverse engineering editor - Overview tab - Console configuration combobox - not possible to save changes

by Vitali Yemialyanchyk (JIRA)

Hibernate Reverse engineering editor - Overview tab - Console configuration combobox - not possible to save changes ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2203 URL: http://jira.jboss.com/jira/browse/JBIDE-2203 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Hibernate Reverse engineering editor - Overview tab - Console configuration combobox - change it's value to other - expected editor should be modified and save should be available - but it is not. Close editor (should propose to save) and open it once more - old value 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, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-2412) Reduce redundant DB info in eclipse seam projects

by Jay Balunas (JIRA)

Reduce redundant DB info in eclipse seam projects ------------------------------------------------- Key: JBIDE-2412 URL: http://jira.jboss.com/jira/browse/JBIDE-2412 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, Seam Affects Versions: 2.1.1 Reporter: Jay Balunas Priority: Minor Helping users during a JBDS lab resulted in this comment, when attempting to fix a user error with setup. There were several locations where we had to make the same change. Quote from Max: "I hope that in the future we can reduce the redundancy of db info (currently it is in that file [hibernate*.properties], DTP connection info and the deployed datasource file)" -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3052) Generate Entities tells me Hibernate Dialect not set when it is

by Max Rydahl Andersen (JIRA)

Generate Entities tells me Hibernate Dialect not set when it is --------------------------------------------------------------- Key: JBIDE-3052 URL: https://jira.jboss.org/jira/browse/JBIDE-3052 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Max Rydahl Andersen Assignee: Dima Geraskov Fix For: 3.0.0.beta1 I've set hibernate dialect in the persistence.xml but when I use Generate Entities the wizard tells me "Hibernate dialect is not set" (without any further explanation. Why is it not picking up the persistence.xml when generating entities ? -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1921) Hibernate Tools User Guide

by Denis Golovin (JIRA)

Hibernate Tools User Guide -------------------------- Key: JBIDE-1921 URL: http://jira.jboss.com/jira/browse/JBIDE-1921 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 2.0.1, 2.1 Reporter: Denis Golovin Fix For: 2.1 There is hibernatetools-ref-guide in https://svn.jboss.org/repos/jbosstools/trunk/hibernatetools/docs/reference that should be available as org.hibernate.user.doc in JBossTools. It should be used for context help in hiberbnate related GUI. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2286) view id selection shows "weird" dialog

by Max Rydahl Andersen (JIRA)

view id selection shows "weird" dialog -------------------------------------- Key: JBIDE-2286 URL: http://jira.jboss.com/jira/browse/JBIDE-2286 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Max Rydahl Andersen Fix For: 3.0.x Not sure if this is a bug or feature request, but here it goes. The dialog for selecting view-id contains "weird things" 1) the root node is the same as project name 2) the project is shown below the root node with all folders/files below it 3) there are other folders shown below it that seem to be non-related. ...what I would have expected was a list of existing view-id's used in the pages.xml, list of whatever page resources that is found inside any view/webcontent folder according to WTP project and finally a "Other" node which would allow me to browse the full project. Maybe this should be a dialog with various options instead of a pure tree to make it simpler for the user ? -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-447) jsf_tools_ref_guide concluding part is required

by Svetlana mukhina (JIRA)

jsf_tools_ref_guide concluding part is required ----------------------------------------------- Key: JBDS-447 URL: https://jira.jboss.org/jira/browse/JBDS-447 Project: Developer Studio Issue Type: Sub-task Components: Doc - JSFTools Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.beta1 jsf_tools_ref_guide concluding part is required -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-2981) Cannot create process definition in root project folder

by John Graham (JIRA)

Cannot create process definition in root project folder ------------------------------------------------------- Key: JBIDE-2981 URL: https://jira.jboss.org/jira/browse/JBIDE-2981 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Environment: jBPM designer: 3.1.5Beta1-N200810230806 Reporter: John Graham Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error. ------------------------------- java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:386) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2669) Seam packager should include mvel*.jar, not just mvel14.jar from ${seam.home}/lib

by Pete Muir (JIRA)

Seam packager should include mvel*.jar, not just mvel14.jar from ${seam.home}/lib --------------------------------------------------------------------------------- Key: JBIDE-2669 URL: https://jira.jboss.org/jira/browse/JBIDE-2669 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Pete Muir Assignee: Max Rydahl Andersen Priority: Critical Older Seam packaged mvel as mvel14.jar - subsequently the jar name was changed to mvel.jar (which is a better name, as mvel14.jar includes version info in the jar name which is bad) -- 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, 5 months

4
9
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 October 2008