Seam validation issues

[pdhaigh]

Hi,

I am using JBDS v2.

The Seam support is great, but there seem to be a reasonable number of flaws in the validation. To list a few:

ERROR: Duplicate variable name when using @DataModel and @Factory:

@DataModel
public ArrayList bookingsForApproval;

@Factory("bookingsForApproval")
public void findBookingsForApproval()
{
bookingsForApproval = new ArrayList(forApprovalBookings.getResultList());
}

WARNING: "0" cannot be resolved in #{featuredFeedback.resultList[0]}

WARNING: components declared in components.xml cannot be resolved. This includes entityManager (i.e. @In EntityManager entityManager gives a warning), identity and a number of central components, as well as user-specified components.

WARNING: pages.xml validation
#{s:hasRole('blah'} gives 2 warnings, one that s cannot be resolved and another that hasRole can't be resolved
All actions such as: #{webpageHome.setId(15)} give validation warnings - seems it doesn't like method expressions.

The project runs fine ignoring these errors, but it's irritating that genuine problems can be masked by these.

Any chance of fixes?

[akazakov]

It seems you are using some early JBDS 2. Some beta or even alpha. Please update it to JBDS 2.0 GA (or JBoss Tools 3.0 GA). We have fixed all these bugs there.

[pdhaigh]

Hi,

I am definately using the GA:

JBoss Developer Studio
Version: 2.0.0.GA
Build id: R200903141247-H4
Build date: 200903141316

And the version of JBoss Tools update site is:

JBoss Tools 3.0.0.GA-R200903141626-H5

The Seam bit is:

Seam Tools for Eclipse

Version: 3.0.0.GA-R200903141626-H5

any suggestions gratefully received..

[akazakov]

Hm... I can't reproduce it in GA and I remeber these bugs in some beta...
Have you updated your JBDS from beta?

[pdhaigh]

Nope, clean install.

Same workbench folder as I had with JBDS v1 - can that have impact?

[akazakov]

It could... Have tried clean/build all your projects?

[pdhaigh]

Yes, cleaned several times..

[akazakov]

Could you create new Seam project and copy the problematic code there? Is the issue still reproducable there? If so could you report it to jira and attache that project.

[pdhaigh]

That seemed ok - deleting all of the Eclipse meta files from my project (including .project) and then recreating the project seems to have resolved the issue.

Thanks for your help.

[akazakov]

Eclipse WTP seemed not to removed old problem markers from old workspace... We changed marker IDs for Seam problem. It could be a reason. But anyway WTP should have removed them...