March 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4773) NPE with Open-On from .jar file

by Yura Zhishko (JIRA)

NPE with Open-On from .jar file ------------------------------- Key: JBIDE-4773 URL: https://jira.jboss.org/jira/browse/JBIDE-4773 Project: JBoss Tools Issue Type: Bug Components: common, jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Yura Zhishko Assignee: Alexey Kazakov 1) Import project from https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... 2) Open paginator.xhtml from mareshkau.jar 3) Try to make Open-on, for example, on h:commandButton tag RESULT: java.lang.NullPointerException at org.jboss.tools.jsf.text.ext.hyperlink.JsfJSPTagNameHyperlinkPartitioner.recognize(JsfJSPTagNameHyperlinkPartitioner.java:78) at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:48) at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:55) at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:55) at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitionTypes(HyperlinkDetector.java:65) at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getPartitionType(BaseHyperlinkDetector.java:120) at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getHyperlinks(BaseHyperlinkDetector.java:52) at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.detectHyperlinks(BaseHyperlinkDetector.java:132) at org.eclipse.wst.sse.ui.internal.hyperlink.OpenHyperlinkAction$1.run(OpenHyperlinkAction.java:60) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.internal.hyperlink.OpenHyperlinkAction.run(OpenHyperlinkAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1191) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmKeyDown(Widget.java:1669) at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:4281) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3977) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4602) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2409) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3471) 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, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4952) No RichFaces components in palette

by Krasimir Goutcev (JIRA)

No RichFaces components in palette ---------------------------------- Key: JBIDE-4952 URL: https://jira.jboss.org/jira/browse/JBIDE-4952 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5.1 JBTools 3.1.0.v200909251801N-H118-M4 Reporter: Krasimir Goutcev Attachments: 2009-09-26_1453.png After new clean install I can't see RichFaces and A4j in palette (see picture) When i try DnD tld in palette nothing happen -- 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, 1 month

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3950) Add Enum type on configuration page for "EnumDecoder" decoder

by Maurice Zeijen (JIRA)

Add Enum type on configuration page for "EnumDecoder" decoder ------------------------------------------------------------- Key: JBIDE-3950 URL: https://jira.jboss.org/jira/browse/JBIDE-3950 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.0.0.CR2 Reporter: Maurice Zeijen The Enum decoder is used to map Strings to a Java enum. The decoder parameters are used to map the value to the Enum value. Here is a configuration example: <resource-config selector="decoder:test"> <resource>org.milyn.javabean.decoders.EnumDecoder</resource> <param name="enumType">example.trgmodel.LineOrderPriority</param> <param name="LOW">NOT_IMPORTANT</param> <param name="MEDIUM">IMPORTANT</param> <param name="HIGH">VERY_IMPORTANT</param> </resource-config> The enumType parameter defines the enumeration object. The other parameters represent the enum mapping (it isn't pretty, I know ;) ). The name of the parameter is the input value and the value of the parameter is the resulting enum name. A good editor could make this mapping easier by looking at the enum type and create the mapping for the several enum names. The user only needs to map the input values. Maybe the graph editor could also be enhanced to make it possible to map an enum to an enum. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1137) Wrong screen shot used within Visual Web Tools Reference Guide documentation Figure 3.65. Visual Page Editor Preferences Window

by Vlado Pakan (JIRA)

Wrong screen shot used within Visual Web Tools Reference Guide documentation Figure 3.65. Visual Page Editor Preferences Window ------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1137 URL: https://jira.jboss.org/jira/browse/JBDS-1137 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - VisualWebTools Affects Versions: 3.0.0.CR2 Environment: JBDS: jbdevstudio-eap-linux-gtk-3.0.0.v201002241510M-H184-CR2 Documentation: http://download.exadel.com/jboss_demos/JBDS_3.0.0.GA.zip Reporter: Vlado Pakan Assignee: Svetlana mukhina JBDS_2guidesversions/en/jsf/html_single/index.html document contains Figure 3.61. Calling Template Dialog which shows different dialog than one which is used by JBDS. Attached is file with dialog used by JBDS. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5958) server supplied esb runtime looks to be completely broken

by Max Rydahl Andersen (JIRA)

