- This topic has 3 replies, 3 voices, and was last updated 17 years, 11 months ago by
.
-
Posts
-
I greatly appreciate the support for JSF EL in 5.0 where one can autocomplete properties of managed beans. One obvious thing I’m missing however is the ability to navigate to the managed bean’s declaration.
The exact functionality I’m looking for would be like the Java editor’s Navigate -> Open Declaration, for which the default key bindings are F3 or ctrl-left mouse. What I would expect is that the first navigate action would take me to the bean’s declaration in the faces-config file and the navigate action after that to the corresponding class definition.
This first action is not available at all, while for the second action there’s a workaround; namely right clicking on the managed bean’s name in the outline of the faces-config file. I would actually much more prefer to be able to directly ctrl-click on either the managed-bean-name or managed-bean-class attributes in the XML source.
To be able to implement the mentioned autocompletion in a JSF page, you must already know of both of these places, so offering a navigate option to the user would probably not have to be that difficult in terms of raw coding.
Arjan,
Thank you for the feedback, the 2nd issue shouldn’t be hard to clear up, and the EL parsing should be improved in the 6.0 release quite a bit.I would really like to see this implemented too.
Currently we have a group of people working with us who are not really that technical. They need to make minor adjustments to JSF pages. If they see something like #{someBean.foo}, they have absolutely no idea where to start looking for “someBean”.
If “someBean” would be navigatable to its xml declaration and java source, this would be a real life saver for us. 🙂
Is there and confirmation that this feature would be in 6.0? Is there any timeframe for when 6.0 will be released (I checked your roadmap, but its a bit out of date).
