February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10809) Can't Resolve Property if Interface Extending another Interface

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-10809: ---------------------------------- Summary: Can't Resolve Property if Interface Extending another Interface Key: JBIDE-10809 URL: https://issues.jboss.org/browse/JBIDE-10809 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M5 Reporter: Cody Lerum This broke in a recently nightly (last 2 weeks) Entity User implements IndexedEntity IndexedEntity extends SearchableEntity SearchableEntity extends BaseEntity entityId is a property of BaseEntity searchResultName is a property of SearchableEntity search.results returns a List<SearchableEntity> {code} <rich:dataTable value="#{search.results}" var="_r" styleClass="standardTable"> <rich:column styleClass="left"> <f:facet name="header">Name</f:facet> <h:link value="#{_r.searchResultName}" outcome="#{_r.entityType.viewId}"> <f:param name="oid" value="#{_r.entityId}" /> </h:link> </rich:column> </rich:dataTable> {code} Gives error "entityId" cannot be resolved searchResultName can be resolved. -- 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

12 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-10199) Cannot use the RESTful Web Services creation wizard with JBossAS7

by Xavier Coulon (Created) (JIRA)

Cannot use the RESTful Web Services creation wizard with JBossAS7 ----------------------------------------------------------------- Key: JBIDE-10199 URL: https://issues.jboss.org/browse/JBIDE-10199 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon The "RESTful Web Services creation" wizard claims that the RESTEasy jars are not found in the project which uses JBossAS7 as a target runtime. Yet, the JAX-RS APIs are available in the classpath. -- 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

12 years, 4 months

10
26
0 / 0

[JBoss JIRA] (JBIDE-10819) vpe not rendering default index.xhtml for JBoss EE Web Project

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10819: ------------------------------------------- Summary: vpe not rendering default index.xhtml for JBoss EE Web Project Key: JBIDE-10819 URL: https://issues.jboss.org/browse/JBIDE-10819 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M5 Reporter: Max Rydahl Andersen Assignee: Yahor Radtsevich Priority: Critical Fix For: 3.3.0.Beta1 Attachments: screenshot0.png Use jboss central to get "JBoss JEE Web Project" example Open .xhtml Assert: layout is more or less similar to what will be shown in browser. Currently it isn't - looks like styles or templates aren't loaded properly. -- 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

12 years, 4 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-10888) OpenShift wizard jobs must be cancelable because they block the UI

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-10888: ------------------------------------- Summary: OpenShift wizard jobs must be cancelable because they block the UI Key: JBIDE-10888 URL: https://issues.jboss.org/browse/JBIDE-10888 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Xavier Coulon Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta1 If an operation on OpenShift takes too much time, the Eclipse UI remains blocked, and the Job cannot be canceled. We must make the jobs cancelable, even if there are side effects (ie, not sure in which state the domain / application will be). As a complement, we should provide a 'refresh' button to let the user manually refresh the OpenShift Express Console view after a few seconds (or minutes). -- 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

12 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-10793) jsf.ui.test failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10793: -------------------------------------- Summary: jsf.ui.test failure Key: JBIDE-10793 URL: https://issues.jboss.org/browse/JBIDE-10793 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.Beta1 {code} Tests run: 72, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 273.291 sec <<< FAILURE! testRenameMethod(org.jboss.tools.jsf.ui.test.refactoring.ELReferencesRenameTest) Time elapsed: 2.356 sec <<< ERROR! java.lang.ClassCastException: org.jboss.tools.common.refactoring.BaseFileChange cannot be cast to org.eclipse.ltk.core.refactoring.TextFileChange at org.jboss.tools.jsf.ui.test.refactoring.ELReferencesRenameTest.renameELReferences(ELReferencesRenameTest.java:62) at org.jboss.tools.jsf.ui.test.refactoring.ELReferencesRenameTest.testRenameMethod(ELReferencesRenameTest.java:42) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) 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) Results : Tests in error: testRenameMethod(org.jboss.tools.jsf.ui.test.refactoring.ELReferencesRenameTest) Tests run: 72, Failures: 0, Errors: 1, Skipped: 0 {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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9635) Duplicate view-handler in faces-config.xml in JBoss Seam/Portlet Project

by Joao Viragine (JIRA)

Duplicate view-handler in faces-config.xml in JBoss Seam/Portlet Project ------------------------------------------------------------------------ Key: JBIDE-9635 URL: https://issues.jboss.org/browse/JBIDE-9635 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBDS 4.1 Reporter: Joao Viragine When we create a Seam Web Project with JBoss Seam Portlet Facet, JBDS generates a duplicate entry for view-handler in faces-config.xml as follow: <?xml version="1.0" encoding="UTF-8"?> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd" version="1.2"> <application> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> <view-handler>org.jboss.portletbridge.application.PortletViewHandler</view-handler> <state-manager>org.jboss.portletbridge.application.PortletStateManager</state-manager> <locale-config> <default-locale>en</default-locale> <supported-locale>bg</supported-locale> <supported-locale>de</supported-locale> <supported-locale>en</supported-locale> <supported-locale>fr</supported-locale> <supported-locale>tr</supported-locale> </locale-config> </application> </faces-config> We should remove the entry: <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-10259) Cannot add JBoss Core Portlet facet if it has been removed before.

