April 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6080) "Use workspace metadata" deployment option is not working for JBoss 6.0.0

by Denis Golovin (JIRA)

"Use workspace metadata" deployment option is not working for JBoss 6.0.0 ------------------------------------------------------------------------- Key: JBIDE-6080 URL: https://jira.jboss.org/jira/browse/JBIDE-6080 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.GA Environment: JBT 3.1.0.GA JBoss 6.0.0.M2 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
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6194) JBoss Maven Integration Tool - problem with deployment

by Svetlana mukhina (JIRA)

JBoss Maven Integration Tool - problem with deployment ------------------------------------------------------ Key: JBIDE-6194 URL: https://jira.jboss.org/jira/browse/JBIDE-6194 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.1.0.GA Environment: Eclipse Version: 3.5.1 Server: JBoss 5.1, EAP 4.3 jdk: tested for 1.5 and 1.6 m2e version: 0.10.0.20100209-0800 JBoss Maven Integration Tool version:1.0.0.v201004140113N-H47-GA Maven version: 2.0.9 Reporter: Svetlana mukhina Assignee: Snjezana Peco Attachments: server_log_for_deployment_fail.txt While documenting a JBoss Maven Integration Tool and I experience a problem with deploying Seam Booking Example - EAR mavenized - seam 2.1.1.GA project to JBoss Server. booking, booking-ear, booking-ejb, booking-parent are built without troubles, but I get the following error while deploying: ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/opt/JBoss_Developer_Studio/jbds20100310/jboss-eap/jboss-as/server/default/deploy/booking-ear.ear/ state=ClassLoader mode=Manual requiredState=PostClassLoader org.jboss.deployers.spi.DeploymentException: Cannot process metadata *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/opt/JBoss_Developer_Studio/jbds20100310/jboss-eap/jboss-as/server/default/deploy/booking-ear.ear/ -> org.jboss.deployers.spi.DeploymentException: Cannot process metadata DEPLOYMENTS IN ERROR: Deployment "vfsfile:/opt/JBoss_Developer_Studio/jbds20100310/jboss-eap/jboss-as/server/default/deploy/booking-ear.ear/" is in error due to the following reason(s): java.lang.ClassNotFoundException: org.jboss.seam.example.booking.RegisterAction from BaseClassLoader@1ad875c{VFSClassLoaderPolicy@191acf Plz, see the full log attached -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6047) Mapping Diagram save doesn't work with caveatemptor-jpa example project

by Vitali Yemialyanchyk (JIRA)

Mapping Diagram save doesn't work with caveatemptor-jpa example project ----------------------------------------------------------------------- Key: JBIDE-6047 URL: https://jira.jboss.org/jira/browse/JBIDE-6047 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.1 Attachments: screenshot-1.jpg -- 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
6
0 / 0

[JBoss JIRA] Created: (JBDS-1207) include WTP 3.1.x fixes into devstudio build

by Max Rydahl Andersen (JIRA)

include WTP 3.1.x fixes into devstudio build -------------------------------------------- Key: JBDS-1207 URL: https://jira.jboss.org/jira/browse/JBDS-1207 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: Build Reporter: Max Rydahl Andersen Assignee: Nick Boldt Fix For: 3.0.1.GA see uber-task for link/info on the builds we need to get included into JBDS -- 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
39
0 / 0

[JBoss JIRA] Created: (JBIDE-6240) Plug-in org.jboss.tools.jsf.ui was unable to load class org.jboss.tools.jsf.ui.editor.menu.JSF2CompositionComponentContrubutionItem.

by Yura Zhishko (JIRA)

