August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-875) When an option of the seam validator is selected to "Ignore" the validator should not check for this validation type

by Adrian Mitev (JIRA)

When an option of the seam validator is selected to "Ignore" the validator should not check for this validation type -------------------------------------------------------------------------------------------------------------------- Key: JBIDE-875 URL: http://jira.jboss.com/jira/browse/JBIDE-875 Project: JBoss Tools Issue Type: Feature Request Environment: rhds beta 1, windows xp, jdk 1.5_0.12 Reporter: Adrian Mitev This will decrease the spend time on the validation if the user doesn't want specific type of validation. -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-822) JBoss adapter classpath's are not visible for tests (and everything else)

by Max Andersen (JIRA)

JBoss adapter classpath's are not visible for tests (and everything else) ------------------------------------------------------------------------- Key: JBIDE-822 URL: http://jira.jboss.com/jira/browse/JBIDE-822 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Marshall Culpepper Priority: Blocker Fix For: 2.0.0.Beta4 Create a junit test that contains this (in a dynamic web project or seam project): import javax.faces.application.FacesMessage; import junit.framework.TestCase; public class Test extends TestCase { public void testShouldNotFail() throws Exception { javax.faces.event.PhaseListener.class.toString(); } } This compiles fine, but will fail with classnotfoundexception on our adapter since the contribute classpath seem to not be considered as part of what should be available for anything launched (e.g. junittests) This is critical for Seam projects to execute tests. Places it is visible we are "special" If you try and edit the junit test launch configuration you will see that all classlibraries except ours is added. If you go to "Targetted runtimes" on a project and click on us the "Runtime composition" shows something very specific to us as if we do it on the default adapter "JBoss 4.2 the JDK" is shown..that makes much more sense. -- 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

18 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (RHDS-168) Installation - JRE selection & eclipse.ini and studio startup

by Aliaksey Nis (JIRA)

Installation - JRE selection & eclipse.ini and studio startup ------------------------------------------------------------- Key: RHDS-168 URL: http://jira.jboss.com/jira/browse/RHDS-168 Project: Red Hat Developer Studio Issue Type: Bug Environment: WindowsXP SP2 rhds-win32-1.0.0.beta1.jar Red Hat Developer Studio Version: 1.0.0 BETA1 Build: 200708290300-nightly JDK 1.5_08 Reporter: Aliaksey Nis Priority: Critical In this build during installation provided selection of JRE (in installation step 4). Selected path stored in eclipse.ini. Problem is - Eclipse (RHDS) don't use this stored path. U can write in eclipse.ini anything, but Eclipse still be loading JRE from registry path: [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment] "CurrentVersion"="1.5" <---------------------- Loading JRE from here. So, if in registry JRE version = 1.6, and in eclipse.ini = JRE 1.5, JRE 1.6 will be loaded. So this new JRE selection in installer is useless. -- 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

18 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-703) Does AS adapter obey the new nice WTP library rules ?

by Max Andersen (JIRA)

Does AS adapter obey the new nice WTP library rules ? ----------------------------------------------------- Key: JBIDE-703 URL: http://jira.jboss.com/jira/browse/JBIDE-703 Project: JBoss Tools Issue Type: Task Components: JBossAS Reporter: Max Andersen Assigned To: Rob Stryker Priority: Critical Just saw this: http://www.mail-archive.com/wtp-dev@eclipse.org/msg02799.html https://bugs.eclipse.org/bugs/show_bug.cgi?id=128851 from http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+WTP If our JBoss AS adapter is listeing to what WTP wants deployed this would be supported out-of-the-box making lib management in WTP *much* more viable than what it is now. But if our JBoss AS adapter is *not* listening to what WTP wants to be deployed we need to either start doing that or implement this support... -- 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

18 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-836) Red Hat XML Editor often fails when opening a components.xml from Seam CVS

by Pete Muir (JIRA)

Red Hat XML Editor often fails when opening a components.xml from Seam CVS -------------------------------------------------------------------------- Key: JBIDE-836 URL: http://jira.jboss.com/jira/browse/JBIDE-836 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Pete Muir To reproduce, get Seam from CVS, try to open examples/seamdiscs/resources/WEB-INF/components.xml. It fails (for me) with Arguement not valid and this stack trace: java.lang.IllegalArgumentException: Argument not valid at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.graphics.GC.setFont(GC.java:3224) at org.eclipse.ui.forms.widgets.ExpandableComposite$ExpandableLayout.layout(ExpandableComposite.java:280) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1337) at org.eclipse.swt.widgets.Composite.layout(Composite.java:896) at org.eclipse.swt.widgets.Composite.layout(Composite.java:854) at org.eclipse.swt.widgets.Composite.layout(Composite.java:817) at org.jboss.tools.common.editor.form.SampleErrorForm$ErrorLayout.layout(SampleErrorForm.java:359) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1337) at org.eclipse.swt.widgets.Composite.layout(Composite.java:896) at org.eclipse.swt.widgets.Composite.layout(Composite.java:854) at org.jboss.tools.common.editor.form.SampleErrorForm.setVisible(SampleErrorForm.java:106) at org.jboss.tools.common.editor.TreeFormPage.doErrorMode(TreeFormPage.java:295) at org.jboss.tools.common.editor.TreeFormPage.setErrorMode(TreeFormPage.java:287) at org.jboss.tools.common.model.ui.editors.multipage.DefaultMultipageEditor.setErrorMode(DefaultMultipageEditor.java:59) at org.jboss.tools.common.editor.ObjectMultiPageEditor.initEditors(ObjectMultiPageEditor.java:453) at org.jboss.tools.jst.web.ui.editors.WebCompoundEditor.doCreatePages(WebCompoundEditor.java:29) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:220) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:102) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) -- 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

