[JBoss JIRA] Created: (JBIDE-9501) Some JST/VPE editos classes use deprecated content assist processors code
by Victor Rubezhny (JIRA)
Some JST/VPE editos classes use deprecated content assist processors code
-------------------------------------------------------------------------
Key: JBIDE-9501
URL: https://issues.jboss.org/browse/JBIDE-9501
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, Visual Page Editor core
Affects Versions: 3.3.0.M2
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Priority: Minor
Fix For: 3.3.x
Some classes in JST/VPE editors use deprecated content assist processors code which is not actual and should be removed.
Since the org.jboss.tools.jst.jsp.contentassist.*ContentAssistProcessor classes are replaced by the recent equivalents (See org.jboss.tools.jst.jsp.contentassist.computers.*CompletionProposalComputer classes), these classes are subject to be removed.
But there are number of JST/VPE classes which use those deprecated and non-actual classes. These classes are to be re-factored using new set of Content Assist computer classes.
The Search on references to org.jboss.tools.jst.jsp.contentassist.*ContentAssistProcessor classes shows the following usages:
org.jboss.tools.jst.jsp.contentassist - src - org.jboss.tools.jst.jsp
FaceletPageContectAssistProcessor
JSPDialogContentProposalProvider
getParentTags(JspContentAssistProcessor)
processor
setContext(Properties)
org.jboss.tools.jst.jsp.jspeditor - src - org.jboss.tools.jst.jsp
JSPTextEditor
AttributeDescriptorValueProviderImpl
processor
org.jboss.tools.jst.jsp.outline - src - org.jboss.tools.jst.jsp
JSPContentOutlineConfiguration
createKbQuery(JspContentAssistProcessor, Node, int)
createNodeActionManager(TreeViewer)
new HTMLNodeActionManager() {...}
contributeAddChildActions(IMenuManager, Node, int, int)
JSPPropertySourceAdapter
createKbQuery(JspContentAssistProcessor)
processor
setTarget(INodeNotifier)
ValueHelper
createContentAssistProcessor() (2 matches)
createPageContext(JspContentAssistProcessor, int)
org.jboss.tools.vpe.editor.template.expression - src - org.jboss.tools.vpe
VpeFunctionSrc
createKbQuery(JspContentAssistProcessor, Node, int, String)
processValue(VpePageContext, Node, String)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10534) test failure in vpe.html
by Nick Boldt (Created) (JIRA)
test failure in vpe.html
------------------------
Key: JBIDE-10534
URL: https://issues.jboss.org/browse/JBIDE-10534
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core, Visual Page Editor Templates
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Yahor Radtsevich
Fix For: 3.3.0.Beta1
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... (failing for 3 builds)
{code}
Error Message
/mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--vpe/sources/tests/org.jboss.tools.vpe.html.test/target/work/data/htmlTest/WebContent/pages/jbide9975( 1 )/CSSImportConstruction.html.xml[/tests/test[1]/TD]: CSS property [height] is [19px], but should be [20px]
Stacktrace
junit.framework.AssertionFailedError: /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--vpe/sources/tests/org.jboss.tools.vpe.html.test/target/work/data/htmlTest/WebContent/pages/jbide9975( 1 )/CSSImportConstruction.html.xml[/tests/test[1]/TD]:
CSS property [height] is [19px], but should be [20px]
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.tools.vpe.base.test.ComponentContentTest.compareStyles(ComponentContentTest.java:114)
at org.jboss.tools.vpe.base.test.ComponentContentTest.performStyleTest(ComponentContentTest.java:368)
at org.jboss.tools.vpe.html.test.HtmlComponentContentTest.testCssImport(HtmlComponentContentTest.java:489)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-9420) JBoss Tools create unnecessary Linked Resources
by Fred Bricon (JIRA)
JBoss Tools create unnecessary Linked Resources
-----------------------------------------------
Key: JBIDE-9420
URL: https://issues.jboss.org/browse/JBIDE-9420
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Alexey Kazakov
Attachments: extra-linked-resources.jpg, extra-linked-resources.zip
When creating a multi module project with maven (war + jar for instance), if the war project installs the JSF facet, then all the sources of its dependent projects are added as linked resources.
It occurs when the KB nature is added. However, I've seen other occurences of the problem, where my eclipse plugins (not dependent on any JavaEE/JSF features) in the workspace also showcase this annoying behavior if JBT is installed.
I'm attaching 2 projects to reproduce the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10565) Wrong EL content assist inside token '#{'
by Viacheslav Kabanovich (Created) (JIRA)
Wrong EL content assist inside token '#{'
-----------------------------------------
Key: JBIDE-10565
URL: https://issues.jboss.org/browse/JBIDE-10565
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.M5
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.Beta1
EXECUTE: Type #{ in attribute value or in text node in xml.
EXECUTE: Set cursor inside that token #|{ and invoke content assist.
FAILURE: JBoss Tools provide all names available for EL (CDI named beans, Seam components, JSF managed beans and resource bundles, etc.)
FAILUTE: If a proposal 'abc' is selected for insertion, it is inserted in this way: #abc}{
ASSERT: JBoss Tools provides nothing for that position.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-9095) "Externalize selected string" - press (or Ctrl+7) when focus is in Snippets view - get NPE
by Vitali Yemialyanchyk (JIRA)
"Externalize selected string" - press (or Ctrl+7) when focus is in Snippets view - get NPE
------------------------------------------------------------------------------------------
Key: JBIDE-9095
URL: https://issues.jboss.org/browse/JBIDE-9095
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.2
Reporter: Vitali Yemialyanchyk
Assignee: Yahor Radtsevich
Priority: Blocker
java.lang.NullPointerException
at org.jboss.tools.jst.jsp.i18n.ExternalizeStringsWizard.getContainerFullPath(ExternalizeStringsWizard.java:346)
at org.jboss.tools.jst.jsp.i18n.ExternalizeStringsWizard.addPages(ExternalizeStringsWizard.java:118)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:605)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.jboss.tools.jst.jsp.i18n.handlers.I18nHandler.execute(I18nHandler.java:122)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
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:241)
at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829)
at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815)
at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4163)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:344)
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:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8009) h:link must not necessarily be nested in a form
by Yahor Radtsevich (JIRA)
h:link must not necessarily be nested in a form
-----------------------------------------------
Key: JBIDE-8009
URL: https://issues.jboss.org/browse/JBIDE-8009
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.2.0.Beta2
Reporter: Yahor Radtsevich
Assignee: Maxim Areshkau
Priority: Minor
Fix For: 3.3.x
In some cases VPE renders h:link as "${value}: This link is disabled as it is not nested within a JSF form" while in browsers is rendered without errors (see screenshot-1.png).
STEPS TO REPRODUCE
1. Import RichFaces 4.0 Showcase into workspace [1].
2. Open the file 'welcome.xhtml'.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months