[JBoss JIRA] Created: (JBIDE-2371) More than one element can be highlighted during CA working
by Tatyana Romanovich (JIRA)
More than one element can be highlighted during CA working
----------------------------------------------------------
Key: JBIDE-2371
URL: http://jira.jboss.com/jira/browse/JBIDE-2371
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
Priority: Minor
EXECUTE: Open JSF file (use JSF KickStart Project, open inputUserName.jsp) in the VPE
EXECUTE: Press and hold Ctrl key, move mouse over the #{Message.header}, then #{Message.prompt_message}, then #{user.name}
FAILURE: All elements are highlighted
EXECUTE: Hold Ctrl key and click on the #{Message.header} expression
ASSERT: CA works correctly
EXECUTE: Switch to the VPE and verify selected before expressions
FAILURE: they are highlighted still
--
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 months
[JBoss JIRA] Created: (JBIDE-2399) Validation of ESB files for specific SOA-P versions
by John Graham (JIRA)
Validation of ESB files for specific SOA-P versions
---------------------------------------------------
Key: JBIDE-2399
URL: http://jira.jboss.com/jira/browse/JBIDE-2399
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: John Graham
Assigned To: John Graham
Given that the SOA-P run time will change from release to release, we need some generic way of validating ESB files in Eclipse projects for specific run time versions. This might be done at the package level (that is, when creating a deployment package), but ideally would be done "live:" as the user makes changes, warnings/errors would appear in the Eclipse Problems view. To accomplish this, we would need to set a (minimum? probably not, because backward compatibility is not supported) "SOA-P run time level" (like the JVM level) and have a validation model for checking. The idea is to avoid simple compatibility errors appearing at run time where they could have been noticed at design time.
(This is related to, but larger than, the ESB reference tracking work.)
--
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, 7 months