October 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10069) JBoss Tools + Openshift - attempting to sign in to OpenShift via Eclipse/JBoss Tools = no respomse

by Len DiMaggio (Created) (JIRA)

JBoss Tools + Openshift - attempting to sign in to OpenShift via Eclipse/JBoss Tools = no respomse -------------------------------------------------------------------------------------------------- Key: JBIDE-10069 URL: https://issues.jboss.org/browse/JBIDE-10069 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Environment: RHEL6 Firefox 3.6.23 Version: Indigo Release Build id: 20110615-0604 JBoss Tools 3.3.0.M4 java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.40.1.9.10.el6_1-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Reporter: Len DiMaggio Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.3.0.M4 To recreate: File->New->Other->OpenShift, then attempt to 'sign in' to OpenShift account. There is no response - see screenshot. Eclipse is not hung, as user can cancel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
6
0 / 0

[JBoss JIRA] (JBIDE-9831) Unable to select JBossWS CXF as the WS Runtime

by Mustafa Musaji (Created) (JIRA)

Unable to select JBossWS CXF as the WS Runtime ---------------------------------------------- Key: JBIDE-9831 URL: https://issues.jboss.org/browse/JBIDE-9831 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.1.Final Environment: JBoss Developer Studio 4.1 JBoss Enterprise Platform (EAP) 5.1 with JBossWS CXF installed Reporter: Mustafa Musaji Assignee: Brian Fitzpatrick When you want to create a CXF Client there is no way to select JBossWS CXF as the WS Runtime. I have a CXF Web Service deployed to JBoss. The wsdl is published to a URL. I go to File->New->Web Services->Web Service Client. At this dialogue box I get to choose my configuration to create the client stubs. When selecting Web Service Runtime, I cannot select JBossWS CXF that is within JBoss. It only gives me options for Apache Axis, Apache CXF and JbossWS. So I then think I need to add a CXF runtime from Window->Preferences->Web Services->CXF.2x Preferences. Once again, this doesn't let me choose a JBossWS CXF runtime other than an Apache CXF runtime. How can I select JBossWS CXF as the CXF runtime of choice? Selecting JBossWS and a JBoss Server With CXF installed does not work either. I choose the CXF JBoss Server Runtime and JBossWS as the Web Service Runtime. The generated classes have the following header. /** * This class was generated by the JAX-WS RI. * JAX-WS RI 2.1.7-09/10/2010 09:17 PM(mockbuild)- * Generated source version: 2.1 * */ Using wsconsume.sh from the same JBoss instance the generated classes have the following header /** * This class was generated by Apache CXF 2.2.6-patch-01 * Tue Oct 04 14:16:01 BST 2011 * Generated source version: 2.2.6-patch-01 * */ As you can see the JBDS still uses JBossWS Native as the stack to build the client stubs from. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

13
25
0 / 0

[JBoss JIRA] (JBIDE-9864) Unable to start AS7

by Libor Zoubek (Created) (JIRA)

Unable to start AS7 ------------------- Key: JBIDE-9864 URL: https://issues.jboss.org/browse/JBIDE-9864 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Environment: Windows, AS 7.0.1 Reporter: Libor Zoubek Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M4 Attempt to start AS7 results to following error {noformat} !ENTRY org.eclipse.debug.ui 4 0 2011-10-07 18:44:30.796 !MESSAGE Tab group extension: org.eclipse.jdt.debug.ui.launchConfigurationTabGroup.remoteJavaApplication for type org.eclipse.jdt.launching.remoteJavaApplication for the * mode has been replaced by extension: org.jboss.tools.common.jdt.debug.ui.launching.launchConfigurationTabGroup.JBossRemoteJavaApplication2 !ENTRY org.eclipse.core.jobs 4 2 2011-10-07 18:44:30.828 !MESSAGE An internal error occurred during: "Starting JBoss 7.0 Runtime Server". !STACK 0 java.lang.IllegalArgumentException: classToLaunch cannot be null at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49) at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.actualLaunch(AbstractJBossStartLaunchConfiguration.java:177) at org.jboss.ide.eclipse.as.core.server.internal.launch.LocalJBossStartLaunchDelegate.actualLaunch(LocalJBossStartLaunchDelegate.java:53) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.actualLaunch(DelegatingStartLaunchConfiguration.java:56) at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.launch(AbstractJBossStartLaunchConfiguration.java:138) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} JBossAS Tools 2.3.0.v20111007-0916-H768-M4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