server supplied esb runtime looks to be completely broken --------------------------------------------------------- Key: JBIDE-5958 URL: https://jira.jboss.org/jira/browse/JBIDE-5958 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR3 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.1.0.CR3 Noticing these lines from JBIDE-5916: "However even after I do this, I notice in my Package Explorer that there is *NO* classpath container containing any ESB jars on hte project. So I check the .classpath file ot see if ANYTHING was added at all, and I see this: <classpathentry kind="con" path="server.supplied/SomeName"/> Aside from the ridiculously short and uninformative name "server.supplied", the adept user will note that this entry was not, actually, server supplied at all, but rather the *other* option, as I outlined abouve and pointed directly to an esb installation. Aside from that, this "server.supplied" is directly visible in the Java Build Path property page, under the Libraries tab. Which means this constant is exposed to users to see." AFAIK we added support in JBoss AS to return esb jar's when asked to supply that for esb facets. This seem to not be used at all, but instead it is inserting broken server.supplied entry into the classpath where it should actually be asking the server via the facet mechanism to provide it when the JBoss Runtime is added to the project! I'm marking this as blocker sine I hope this is a trivial fix so we can just use the standard mechanism and at least get rid of that broken server.supplied entry. If not, well lets discuss options. -- 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, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6003) JBoss Tools Update site page should mention Gef update

by Denis Golovin (JIRA)

JBoss Tools Update site page should mention Gef update ------------------------------------------------------ Key: JBIDE-6003 URL: https://jira.jboss.org/jira/browse/JBIDE-6003 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.CR3 Reporter: Denis Golovin Fix For: 3.1.0.GA When using Eclipse EPP for JEE developers smooks installation from update site fails wit error about missing Zest dependency -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6013) Wrong Import of Existing JSF project by the use of the context menu in Web Projects explorer

by Svetlana Yasenovich (JIRA)

Wrong Import of Existing JSF project by the use of the context menu in Web Projects explorer -------------------------------------------------------------------------------------------- Key: JBIDE-6013 URL: https://jira.jboss.org/jira/browse/JBIDE-6013 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Environment: v201003032254M-H39-CR3 Win XP Reporter: Svetlana Yasenovich Assignee: Viacheslav Kabanovich 1. Import the project https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... by the use of TortoiseSVN into disk D: 2. Open Studio (it is on disk C:) 3. In Web project explorer make Import existing JSF project by the use of the context menu and indicate imported JBIDE3247 project on disk D: 4. Choose Local Deployer Runtime and click Finish button ASSERT FAILED: folder JBIDE3247 in the workspace contains only .settings, .classpath and .project -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4635) OpenOn works incorrectly for custom elements which definition packed into jar file

by Maxim Areshkau (JIRA)

OpenOn works incorrectly for custom elements which definition packed into jar file ---------------------------------------------------------------------------------- Key: JBIDE-4635 URL: https://jira.jboss.org/jira/browse/JBIDE-4635 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M2 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.M3 1) import https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... project into workspace 2) open file /JBIDE3247/WebContent/pages/index.xhtml 3) make open on for some custom tag on this page(ma:paginator, c:inputCurrency or etc...) 4) jboss xml editor will be opened, but button link with editor from package explorer will be not working ASSERT This button should be working 5) if you open "Web App Libraries/mareshkau.jar/META-INF/mareshkau.taglib.xml" manualy in editor, button link to working and custom elements open on working to. -- 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, 1 month

6
22
0 / 0

[JBoss JIRA] Created: (JBIDE-5509) Seam Portlet Project - datasource deployment not available

by Dominik Pospisil (JIRA)

Seam Portlet Project - datasource deployment not available ---------------------------------------------------------- Key: JBIDE-5509 URL: https://jira.jboss.org/jira/browse/JBIDE-5509 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal Affects Versions: 3.1.0.CR1 Reporter: Dominik Pospisil Project created using "New Dynamic web Project" wizard with "JBoss Seam Portlet Project v2.0" configuration does not expose associted datasource for deployment. As a result deployment of the project fails. Steps to reproduce: 1) File -> New -> Dynamic Web Project 2) Select "JBoss Seam Portlet Project v2.0" configuration 3) Choose propper runtimes, finish. 4) Right click project, choose Run as -> Run on server 5) Run as resource deployment configuration dialog does not contain project datasource as expected. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6011) Integrate JBoss Tools with JSFUnit

by Stan Silvert (JIRA)

Integrate JBoss Tools with JSFUnit ---------------------------------- Key: JBIDE-6011 URL: https://jira.jboss.org/jira/browse/JBIDE-6011 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, testing Reporter: Stan Silvert Fix For: LATER Integrate JBoss Tools with JSFUnit -- 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, 1 month

1
0
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 March 2010