September 2007 - jbosstools-issues

[JBoss JIRA] Commented: (JBIDE-759) Problem with "add project" to jboss server.

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-759?page=comments#action_12375778 ] Rob Stryker commented on JBIDE-759: ----------------------------------- Link to eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=202541 > Problem with "add project" to jboss server. > ------------------------------------------- > > Key: JBIDE-759 > URL: http://jira.jboss.com/jira/browse/JBIDE-759 > Project: JBoss Tools > Issue Type: Bug > Components: JBossAS > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Priority: Critical > Attachments: add project.jpg, rhds seam proect.zip > > > There is something wrong with "add project" window. When i add the project and then open add/remove project window again, i can add the same project again and again. I'm providing a screen shot to the issue. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-759) Problem with "add project" to jboss server.

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-759?page=comments#action_12375777 ] Rob Stryker commented on JBIDE-759: ----------------------------------- This is a problem with both WTP and the Seam plugins. The issue here is as follows. When you make a new Seam Project, 3 projects are created, Seampro, Seampro-ear, and Seampro-ejb. Theoretically eclipse should interpret these all as different "Modules", and normally they would. However, after browsing the org.eclipse.wst.common.component in each of the projects, I found the following lines: <wb-module deploy-name="Seampro"> (in the ear) <wb-module deploy-name="Seampro"> (in the war) <wb-module deploy-name="Seampro-ejb"> (in the ear) What this causes is the following: Both the ear and the war *think* their module ID is Seampro,org.eclipse.jst.jee.server:Seampro So when you go to add/remove a project from a server, or if you deploy the EAR but restart your eclipse installation, WTP will think it is the WAR, NOT THE EAR. Further attempts to publish will assume it's the war. A user in IRC also experienced similar behavior, where without restarting, he tried to full-republish his ear and it instead tried to publish the war. I am filing a bug in eclipse for allowing two different projects in the same ModuleFactory to keep the same id. I am also going to post about this on JBossTools-dev so that it gets maximum exposure. > Problem with "add project" to jboss server. > ------------------------------------------- > > Key: JBIDE-759 > URL: http://jira.jboss.com/jira/browse/JBIDE-759 > Project: JBoss Tools > Issue Type: Bug > Components: JBossAS > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Priority: Critical > Attachments: add project.jpg, rhds seam proect.zip > > > There is something wrong with "add project" window. When i add the project and then open add/remove project window again, i can add the same project again and again. I'm providing a screen shot to the issue. -- 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, 2 months

1
0
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, 2 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, 2 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-886) system copy deployer creates a configuration in the servers folder and it should not

by Rob Stryker (JIRA)

system copy deployer creates a configuration in the servers folder and it should not ------------------------------------------------------------------------------------ Key: JBIDE-886 URL: http://jira.jboss.com/jira/browse/JBIDE-886 Project: JBoss Tools Issue Type: Task Components: JBossAS Reporter: Rob Stryker Priority: Minor -- 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, 2 months

1
2
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, 2 months

3
4
0 / 0

[JBoss JIRA] Closed: (RHDS-139) VPE on Linux (required settings)

by Anatoly Fedosik (JIRA)

[ http://jira.jboss.com/jira/browse/RHDS-139?page=all ] Anatoly Fedosik closed RHDS-139. -------------------------------- Resolution: Done "How to install VPE on Linux" instruction is here: https://labs.jboss.com/wiki/JBosstoolsVisualEditorFAQ > VPE on Linux (required settings) > -------------------------------- > > Key: RHDS-139 > URL: http://jira.jboss.com/jira/browse/RHDS-139 > Project: Red Hat Developer Studio > Issue Type: Task > Components: Doc - RHDS GettingStartedGuide > Reporter: Anatoly Fedosik > Assigned To: Anton Klimkovich > Fix For: 1.0.0.beta2 > > > There is a need to test 1.6.2 section in Getting started guide, link: http://www.redhat.com/developers/rhds/Getting_Started_Single/#FAQ > to be exact: Visual Editor does not start under Linux > Do we need these steps: > 1) On Red Hat based Linux distributions install the xpLib.i386 package > 2) ln -s libstdc++.so.5.0.7 libstdc++.so.5 > or we need the following package: > yum install compat-libstdc++-33 > in order to install VPE on Linux -- 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, 2 months

1
0
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, 2 months

4
7
0 / 0

[JBoss JIRA] Closed: (JBIDE-764) Workspace refreshing problems after manual removing projects .

by Aliaksey Nis (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-764?page=all ] Aliaksey Nis closed JBIDE-764. ------------------------------ Closed. > Workspace refreshing problems after manual removing projects . > -------------------------------------------------------------- > > Key: JBIDE-764 > URL: http://jira.jboss.com/jira/browse/JBIDE-764 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Reporter: Anton Klimkovich > Assigned To: Alexey Kazakov > Attachments: NPE.txt > > > First situation: > 1 Create JSFKickStart project > 2 Delete it manualy from workspace > After deleting workspace will be refreshed in RHDS but some problems and exception will be( java.lang.NullPointerException > at org.eclipse.jdt.internal.core.JavaProject.getPackageFragmentRoot(JavaProject.java:1789 ...) > Log attached > Second situation > 1 Create JSFKickStart project (name - Test) > 2 Close RHDS > 3 Delete project manualy from workspace > 4 Run RHDS > 5 Try to create JSFKickStart with the name equal to deleting project. (name - Test) > You will see the message that the project with such name already exist in workspace. -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2007