March 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1388) support remote hosts/external started AS adapter

by Max Andersen (JIRA)

support remote hosts/external started AS adapter ------------------------------------------------ Key: JBIDE-1388 URL: http://jira.jboss.com/jira/browse/JBIDE-1388 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 people like to start there server manually and just hook up to it via remote debugging - we should make that easy (its trivial via eclipse support for remote debugging) should be an option on the servers, doesnt require new server/runtime type if local server. Only catch is that the server might not even be accessible via filesystem - how should we handle deploy and runtime lib situation ? (my best bet is just that these would be unspecified and not provide those features) -- 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, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (JBDS-1016) Usability issue with Seam Web Project Wizard

by Joshua Wulf (JIRA)

Usability issue with Seam Web Project Wizard -------------------------------------------- Key: JBDS-1016 URL: https://jira.jboss.org/jira/browse/JBDS-1016 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Mac OS X 10.4.11 32 bit PPC Reporter: Joshua Wulf The Seam Web Project Wizard changes the Configuration when the Target runtime is changed. Although it starts out with "Dynamic Web Application for Seam 2.0" selected by default, if the Target runtime is changed the Configuration selection is changed to match the Target Runtime. This results in an error "Seam facet must be enabled." Changing the Target Runtime back to the original one does not remove the error. There are two ways to remove the error message. One is to manually change the Configuration back to "Dynamic Web Application for Seam 2.x". Since it is not possible to move forward from this page without enabling the Seam facet, the configuration should not automatically change to one that does not have Seam facet enabled. The situation is more complicated, and worse, however, because the other way to remove the error message is to manually modify the Configuration using the "Modify" button. If the user does this, and enables JavaServer Faces and Seam, the error message will disappear and they will be able to move forward. However, when it comes time to select the Seam runtime the user will run into a problem. In the Modify Configuration screen where the user enabled the Seam facet, the unique option there was fixed at version 2.2. If the Seam runtime the user wishes to use is not 2.2 then they will get an error that the Seam runtime is an incompatible version. They will be unable to select any other version in the version drop-down box. So there are three problems: 1. The Configuration changes automatically to one incompatible with a Seam Web Project if the Target runtime is changed. 2 . Although a user may try to clear the resultant error message by changing the runtime back to the original one, the error message will remain, as the dialog will change the configuration to another incompatible one. If the user did not notice the original default configuration (which they may well not if they are moving from top to the bottom of the wizard, which will be the usual case), they have no way of knowing how to clear the error message. 3. If the user clicks on the tempting "Modify" button and manually enables Seam they can run into a problem several screens later (error message saying Seam version is incompatible and only 2.2 in the version drop-down box) with no obvious way to resolve it. The workaround is to document this quirk, but that defeats the purpose of an intuitive in-IDE wizard that guides you through setting up the project. I would recommend making the configuration stay on the default, even when the Target runtime is changed. If the user sees an incompatible version of Seam there when they scan down, they are likely to click it to see if a compatible version of Seam is there. If they see "Default configuration for X runtime" with a description saying "A good starting point... Additional facets can later be installed to add new functionality to the project" and an error message saying "Seam facet must be enabled", then their likely response will be to modify the configuration to "add new functionality" to the "good starting point" that the wizard has selected for them. -- 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, 8 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-8609) AS7 server adapter does not check if deploy directory, that the user chooses, is valid

by Andre Dietisheim (JIRA)

AS7 server adapter does not check if deploy directory, that the user chooses, is valid -------------------------------------------------------------------------------------- Key: JBIDE-8609 URL: https://issues.jboss.org/browse/JBIDE-8609 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5725) JBossWS WSDL are not deployed under the right folder

by StÃ©phane Daviet (JIRA)

JBossWS WSDL are not deployed under the right folder ---------------------------------------------------- Key: JBIDE-5725 URL: https://jira.jboss.org/jira/browse/JBIDE-5725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: GNU/Linux Ubuntu Karmic Koala 9.10, kernel 2.6.31-17-generic Reporter: StÃ©phane Daviet Priority: Minor Developping web services with Seam, my EAR is well deployed under the .metadata folder of Eclipse (.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Runtime_Server/deploy/), but the WSDLs are deployed under the native JBoss deploy directory (/opt/jboss-4.2.3.GA/server/default/data/ for me). Hereunder, the log showing the problem : [...] 18:01:15,533 INFO [EJB3Deployer] Deployed: file:/media/donnees/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Runtime_Server/deploy/odma-ws-ear.ear/odma-ws.jar/ [...] 18:01:18,906 INFO [WSDLFilePublisher] WSDL published to: file:/opt/jboss-4.2.3.GA/server/default/data/wsdl/odma-ws-ear.ear/odma-ws.jar/InscriptionDeploiement3850228908865809879.wsdl [...] -- 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, 8 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8614) AS7 server adapter: Link "Open launch configuration" is confusing

by Andre Dietisheim (JIRA)

AS7 server adapter: Link "Open launch configuration" is confusing ----------------------------------------------------------------- Key: JBIDE-8614 URL: https://issues.jboss.org/browse/JBIDE-8614 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Attachments: change-with-runtime-only.png, open-launch-config.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8589) Opening the seam forge tools console goes into an infinite loop on windows

by Fred Bricon (JIRA)

