Board index PrimeFaces Core Feedback for NetBeans

Feedback for NetBeans

Components, Ajax Framework, Utilities and More.

Post 17 Oct 2012, 21:55
kukeltje Expert Member

Posts: 3277
Location: Netherlands
Productivity is (imo)
- Code completion (css, attributes, EL, CDI beans, entities, jsf/facelets)
- Validation (css, attributes, CDI beans, entities jsf/facelets)
- Code navigation (ctrl-click)
- Hot deployment on a running server
- etc..

That is something that happens day in day out. Generating crud apps based on a database is nice, but having the entities generated, and maybe some controller is more then enough. The UI stuff is most of the time not what you want and changing things is almost as much work as starting from scratch.

Keeping an IDE up to date with the often improving and chaning components AND having al of the above IN the graphical design part is SOOOO difficult that it is not worth the effort of at least the Primefaces Team. (Not even JBoss has a full graphical IDE for their richfaces components afaik and not sure about Oracle.)
Ronald van Kuijk
______________________________
PrimeFaces 3.5.3 | Jboss 7.2.0 | Mojarra 2.1.18
Fedora 16, Firefox 20.0
Read the forum posting rules

Post 17 Oct 2012, 23:12

Posts: 14315
Location: Cybertron

Visual editor is only good to sell the product to managers.
PrimeFaces Lead

Post 18 Oct 2012, 00:48

Posts: 84
Location: Mexico
I hope you will agree with me that the support for Expression Language in JSF must be improved. Here are the problems I encountered:

Expression Language code completion feature in Netbeans for JSF always suggest parameters for method expressions (or empty parentheses if the method has zero paremeters).
For example, If I have a class called Bean and a method with signature public List suggest(String s) then Netbeans complete the EL like #{bean.suggest(s)}

As you can see, I have to remove the parentheses and the suggested parameters because if I dont then the code will not run.
In the previous example, i have to edit the code to #{bean.suggest}

But when I remove it, then I have two problems:
· Code navigation (Ctrl + click on the method expression) will not navigate to the source code
· Method Refactoring in source code will not apply in the method expressions

Does anyone has the same problem?
PrimeFaces 3.4 SNAPSHOT | GlassFish 3.1.2.2 | Mojarra 2.1.6 | NetBeans 7.2

Post 18 Oct 2012, 09:44
andyba User avatar
Expert Member

Posts: 1471
Location: Steinfeld, near Bremen/Osnabrück, DE

arturo wrote:
I hope you will agree with me that the support for Expression Language in JSF must be improved. Here are the problems I encountered:

Expression Language code completion feature in Netbeans for JSF always suggest parameters for method expressions (or empty parentheses if the method has zero paremeters).
For example, If I have a class called Bean and a method with signature public List suggest(String s) then Netbeans complete the EL like #{bean.suggest(s)}

As you can see, I have to remove the parentheses and the suggested parameters because if I dont then the code will not run.
In the previous example, i have to edit the code to #{bean.suggest}

But when I remove it, then I have two problems:
· Code navigation (Ctrl + click on the method expression) will not navigate to the source code
· Method Refactoring in source code will not apply in the method expressions

Does anyone has the same problem?

These are issues to do with NetBeans itself and has nothing to do with PrimeFaces support in NetBeans.
PF 3.0.1, PF 3.1, PF 3.2, PF 3.3, PF 3.4.1, PF 3.4.2, PF 3.5
Glassfish 3.1.2.2, Mojarra 2.x, under both Java 6 and Java 7.
If you haven't read the forum rules read them now
My blog: http://onthefaceofthings.blogspot.de/
PrimeFaces Project

Post 18 Oct 2012, 09:49

Posts: 14315
Location: Cybertron

NetBeans Team is very friendly and always look for ways to improve the tooling in NetBeans. Try posting this in NetBeans tracker and let's see their response. They are watching this post as well.
PrimeFaces Lead

Previous

Return to PrimeFaces Core