June 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-6406) NPE when deleting EAR project

by Libor Zoubek (JIRA)

NPE when deleting EAR project ----------------------------- Key: JBIDE-6406 URL: https://jira.jboss.org/browse/JBIDE-6406 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.GA, 3.1.x Reporter: Libor Zoubek Attachments: delete.ear.npe.log I've got NPE in .log file. This does not seam to affect behavior. Steps to reproduce: 1. create EAR project (with application.xml) 2. create dynamic web project and add it to EAR 3. delete ear project Project is deleted, everything seems OK, only NPE in log file appears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6402) features must now depend on org.eclipse.jsf.feature as well as org.eclipse.jst.web_core.feature/org.eclipse.jst.web_ui.feature

by Nick Boldt (JIRA)

features must now depend on org.eclipse.jsf.feature as well as org.eclipse.jst.web_core.feature/org.eclipse.jst.web_ui.feature ------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6402 URL: https://jira.jboss.org/browse/JBIDE-6402 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2-Helios, 3.2.0.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov >From David Williams on cross-projects-issues-dev(a)eclipse.org: This was required to allow more flexible packaging options and, more importantly, independent maintenance releases in the future. See bug 302896. https://bugs.eclipse.org/bugs/show_bug.cgi?id=302896 The implication is that anyone that has a feature that prereqs or installs org.eclipse.jst.web_core.feature, or org.eclipse.jst.web_ui.feature will now have to also prereq or install org.eclipse.jsf.feature -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-6395) [Helios] Project Examples not loading once selected?

by Brian Fitzpatrick (JIRA)

[Helios] Project Examples not loading once selected? ---------------------------------------------------- Key: JBIDE-6395 URL: https://jira.jboss.org/browse/JBIDE-6395 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2-Helios Reporter: Brian Fitzpatrick Assignee: Snjezana Peco Priority: Critical Fix For: 3.2-Helios I know some changes were already made to the Project Examples code to overcome some compile errors, but when I attempt to actually create an example in Helios, I'm getting an exception. It seems that the path being passed to the import method in Eclipse isn't getting the right workspace-relative path value? !ENTRY org.jboss.tools.project.examples 4 0 2010-06-01 10:39:37.268 !MESSAGE Path must include project and resource name: /webservice_producer !STACK 0 java.lang.IllegalArgumentException: Path must include project and resource name: /webservice_producer at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1795) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:221) at org.eclipse.ui.wizards.datatransfer.ImportOperation.importFolder(ImportOperation.java:718) at org.eclipse.ui.wizards.datatransfer.ImportOperation.importRecursivelyFrom(ImportOperation.java:786) at org.eclipse.ui.wizards.datatransfer.ImportOperation.importRecursivelyFrom(ImportOperation.java:791) at org.eclipse.ui.wizards.datatransfer.ImportOperation.execute(ImportOperation.java:393) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard.importSingleProject(NewProjectExamplesWizard.java:423) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard.importProject(NewProjectExamplesWizard.java:329) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard$2.runInWorkspace(NewProjectExamplesWizard.java:160) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1222) Include fix from JBPAPP-4259 in EAP 5.0 and EAP 5.1 based JBDS

by Max Rydahl Andersen (JIRA)

Include fix from JBPAPP-4259 in EAP 5.0 and EAP 5.1 based JBDS -------------------------------------------------------------- Key: JBDS-1222 URL: https://jira.jboss.org/browse/JBDS-1222 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 3.0.0.GA Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 3.0.2.GA, 3.1.0.beta1 Seam has a bug in EAP 5.0 that makes it generate AS 5 incompatible pages. JBPAPP-4259 fixes it in EAP 5.1 but for Seam to work with JBDS 5.0.x should be fixed too. (was asked to report this in downstream products by EAP production team) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
7
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2010