[JBoss JIRA] Created: (JBIDE-9232) JBoss 7: JSF 2 apps stop working
by Juergen Zimmermann (JIRA)
JBoss 7: JSF 2 apps stop working
--------------------------------
Key: JBIDE-9232
URL: https://issues.jboss.org/browse/JBIDE-9232
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
I'm using JBossTools 3.3_stable_branch.aggregate-Update-2011-06-18_05-30-41-H2.
Now I tried the latest Jenkins Build 1267 of JBoss 7 and I'm getting a classpath issue regarding JSF 2: JBoss Tools is including
* jsf-api-1.2_13.jar from modules/javax/faces/api/1.2
* jboss-jsf-api_2.0_spec-1.0.0.Final.jar from modules/javax/faces/api/main
It looks like the 1.2 stuff is included earlier in the classpath, so that e.g. ExternalContext.getFlash(), ExternalContext.invalidateSession() or Application.createComponent(FacesContext,String,String) are not available.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8008) SeamProjectNewWizardTest.testJiraJbide1111 failure
by Alexey Kazakov (JIRA)
SeamProjectNewWizardTest.testJiraJbide1111 failure
--------------------------------------------------
Key: JBIDE-8008
URL: https://issues.jboss.org/browse/JBIDE-8008
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Alexey Kazakov
junit.framework.AssertionFailedError: Finish button is disabled at first wizard page in spite of created JBoss AS Runtime, Server, DB Connection and Seam Runtime and valid project name.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest.testJiraJbide1111(SeamProjectNewWizardTest.java:130)
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 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:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
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:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47)
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:369)
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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-9278) Conflicting dependency prevents installation of JBoss Tools for Eclipse Indigo
by Rick Wagner (JIRA)
Conflicting dependency prevents installation of JBoss Tools for Eclipse Indigo
------------------------------------------------------------------------------
Key: JBIDE-9278
URL: https://issues.jboss.org/browse/JBIDE-9278
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M2
Environment: 64-bit Fedora, Eclipse 3.7
Reporter: Rick Wagner
With a new download of eclipse-jee-indigo-M6a-linux-gtk-x86_64.tar.gz, I get the following message when trying to install All JBoss Tools 3.3. I'm following Max's latest blog about this combination, but the installation isn't working for me. Thanks!
Cannot complete the install because of a conflicting dependency.
> Software being installed: Runtime Initialization 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20110624-0453-H4-M2)
> Software currently installed: Eclipse IDE for Java EE Developers 1.4.0.20110319-2300 (epp.package.jee 1.4.0.20110319-2300)
> Only one of the following can be installed at once:
> Common Navigator View 3.5.100.I20110524-0800 (org.eclipse.ui.navigator 3.5.100.I20110524-0800)
> Common Navigator View 3.5.0.I20100601-0800 (org.eclipse.ui.navigator 3.5.0.I20100601-0800)
> Common Navigator View 3.5.100.I20110519-0100 (org.eclipse.ui.navigator 3.5.100.I20110519-0100)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 1.4.0.20110319-2300 (epp.package.jee 1.4.0.20110319-2300)
> To: org.eclipse.epp.package.jee.feature.feature.group [1.4.0.20110319-2300]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.4.0.20110319-2300 (org.eclipse.epp.package.jee.feature.feature.group 1.4.0.20110319-2300)
> To: org.eclipse.platform.feature.group [3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu]
> Cannot satisfy dependency:
> From: Eclipse Platform 3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu (org.eclipse.platform.feature.group 3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu)
> To: org.eclipse.ui.navigator [3.5.0.I20100601-0800]
> Cannot satisfy dependency:
> From: JBoss Runtime Initializer 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime 1.3.0.v20110624-0453-H4-M2)
> To: bundle org.eclipse.ui.navigator 3.5.100
> Cannot satisfy dependency:
> From: Runtime Initialization 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20110624-0453-H4-M2)
> To: org.jboss.tools.runtime [1.3.0.v20110624-0453-H4-M2]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[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, 10 months
[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, 10 months
[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, 10 months
[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, 10 months