September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1893) Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages

by Anton Klimkovich (JIRA)

Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages ------------------------------------------------------------------------------- Key: JBIDE-1893 URL: http://jira.jboss.com/jira/browse/JBIDE-1893 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 2.0.1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create JSF with Facelets kickstart project EXECUTE: Create JSF1.2 kickstart project EXECUTE: Window->Preferenses -> JBossTools->Web->JSF->JSF Pages EXECUTE: Press Add button EXECUTE: Press Browse button ASSERT: Two projects available: JSF with Facelets and JSF1.2 kickstarts EXECUTE: Expand pages folder in JSF with Facelets project ASSERT: *.xhtml pages shoul be available . FAILURE: *.xhtml pages are not available . -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (RHDS-321) Warning in the case of incorrect bean references

by Florian Marwede (JIRA)

Warning in the case of incorrect bean references ------------------------------------------------ Key: RHDS-321 URL: http://jira.jboss.com/jira/browse/RHDS-321 Project: Red Hat Developer Studio Issue Type: Feature Request Reporter: Florian Marwede Priority: Minor See forum thread. The warning should behave like a eclipse warning (yellow underline in the editor and also appear in problem view). It must be configurable, so you can switch it off when you manage your beans in a way RHDS can't analyze. -- 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.

by Denis Golovin (JIRA)

CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation. ------------------------------------------------------------------------------------------- Key: JBDS-1708 URL: https://issues.jboss.org/browse/JBDS-1708 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.1.0.M1 Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux 32bit, Java Sun JDK 1.6_25 Reporter: Vlado Pakan Assignee: Denis Golovin Priority: Critical Fix For: 4.1.0.CR2 Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png, screenshot82.png When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime. It's recognized as AS v.4.3.0 and added to available runtimes during installation. But after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime and therefore there is a warning displayed in Edit Server Runtime Environment dialog. When added manually via Preferences > Server Runtime > Environments > Add it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed in Edit Server Runtime Environment dialog. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-1796) JBDS update site builds should use .GA when parent pom has .Final as the BUILD_ALIAS (artifact suffix)

by Nick Boldt (JIRA)

JBDS update site builds should use .GA when parent pom has .Final as the BUILD_ALIAS (artifact suffix) ------------------------------------------------------------------------------------------------------ Key: JBDS-1796 URL: https://issues.jboss.org/browse/JBDS-1796 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, updatesite Affects Versions: 4.1.0.CR4, 5.0.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.GA, 5.0.0.M3 Add this (or similar) to 4.1 and 5.0 _stable_branch jobs which build com.jboss features/plugins: # If .Final in JBT, use .GA in JBDS if [[ $(cat ${WORKSPACE}/build/parent/pom.xml | grep "<BUILD_ALIAS>Final</BUILD_ALIAS>") ]]; then export MAVEN_FLAGS="${MAVEN_FLAGS} -DBUILD_ALIAS=GA"; fi; echo $MAVEN_FLAGS Meanwhile, JBDS product build is still controlled via the version.properties file in SVN. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9224) Cleaning job freeze during cleaning JPA projects

by Jiri Peterka (JIRA)

Cleaning job freeze during cleaning JPA projects ------------------------------------------------ Key: JBIDE-9224 URL: https://issues.jboss.org/browse/JBIDE-9224 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Environment: JBT 3.3.0.m2, L64 Reporter: Jiri Peterka Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: clean-jpa-project-freeze.txt Probably rare issue, see thread-dump -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9222) JPA: GenericGenerator composite doesn't update when switch between classes

by Dmitry Geraskov (JIRA)

JPA: GenericGenerator composite doesn't update when switch between classes -------------------------------------------------------------------------- Key: JBIDE-9222 URL: https://issues.jboss.org/browse/JBIDE-9222 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M2, 3.3.0.M3 Test case: 1. Create 2 entities - one with GenericGenerator (Entity1), another without it(Entity2) 2. Set cursor in source code near public class Entity1.. 3. Open JPA Details view, go to GenericGenerator composite 4. Swithc to Entity2 FAILURE: Composite is not updated -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8669) Dot character is not supported in DB schema name in Hibernate Configuration

