May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8839) JSF project opened in Project explorer has 2 nodes with same content

by Vlado Pakan (JIRA)

JSF project opened in Project explorer has 2 nodes with same content -------------------------------------------------------------------- Key: JBIDE-8839 URL: https://issues.jboss.org/browse/JBIDE-8839 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Affects Versions: 3.2.1.M1 Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105011951R-H359-M1 Reporter: Vlado Pakan Assignee: Max Rydahl Andersen For JSF project there are two similar nodes with labels "Web Resources : WebContent" and "WebContent". See attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8801) Seam Facet Install Delegate should not copy resources and libraries from Seam Runtime

by Daniel Azarov (JIRA)

Seam Facet Install Delegate should not copy resources and libraries from Seam Runtime ------------------------------------------------------------------------------------- Key: JBIDE-8801 URL: https://issues.jboss.org/browse/JBIDE-8801 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Daniel Azarov Assignee: Daniel Azarov -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
17
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, 9 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-8934) OpenOn throws NullPointerException on tag attribute values which contain path to image file

by Daniel Azarov (JIRA)

OpenOn throws NullPointerException on tag attribute values which contain path to image file ------------------------------------------------------------------------------------------- Key: JBIDE-8934 URL: https://issues.jboss.org/browse/JBIDE-8934 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Daniel Azarov Assignee: Alexey Kazakov Fix For: 3.3.x Attachments: WorkspaceFileHyperlinkException.log Test Case: 1. Create Seam Web War project 2. Open 'WebContent/home.xhtml' file in Visual Page Editor 3. Point mouse to "/img/seamlogo.png" tag attribute value and press Ctrl button FAIL: NullPointerException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8854) JBT 3.7.0 nightly build installation errors

by Isaac Rooskov (JIRA)

JBT 3.7.0 nightly build installation errors ------------------------------------------- Key: JBIDE-8854 URL: https://issues.jboss.org/browse/JBIDE-8854 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 3.3.x Environment: Fedora 14 64bit with Eclipse Indigo M6a Reporter: Isaac Rooskov Assignee: Nick Boldt Two issues present when installing from the 3.7.0 nightly build update site within Eclipse Indigo M6a: 1) Upon clicking everything in the list of install items (except the one that says "All JBoss Tools 3.2.0"), after everything is downloaded and the installation begins, this error appears: An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.jboss.tools.esb.core,1.5.0.v20110504-0713-H212-M1 No repository found containing: org.eclipse.update.feature,org.jboss.tools.esb.feature,1.3.0.v20110504-0713-H212-M1 No repository found containing: osgi.bundle,org.jboss.tools.esb.project.core,1.4.0.v20110504-0713-H212-M1 No repository found containing: osgi.bundle,org.jboss.tools.esb.project.ui,1.4.0.v20110504-0713-H212-M1 No repository found containing: osgi.bundle,org.jboss.tools.esb.ui,1.4.0.v20110504-0713-H212-M1 No repository found containing: osgi.bundle,org.jboss.tools.esb.validator,1.4.0.v20110504-0713-H212-M1 2)Upon skipping components that the above files relate to, installation completes and Eclipse is restarted. Upon re-launching Eclipse the following error is displayed before a workspace location is asked for: An error has occurred. See the log file /home/irooskov/Work/JBT/eclipse/configuration/<random_long_number_string>.log. Within the generated log file, the following can be found: !ENTRY org.eclipse.equinox.registry 4 0 2011-05-05 08:27:17.902 !MESSAGE Unable to create output stream for registry cache. !STACK 0 java.io.FileNotFoundException: /home/irooskov/Work/JBT/eclipse/configuration/org.eclipse.core.runtime/.extraData3426067224546608204.new (Too many open files) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:179) at java.io.FileOutputStream.<init>(FileOutputStream.java:131) at org.eclipse.core.internal.registry.TableWriter.openFiles(TableWriter.java:96) at org.eclipse.core.internal.registry.TableWriter.saveCache(TableWriter.java:78) at org.eclipse.core.internal.registry.ExtensionRegistry.stop(ExtensionRegistry.java:802) at org.eclipse.core.internal.registry.osgi.Activator.stopRegistry(Activator.java:151) at org.eclipse.core.internal.registry.osgi.Activator.stop(Activator.java:66) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1160) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:690) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:597) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
25
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, 9 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, 9 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8856) Deployment tab: should only list projects that were added to the adapter

by Andre Dietisheim (JIRA)

Deployment tab: should only list projects that were added to the adapter ------------------------------------------------------------------------ Key: JBIDE-8856 URL: https://issues.jboss.org/browse/JBIDE-8856 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.M2 Attachments: project-that-isnt-added-is-listed.png On the "Deployment" tab of the server adapter editor we currently list all dynamic web projects that are available. We do not only list those that were added to the adapter. This is confusing in my eyes. The tomcat adapter, which also has a deployment tab, only lists the projects that were added to the adapter. IMHO this is what a inexperienced user would expect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9041) AS7: switching deployment mode (exploded->war) does not redeploy

by Andre Dietisheim (JIRA)

AS7: switching deployment mode (exploded->war) does not redeploy ---------------------------------------------------------------- Key: JBIDE-9041 URL: https://issues.jboss.org/browse/JBIDE-9041 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 Attachments: switch-exploded-war.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9030) Update the m2eclipse requirements to use m2eclipse-wtp 0.12.0

by Fred Bricon (JIRA)

Update the m2eclipse requirements to use m2eclipse-wtp 0.12.0 ------------------------------------------------------------- Key: JBIDE-9030 URL: https://issues.jboss.org/browse/JBIDE-9030 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng, maven Affects Versions: 3.2.1.M1 Reporter: Fred Bricon Assignee: Nick Boldt Fix For: 3.2.1.Final m2eclipse-wtp 0.12.0 has been released early May. It should be used in the m2eclipse requirements. Version 0.12.0.20110421-1500 is available from http://m2eclipse.sonatype.org/sites/m2e-extras/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
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 May 2011