September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4827) Create automated UI functional tests for Hibernate Tools

by Jiri Peterka (JIRA)

Create automated UI functional tests for Hibernate Tools -------------------------------------------------------- Key: JBIDE-4827 URL: https://jira.jboss.org/jira/browse/JBIDE-4827 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 3.1.0.CR1 Reporter: Jiri Peterka Fix For: 3.0.0.cr1 Create automated UI functional tests for Hibernate Tools. Test cases will be follow manual test cases. -- 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

16 years

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4693) Provide cheat sheets

by Xue Peng (JIRA)

Provide cheat sheets --------------------- Key: JBIDE-4693 URL: https://jira.jboss.org/jira/browse/JBIDE-4693 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.M3 Reporter: Xue Peng Assignee: Xue Peng Provide cheat sheets to help the user can easily understand how to use the Smooks configuration editor. -- 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

16 years

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4304) Autoconfigure datasources from JBoss in DTP

by Max Rydahl Andersen (JIRA)

Autoconfigure datasources from JBoss in DTP ------------------------------------------- Key: JBIDE-4304 URL: https://jira.jboss.org/jira/browse/JBIDE-4304 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Max Rydahl Andersen Fix For: 3.1.0.M1, 3.1.0.M2 It would be great if DTP would automatically (or semi-automatically) could be configured to pickup the -ds.xml in a server runtime so users didn't have to set it up. Not sure where in the ui we should have this, a couple of options come to my mind: 1) At AS Server/runtime creation have a checkbox saying "Configure -ds.xml automatically in DTP" and then we will keep DTP informed about the -ds.xml files for it to pick up 2) In DTP's ui have a way to add or maybe only import a -ds.xml and have it preconfigured. The biggest issue will be to know which drivers we should be using for -ds.xml... Things that should be considered: If users changes the -ds.xml how does DTP learn about it ? If the users remove the -ds.xml how does DTP react ? If the users add .? Needs investigation into if DTP have extensions point that allows for this kind of 'monitored' resources to update the connections; or if it is better to simply just have a way to "import" settings from ds.xml's (and then possibly have a manual refresh to pickup changes) Or have both. The usecase for this is to be able to use already existing and newly added -ds.xml files from within Eclipse with minimal setup, i.e. for Seam and Dali projects. (I think this is a duplicate, but couldn't find 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

16 years

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2361) If project name contains '!' character, components can't be recognized in the VPE

by Tatyana Romanovich (JIRA)

If project name contains '!' character, components can't be recognized in the VPE --------------------------------------------------------------------------------- Key: JBIDE-2361 URL: http://jira.jboss.com/jira/browse/JBIDE-2361 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.alpha Environment: JBoss Developer Studio Version: 1.1.0 Build id: 200806161541-nightly Build date: 06/16/2008 15:46 Reporter: Tatyana Romanovich Assigned To: Maxim Areshkau EXECUTE: Create JSF KickStartWithoutLibs (JSF Env: JSF 1.2) project EXECUTE: Set name of project to any string with "!" character (testProject!) EXECUTE: Open any jsp file in the VPE FAILURE: All components are not recognized on the Visual, Source panes and on the Preview tab. "Unknown tag" tool tips appear. -- 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

16 years

6
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step

by Denis Golovin (JIRA)

HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step ----------------------------------------------------------------------------------------- Key: JBIDE-4918 URL: https://jira.jboss.org/jira/browse/JBIDE-4918 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Several notes about hibernate.cfg.xml from Hibermate documentation: 1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e. into source folder it will in case of SessionFactory sf = new Configuration().configure().buildSessionFactory(); additional info is here (http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...) 2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In this case it can be loaded by code SessionFactory sf = new Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory(); Considering that, withatd should: 1. Provide default values based on current selection in Package Explorer - if package or source folder is selected in Package explorer wizard should have the same selection in wizard - if any other folder outside source folder is selected in Package Explorer, wizard should select first source folder available in project 2. Now validation of selected file name take place on second step, that should be done on first one. 3. Validation should be not so strict but more informative: - File extension must be .xml (error) - File extension should be .xml - If location for file is not within src folder (warning) - Configuration placed outside CLASSPATH will not be available at run-time - If location is src root and file name is 'hibernate.cfg.xml' (no errors or warnings) - This wizard allows you to create a configuration for Hibernate Console - If location is src root and file name is not 'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}' you'll have to pass file name to Configuration.configure() method - If location is within src root but not src root and file name is not 'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}' you'll have to provide path file to Configuration.configure() method (not sure if that true) (Messages need to be discussed) 4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be entered -- 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

16 years

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4824) adjust to proper usage of w3c dom and the changes in upcoming WTP 3.2

