July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9301) Cannot deploy portlets to EPP server from with JBT 3.3.0.M2 or JBDS 5.0.0.M2

by Isaac Rooskov (JIRA)

Cannot deploy portlets to EPP server from with JBT 3.3.0.M2 or JBDS 5.0.0.M2 ---------------------------------------------------------------------------- Key: JBIDE-9301 URL: https://issues.jboss.org/browse/JBIDE-9301 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.3.0.M2 Environment: Fedora 14, JBT 3.3.0.M2 (also tested on JBDS 5.0.0.M2), EPP 5.1.0, Java 1.6 Reporter: Isaac Rooskov Assignee: Snjezana Peco Priority: Critical After creating a Dynamic Web Project and adding Portlet capabilities to it (and correct facets), I add the project to the EPP server I have setup within JBT (or JBDS) through the 'Add and Remove...' system, however the project does not deploy to the server. I also tried deploying through highlighting the project in the 'Project Explorer' and clicking on the green arrow button and selecting 'Run As' -> 'Run on Server', but still did not work (I tried these things before the server was started and while the server was running -> should have worked in both cases). I can confirm however that using the 'Export' option and exporting as a 'WAR file' allows me to create a WAR file of the project and then manually place it into the 'deploy' folder of the server profile in use (for all of this it was the 'default' profile), and this would work -> both when the server was stopped and while it was running. This to me seems like a huge issue (perhaps even deserves to be a blocker). If I can assist by providing any further information please let me know. Isaac -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear

by Aliaksey Nis (JIRA)

Warning related to incorrect Seam project name don't appear ----------------------------------------------------------- Key: JBIDE-5284 URL: https://jira.jboss.org/jira/browse/JBIDE-5284 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Optional Attachments: NoWarningSeam.JPG Related to JBIDE-5223 EXECUTE: New Seam project. EXECUTE: Input name "blahblah+". EXECUTE: Press next few times. ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name. FAILURE: No warning appears. It appears only if you press Back, then Next again. Screenshot 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

14 years, 7 months

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-9228) Bad static constructor code in WebtoolsProjectJBossClasspathContainerInitializer

by Max Rydahl Andersen (JIRA)

Bad static constructor code in WebtoolsProjectJBossClasspathContainerInitializer -------------------------------------------------------------------------------- Key: JBIDE-9228 URL: https://issues.jboss.org/browse/JBIDE-9228 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M3 xcoulon got the following exception when running with the plugins installed that AS requires Problem is most likely that the class constructor code in (the static blocks) contains: public static final IProjectFacet WEB_FACET = ProjectFacetsManager.getProjectFacet(FACET_WEB); public static final IProjectFacet EJB_FACET = ProjectFacetsManager.getProjectFacet(FACET_EJB); public static final IProjectFacet EAR_FACET = ProjectFacetsManager.getProjectFacet(FACET_EAR); public static final IProjectFacet UTILITY_FACET = ProjectFacetsManager.getProjectFacet(FACET_UTILITY); public static final IProjectFacet CONNECTOR_FACET = ProjectFacetsManager.getProjectFacet(FACET_CONNECTOR); public static final IProjectFacet APP_CLIENT_FACET = ProjectFacetsManager.getProjectFacet(FACET_APP_CLIENT); public static final IProjectFacet JSF_FACET = ProjectFacetsManager.getProjectFacet(FACET_JSF); public static final IProjectFacet JPA_FACET = ProjectFacetsManager.getProjectFacet(FACET_JPA); which my guess says will fail if those facet's are not declared/available. These facets should be declared as dependencies or the code fixed to handle them not being available. java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performOk(FacetsPropertyPage.java:289) at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) 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:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4163) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4163) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) 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: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: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) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider.isPrimaryFacet(ProjectRuntimeClasspathProvider.java:86) at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider.getClasspathEntries(ProjectRuntimeClasspathProvider.java:70) at org.eclipse.jst.common.project.facet.core.internal.RuntimeClasspathProvider.getClasspathEntries(RuntimeClasspathProvider.java:51) at org.eclipse.jst.common.project.facet.core.ClasspathHelper.addClasspathEntries(ClasspathHelper.java:131) at org.eclipse.jst.j2ee.web.project.facet.WebFacetInstallDelegate.execute(WebFacetInstallDelegate.java:169) 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.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9263) Ignore launch command code is duplicated across several classes

by Andre Dietisheim (JIRA)