Opening the seam forge tools console goes into an infinite loop on windows -------------------------------------------------------------------------- Key: JBIDE-8589 URL: https://issues.jboss.org/browse/JBIDE-8589 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Environment: Windows 7, Helios SR2, Forge Tools 1.0.0.v20110311-0200-H17-Alpha1 from the nightly build Reporter: Fred Bricon Assignee: Alexey Kazakov Priority: Blocker After opening the Forge Console view, if I click on the Start forge button, whether I selected a project beforehand or not, the console goes into an infinite loop, eating all the CPU. Relevant parts of the thread dump are {noformat} "main" prio=6 tid=0x01399400 nid=0x1bcc runnable [0x0039d000] java.lang.Thread.State: RUNNABLE at org.eclipse.swt.internal.win32.OS.ScriptPlace(Native Method) at org.eclipse.swt.graphics.TextLayout.shape(TextLayout.java:3337) at org.eclipse.swt.graphics.TextLayout.computeRuns(TextLayout.java:356) at org.eclipse.swt.graphics.TextLayout.getBounds(TextLayout.java:1565) at org.eclipse.swt.custom.StyledTextRenderer.calculate(StyledTextRenderer.java:212) at org.eclipse.swt.custom.StyledTextRenderer.calculateClientArea(StyledTextRenderer.java:229) at org.eclipse.swt.custom.StyledText.resetCache(StyledText.java:7783) at org.eclipse.swt.custom.StyledText.handleTextChanged(StyledText.java:6202) at org.eclipse.swt.custom.StyledText$6.textChanged(StyledText.java:5636) at org.eclipse.ui.internal.console.ConsoleDocumentAdapter.documentChanged(ConsoleDocumentAdapter.java:375) - locked <0x14fac538> (a org.eclipse.ui.internal.console.ConsoleDocumentAdapter) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged2(AbstractDocument.java:769) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:736) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:721) at org.eclipse.jface.text.AbstractDocument.fireDocumentChanged(AbstractDocument.java:796) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1191) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) at org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.java:82) - locked <0x14fac298> (a org.eclipse.ui.internal.console.ConsoleDocument) at org.jboss.tools.seam.forge.console.Console$1.run(Console.java:148) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) - locked <0x14fc7df0> (a org.eclipse.swt.widgets.RunnableLock) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.WorkbenchWindow.canHandleShellCloseEvent(WorkbenchWindow.java:817) at org.eclipse.jface.window.Window$3.shellClosed(Window.java:686) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98) 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.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:308) at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1665) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4164) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1598) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2038) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2454) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:497) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4253) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1598) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2038) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2454) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:497) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4253) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1598) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2038) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) {noformat} Full thread dumps are available [here|http://pastie.org/1670643] and [there|http://pastie.org/1670653] The infinite loop keeps displaying $ [noproject] myworkspace For the record, I've seen similar behavior trying to get maven shell working under eclipse. Both projects use jline regards, Fred Bricon -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4436) Extended Support AS

by Max Rydahl Andersen (JIRA)

Extended Support AS ------------------- Key: JBIDE-4436 URL: https://jira.jboss.org/jira/browse/JBIDE-4436 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Reporter: Max Rydahl Andersen Fix For: LATER Work with AS team to make sure we got the API to provide better integration with AS for i.e. remote deployment, better/stable API that does not require JMX, ... -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8502) Cancel button doesn't work while searching via JBoss Tools Runtime Detection

by Jiri Peterka (JIRA)

Cancel button doesn't work while searching via JBoss Tools Runtime Detection ---------------------------------------------------------------------------- Key: JBIDE-8502 URL: https://issues.jboss.org/browse/JBIDE-8502 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.2.0.Final Environment: JBDS 4.0.0.GA H180, OSX 10.5, 64 bit Reporter: Jiri Peterka Steps: 1. Preferences -> Jboss Tools Runtime Detection 2. Add some higher folder (~ for example) 3. Try to cancel searching operation via Cancel button ERROR: Unable to cancel -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8597) Move from m2e 0.12 to 0.13 in trunk / 3.3.indigo branch

by Nick Boldt (JIRA)

Move from m2e 0.12 to 0.13 in trunk / 3.3.indigo branch ------------------------------------------------------- Key: JBIDE-8597 URL: https://issues.jboss.org/browse/JBIDE-8597 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Snjezana Peco Investigate moving from m2eclipse 0.12 [0] (currently mirrored here [1] and composited here [2], [3]) to 0.13 [4] [0] https://repository.sonatype.org/content/sites/forge-sites/m2e/0.12.1/S/0.... [1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/0.12/ [2] http://download.jboss.org/jbosstools/updates/indigo/ [3] http://download.jboss.org/jbosstools/updates/helios/ [4] https://repository.sonatype.org/content/sites/forge-sites/m2e/0.13.0/N/ Two major items to do: * [Sneja] work around GAV/package name changes (org.sonatype.* -> org.eclipse.*) * [Nick] set up new mirror / composite / target platform When you decide what version of m2e 0.13.* you want me to mirror, let me know and I'll add it to [2] and our 3.3.indigo branch target platform. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7281) Wizards should not allow user to select unsupported JAX-WS spec version

by Lukas Jungmann (JIRA)

Wizards should not allow user to select unsupported JAX-WS spec version ----------------------------------------------------------------------- Key: JBIDE-7281 URL: https://jira.jboss.org/browse/JBIDE-7281 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a dynamic web project with target runtime set to JBossAS6-M5 -create a ws client there with JAX-WS spec set to 2.1 and finish the wizard => generated code is of JAX-WS version 2.2 default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version. Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact the generated code is of version 2.2 jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o /tmp/fff -k http://footballpool.dataaccess.eu/data/info.wso?WSDL Could not find log4j.xml configuration, logging to console. WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS 2.1. log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). log4j:WARN Please initialize the log4j system properly. Loading FrontEnd jaxws ... Loading DataBinding jaxb ... wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff -allowElementReferences http://footballpool.dataaccess.eu/data/info.wso?WSDL wsdl2java - Apache CXF 2.2.10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
7
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 March 2011