by Max Rydahl Andersen (JIRA)

adjust to proper usage of w3c dom and the changes in upcoming WTP 3.2 --------------------------------------------------------------------- Key: JBIDE-4824 URL: https://jira.jboss.org/jira/browse/JBIDE-4824 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Max Rydahl Andersen Assignee: Vitali Yemialyanchyk Not sure how much this affects us but the following were posted to WTP-DEV mailing list: "In an effort to become more compliant with the W3C DOM specification, we are planning to make changes that may require action on your behalf. The current behavior of the WTP implementation of org.w3c.dom.Element returns null for getAttribute(String) and getAttributeNS(String) if the attribute value is not specified. After the change, calls to these methods will return an empty string if the attribute value is not specified. This change is required to comply with the interface, and will correct various NullPointerExceptions when EMF is used with our DOM implementation and the EMF code is undeniably correct. What is required? If your code was depending on the DOM returning null to indicate a missing attribute, the code should be changed to hasAttribute(String) or hasAttributeNS(String) before obtaining the value. When will this change be implemented? During Milestone 3 of WTP 3.2. Where can I find more information? https://bugs.eclipse.org/bugs/show_bug.cgi?id=272378" We had some code in th reveng.xml editing which I believe depended on this kind of behavior. Best to adjust to the spec so we work on both versions. -- 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

16 years

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4155) Allow publish on build

by Chris Bredesen (JIRA)

Allow publish on build ---------------------- Key: JBIDE-4155 URL: https://jira.jboss.org/jira/browse/JBIDE-4155 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: UpStream Affects Versions: 3.0.0.GA Reporter: Chris Bredesen Priority: Minor As a developer using JBoss Tools to publish projects to JBoss Application Server, I'd like to be able to turn off automatic publishing and publish only when the project is built. When the automatic publish interval is long enough to not be distracting, it is too slow for rapid turnaround. When it's short enough to create rapid turnaround, it often blocks other actions such as building or re-saving a view file. Allowing the user to control this and simply hook the publish to a [manual] build would solve both problems. See forum reference for details. -- 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

16 years

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3373) f:facet processing for xhtml pages using JSF tags

by Yura Zhishko (JIRA)

f:facet processing for xhtml pages using JSF tags ------------------------------------------------- Key: JBIDE-3373 URL: https://jira.jboss.org/jira/browse/JBIDE-3373 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau Insert next source example code into the page: <h:panelGrid columns="2" border="5" width="250" rules="all" frame="above" cellpadding="4" cellspacing="6" bgcolor="silver" style="COLOR: #ff0080; BACKGROUND-COLOR: #ffff00; TEXT-DECORATION: underline; FONT-STYLE: italic; FONT-WEIGHT: bold; FONT-SIZE: xx-large; FONT-FAMILY: 'Arial Black';" styleClass="" captionClass="myStyle0" columnClasses="" rowClasses="" headerClass="" footerClass="" > <f:facet name="footer"> <p>sdlfsd</p> <p>dsfjal</p> <input type="button">fsdadf</input> gkhadjksfg </f:facet> <h:outputText value="begin"/> </h:panelGrid> VPE doesn't render usuall html tags and simple text, but browsers do it. <f:facet> can content only one UIComponent for JSF components. -- 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

16 years

5
27
0 / 0

[JBoss JIRA] Created: (JBIDE-3872) No space between style classes which have been applied from CSS dialog

by Yura Zhishko (JIRA)

No space between style classes which have been applied from CSS dialog ---------------------------------------------------------------------- Key: JBIDE-3872 URL: https://jira.jboss.org/jira/browse/JBIDE-3872 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.GA Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor 1) Open/create CSS file 2) Add next content to created CSS file: .myClass1, .myClass2 { background-color: red; } 3) Choose any componenet on the page that support styleClass or class attribute and make a mouseclick on it 4) Click the button opposite styleClass or class attribute in Properties view 5) Check Style class and choose the line with classes from step 2 6) Press OK FAILURE: There is no space between style classes in styleClass attribute. -- 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

16 years

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2809) Option to specify the project(s) names in the "Seam Web project" wizard

by Adrian Mitev (JIRA)

Option to specify the project(s) names in the "Seam Web project" wizard ----------------------------------------------------------------------- Key: JBIDE-2809 URL: https://jira.jboss.org/jira/browse/JBIDE-2809 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.alpha Reporter: Adrian Mitev Priority: Minor Let's say i want to name my web project "MyProject-war" and the ejb project should not be "MyProject-war-ejb", it should be "MyProject-ejb" .. the same for ear and test projects. -- 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

16 years

5
18
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 September 2009