- This topic has 11 replies, 5 voices, and was last updated 11 years, 5 months ago by
.
-
Posts
-
JSF 2.0 validation is much improved in version 9, but there are still some problems.
One of these problems is that MyEclipse does not recognize method calls as valid in EL. For instance
<h:someTag value=”#{somemethod(param1, param2)}” />
will be flaged with a warning as being invalid EL.
JeffreyGetzin,
I have escalated your post to dev team members. They would get back to you on this.
Sorry for the inconvenience.
Joy,
I’m more concerned that it’s been a full month since I posted this issue. The bug itself not a show-stopper issue, but MyEclipse support has been very sluggish in responding to issues. Perhaps you need more staff?
Jeff
JeffreyGetzin,
We apologize for not acknowledging your post earlier. The issue has been long filed as a PR and you can expect to see the fix in the coming build.
Sorry for the delay.We will make sure to be more prompt next time on.
Thank you for the patience.This is still not working in v10 – it’s been 18 months, what gives?! This is a show stopper for my project.
twinfeats,
I could not replicate the issue at my end on MyEclipse 10.6.
Could you provide below details to help us investigate further –
1. Open MyEclipse IDE, from menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here.
2. If you are not on MyEclipse 10.6, then please update to 10.6 version. If you can still replicate the issue on MyEclipse 10.6 then please attach the screenshot of the error.Yes, I’m on 1.6. Here is a simple test managed bean:
package com.retalix.powerplus.jsf;
import javax.faces.bean.ApplicationScoped;
import javax.faces.bean.ManagedBean;@ManagedBean
@ApplicationScoped
public class SecurityBean {
public String getAValueWithParm(String name) {
return name;
}public String getAValue() {
return “”;
}
}Attached is a screenshot of a test xhtml showing the available auto-complete choices for this bean. AValue is listed but AValueWithParm is not. Additionally, if I start typing get to see if it then detects the method, I still get no results.
twinfeats,
1) Can you switch to a new workspace, create a new project with sample code and check if you can replicate the issue ? It might also be a workspace/cache issue.
2) If you can still replicate the issue, can you please attach the sample project which replicates this issue to help us investigate further ?
Attached is the requested new sample project taken from a new, clean workspace. Problem still exists in this sample.
twinfeats,
It seems to be an issue with getter property. If there is no parameter for the getter property, then the autocomplete works.
Can you please recheck if the parameter is supported for getter property ?
You can cross post to development supported forums for better support.
