April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1159) JBDS 3.0.0 JMX user guide issues

by Jiri Peterka (JIRA)

JBDS 3.0.0 JMX user guide issues -------------------------------- Key: JBDS-1159 URL: https://jira.jboss.org/jira/browse/JBDS-1159 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - JMX Affects Versions: 3.0.0.CR2-doc Reporter: Jiri Peterka Assignee: Svetlana mukhina Fix For: 3.0.0.GA-doc JMX Doc issues: MODIFY: "2.2 Tomcat Managing" chapter. There should be exact link pointing to specific howto establish this. MODIFY: "2.3" Eclipse Equinox Managing" There is "Select JMX Server > Open Connection and click on OK". I can't see anything like that in JBDS 3.0.0 GA, any hint? MODIFY: "service:jmx:rmi:///jndi/rmi://:8118/jmxserver:" gives me error. An error occurred while opening the connection. Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused] Add information to make it working OLD: Open the JBoss Servers View or the Servers View NEW: Open the Servers View OLD: In the JBoss Community section, select a server version NEW: In the JBoss Enterprise Middleware or in Jboss Counity sectionm, select a server profile OLD: Finish the wizard and note that you have a new entry in both the JBoss Server View and the MBean Explorer NEW: Finish the wizard and note that you have a new entry in both the Servers View and the MBean Explorer MODIFY: "The default JMX URL service:jmx:rmi:///jndi/rmi://localhost:3000/jmxrmi" doesn't work fo me An error occurred while opening the connection. Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] Plese provide hint for this or modify to working howto -- 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

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7800) Right Click -> Properties on EAP Runtime library causes error dialog.

by John Doyle (JIRA)

Right Click -> Properties on EAP Runtime library causes error dialog. --------------------------------------------------------------------- Key: JBIDE-7800 URL: https://jira.jboss.org/browse/JBIDE-7800 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta2 Environment: jbdevstudio-eap-linux-gtk-4.0.0.v201012030520R-H26-Beta2.jar on RHEL 5 Reporter: John Doyle Assignee: Rob Stryker Fix For: 3.2.0.CR1 1) Help -> Project Examples... -> Seam -> Seam 2.2 DVD Store Example - EAR (including a test project); 2) Expand "dvdstore22-ejb" folder 3) Right click on "Jboss Enterprise Application Platform 5.x runtime .." -> Properties 4) in the opened window "Properties for Jboss Enterprise Application Platform ..." click on "Classpath Container" There is no error in the log, but the Error dialog (with the message: "The currently displayed page contains invalid values" will pop out. The dialog results because the ClasspathContainerPreferencePage returns false from PreferenceDialog.isCurrentPageValid( ). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7514) Support AS 7

by Max Andersen (JIRA)

Support AS 7 ------------ Key: JBIDE-7514 URL: https://jira.jboss.org/browse/JBIDE-7514 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.2.0.Beta1 Reporter: Max Andersen Assignee: Rob Stryker Fix For: 3.2.0.CR1, 3.2.x AS 7 Alpha 1 is out and would be good if we could start/stop it - even if just means extending the Basic Server to have a start/stop script it can launch. -- 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, 9 months

7
15
0 / 0

[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, 9 months

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

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8687) JSF tooling adds an Faces Servlet declaration with no servlet mappings on project import

by Dan Allen (JIRA)

JSF tooling adds an Faces Servlet declaration with no servlet mappings on project import ---------------------------------------------------------------------------------------- Key: JBIDE-8687 URL: https://issues.jboss.org/browse/JBIDE-8687 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Final Reporter: Dan Allen Assignee: Alexey Kazakov When importing a Java EE 6 webapp that contains a faces-config.xml descriptor, the JSF tooling unnecessarily adds a Faces Servlet declaration to the web.xml. The Faces Servlet is not required in Java EE 6 (at least on JBoss AS and GlassFish). What's worse, the Servlet is added with no mappings, so it completely breaks JSF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
25
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 April 2011