Plug-in org.jboss.tools.jsf.ui was unable to load class org.jboss.tools.jsf.ui.editor.menu.JSF2CompositionComponentContrubutionItem. ------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6240 URL: https://jira.jboss.org/jira/browse/JBIDE-6240 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.next Reporter: Yura Zhishko Assignee: Alexey Kazakov Open trunk\jsf\tests\org.jboss.tools.jsf.vpe.jsf.test\resources\jsf2test\WebContent\resources\ezcomp\loginPanel.xhtml page. Call context menu on composite:interface component. RESULT: org.eclipse.core.runtime.CoreException: Plug-in org.jboss.tools.jsf.ui was unable to load class org.jboss.tools.jsf.ui.editor.menu.JSF2CompositionComponentContrubutionItem. at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:180) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:162) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:874) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:873) at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:150) at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:143) at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:123) at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:737) at org.eclipse.jface.action.MenuManager.update(MenuManager.java:818) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:470) 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:4619) 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:3936) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3497) 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:585) 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) Caused by: java.lang.ClassNotFoundException: org.jboss.tools.jsf.ui.editor.menu.JSF2CompositionComponentContrubutionItem at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326) at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160) ... 48 more -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6167) Move Proposal Info gathering for EL Proposals from resolve cycles to the proposal itself

by Victor Rubezhny (JIRA)

Move Proposal Info gathering for EL Proposals from resolve cycles to the proposal itself ----------------------------------------------------------------------------------------- Key: JBIDE-6167 URL: https://jira.jboss.org/jira/browse/JBIDE-6167 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.GA Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.1 The problem is that we calculate Javadoc info for each proposal using a long running JavadocContentAccess2 methods. But this is not a proper place for such calculations. Need to move the Proposal Javadoc Information calculation into the Proposal itself, so let this information to be collected as it's needed. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6024) JBoss AS adapter deploys only recently changed files and removes everithing else

by Denis Golovin (JIRA)

JBoss AS adapter deploys only recently changed files and removes everithing else --------------------------------------------------------------------------------- Key: JBIDE-6024 URL: https://jira.jboss.org/jira/browse/JBIDE-6024 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR2 Environment: JBoss Tools 3.1.0.GA candidate v201003050540R-H56-GA Reporter: Denis Golovin Assignee: Rob Stryker Fix For: 3.1.0.GA The steps to replicate the issue are explained in this post http://community.jboss.org/message/526847#526847. I cannot confirm yet but it looks like problem should be replicated for any project after couple hours of waiting. I was able to get the same problems after I tried to change ad deploy files after 4 hours. Now it happens every time even after restoring deployment with Full Publish action in Servers View -- 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

7
27
0 / 0

[JBoss JIRA] Created: (JBIDE-6054) NullPointerException when trying to rename method

by Vadim Berezniker (JIRA)

NullPointerException when trying to rename method ------------------------------------------------- Key: JBIDE-6054 URL: https://jira.jboss.org/jira/browse/JBIDE-6054 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.GA Reporter: Vadim Berezniker I have a seam-gen ant based project. When I attempt to rename a method, the refactoring process sits there for a bit in "Checking preconditions" state and then I get an error dialog that says "The participant '<method name>' caused an internal error and has been disabled for refactoring." The following exception is seen in the Eclipse log right after the message: !ENTRY org.eclipse.ltk.core.refactoring 4 10000 2010-03-13 00:18:41.025 !MESSAGE Internal Error !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:256) at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:131) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.searchInCach(RefactorSearcher.java:210) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:188) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:148) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.findELReferences(RefactorSearcher.java:114) at org.jboss.tools.jsf.ui.el.refactoring.RenameMethodParticipant.checkConditions(RenameMethodParticipant.java:70) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:257) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:211) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) I recently updated to 3.1 -- 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
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5897) "targer" instead of "target" used in properties view

by Max Rydahl Andersen (JIRA)

"targer" instead of "target" used in properties view ---------------------------------------------------- Key: JBIDE-5897 URL: https://jira.jboss.org/jira/browse/JBIDE-5897 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Vitali Yemialyanchyk Fix For: 3.1.1 "targer" shown in all the screenshots of the whatsnew and noteworthy for CR2 -- 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: (TOOLSDOC-59) Test Assign

by Ben Clare (JIRA)

Test Assign ----------- Key: TOOLSDOC-59 URL: https://jira.jboss.org/jira/browse/TOOLSDOC-59 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Clare Testing assign provileges -- 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

1
2
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 April 2010