April 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2042) Problems in html table template

by Denis Maliarevich (JIRA)

Problems in html table template ------------------------------- Key: JBIDE-2042 URL: http://jira.jboss.com/jira/browse/JBIDE-2042 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.beta1 Reporter: Denis Maliarevich Assigned To: Maxim Areshkau Attachments: table in VPE.png 1. Layout differs from the browser view. (see attachment) 2. Wrong layout after table cells resizing. -- 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, 11 months

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-2104) VPE Preferences has wrong suggestion for "Default Editor Tab"

by Andrei Scherbovich (JIRA)

VPE Preferences has wrong suggestion for "Default Editor Tab" ------------------------------------------------------------- Key: JBIDE-2104 URL: http://jira.jboss.com/jira/browse/JBIDE-2104 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1.0.beta1 Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau VPE Preferences has wrong suggestion for "Default Editor Tab". Now we have ( Visual/Source | Source | Visual ) and anyway "Visual" and "Source" don't work. I think we should have ( Visual/Source | Preview ) suggestion. -- 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, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2045) The Visual Page Editor crashes Eclipse on Linux

by Snjezana Peco (JIRA)

The Visual Page Editor crashes Eclipse on Linux ----------------------------------------------- Key: JBIDE-2045 URL: http://jira.jboss.com/jira/browse/JBIDE-2045 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.beta1 Reporter: Snjezana Peco Assigned To: Snjezana Peco Fix For: 2.1 Max has noticed that VPE crashes Eclipse on Linux GTK when opening,editing,closing more files. I have succeeded to reproduce the crash.The cause of the crash is SWT bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=207206 . The bug is fixed today in Eclipse 3.4 I will create org.eclipse.swt.gtk.x86 fragments for Eclipse 3.3.1.1 and Eclipse 3.3.2. This will fix the issue with JUnit tests. I will also include a fix for the memory leak described in http://dev.eclipse.org/newslists/news.eclipse.platform.swt/msg38540.html . -- 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, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2090) ConcurrentModificationException occurs during the Seam validation

by Snjezana Peco (JIRA)

ConcurrentModificationException occurs during the Seam validation ----------------------------------------------------------------- Key: JBIDE-2090 URL: http://jira.jboss.com/jira/browse/JBIDE-2090 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.beta1 Environment: I got the exception a few times on Linux, but I am not sure if this is a Linux specific issue Reporter: Snjezana Peco Sometimes when executing the Seam validation, I get ConcurrentModificationException. Steps to reproduce: - create a large Seam project (as described in http://jira.jboss.com/jira/browse/JBIDE-1105#action_12394448 , for instance) - open a few files in the VPE editor - select the WebContent directory and choose Source>Format - edit files during the Seam validation Stack trace: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at org.jboss.tools.common.model.util.TypeInfoCollector.getProperties(TypeInfoCollector.java:843) at org.jboss.tools.common.model.util.TypeInfoCollector.getPropertyPresentations(TypeInfoCollector.java:883) at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:620) at org.jboss.tools.seam.internal.core.el.SeamELCompletionEngine.resolveSeamELOperand(SeamELCompletionEngine.java:330) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateElOperand(SeamELValidator.java:293) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateEl(SeamELValidator.java:271) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateString(SeamELValidator.java:260) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateNodeContent(SeamELValidator.java:240) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:221) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:225) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateChildNodes(SeamELValidator.java:225) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateDom(SeamELValidator.java:194) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateFile(SeamELValidator.java:153) at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validate(SeamELValidator.java:106) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:79) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:64) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75) 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, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-2116) Getting java.lang.NoClassDefFoundError when opening an *.xhtml file in JBoss Tools HTML Editor on Mac

by Jeff Markham (JIRA)