by Lucia Jelinkova (Created) (JIRA)

Cannot add JBoss Core Portlet facet if it has been removed before. ------------------------------------------------------------------- Key: JBIDE-10259 URL: https://issues.jboss.org/browse/JBIDE-10259 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.3.0.M4 Reporter: Lucia Jelinkova Assignee: Snjezana Peco When I try to remove JBoss Core Portlet facet from a project (using Properties dialog) and then add it again, I get an error about duplicate entry: Build path contains duplicate entry: 'org.jboss.tools.portlet.core.internal.portletlibrarycontainer.runtime' -- 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

12 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-10260) Inconsistent output of Create Portlet Wizard when leaving default

by Lucia Jelinkova (Created) (JIRA)

Inconsistent output of Create Portlet Wizard when leaving default ----------------------------------------------------------------- Key: JBIDE-10260 URL: https://issues.jboss.org/browse/JBIDE-10260 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.3.0.M4 Reporter: Lucia Jelinkova Assignee: Snjezana Peco I have a project with JBoss JSF Portlet facet. I want to create a JSF portlet and leave as many default as I can. However, different files are generated if I click the Finish button on the first or on the last page of wizard. Scenario A: 1. Show the wizard 2. Click Next through all pages and leave defaults there 3. Click Finish 4. The WEB-INF contains the following files: faces-config.xml, portlet.xml and web.xml Scenario B: 1. Show the wizard 2. Click finish on the first or the second wizard page (do not go to the last page of wizard) 4. The WEB-INF contains the files from the previous scenario as well as these additional ones: default-object.xml, portlet-instances.xml, jboss-app.xml, jboss-portlet.xml The generated file jboss-app.xml causes that the whole project will not be deployed to the server due to the missing DTD file: java.io.FileNotFoundException: http://www.jboss.org/dtd/jboss-app_2_6.dtd -- 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

12 years, 4 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-10673) NullPointerException when creating Dynamic Web Project with JSF Portlet facet and no targeted runtime

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-10673: --------------------------------------- Summary: NullPointerException when creating Dynamic Web Project with JSF Portlet facet and no targeted runtime Key: JBIDE-10673 URL: https://issues.jboss.org/browse/JBIDE-10673 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.3.0.M5 Reporter: Lucia Jelinkova Assignee: Snjezana Peco When I try to create a Dynamic Web Project with JBoss JSF Portlet Facet but I do not select any runtime and on all wizard pages select to disable library configuration, after hiting Finish button an error dialog appears with NullPointerException. The project is then created but without the JBoss JSF Portlet facet. Exception in error log: java.lang.NullPointerException at org.jboss.tools.portlet.core.JBossWebUtil.getFacesConfig(JBossWebUtil.java:243) at org.jboss.tools.portlet.core.internal.project.facet.JSFPortletFacetInstallDelegate.getFacesConfigFile(JSFPortletFacetInstallDelegate.java:217) at org.jboss.tools.portlet.core.internal.project.facet.JSFPortletFacetInstallDelegate.configureFacesConfig(JSFPortletFacetInstallDelegate.java:109) at org.jboss.tools.portlet.core.internal.project.facet.JSFPortletFacetInstallDelegate.execute(JSFPortletFacetInstallDelegate.java:90) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:282) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10867) Fix conflcting Birt features versions in our Repository

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-10867: -------------------------------------- Summary: Fix conflcting Birt features versions in our Repository Key: JBIDE-10867 URL: https://issues.jboss.org/browse/JBIDE-10867 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Environment: any Reporter: Mickael Istria Assignee: Mickael Istria Using repository http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S... trunk/birt$ mvn install -Dmaven.test.skip=true -DskipTests=true -DtychoVersion=0.14.0-SNAPSHOT ... [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.birt.feature.feature.group 1.3.0.qualifier [ERROR] Only one of the following can be installed at once: [org.eclipse.birt.chart.ui 3.7.1.v20110905, org.eclipse.birt.chart.ui 3.7.2.v20120130] [ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.feature.group 3.7.1.v20110905-7r9e7DFQCnvKN75--lXE5 depends on: org.eclipse.birt.chart.ui [3.7.1.v20110905] [ERROR] Cannot satisfy dependency: org.eclipse.birt.feature.group 3.7.2.v20120130-BDF9E9bGTzuHh02eP-27WvmBpq8k depends on: org.eclipse.birt.chart.ui [3.7.2.v20120130] [ERROR] Cannot satisfy dependency: org.jboss.tools.birt.feature.feature.group 1.3.0.qualifier depends on: org.eclipse.birt.chart.feature.group 2.5.0 [ERROR] Cannot satisfy dependency: org.jboss.tools.birt.feature.feature.group 1.3.0.qualifier depends on: org.eclipse.birt.feature.group 2.5.0 -- 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

12 years, 4 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012