18 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-577) Problems with JBOSS server (Run Button don't work, incorrect server status view)

by Aliaksey Nis (JIRA)

Problems with JBOSS server (Run Button don't work, incorrect server status view) -------------------------------------------------------------------------------- Key: JBIDE-577 URL: http://jira.jboss.com/jira/browse/JBIDE-577 Project: JBoss Tools Issue Type: Bug Components: JBossAS Environment: WindowsXP SP2 rhds-win32-1.0.0.alpha.jar Red Hat Developer Studio Version: 1.0.0 Build: build 20070711-nightly JDK 1.5_08 Reporter: Aliaksey Nis Assigned To: Rob Stryker Priority: Critical At newly installed studio. 1. Create JSF 1.2 KickStart project (with registration on server in creation wizard) 2. Start JBoss AS server, included to studio. First problem - server already started, but in Server view still shown that server "starting" (look at screenshot JbossServer.jpg). After running application server status changed to "Started". 3. Press "Run application" button. Second problem. Message appears, that project don't registered on server (but it registered...) Same problem was in EXIN-151. When i write in browser's command promt http://127.0.0.1:8080/[Application name] test project works fine. 4. Press stop button on Server view. Server stopped with next info in server console (JbossServerExc.txt) 5. Starting server again - (JbossServerExc2.txt), server started, but application don't work 6. Again stop server - error message "JBoss AS can't start" appear, with no info in it. 7. Restart studio. Start server. Now server started with next console log (JbossServerStart.txt). Application's work on server (with command promt in browser). After server stops - no errors appear. Starting-stoping again server shows same results. So, summary is - button "Run application" need to be fixed. Server status need to be fixed. Unknown errors in logs is optional. -- 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

18 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-786) Cannot configure classpath in JBoss Server launch configuration

by Noah Adams (JIRA)

Cannot configure classpath in JBoss Server launch configuration --------------------------------------------------------------- Key: JBIDE-786 URL: http://jira.jboss.com/jira/browse/JBIDE-786 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Environment: Windows 2000, eclipse 3.3 europa, jre 1.6.0_01 also verified on a machine running Windows XP and jre 1.5.0_6 Reporter: Noah Adams I seem to be unable to modify the classpath in a launch configuration for a JBoss server. Here are the steps I followed: Installed europa "Eclipse IDE for Java EE Developers" package and JBossTools 2.0.0.beta3 Choose New->New Server from the JBoss toolbar icon Select "JBoss AS 3.2" from the "JBoss, a division of Red Hat" folder and click next (also seems to happen if I lie and choose 4.0 or 4.2) browse to my jboss folder (c:\jboss-3.2.7) and click next accept the default name and click finish now bring up the JBoss server view and right click on the new server and select edit launch configuration click the Classpath tab and choose User Entries (although the same seems to happen for Server Entries) click Advanced->Add External Folder and select a folder (adding a jar seems to have the same problem) the folder shows up in the classpath list, so I click OK but now if I bring up the launch configuration again, the folder is gone! I can successfully edit other items in the lanch configuration like the VM arguments -- 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

18 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-698) VPE error message points to exadel.com

by Bryan Che (JIRA)

VPE error message points to exadel.com -------------------------------------- Key: JBIDE-698 URL: http://jira.jboss.com/jira/browse/JBIDE-698 Project: JBoss Tools Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.0.20070808 Environment: Fedora 7 Reporter: Bryan Che Priority: Critical I tried opening a page in VPE on my Fedora 7 box. This showed the error message in the VPE: "The VPE editor can't be run because your system environment needs to be changed slightly. Find out more" The "Find out more" links to an exadel.com page. We should update/move the content to within RHDS and not point at exadel.com -- 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

18 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-704) Can't remove Palette Group.

by Alexey Kazakov (JIRA)

Can't remove Palette Group. --------------------------- Key: JBIDE-704 URL: http://jira.jboss.com/jira/browse/JBIDE-704 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Alexey Kazakov Assigned To: Viacheslav Kabanovich 1. Open Red Hat Palette. 2. Open Palette Editor. 3. Try to remove any Group. Nothing happens. -- 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

18 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-781) Red Hat Pallete View: Pallete can't load icon for element "Ajax4Jsf tag lib".

by Alexey Kazakov (JIRA)

Red Hat Pallete View: Pallete can't load icon for element "Ajax4Jsf tag lib". ----------------------------------------------------------------------------- Key: JBIDE-781 URL: http://jira.jboss.com/jira/browse/JBIDE-781 Project: JBoss Tools Issue Type: Bug Reporter: Alexey Kazakov Assigned To: Viacheslav Kabanovich 1. Clean Worspace. 2. Open Studio. 3. Open Pallete. 4. See element "Ajax4Jsf tag lib". Icon is missing. Actually it's null. 5. Close Studio. Eclipse throws NullPointerException. Closing/Opening Pallete helps. So Pallete can't load only first icon of elements. -- 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

18 years, 7 months

3
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 August 2007