May 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4927) There isa no way to edit JMX Connection properties in MBean Explorer

by Denis Golovin (JIRA)

There isa no way to edit JMX Connection properties in MBean Explorer -------------------------------------------------------------------- Key: JBIDE-4927 URL: https://jira.jboss.org/jira/browse/JBIDE-4927 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jmx Affects Versions: 3.1.0.M4 Reporter: Denis Golovin -- 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

15 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-1215) The installer could not find EAP 4.3 Seam runtimes in recent CPs

by Dominik Pospisil (JIRA)

The installer could not find EAP 4.3 Seam runtimes in recent CPs ---------------------------------------------------------------- Key: JBDS-1215 URL: https://jira.jboss.org/jira/browse/JBDS-1215 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Dominik Pospisil The location of Seam runtimes bundled in EAP 4.3 has changed in recent CPs. The instaler could no more find bundled Seam runtimes. The location changed from: jboss-eap-4.3/seam jboss-eap-4.3/seamfp to jboss-eap-4.3/seam1 jboss-eap-4.3/seam2 -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6182) jboos-birt-servlet.jar updated for BIRT 2.5.1 and 2.5.2

by Javier RodrÃguez (JIRA)

jboos-birt-servlet.jar updated for BIRT 2.5.1 and 2.5.2 ------------------------------------------------------- Key: JBIDE-6182 URL: https://jira.jboss.org/jira/browse/JBIDE-6182 Project: Tools (JBoss Tools) Issue Type: Patch Components: birt Affects Versions: 3.1.0.GA Environment: JBoss Tools 3.1.0.GA, Seam 2.2.0.GA, BIRT 2.5.1 and BIRT 2.5.2 Reporter: Javier RodrÃguez Assignee: Snjezana Peco Fix For: 3.1.0.GA BIRT 2.5.1 -> Error passing data parameters to embedded Birt Report. BIRT 2.5.2 -> Previous error + 'NoSuchMethod' Exception when rendering report -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-973) Splash Screen has wrong Version

by Vlado Pakan (JIRA)

Splash Screen has wrong Version ------------------------------- Key: JBDS-973 URL: https://jira.jboss.org/jira/browse/JBDS-973 Project: JBoss Developer Studio Issue Type: Bug Components: ui/branding Affects Versions: 2.1.1 Environment: Linux 32 bit Reporter: Vlado Pakan Splash screen displayed when Studio is starting has wrong version number 2.1.0 GA instead 2.1.1 GA. -- 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

15 years, 10 months

6
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5968) JSF Portlet Facet always adds richfaces fragments to web.xml

by Dominik Pospisil (JIRA)

JSF Portlet Facet always adds richfaces fragments to web.xml ------------------------------------------------------------ Key: JBIDE-5968 URL: https://jira.jboss.org/jira/browse/JBIDE-5968 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Dominik Pospisil JSF Portlet Facet always adds richfaces fragments to web.xml. Created project could not be deployed due to missing richfaces libraries. Steps to reproduce: 1) File -> New -> Dynamic Web Project 2) Select EPP 4.3 Runtime 3) Click Modify on Runtime configuration 4) Select JSF 1.2 facet and JBoss Core Portlet and JBoss JSF Portlet facets 5) Click OK, 5x next 6) JBoss JSF Portlet Capabilities - do NOT select Add/Change richfaces libraries 7) click Finish Geneated web.xml contains following fragment which I guess should not be there: <context-param> <param-name>org.richfaces.LoadStyleStrategy</param-name> <param-value>NONE</param-value> </context-param> <context-param> <param-name>org.richfaces.LoadScriptStrategy</param-name> <param-value>NONE</param-value> </context-param> <context-param> <param-name>org.ajax4jsf.RESOURCE_URI_PREFIX</param-name> <param-value>rfRes</param-value> </context-param> <filter> <display-name>Ajax4jsf Filter</display-name> <filter-name>ajax4jsf</filter-name> <filter-class>org.ajax4jsf.Filter</filter-class> </filter> <filter-mapping> <filter-name>ajax4jsf</filter-name> <servlet-name>Faces Servlet</servlet-name> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping> When removed from web.xml, portlet deploys correctly. Server console shows: 14:51:25,306 INFO [TomcatDeployer] deploy, ctxPath=/testProject3, warUrl=.../deploy/testProject3.war/ 14:51:25,723 ERROR [ContainerBase] Exception starting filter ajax4jsf java.lang.ClassNotFoundException: org.ajax4jsf.Filter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1364) -- 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

15 years, 10 months

4
15
0 / 0

[JBoss JIRA] Created: (JBDS-950) Refactoring of Managed Bean/Methods/Properties which are used in ELs

by Svetlana mukhina (JIRA)

