August 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8524) CDI view

by Alexey Kazakov (JIRA)

CDI view -------- Key: JBIDE-8524 URL: https://issues.jboss.org/browse/JBIDE-8524 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x For example: - Project 1 - @Named - Qualifiers - Scopes - Decorators - Interceptors - Binding type ... - Project 2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8445) Add preference disabling attribute validation in JBoss Tools XML editor.

by Viacheslav Kabanovich (JIRA)

Add preference disabling attribute validation in JBoss Tools XML editor. ------------------------------------------------------------------------ Key: JBIDE-8445 URL: https://issues.jboss.org/browse/JBIDE-8445 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Besides, this framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6085) Implement Validation of ESB config file

by Viacheslav Kabanovich (JIRA)

Implement Validation of ESB config file --------------------------------------- Key: JBIDE-6085 URL: https://jira.jboss.org/jira/browse/JBIDE-6085 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.GA Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.next We have no validation implemented for consistency of objects, especially of actions that formally may be supplied by any set of properties while each action class requires a specific configuration. We should implement validation similar to that we have for beans in Seam and CDI. Documentation on ESB contains many rules on consistency of ESB objects not covered by simply complying with xml schema. -- 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

13 years

4
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4973) OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema.

by Anton Klimkovich (JIRA)

OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema. ------------------------------------------------------------------------------------------------ Key: JBIDE-4973 URL: https://jira.jboss.org/jira/browse/JBIDE-4973 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, Seam Affects Versions: 3.1.0.M4 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create Seam 2.0 or Seam 2.2 web project EXECUTE: Open components.xml EXECUTE: Make OpenOn on xsi:schemaLocation= "... http://jboss.com/products/seam/core-2.0.xsd for example FAILURE: File with schema isn't found EXECUTE: Make OpenOn on xsi:schemaLocation= "http://jboss.com/products/seam/core " ASSERT: Web Browser with JBoss.com page is opened; XML schema description should exists FAILURE: JBoss.com is opened with 404 - Page Not Found error on the page. -- 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

13 years

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed

by Denis Golovin (JIRA)

New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4920 URL: https://jira.jboss.org/jira/browse/JBIDE-4920 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Priority: Trivial 1. EXECUTE: Create Java Project 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry 5. EXECUTE: Press '<Back' 6. EXECUTE: Press 'Next>' and select 'Classpath' tab 7. ASSERT: State is the same as it was after 4 step 4 above executed Now it restores default values -- 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

13 years

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8528) Refactoring a Class that is used in a context, doesn't refactor the context Type

by Ehrann Mehdan (JIRA)

Refactoring a Class that is used in a context, doesn't refactor the context Type -------------------------------------------------------------------------------- Key: JBIDE-8528 URL: https://issues.jboss.org/browse/JBIDE-8528 Project: Tools (JBoss Tools) Issue Type: Bug Components: FreeMarker Affects Versions: 3.3.x Environment: Windows XP, Reporter: Ehrann Mehdan In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi Build id: M20110210-1200 This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" <tag attribute="${data.someValue}">... This code will (removed opening tag bracket) tag attribute="${data.someValue}">... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4455) Add JUnit tetst for org.hibernate.eclipse.mapper.editors.reveng

by Denis Golovin (JIRA)

Add JUnit tetst for org.hibernate.eclipse.mapper.editors.reveng --------------------------------------------------------------- Key: JBIDE-4455 URL: https://jira.jboss.org/jira/browse/JBIDE-4455 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0.M2 1. Test editor is opened on reveng XML file. 2. Test editor is able to process all kinds of elements in xml file. tests should try to achieve at least 100% classes coverage for org.hibernate.eclipse.mapper.editors.reveng package. -- 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

13 years

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8527) Content Assist on org.w3c.Document content assist is wrong, should use the default Freemarker XML model wrapper conventions

by Ehrann Mehdan (JIRA)

Content Assist on org.w3c.Document content assist is wrong, should use the default Freemarker XML model wrapper conventions --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8527 URL: https://issues.jboss.org/browse/JBIDE-8527 Project: Tools (JBoss Tools) Issue Type: Bug Components: FreeMarker Affects Versions: 3.3.x Reporter: Ehrann Mehdan Priority: Minor In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi Build id: M20110210-1200 Putting a context model that includes a DOM object (org.w3c.Document) and using content assist provides the wrong content suggestions: Instead of using the DOM object wrapper (e.g. by providing also an XSL schema or a sample XML) it produces the properties of the Document class This requires an enhancement to the context tab, allowing to add an XSD or a sample XML to be used as a base for the correct content assist -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3894) Add JUnit test for org.jboss.tools.hibernate.ui.xml.editor

by Denis Golovin (JIRA)

Add JUnit test for org.jboss.tools.hibernate.ui.xml.editor ---------------------------------------------------------- Key: JBIDE-3894 URL: https://jira.jboss.org/jira/browse/JBIDE-3894 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: QA Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 -- 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

13 years

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components

by Denis Golovin (JIRA)

Create Stress JUnit Test Suite withch is included all available JUnit tests from all components ----------------------------------------------------------------------------------------------- Key: JBIDE-3937 URL: https://jira.jboss.org/jira/browse/JBIDE-3937 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 Why we need this? The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems. It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite. -- 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

13 years

1
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2011