Error after renaming Seam-ejb project
-------------------------------------
Key: JBIDE-2435
URL: http://jira.jboss.com/jira/browse/JBIDE-2435
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 2.1.2
Reporter: Anton Klimkovich
Priority: Minor
EXECUTE: Create Seam Ear web project
EXECUTE: In Package Explorer right mouse click on seam-ejb project and select refactor->rename
EXECUTE: Input another name and press Ok button (For example from seam-ejb to newseam-ejb)
FAILURE: Could not delete launch configuration for: {project name}
May be this issue related to JBIDE-2250
--
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
Invalid thread access exception is occured after set new connection on JPA Facet wizard while creating new seam web project.
----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2398
URL: http://jira.jboss.com/jira/browse/JBIDE-2398
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Reporter: Anton Klimkovich
Attachments: exception.txt
EXECUTE: Open New Seam Project wizard
EXECUTE: Press Modify button near Configuration field
EXECUTE: Set checkbox on Java Persistence and press ok button
EXECUTE: Press Next button on New Seam Project wizard
EXECUTE: Click on "Add connection" link on JPA Facet wizard
EXECUTE: Select HSQLDB from proposal list
EXECUTE: Press Next button and Finish button
FAILURE: Invalid thread access exception is occured
--
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
TestNG fails for action in Seam 2.0.x web project when server is running.
-------------------------------------------------------------------------
Key: JBIDE-2454
URL: http://jira.jboss.com/jira/browse/JBIDE-2454
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.1.2
Reporter: Anton Klimkovich
EXECUTE: Create Seam 2.0.x web project (War or Ear)
EXECUTE: Create Action
EXECUTE: Run the project on the JBOss AS
EXECUTE: Run TestNG for ActionTest.xml
FAILURE: TestNG failed.
Log attached.
TestNG works for action created in Seam 1.2.x web project.
--
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
Some bugs for <rich:progressBar> component representation in VPE.
-----------------------------------------------------------------
Key: JBIDE-2405
URL: http://jira.jboss.com/jira/browse/JBIDE-2405
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 3.0.0.alpha
Environment: Version: 1.1.0
Build id: 200806190155-nightly
Reporter: Andrei Scherbovich
Assigned To: Eugene Stherbin
Priority: Minor
1) "lable" attribute doesn't work in VPE
2) displaying information on progress bar with help of <h:outputText> nested component doesn't work
SEE TEST FILE ATTACHED. Picture in VPE should be the same as in browser.
--
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
Strange place of hibetnate buttons
-----------------------------------
Key: JBIDE-2270
URL: http://jira.jboss.com/jira/browse/JBIDE-2270
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Reporter: Krasimir Goutcev
Attachments: pic.jpg
Why the button for execute of HQL and for clear HQL Editor are on сsuch different places? (see picture)
I suggest they stay in one toolbar.
--
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