7
6
0 / 0

[JBoss JIRA] (JBDS-1904) mylyn.tasks.ui feature is missing on extras

by Libor Zoubek (Created) (JIRA)

mylyn.tasks.ui feature is missing on extras ------------------------------------------- Key: JBDS-1904 URL: https://issues.jboss.org/browse/JBDS-1904 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, updatesite Affects Versions: 5.0.0.M4 Reporter: Libor Zoubek Priority: Blocker Fix For: 5.0.0.M4 Installation of extras must work without any other updatesite defined, right? I am installing extras using script. This is what I get when I install all extras without any other that extras updatesite defined {noformat} [groovy] !ENTRY org.eclipse.equinox.p2.director 4 1 2011-10-25 22:38:46.256 [groovy] !MESSAGE Cannot complete the install because one or more required items could not be found. [groovy] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-10-25 22:38:46.257 [groovy] !MESSAGE Software being installed: Mylyn (Selected) 1.1.0.v20111025-0135-H35-M4 (com.jboss.jbds.mylyn.feature.feature.group 1.1.0.v20111025-0135-H35-M4) [groovy] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-10-25 22:38:46.257 [groovy] !MESSAGE Missing requirement: Mylyn (Selected) 1.1.0.v20111025-0135-H35-M4 (com.jboss.jbds.mylyn.feature.feature.group 1.1.0.v20111025-0135-H35-M4) requires 'org.eclipse.mylyn.tasks.ui [3.6.2.v20110826-0100]' but it could not be found {noformat} This is what I get when I install all extras with addidional core + jbds target platform sites defined {noformat} [groovy] !ENTRY org.eclipse.equinox.p2.director 4 1 2011-10-25 22:44:02.507 [groovy] !MESSAGE Cannot complete the install because one or more required items could not be found. [groovy] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-10-25 22:44:02.511 [groovy] !MESSAGE Software being installed: Mylyn (Selected) 1.1.0.v20111025-0135-H35-M4 (com.jboss.jbds.mylyn.feature.feature.group 1.1.0.v20111025-0135-H35-M4) [groovy] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-10-25 22:44:02.512 [groovy] !MESSAGE Missing requirement: Mylyn (Selected) 1.1.0.v20111025-0135-H35-M4 (com.jboss.jbds.mylyn.feature.feature.group 1.1.0.v20111025-0135-H35-M4) requires 'org.apache.commons.io [2.0.1.v201105210651]' but it could not be found {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

8
8
0 / 0

[JBoss JIRA] (JBIDE-9836) Web Fragment projects are deployed as exploded jars

by Fred Bricon (Created) (JIRA)

Web Fragment projects are deployed as exploded jars --------------------------------------------------- Key: JBIDE-9836 URL: https://issues.jboss.org/browse/JBIDE-9836 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Fred Bricon Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M4 Attachments: web-fragment.zip Following up https://issues.sonatype.org/browse/MECLIPSEWTP-181. Web Fragment projects are deployed as exploded jars in AS7 instead of zipped archives (probably other AS'es too). This leads to a deployment failure : {noformat} 10:11:40,572 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "web.war" 10:11:40,600 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."web.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."web.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "web.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: failed to process "/home/fbricon/Dev/servers/jboss-as-web-7.0.2.Final/standalone/deployments/web.war/WEB-INF/lib/fragment.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:118) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: failed to process "/home/fbricon/Dev/servers/jboss-as-web-7.0.2.Final/standalone/deployments/web.war/WEB-INF/lib/fragment.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:173) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:151) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:112) ... 6 more Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [:1.6.0_26] at java.util.zip.ZipFile.<init>(ZipFile.java:127) [:1.6.0_26] at java.util.jar.JarFile.<init>(JarFile.java:135) [:1.6.0_26] at java.util.jar.JarFile.<init>(JarFile.java:99) [:1.6.0_26] at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:95) at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:81) at org.jboss.vfs.VFS.mountZip(VFS.java:408) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:168) ... 8 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9553) Forge Runtime is lost when eclipse is restarted

