[
http://jira.jboss.com/jira/browse/JBIDE-1187?page=comments#action_12385767 ]
Victor Rubezhny commented on JBIDE-1187:
----------------------------------------
As I see the initial problem is gone and now in my project I don't see any messages on
EL expressions like #{xxxHome.instance} .
Many warnings are gone from the Problems View for my test project, but few of them still
exist.
While I'd looking deep into testEntityHome.instance staff I saw that the class looks
like the following:
public class testEntityHome extends EntityHome<testEntity>...
While EntityHome is parameterized with testEntity type we're getting objects of type
testEntity by calling the getinstance() method (or by accessing the
testEntityHome.instance property). Now It works fine and I can see its (of type
testEntity) properties and methods.
But in the page testEntityList I see the EL expressions like
"#{testEntity.name}" which use the "testEntity" directly and I see
the same warnings as they was before for testEntityHome.instance:
Severity and Description Path Resource Location Creation Time Id
testEntity cannot be
resolved test/WebContent testEntityList.xhtml L/test/WebContent/testEntityList.xhtml 1194015090421 86
I investigated that there is no Seam Project variable in my project for testEntity.
Is it normal?
Properties from superclass of a library class not recognized by
autocomplete, validator or F3
---------------------------------------------------------------------------------------------
Key: JBIDE-1187
URL:
http://jira.jboss.com/jira/browse/JBIDE-1187
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Reporter: Gavin King
Assigned To: Victor Rubezhny
Priority: Critical
Fix For: 2.0.0.CR1
To reproduce, run "Seam Generate Entities", and look at the XxxxEdit pages.
EL expressions like #{xxxHome.instance} are flagged with a warning when they should not
be.
Well, XxxxHome properties are recognized, as are EntityHome properties, but Home
properties are not recognized.
It seems to be a prob that properties on superclasses of binary classes are not detected.
--
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