Getting java.lang.NoClassDefFoundError when opening an *.xhtml file in JBoss Tools HTML Editor on Mac ----------------------------------------------------------------------------------------------------- Key: JBIDE-2116 URL: http://jira.jboss.com/jira/browse/JBIDE-2116 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, Visual Page Editor Affects Versions: 2.1.0.beta1 Environment: Mac OS X 10.5.2 java -version java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237) Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing) 1.0.0.GA base installation with 2.1 beta updates Reporter: Jeff Markham In Seam perspective, selected New | Seam Entity. Went to web project to open generated *.xhtml error and received dialog with message: An error has occurred. See error log for more details. java.lang.NoClassDefFoundError Error log: eclipse.buildId=unknown java.version=1.5.0_13 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US Framework arguments: -keyring /Users/jmarkham/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws carbon -arch x86 -keyring /Users/jmarkham/.eclipse_keyring -consoleLog -showlocation Error Tue Apr 22 22:53:11 EDT 2008 Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.NoClassDefFoundError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68) at org.jboss.tools.vpe.editor.toolbar.format.TextFormattingToolBar.createItems(TextFormattingToolBar.java:104) at org.jboss.tools.vpe.editor.toolbar.SplitToolBar.createToolBarControl(SplitToolBar.java:36) at org.jboss.tools.vpe.editor.toolbar.VpeToolBarManager.addToolBar(VpeToolBarManager.java:86) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:152) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:618) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:219) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:414) 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:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:398) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2688) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651) at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2565) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:286) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613) 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:857) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199) 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:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1295) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3350) at org.eclipse.swt.widgets.Control.sendTrackEvents(Control.java:2734) at org.eclipse.swt.widgets.Control.kEventControlTrack(Control.java:1953) at org.eclipse.swt.widgets.Widget.controlProc(Widget.java:367) at org.eclipse.swt.widgets.Display.controlProc(Display.java:835) at org.eclipse.swt.internal.carbon.OS.CallNextEventHandler(Native Method) at org.eclipse.swt.widgets.Tree.kEventMouseDown(Tree.java:2363) at org.eclipse.swt.widgets.Widget.mouseProc(Widget.java:1262) at org.eclipse.swt.widgets.Display.mouseProc(Display.java:2819) at org.eclipse.swt.internal.carbon.OS.SendEventToEventTarget(Native Method) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2938) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1352) Nondeterministic choosing between jboss-service.xml and jboss-minimal.xml for discovering port

by Rob Stryker (JIRA)

Nondeterministic choosing between jboss-service.xml and jboss-minimal.xml for discovering port ---------------------------------------------------------------------------------------------- Key: JBIDE-1352 URL: http://jira.jboss.com/jira/browse/JBIDE-1352 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.CR1 Reporter: Rob Stryker Assigned To: Rob Stryker Priority: Minor Fix For: 2.0.1 When automatically discovering server port from a server object (for shutdown, twiddle, xpath editing purposes) jboss-service.xml has an equal chance of being discovered as jboss-minimal.xml regardless of which configuration is used. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2053) There are no default ports for JBoss AS 5.0 in XML Configuration on JBoss Server View.

by Anton Klimkovich (JIRA)

There are no default ports for JBoss AS 5.0 in XML Configuration on JBoss Server View. -------------------------------------------------------------------------------------- Key: JBIDE-2053 URL: http://jira.jboss.com/jira/browse/JBIDE-2053 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.1.0.beta1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Preferences-> Server -> Installed Runtimes EXECUTE: Add new runtime EXECUTE: Set pass to JBoss AS 5.0 EXECUTE: Open JBoss Server View EXECUTE: Add New server EXECUTE: Select JBoss AS 5.0 ASSERT: Folder Ports with default ports in XML Configuration FAILURE: There are no default ports for JBoss AS 5.0 in XML Configuration -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2060) Wrong auggestion of code completion in jsf

by Victor Rubezhny (JIRA)

Wrong auggestion of code completion in jsf ------------------------------------------ Key: JBIDE-2060 URL: http://jira.jboss.com/jira/browse/JBIDE-2060 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, jsp/jsf/xml source editing Affects Versions: 2.1 Environment: JBoss Tools 2.1 latest build Reporter: Victor Rubezhny When a bean contains a methods like getXXX(param1, ...paramx) (which has 1 or more parameters), the content assist shows these methods as properties. When a bean contains a methods like setXXX(param1, param2, ...paramx) (which has more than 1 parameters) ro has no parameters at all, the content assist shows these methods as properties. -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-261) Legacy-jsf-struts guide splitting

by Svetlana mukhina (JIRA)

Legacy-jsf-struts guide splitting --------------------------------- Key: JBDS-261 URL: http://jira.jboss.com/jira/browse/JBDS-261 Project: Developer Studio Issue Type: Task Components: Doc - legacy-jsf-struts guide Affects Versions: 1.0.0.GA Reporter: Svetlana mukhina Assigned To: OLga Chikvina Fix For: 1.0.1 Legacy-jsf-struts should be separated to JSF and Struts guides -- 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, 11 months

3
18
0 / 0

[JBoss JIRA] Created: (JBDS-301) JSF Tools Ref Guide update

by Anatoly Fedosik (JIRA)

JSF Tools Ref Guide update -------------------------- Key: JBDS-301 URL: http://jira.jboss.com/jira/browse/JBDS-301 Project: Developer Studio Issue Type: Task Components: Doc - JSFTools Affects Versions: LATER Reporter: Anatoly Fedosik Assigned To: Anatoly Fedosik The guide should describe JSF using according to JBossTools (not JBDS !). 1. Remove mention about JBDS 2. Retake screens -- 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, 11 months

2
3
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 April 2008