by George Gastaldi (JIRA)

Forge Runtime is lost when eclipse is restarted ----------------------------------------------- Key: JBIDE-9553 URL: https://issues.jboss.org/browse/JBIDE-9553 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: George Gastaldi If you configure a new Forge runtime and restart eclipse, the installed Forge runtime disappears from the "Forge Runtime" tab. Tested with the nightly build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9271) Workspace locks/slow when Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project'

by Lincoln Baxter III (JIRA)

Workspace locks/slow when Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project' ------------------------------------------------------------------------------------------------- Key: JBIDE-9271 URL: https://issues.jboss.org/browse/JBIDE-9271 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), maven Environment: Linux Ubuntu x64 Natty Eclipse Indigo 3.7 Java 1.6.0_24 Reporter: Lincoln Baxter III Assignee: Alexey Kazakov Invoking 'CDI (Contexts and Dependency Injection Builder)' on 'project' causes the workspace to lock whenever a file is changed. Check out this project: https://github.com/ocpsoft/rewrite Import in to workspace as maven project. Open a source file in API. Change the file. Try to change or save any other file (the workspace locks while it waits for CDI builder to finish.) Very annoying :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

8
28
0 / 0

[JBoss JIRA] (JBIDE-10042) Tooltip for feeds in central shows up even though central does not have focus

by Max Rydahl Andersen (Created) (JIRA)

Tooltip for feeds in central shows up even though central does not have focus ----------------------------------------------------------------------------- Key: JBIDE-10042 URL: https://issues.jboss.org/browse/JBIDE-10042 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Max Rydahl Andersen Priority: Critical Fix For: 3.3.0.Beta1 I multiple times got a tooltip "stuck" in front of project example UI and other dialogs that showsup on top of Central. Looks like we are showing the tooltips even though the editor does not have focus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10028) JBoss Central Editor Maximize/Restore actions freeze UI and loads CPU

by Denis Golovin (Created) (JIRA)

JBoss Central Editor Maximize/Restore actions freeze UI and loads CPU --------------------------------------------------------------------- Key: JBIDE-10028 URL: https://issues.jboss.org/browse/JBIDE-10028 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.M4 Environment: Linux GTK x86 Reporter: Denis Golovin After any operation related to Maximize/Restore UI is freezes for noticeable time, one CPU is loaded 100% and after some time OS ask about killing eclipse window. After any EXEC: step in test case UI is freezes. Always reproducible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

16
22
0 / 0

[JBoss JIRA] (JBIDE-9976) Tooltips in JBoss Central crash in Windows 7 64bits

by Fred Bricon (Created) (JIRA)

Tooltips in JBoss Central crash in Windows 7 64bits --------------------------------------------------- Key: JBIDE-9976 URL: https://issues.jboss.org/browse/JBIDE-9976 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.M4 Environment: Windows 7 64bits, JDK 7 64bits Reporter: Fred Bricon Priority: Blocker Fix For: 3.3.0.M4 When JBoss Central is open, if the mouse cursor hovers over the News feed, a SWT error occurs : {noformat} org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(SWT.java:4308) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:683) at org.eclipse.swt.browser.Browser.<init>(Browser.java:99) at org.jboss.tools.central.editors.FeedsToolTip.createToolTipContentArea(FeedsToolTip.java:173) {noformat} Following the error popup, another window is opened, asking : {noformat} An SWT error has occurred. You are recommended to exit the workbench. Subsequent errors may happen and exit the workbench without warning. See the .log file for more details. Do you want to exit the workbench? (Yes / No) {noformat} Since xulrunner is not compatible with 64bits JVM on Windows, this is not surprising. I guess if can't find another to display the tooltips (not using a browser), they should not be displayed at all (if xulrunner is missing). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
6
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 October 2011