by Boris Na (JIRA)

Dot character is not supported in DB schema name in Hibernate Configuration --------------------------------------------------------------------------- Key: JBIDE-8669 URL: https://issues.jboss.org/browse/JBIDE-8669 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: LATER Environment: Hibernate tools version is 3.4.0.v20110215-1252-H31-GA (by the way it's not listed in the Jira version menu) Win XP Eclipse Helios Service Release 1 WTP 3.2.3 Dali 2.3.3 MySQL 5.5.9 Reporter: Boris Na Assignee: Max Rydahl Andersen Priority: Minor 1/ Create a schema on MySQL called: myschema.domain 2/ Create a JPA project 3/ Create an entity called myEntity 4/ Create The corresponding Table (via generated script) 5/ Configure Data Source Explorer to the connection => This works well 6/ Configure Hibernate explorer (using above connection) 7/ Try to open the Database part of this view => you get an SQL exception: org.hibernate.exception.SQLGrammarException: Could not get list of suggested identity strategies from database. Probably a JDBC driver problem. (...) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.DOMAIN like 'myentity'' at line 1 (...) Hint: I just checked the SQL query (via MySQL proxy) and it lacks `` around the schema name in one query: show table status from MYSCHEMA.DOMAIN like 'myentity' Just replace dot by underscore and everything works well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9250) jspx, tagx file should be opened using xhtml editor

by Maxim Areshkau (JIRA)

jspx, tagx file should be opened using xhtml editor --------------------------------------------------- Key: JBIDE-9250 URL: https://issues.jboss.org/browse/JBIDE-9250 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov jspx, tagx files have xml syntext and should be opened using xhtml editor. Because #1)in this files possible using el expresions in text; #2) when we drop items from pallete, taglibs registered incorrectyly JBIDE-9237 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9092) Wrong attribute name proposals appear in CA Window for CSS styles inside <style></style> tag

by Victor Rubezhny (JIRA)

Wrong attribute name proposals appear in CA Window for CSS styles inside <style></style> tag -------------------------------------------------------------------------------------------- Key: JBIDE-9092 URL: https://issues.jboss.org/browse/JBIDE-9092 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Environment: Eclipse 3.7, WTP 3.3 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.3.0.M3 Wrong tag attribute name proposals appear in CA Window for CSS styles inside <style></style> tag when: 1. There is at least one whitespace character is placed between opening and closing "style" tags and 2. The CA is invoked when the cursor is pointed right after the opening tag (i.e. "<style type="text/css">| </style>", where "|"-char indicates the cursor position. In such cases WTP suggests proposals for a tag attribute name insertion, as well as CSS proposals. Probably it's WTP's issue, because: 1. WTP decides which kind of proposals are to be calculated at some cursor position. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9051) Tooling shows errors if the view-id parameter in a restrict tag contains a hashtag or Seam EL and no '?' (query param delimiter)

by Ian Hands (JIRA)

Tooling shows errors if the view-id parameter in a restrict tag contains a hashtag or Seam EL and no '?' (query param delimiter) -------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9051 URL: https://issues.jboss.org/browse/JBIDE-9051 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Environment: RHEL6, Eclipse 3.6, Current release of JBoss tools Also noticed error in JBDS 4.x Reporter: Ian Hands Assignee: Alexey Kazakov Priority: Minor I see that the IDE detects errors if I have a URL in a view-id attribute that has a hastag or Seam EL, and does not have any query parameters. example: <exception class="org.jboss.seam.security.AuthorizationException" log-level="trace"> <http-error error-code="403"/> <redirect view-id="/403.xhtml#{restrictHelper.hashTag}"/> </exception> A work around would be to simply use: <redirect view-id="/403.xhtml?#{restrictHelper.hashTag}"/> This is still a valid URL, and does not cause the tooling to show errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
8
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 2011