February 2010 - jbosstools-issues

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

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3845) Code assist for #{messages['...']} should suggest properties when user types "[".

by Alexey Kazakov (JIRA)

Code assist for #{messages['...']} should suggest properties when user types "[". --------------------------------------------------------------------------------- Key: JBIDE-3845 URL: https://jira.jboss.org/jira/browse/JBIDE-3845 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.1.0 Now it we suggest properties only after "." We should recognize "[" as well. -- 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
21
0 / 0

[JBoss JIRA] Created: (JBIDE-3288) CSS Class Wizard UI improvements (second version)

by Yura Zhishko (JIRA)

CSS Class Wizard UI improvements (second version) ------------------------------------------------- Key: JBIDE-3288 URL: https://jira.jboss.org/jira/browse/JBIDE-3288 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Used from the vpe it should give a dropdown with the included .css files if possible, again to avoid unecessary manual browsing 2) On new styles (style attribute is empty) it would be good to remember the previous editied external css -- 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

6
21
0 / 0

[JBoss JIRA] Created: (JBIDE-5535) New Web Service

by Burr Sutter (JIRA)

New Web Service --------------- Key: JBIDE-5535 URL: https://jira.jboss.org/jira/browse/JBIDE-5535 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard. The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following: package com.jboss.lab; import javax.jws.WebMethod; import javax.jws.WebService; @WebService public class MyWebService { @WebMethod public String sayHello(String name) { return "Hello2 " + name + "!"; } } And the appropriate entries in the web.xml. <servlet> <servlet-name>MyWebServiceServlet</servlet-name> <servlet-class>com.jboss.lab.MyWebService</servlet-class> </servlet> <servlet-mapping> <servlet-name>MyWebServiceServlet</servlet-name> <url-pattern>/MyWebService</url-pattern> </servlet-mapping> See screenshots for current functionality. This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBDS-411) Need 64-bit windows support

by Samuel Mendenhall (JIRA)

Need 64-bit windows support --------------------------- Key: JBDS-411 URL: https://jira.jboss.org/jira/browse/JBDS-411 Project: Developer Studio Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Samuel Mendenhall Assignee: Max Rydahl Andersen JBDS is not usable on a 64-bit Windows machine. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1608) Hibernate Configuration view should display all database

by Vitali Yemialyanchyk (JIRA)

Hibernate Configuration view should display all database --------------------------------------------------------- Key: JBIDE-1608 URL: http://jira.jboss.com/jira/browse/JBIDE-1608 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Fix For: LATER Look at the attached file hibernate.cfg.xml - if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql</property> Hibernate Configuration view -> ... -> Database display correctly mysql database - but if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306</property> look like this Hibernate Configuration view -> ... -> Database display nothing and the user can't understand what is wrong - I provide 2 screenshots the same if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql1</property> mysql1 - there is no such DB as I think in first case Hibernate Configuration should display all mysql DBs and in the second case the user should get message - something like "Can't find shuch DB" Other thing - then I press right mouse button on Hibernate Configuration view -> ... -> Database - I expect to get possibility to configure DB URL and may be some other properties - the best thing here if I'll get some dialog - or at least possibility to open hibernate.cfg.xml for edit. For this I'll create other new 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

14 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4009) Add Open On feature for jBPM GPD

by Joao Paulo Viragine (JIRA)

Add Open On feature for jBPM GPD -------------------------------- Key: JBIDE-4009 URL: https://jira.jboss.org/jira/browse/JBIDE-4009 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Affects Versions: 3.0.0.CR2 Environment: JBDS 2.0.0.CR2 Reporter: Joao Paulo Viragine Priority: Minor It would be great if we could use Open On in jBPM GPD. (Source view mode) E.g. Open class when click in a: <action class="com.sample.action.MessageActionHandler"> -- 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, 10 months

6
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5610) Avoid empty preference pages

by Jiri Peterka (JIRA)

Avoid empty preference pages ---------------------------- Key: JBIDE-5610 URL: https://jira.jboss.org/jira/browse/JBIDE-5610 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.CR1 Environment: JBT Build date 201001051956 Reporter: Jiri Peterka Fix For: 3.1.0.GA Attachments: empty1.png, empty2.png, empty3.png, empty4.png Avoid empty Preference pages in Windows Preferences (for example JBoss jBPM or BPEL, see screenshots). Possible solution: Add addional text or move some general setting into it. -- 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, 10 months

5
14
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 February 2010