September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12126) Inform user that the selected project does not contain portlet.xml file

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12126: --------------------------------------- Summary: Inform user that the selected project does not contain portlet.xml file Key: JBIDE-12126 URL: https://issues.jboss.org/browse/JBIDE-12126 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Portal/GateIn Affects Versions: 3.3.0.CR1 Reporter: Lucia Jelinkova Assignee: Snjezana Peco Fix For: 3.3.1 When I try to create a Java portlet for a Dynamic web project that does not have the portlet.xml file, the error is logged into Error log. {code} java.lang.RuntimeException: The portlet.xml file doesn't exist at org.jboss.tools.portlet.ui.PortletUIActivator.getPortletXmlFile(PortletUIActivator.java:90) at org.jboss.tools.portlet.ui.internal.wizard.NewPortletClassDataModelProvider.validate(NewPortletClassDataModelProvider.java:353) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.validate(DataModelImpl.java:377) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.isValid(DataModelImpl.java:423) at org.eclipse.jst.servlet.ui.internal.wizard.NewWebArtifactWizard.canFinish(NewWebArtifactWizard.java:66) at org.eclipse.jface.wizard.WizardDialog.updateButtons(WizardDialog.java:1345) at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1334) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1265) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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:257) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277) 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.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) {code} However, if user does not have error log displayed he / she has no clue what has happened. Could you provide a warning in the wizard about missing portlet.xml file (and that it won't be generated automatically)? In that case the message's severity in Error log can be changed from error to warning too. -- 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

13 years, 6 months

4
17
0 / 0

[JBoss JIRA] (JBIDE-12579) m2e eclipse error in multiple.target

by Paul Richardson (JIRA)

Paul Richardson created JBIDE-12579: --------------------------------------- Summary: m2e eclipse error in multiple.target Key: JBIDE-12579 URL: https://issues.jboss.org/browse/JBIDE-12579 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.0.x Reporter: Paul Richardson Assignee: Nick Boldt Updated to the HEAD (r 43577) version of multiple.target this morning and tried to apply it as the target platform in eclipse. However, it fails with an error concerning m2e's feature group cannot be found. Attached a diff of what I think should be the fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6072) rich:panel do not render its surplus tags in VPE

by Denis Maliarevich (JIRA)

rich:panel do not render its surplus tags in VPE ------------------------------------------------ Key: JBIDE-6072 URL: https://jira.jboss.org/jira/browse/JBIDE-6072 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.1.0.GA Reporter: Denis Maliarevich Assignee: Denis Maliarevich Priority: Minor Fix For: 3.2.next Problem: On server rich:panel renders unwanted elements for instance additional footer facet in panel's content. But VPE does NOT show elements that are not allowed by richfaces tag specification. Solution: Show surplus tags in VPE for rich:panel. Example: <rich:panel> <f:facet name="header"> PHead111 <h:outputText>PanelHeader1</h:outputText> <h:outputText>PanelHeader2</h:outputText> <h:outputText>PanelHeader3</h:outputText> <span>P1Head</span> PHead </f:facet> <f:facet name="footer"> <h:outputText>Col 1 footer3</h:outputText> <span>COL1FOOT</span> C1FText FooterFacet </f:facet> Panel Content </rich:panel> Behaviour: Text "COL1FOOT C1FText FooterFacet" should be rendered in the panel's content. -- 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

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3225) Components should render usual text inside

by Yura Zhishko (JIRA)

Components should render usual text inside ------------------------------------------ Key: JBIDE-3225 URL: https://jira.jboss.org/jira/browse/JBIDE-3225 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor 1) DND or create any component from the list below 2) Print usual text inside component ASSERT: Text should be rendered in VPE RESULT: Text isn't rendered Here is list of components with the same behavior: <rich:inplaceInput> <rich:inplaceSelect> <rich:inputNumberSlider> <rich:inputNumberSpinner> <rich:paint2D> <rich:spacer> <a4j:actionparam> <a4j:commandButton> <a4j:push> <a4j:log> <h:commandButton> <h:inputHidden> <h:inputText> <h:inputTextarea> <h:messages> <h:selectBooleanCheckbox> -- 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

13 years, 6 months

6
22
0 / 0

[JBoss JIRA] (JBIDE-12421) <a4j:log> tag has very huge height, this is wrong representation

by Denis Maliarevich (JIRA)

Denis Maliarevich created JBIDE-12421: ----------------------------------------- Summary: <a4j:log> tag has very huge height, this is wrong representation Key: JBIDE-12421 URL: https://issues.jboss.org/browse/JBIDE-12421 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.4.0.M1 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Priority: Minor Fix For: 3.4.0.M1 <a4j:log> template should be updated. -- 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

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12262) org.jboss.tools.jsf.vpe.jsf.test failure

by Alexey Kazakov (JIRA)

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12263) org.jboss.tools.jsf.vpe.seam.test failure

by Alexey Kazakov (JIRA)

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)

by Gabriel De Repentigny (JIRA)

13 years, 6 months

9
31
0 / 0

[JBoss JIRA] (JBIDE-12344) Eclipse 3.8: Rotate editor's icon is disabled when web page is opened.

by Denis Maliarevich (JIRA)

Denis Maliarevich created JBIDE-12344: ----------------------------------------- Summary: Eclipse 3.8: Rotate editor's icon is disabled when web page is opened. Key: JBIDE-12344 URL: https://issues.jboss.org/browse/JBIDE-12344 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.4.0.M1 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Fix For: 3.4.0.M1 Attachments: rotateDisabled.png When a web page is opened in VPE in Eclipse 3.8 -- Rotate editor's icon is disabled on the toolbar. There is a state while opening the page, when all the vpe toolbar items are disabled (just for 1 sec or less) but then they get enabled (except i18n icon). Rotate editor's icon still disabled after the page has been loaded and opened. -- 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

13 years, 6 months

2
9
0 / 0

[JBoss JIRA] (JBIDE-12395) Error in error log when opening Preferences for web page opened in VPE

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-12395: ----------------------------------- Summary: Error in error log when opening Preferences for web page opened in VPE Key: JBIDE-12395 URL: https://issues.jboss.org/browse/JBIDE-12395 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.4.0.M1 Environment: JBT 3.4.0.v20120801-1025-H5341-M1, Linux 64bit+KDE, Java Sun 1.7.0._04, Eclipse Juno SR03 Reporter: Vlado Pakan Assignee: Yahor Radtsevich Fix For: 3.4.0.M1 1. Create JSF2.0 Kick Start project 2. Open inputname.xhtnl page 3. Click on Preference toolitem within workbench toolbar ERROR: In Error log appears this error: Cannot convert RGB color to string, because it is null An exception stack trace is not available. -- 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

13 years, 6 months

2
7
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 September 2012