July 2009 - jbosstools-issues - Jboss List Archives

[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: (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-3183) We create clone for nodes which we shouldn't clone

by Maxim Areshkau (JIRA)

We create clone for nodes which we shouldn't clone -------------------------------------------------- Key: JBIDE-3183 URL: https://jira.jboss.org/jira/browse/JBIDE-3183 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.alpha Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.cr1 If in EL expression exist node bean.name, but we use on page bean.name1, for this node we create clone. -- 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-4534) Execution JUnit tests for VPE sometimes sleeps for long time

by Maxim Areshkau (JIRA)

Execution JUnit tests for VPE sometimes sleeps for long time ------------------------------------------------------------ Key: JBIDE-4534 URL: https://jira.jboss.org/jira/browse/JBIDE-4534 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Critical Fix For: 3.1.0.M3 Execution of junit tests sometimes sleeps. Hard to reproduce. In VpeController see line 266, place of main thread sleep. if (xm != null) { WebProject.getInstance(xm).getTaglibMapping().revalidate( WebAppHelper.getWebApp(xm)); } Method 'revalidate' is synchronized and blocked by other thread. See threads stacks in attachment. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2990) Exception is occured when open inpuUserName.jsp from JSF KickStart project.

by Anton Klimkovich (JIRA)

Exception is occured when open inpuUserName.jsp from JSF KickStart project. --------------------------------------------------------------------------- Key: JBIDE-2990 URL: https://jira.jboss.org/jira/browse/JBIDE-2990 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Reporter: Anton Klimkovich Assignee: Maxim Areshkau EXECUTE: Create jsf 1.2 kickstart project EXECUTE: Open inpuUserName.jsp FAILURE: Illegal character in authority at index 7: file://C:\jbdevstudio2.0Beta1\studio\eclipse\plugins\org.jboss.tools.vpe_3.0.0.Beta1-N200810231916\ve\EditorOverride.css An exception stack trace is not available. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3061) Visual part of VPE does not react to any key-typing

by Max Rydahl Andersen (JIRA)

Visual part of VPE does not react to any key-typing --------------------------------------------------- Key: JBIDE-3061 URL: https://jira.jboss.org/jira/browse/JBIDE-3061 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Maxim Areshkau Priority: Critical Fix For: 3.0.0.beta1 As subject says - typing characters does not work, neither does delete key etc. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3410) java.lang.NullPointerException when try to open page in CR1-20081215 nightly

by Yura Zhishko (JIRA)

java.lang.NullPointerException when try to open page in CR1-20081215 nightly ---------------------------------------------------------------------------- Key: JBIDE-3410 URL: https://jira.jboss.org/jira/browse/JBIDE-3410 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Environment: jbdevstudio-win32-2.0.0.CR1-N200812150006 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Critical 1) Open jbdevstudio-win32-2.0.0.CR1-N200812150006 2) Import attached project 3) Open allComponents.xhtml java.lang.NullPointerException at org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:313) at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:186) at org.jboss.tools.jsf.vpe.ajax4jsf.Activator.getPluginResourcePath(Activator.java:68) at org.jboss.tools.jsf.vpe.ajax4jsf.template.Ajax4JSFMediaOutput.getAbsoluteResourcePath(Ajax4JSFMediaOutput.java:65) at org.jboss.tools.jsf.vpe.ajax4jsf.template.Ajax4JSFMediaOutput.create(Ajax4JSFMediaOutput.java:48) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:467) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:224) at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:314) at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:767) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:553) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:548) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$5.onLoadWindow(MozillaEditor.java:292) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:407) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:341) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:773) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:247) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:447) 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.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:263) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1410) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:944) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$27.runWithException(Workbench.java:1361) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2293) 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.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32) 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(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) -- 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-3588) Name off CSS style class is dublicated in CSS dialog combobox

by Yura Zhishko (JIRA)

Name off CSS style class is dublicated in CSS dialog combobox ------------------------------------------------------------- Key: JBIDE-3588 URL: https://jira.jboss.org/jira/browse/JBIDE-3588 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Sergey Dzmitrovich Priority: Minor 1) Call CSS dialog on any CSS style class in CSS file 2) Check combobox for a style 3) Go to the end of list RESULT: Style class name is dublicated -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3508) Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE

by Karl Philipp (JIRA)

Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE ----------------------------------------------------------------------------------------- Key: JBIDE-3508 URL: https://jira.jboss.org/jira/browse/JBIDE-3508 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.0.0.CR2 Environment: Windows XP SP3, Eclipse 3.4 "GANYMEDE", Web Tools 3.0.3, RichFaces-VPE-win32-3.0.0.CR2-N200901081811, RichFaces 3.2.2.SR1, JSF 1.2 RI, Facelets 1.1.14 Reporter: Karl Philipp Orphaned namedspaced end tags such as </rich:panel> are not detected by the validation algorithm in contrast to orphaned namedspaced start tags: <h:form id="searchForm"> <rich:panel> <f:facet name="header"> <h:outputText value="ServiceProvider" /> </f:facet> <a4j:commandButton value="Search" action="#{sps.search}" /> </rich:panel> </h:form> </rich:panel> The last end tag </rich:panel> above is orphaned but not detected as invalid by VPE. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4667) Import Tags from TLD file works wrong after second calling

by Yura Zhishko (JIRA)

Import Tags from TLD file works wrong after second calling ---------------------------------------------------------- Key: JBIDE-4667 URL: https://jira.jboss.org/jira/browse/JBIDE-4667 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor 1) Create any project 2) Open JBoss Palette 3) Press Import button 4) In Import tags from TLD File dialog press Browse... button 5) Choose any tag lib, for example, x-1_0-rt.tld 6) Press OK button ASSERT: All fields in Import tags from TLD File dialog: TLD File*, Name*, Default Prefix, Library URI are filled 7) Press Cancel button 8) Repeat steps 3-6 ASSERT: Result is the same: All fields in Import tags from TLD File dialog: TLD File*, Name*, Default Prefix, Library URI are filled. ASSERT FAILED: Only TLD File* path is filled. -- 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
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 July 2009