Refactoring of Managed Bean/Methods/Properties which are used in ELs -------------------------------------------------------------------- Key: JBDS-950 URL: https://jira.jboss.org/jira/browse/JBDS-950 Project: JBoss Developer Studio Issue Type: Task Components: Doc - JSFTools, Doc - RHDS GSG, Doc - Seam Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc /trunk/documentation/whatsnew/seam/seam-news-3.1.0.M4.html: "Rename action for Seam Components/Methods/Properties: Rename action for Seam Components/Methods/Properties also shows all resources that has references renamed element in EL Rename actions are available: * from context menu on a Seam component inside Seam Components View * from context menu on a method/property in Java Source editor" also see the linked task -- 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

15 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBDS-1187) Configuration plugin errors in feature.xml file

by Eric D. Schabell (JIRA)

Configuration plugin errors in feature.xml file ------------------------------------------------ Key: JBDS-1187 URL: https://jira.jboss.org/jira/browse/JBDS-1187 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 3.0.0.GA Environment: Fedora 12, x86_64, lenovo T500 Reporter: Eric D. Schabell Priority: Minor Clean install of JBDS 3.0 and want to add plugin JD (decompiler), enable feature Preferences -> General -> Capabilities -> Classic Update, then try to add JD as new plugin remote location in update software section gives errors on this file which block further installation: jbdevstudio/studio/eclipse/features/org.jboss.tools.runtime.feature_1.1.0.v201003100055R-H50-GA/feature.xml Errors are 2: 1) only one URL tag allowed, it detects more than one 2) no closing FEATURE tag Fixed by removing the LICENSE line with URL and complete copyright section leaving only this: <?xml version="1.0" encoding="UTF-8"?> <feature id="org.jboss.tools.runtime.feature" label="%featureName" version="1.1.0.v201003100055R-H50-GA" provider-name="%providerName"> <description> %description </description> <copyright> JBoss by Red Hat Copyright 2009-2010, JBoss by Red Hat, and individual contributors as indicated by the @authors tag. See the copyright.txt in the distribution for a full listing of individual contributors. </copyright> <plugin id="org.jboss.tools.runtime" download-size="0" install-size="0" version="1.1.0.v201003100055R-H50-GA" unpack="false"/> </feature> -- 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

15 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5993) NullPointerException

by Alexey Kazakov (JIRA)

NullPointerException --------------------- Key: JBIDE-5993 URL: https://jira.jboss.org/jira/browse/JBIDE-5993 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.1 1. Create a Seam project. 2. Open home.xhtml 3. Select <li> (the whole tag) 4. Right Mouse Click 5. See eclipse log: java.lang.NullPointerException at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanNodeContent(SeamRefactorContributionFactory.java:321) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:308) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.scanChildNodes(SeamRefactorContributionFactory.java:312) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.checkContextVariableInDOM(SeamRefactorContributionFactory.java:284) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.createContributionItems(SeamRefactorContributionFactory.java:199) at org.eclipse.ui.internal.menus.ProxyMenuAdditionCacheEntry.createContributionItems(ProxyMenuAdditionCacheEntry.java:60) at org.eclipse.ui.internal.menus.WorkbenchMenuService$5.run(WorkbenchMenuService.java:561) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.menus.WorkbenchMenuService.processAdditions(WorkbenchMenuService.java:622) at org.eclipse.ui.internal.menus.WorkbenchMenuService.addContributionsToManager(WorkbenchMenuService.java:683) at org.eclipse.ui.internal.menus.WorkbenchMenuService.populateContributionManager(WorkbenchMenuService.java:669) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:203) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:203) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:76) at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:357) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:335) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:338) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:469) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:491) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:4270) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3974) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1578) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2010) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:254) at org.eclipse.swt.widgets.Display.runPopups(Display.java:3906) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3467) 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(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: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

15 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5948) A lot of exceptions are thorwn by CDI model if user changes source folder.

by Alexey Kazakov (JIRA)

A lot of exceptions are thorwn by CDI model if user changes source folder. -------------------------------------------------------------------------- Key: JBIDE-5948 URL: https://jira.jboss.org/jira/browse/JBIDE-5948 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 3.1.1, 3.2.next 1. Create any CDI project (enable CDI support for a java project). 2. Build the project. 3. Create an alternative source folder. 4. Set this new folder as source instead of first one. 5. Build the project. See Eclipse log. There are a lot of exceptions like Java Model Exception: Java Model Status [JavaSource [in tck] is not on its project's build path] See the attached log for details. I tested it on CDI TCK 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

15 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6272) Portletbridge 2.0.0.FINAL doesn't recognize the javax.faces.LIFECYCLE_ID parameter

by Snjezana Peco (JIRA)

Portletbridge 2.0.0.FINAL doesn't recognize the javax.faces.LIFECYCLE_ID parameter ---------------------------------------------------------------------------------- Key: JBIDE-6272 URL: https://jira.jboss.org/jira/browse/JBIDE-6272 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.1.0.GA Reporter: Snjezana Peco Assignee: Snjezana Peco This parameter was necessary in earlier 2.0.x versions of Seam portlets. -- 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

15 years, 10 months

2
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 May 2010