2:09 p.m.
Alexey Kazakov created JBIDE-10872:
--------------------------------------
Summary: EL incremental validation doesn't work for complex ELs.
Key: JBIDE-10872
URL: https://issues.jboss.org/browse/JBIDE-10872
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:45 p.m.
[
https://issues.jboss.org/browse/JBIDE-10872?page=com.atlassian.jira.plugi...
]
Alexey Kazakov updated JBIDE-10872:
-----------------------------------
Description:
1. Create Seam 2 project.
2. Add the following classes to the project:
{code}
@Name("comp")
public class Authenticator {
public Test getTest() {
return new Test();
}
}
{code}
{code}
public class Test {
public Test2 getString() {
return "";
}
}
{code}
{code}
public class Test2 {
public String getOldString() {
return "";
}
}
{code}
3. Open home.xhtml
4. Add #{comp.test.string.oldString} there
5. Rename getOldString() to getNewString() in Test2.java (Don't use refactoring
dialog!). Save the file.
6. FAILURE: #{comp.test.string.oldString} does NOT have a problem marker -
'oldString' can't be resolved.
7. Make any changes in home.html to re-validate the file.
8. ASSERT: #{comp.test.string.oldString} does have a problem marker - 'oldString'
can't be resolved.
9. Rename getNewString() back to getOldString() in Test2.java (don't use refactoring
dialog). Save the file.
10. FAILURE: #{comp.test.string.oldString} still has a problem marker but it should not.
EL incremental validation doesn't work for complex ELs.
-------------------------------------------------------
Key: JBIDE-10872
URL: https://issues.jboss.org/browse/JBIDE-10872
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
1. Create Seam 2 project.
2. Add the following classes to the project:
{code}
@Name("comp")
public class Authenticator {
public Test getTest() {
return new Test();
}
}
{code}
{code}
public class Test {
public Test2 getString() {
return "";
}
}
{code}
{code}
public class Test2 {
public String getOldString() {
return "";
}
}
{code}
3. Open home.xhtml
4. Add #{comp.test.string.oldString} there
5. Rename getOldString() to getNewString() in Test2.java (Don't use refactoring
dialog!). Save the file.
6. FAILURE: #{comp.test.string.oldString} does NOT have a problem marker -
'oldString' can't be resolved.
7. Make any changes in home.html to re-validate the file.
8. ASSERT: #{comp.test.string.oldString} does have a problem marker - 'oldString'
can't be resolved.
9. Rename getNewString() back to getOldString() in Test2.java (don't use refactoring
dialog). Save the file.
10. FAILURE: #{comp.test.string.oldString} still has a problem marker but it should not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-10872?page=com.atlassian.jira.plugi...
]
Daniel Azarov resolved JBIDE-10872.
-----------------------------------
Assignee: Alexey Kazakov (was: Daniel Azarov)
Resolution: Done
verified
EL incremental validation doesn't work for complex ELs.
-------------------------------------------------------
Key: JBIDE-10872
URL: https://issues.jboss.org/browse/JBIDE-10872
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
1. Create Seam 2 project.
2. Add the following classes to the project:
{code}
@Name("comp")
public class Authenticator {
public Test getTest() {
return new Test();
}
}
{code}
{code}
public class Test {
public Test2 getString() {
return "";
}
}
{code}
{code}
public class Test2 {
public String getOldString() {
return "";
}
}
{code}
3. Open home.xhtml
4. Add #{comp.test.string.oldString} there
5. Rename getOldString() to getNewString() in Test2.java (Don't use refactoring
dialog!). Save the file.
6. FAILURE: #{comp.test.string.oldString} does NOT have a problem marker -
'oldString' can't be resolved.
7. Make any changes in home.html to re-validate the file.
8. ASSERT: #{comp.test.string.oldString} does have a problem marker - 'oldString'
can't be resolved.
9. Rename getNewString() back to getOldString() in Test2.java (don't use refactoring
dialog). Save the file.
10. FAILURE: #{comp.test.string.oldString} still has a problem marker but it should not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-10872?page=com.atlassian.jira.plugi...
]
Vlado Pakan closed JBIDE-10872.
-------------------------------
Verified on jbdevstudio-product-eap-linux-gtk-5.0.0.v201202250031M-H77-Beta1.
EL incremental validation doesn't work for complex ELs.
-------------------------------------------------------
Key: JBIDE-10872
URL: https://issues.jboss.org/browse/JBIDE-10872
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
1. Create Seam 2 project.
2. Add the following classes to the project:
{code}
@Name("comp")
public class Authenticator {
public Test getTest() {
return new Test();
}
}
{code}
{code}
public class Test {
public Test2 getString() {
return "";
}
}
{code}
{code}
public class Test2 {
public String getOldString() {
return "";
}
}
{code}
3. Open home.xhtml
4. Add #{comp.test.string.oldString} there
5. Rename getOldString() to getNewString() in Test2.java (Don't use refactoring
dialog!). Save the file.
6. FAILURE: #{comp.test.string.oldString} does NOT have a problem marker -
'oldString' can't be resolved.
7. Make any changes in home.html to re-validate the file.
8. ASSERT: #{comp.test.string.oldString} does have a problem marker - 'oldString'
can't be resolved.
9. Rename getNewString() back to getOldString() in Test2.java (don't use refactoring
dialog). Save the file.
10. FAILURE: #{comp.test.string.oldString} still has a problem marker but it should not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4637
days inactive
4654
days old
jbosstools-issues@lists.jboss.org
3 comments
3 participants
participants (3)
-
Alexey Kazakov (JIRA) -
Daniel Azarov (JIRA)
-
Vlado Pakan (JIRA)