[
http://jira.jboss.com/jira/browse/JBIDE-903?page=all ]
Aliaksey Nis reopened JBIDE-903:
--------------------------------
Reopened.
In JSF 1.1.02
1. Create KickStart without libs
2. Open faces-config
3. Find </managed-beans>, set cursor after this
*. Press ctrl+space - all work
4. Delete ">" symbol.
5. Save file (ctrl+s or from Main menu)
6. Write ">" symbol back
7. Press Enter after </managed-beans>
*. Press ctrl+space - all work
8. Save and Exit (via pressing X button)
9. Open faces-config again, set cursor at empty line created in 7.
Press ctrl+space - no CA at all, and exception fall each time u press CA.
In JSF 1.2
1. Create KickStart without libs
2. Open faces-config
3. Find </managed-beans>, set cursor after this
Press ctrl+space - no content assist. (JBIDE-844)
4. Delete ">" symbol.
5. Save file (ctrl+s or from Main menu)
6. Write ">" symbol back
7. Press Enter after </managed-beans>
Press ctrl+space - all work now
8. Save and Exit (via pressing X button)
9. Open faces-config again, set cursor at empty line created in 7.
Press ctrl+space - no CA at all, and exception fall each time u press CA.
Log attached - ModelError.txt
Proposal list is empty for faces-config.xml form based editor on
source tab
---------------------------------------------------------------------------
Key: JBIDE-903
URL:
http://jira.jboss.com/jira/browse/JBIDE-903
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.Beta3
Environment: Windows XP Professional
Reporter: Denis Golovin
Assigned To: Viacheslav Kabanovich
Fix For: 2.0.0.Beta4
1. EXECUTE: Create JSF KikStart project.
2. ASSERT: Check that JSF project with given parameters appears in resources tree
3. EXECUTE: Open WebContent/WEB-INF/faces-config.xml in created project
4. ASSERT: Editor opened on Tree tab
5. EXECUTE: Switch to source tab
6. EXECUTE: Put cursor inside <managed-bean> element and press Ctrl+Space
7. ASSERT: Content proposals list shows children nodes allowed for managed-bean element
FAILURE: Proposal list shows only XML templates
--
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