June 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4420) Deployment of JSF with Facelets KickStart project to the JBoss AS 4.2.3 and AS 4.3 failed.

by Anton Klimkovich (JIRA)

Deployment of JSF with Facelets KickStart project to the JBoss AS 4.2.3 and AS 4.3 failed. ------------------------------------------------------------------------------------------- Key: JBIDE-4420 URL: https://jira.jboss.org/jira/browse/JBIDE-4420 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M1 Environment: eclipse-SDK-3.5RC3-win32 JBossTools-ALL-win32-3.1.0.M1-N200906032024-H234 Reporter: Anton Klimkovich EXECUTE: JSF with Facelets KickStart project EXECUTE: Set New server runtime environment (JBoss AS 4.2.3 or AS 4.3 from JBoss EAP ) EXECUTE: Add project to the server EXECUTE: Run project on the server FAILURE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener java.lang.UnsupportedClassVersionError: Bad version number in .class file 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

16 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2965) Some exceptions are occured when add new XPath to the AS.

by Anton Klimkovich (JIRA)

Some exceptions are occured when add new XPath to the AS. --------------------------------------------------------- Key: JBIDE-2965 URL: https://jira.jboss.org/jira/browse/JBIDE-2965 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.beta1 Reporter: Anton Klimkovich EXECUTE: Open JBoss Server view EXECUTE: Select XML Configurations -> Ports EXECUTE: Open Properties view EXECUTE: Select New XPath from context menu EXECUTE: Input name EXECUTE: Input //Connector[@address='${jboss.bind.address}']/ as XPath Pattern EXECUTE: Input Attribute Name FAILURE: Unhandled event loop exception Exception2.txt attached EXECUTE: Press Finish button FAILURE: Error refreshing view (descriptorXPathViewProvider) Exception.txt -- 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

16 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-1534) Faclets xhtml page wizard with facelets template selection from target project

by Denis Golovin (JIRA)

Faclets xhtml page wizard with facelets template selection from target project ------------------------------------------------------------------------------ Key: JBIDE-1534 URL: http://jira.jboss.com/jira/browse/JBIDE-1534 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Denis Golovin That would allow create new pages for Seam projects from scratch if you not need form, action,entity and conversation. -- 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

16 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4437) Seam Refactor: Exception while attempt to rename Seam component from jar file

by Daniel Azarov (JIRA)

Seam Refactor: Exception while attempt to rename Seam component from jar file ----------------------------------------------------------------------------- Key: JBIDE-4437 URL: https://jira.jboss.org/jira/browse/JBIDE-4437 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Daniel Azarov Assignee: Daniel Azarov Testcase: 1. Create "test" seam war project 2. Open Seam Components view 3. Open test->org.jboss.seam.core->init 4. Select "Rename Seam Component" popup menu item on "init" component 5. Type new name for component 6. Press Next button FAIL: Exception: java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:583) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:422) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:74) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:114) at org.jboss.tools.seam.ui.wizard.RenameComponentWizard$RenameComponentWizardPage.getNextPage(RenameComponentWizard.java:121) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) 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.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:143) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:155) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.invokeRenameComponentWizard(SeamRefactorContributionFactory.java:378) at org.jboss.tools.seam.ui.views.actions.RenameComponentAction.run(RenameComponentAction.java:49) 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:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2393) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2357) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2209) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284) at org.eclipse.equinox.launcher.Main.main(Main.java:1260) Caused by: java.lang.NullPointerException at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.findAnnotations(SeamRenameProcessor.java:170) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.findAnnotations(SeamRenameProcessor.java:156) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.renameComponent(SeamRenameProcessor.java:533) at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.createChange(RenameComponentProcessor.java:85) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:290) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124) 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) -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4438) Fix Hibernate Tools eclipse plugins compile errors in Eclipse 3.5 RC3

by Vitali Yemialyanchyk (JIRA)

Fix Hibernate Tools eclipse plugins compile errors in Eclipse 3.5 RC3 --------------------------------------------------------------------- Key: JBIDE-4438 URL: https://jira.jboss.org/jira/browse/JBIDE-4438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Fix For: 3.1.0.M2 -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4365) Deployment in AS is failed, when server started.

by Yura Zhishko (JIRA)

Deployment in AS is failed, when server started. ------------------------------------------------ Key: JBIDE-4365 URL: https://jira.jboss.org/jira/browse/JBIDE-4365 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M1 Environment: jboss-eap 4.3 jbdevstudio-eap-win32-2.1.0.M1-N200905190437-H189 Reporter: Yura Zhishko Assignee: Rob Stryker Priority: Critical 1) Run studio in new workspace 2) Create new JSF kickstart project with facelets using jboss-eap runtime 3) Run it on jboss-eap 4.3 ASSERT: ALL is OK 4) Don't stop server 5) Create another new JSF kickstart project using jboss-eap runtime but do not add this project into server scope or delete it, if it happened. 6) Right mouse click on the project from point 4 in Package explorer -> Run on server -> jboss-eap -> Finish RESULT: Deployment is failed. Project didn't start. Publish function isn't available (see screenshot-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

16 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2095) .svn and CVS/ folders should be excluded from filesets by default

by Galder Zamarreno (JIRA)

.svn and CVS/ folders should be excluded from filesets by default ----------------------------------------------------------------- Key: JBIDE-2095 URL: http://jira.jboss.com/jira/browse/JBIDE-2095 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.beta1 Reporter: Galder Zamarreno > 3.- .svn/ and CVS/ folders should be excluded from filesets by default. > > Maybe an option in preferences of Project Archives? I understand the reasoning but having a set of global default excludes will make the packaging non-deterministic. What I would suggest is that you could set this per archive and then set those as defaults for new archives which users can adapt to their needs. Put that in jira too. -- 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

16 years, 5 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4434) JBAS-6794

by Rob Stryker (JIRA)

JBAS-6794 --------- Key: JBIDE-4434 URL: https://jira.jboss.org/jira/browse/JBIDE-4434 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Rob Stryker -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4428) Default name for EAP 4.3 is JBoss 4.3 ..should be JBoss EAP 4.3

by Max Rydahl Andersen (JIRA)

Default name for EAP 4.3 is JBoss 4.3 ..should be JBoss EAP 4.3 --------------------------------------------------------------- Key: JBIDE-4428 URL: https://jira.jboss.org/jira/browse/JBIDE-4428 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M1, 3.0.1.GA Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.0.2.GA, 3.1.0.M2 Create JBoss Enterprise Application Platform and you'll see that the default name is JBoss 4.3 which is misleading since such a thing does not exist. Should be JBoss EAP and Eclipse 3.5 apparently got the fix that allow us to control this. -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-758) renumber JIRA values for JBDS: 2.0.x -> 2.1.0, 2.1.0 -> 3.0.0.M1, M2...

by Nick Boldt (JIRA)

renumber JIRA values for JBDS: 2.0.x -> 2.1.0, 2.1.0 -> 3.0.0.M1, M2... ----------------------------------------------------------------------- Key: JBDS-758 URL: https://jira.jboss.org/jira/browse/JBDS-758 Project: Developer Studio Issue Type: Bug Reporter: Nick Boldt Assignee: Max Rydahl Andersen "Affects Version" and "Fix Version" values to match our planned releases this year. Suggest we remove everything except these: Unknown 1.1.0 (includes JBT 2.1?) 2.0.0 (includes JBT 3.0.0) 2.1.0 (includes JBT 3.0.x) 3.0.0.M1 (includes JBT 3.1.0.M1) 3.0.0.M2 (...) LATER -- 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

16 years, 5 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2009