Ignore launch command code is duplicated across several classes ---------------------------------------------------------------- Key: JBIDE-9263 URL: https://issues.jboss.org/browse/JBIDE-9263 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 The following code snippet, that gets the "ignore launch command" setting from pereferences is duplicated across serveral classes {code} String tmp = callback.getServer().getAttribute(IJBossToolingConstants.IGNORE_LAUNCH_COMMANDS, (String)null); Boolean b = tmp == null ? new Boolean(false) : new Boolean(tmp); executeShellScripts.setSelection(b.booleanValue()); {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9424) Provide the ability to deploy OSGi bundles

by David Bosschaert (JIRA)

Provide the ability to deploy OSGi bundles ------------------------------------------ Key: JBIDE-9424 URL: https://issues.jboss.org/browse/JBIDE-9424 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: David Bosschaert Assignee: Rob Stryker AS7 supports OSGi bundles as deployments, and Eclipse supports the creation of OSGi bundles through the built-in PDE tooling (see [1] for an example). However, OSGi bundles developed with Eclipse PDE can't be deployed via the JBDS to AS7 yet. Support for deploying OSGi bundles to AS7 should be added to the JBoss Tooling. [1] https://docs.jboss.org/author/display/AS7/Helloworld+OSGi+quickstart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-9267) move keys/messages from CoreAS7Messages to Messages in org.jboss.ide.eclipse.as.core (provide unique message class/properties per plugin)

by Andre Dietisheim (JIRA)

move keys/messages from CoreAS7Messages to Messages in org.jboss.ide.eclipse.as.core (provide unique message class/properties per plugin) ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9267 URL: https://issues.jboss.org/browse/JBIDE-9267 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9323) Possibility to contribute on vpe toolbar in eclipse

by Maxim Areshkau (JIRA)

Possibility to contribute on vpe toolbar in eclipse --------------------------------------------------- Key: JBIDE-9323 URL: https://issues.jboss.org/browse/JBIDE-9323 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Affects Versions: 3.3.0.M2 Reporter: Maxim Areshkau Assignee: Yahor Radtsevich VPE icons have some logic behind them(disabled when visual part not visible). We need possibility to contribute on this toolbar. For now this is inpossible. Because refresh icon function has hardcoded commands'id. Better to refresh all commands on some org.jboss.tools.vpe.category. That allows contribute to vpe-toolbar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-2242) Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project.

by Anton Klimkovich (JIRA)

Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project. ----------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2242 URL: http://jira.jboss.com/jira/browse/JBIDE-2242 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.GA Reporter: Anton Klimkovich Assigned To: Maxim Areshkau Priority: Minor EXECUTE: Create default Seam project EXECUTE: Open menu.xhtml EXECUTE: Make DnD of JBoss Ajax4jsf tag on the page from Palette. FAILURE: <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> inserted instead of xmlns:h="http://java.sun.com/jsf/html" ASSERT: Seam gen should create xhtml pages with declaration that tells it's a XHTML. (<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">) All pages w/o declaration are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9410) consider building vpe and jsf as a single hudson job or reorganize dependencies between jsf and vpe/xulrunner features

by Nick Boldt (JIRA)

consider building vpe and jsf as a single hudson job or reorganize dependencies between jsf and vpe/xulrunner features ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9410 URL: https://issues.jboss.org/browse/JBIDE-9410 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, Visual Page Editor core, XULRunner Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.M3 I have been wrestling with this problem (or similar) for about the last two weeks: {code} [INFO] [Software being installed: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT, Only one of the following can be installed at once: [ org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1947-H410-M3], Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.richfaces.feature.feature.group 0.0.0, Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.xulrunner.feature.feature.group 0.0.0, Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group 3.3.0.v20110726-1419-H339-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1048-H409-M3], Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group 1.9.216.v20110726-1947-H410-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1947-H410-M3]] Basically, this is caused by VPE spinning a build which includes org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, then JSF (richfaces) spins and picks up that H409 build and includes it in its site. Then, while the JBDS update site is spinning, the VPE build spins again and now depends on H410 instead of H409. Because the aggregate can only include ONE version and each feature has strict version requirements, there is no solution for p2 to be able to create a site with the two inputs. So, either we need to build these two components together as a single job, or we need some other way to ensure this "vpe respin breaks jsf installability" problem is solved. Maybe the richfaces.feature should DEPEND ON the xulrunner.feature instead of INCLUDING the org.jboss.tools.xulrunner.initializer plugin? Or just depend on that single plugin? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9112) AS7: deployment fails when switching from zipped -> exploded deployment and changing a single resource

by Andre Dietisheim (JIRA)

AS7: deployment fails when switching from zipped -> exploded deployment and changing a single resource ------------------------------------------------------------------------------------------------------ Key: JBIDE-9112 URL: https://issues.jboss.org/browse/JBIDE-9112 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Environment: JBoss AS7 Beta4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
10
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 July 2011