Geertjan's Blog

  • May 4, 2008

RichFaces for NetBeans IDE 6.1 (Part 2)

Geertjan Wielenga
Product Manager
In the comments to my announcement about RichFaces in NetBeans IDE 6.1, yesterday, someone asked for tag completion. Well, that's already possible automatically when you install the plugin I mentioned yesterday. Since the libraries are on the classpath and the necessary declarations are generated right into the JSP page, you can immediately use tag completion (Ctrl-Space) in the generated page, as well as in any other JSP page where you add the declarations, which will result in you getting documentation as well as tag completion:

Also, you can use code completion to access managed beans...

...as well as their content:

Secondly, I created the start of a RichFaces palette, which you can get here:


Currently only two code snippets for RichFaces are in the palette (Aristotle Onassis and Donald Trump, haha) representing a RichFaces calendar and a RichFaces ComboBox. The tooltip shows exactly what will be generated when you drag/drop the item into the JSP page:

I am no RichFaces expert (having only heard of it the first time 2 days ago), so please tell me what else to add, any code snippets that you think are essential in this context, just leave a message at the end of this blog entry and I will extend the palette. Also, note that you can manually add your own snippets to the RichFaces palette, if you follow the instructions on the abovementioned plugins page.

Join the discussion

Comments ( 16 )
  • Wouter van Reeven Sunday, May 4, 2008

    Hey Geertjan,

    This is great. As I already sent you via email, these things would be nice to have:

    - automatic addition of taglib declarations when creating a new JSP or Facelets page

    - all RichFaces and Ajax4Jsf tags in the Component Palette

    - Visual Web support

    Let's have a chat on how to achieve this during JavaOne.

    Greets, Wouter

  • finc Sunday, May 4, 2008


    but rich:comboBox doesn't exist and calendar isn't valid :)

    Rich Faces support is better with facelets.

  • Geertjan Sunday, May 4, 2008

    What do you mean, finc? Both work fine, both come from the RichFaces taglibs. So, please explain. Also, please tell me what would be better to add. Again, I am new to this, only providing the tools, and am dependent on people like you telling me what should be made available.

  • Daoud AbdelMonem Faleh Sunday, May 4, 2008

    Hey Geertjan,

    Am a regular of your blog even thought this is the first time I post a comment here. Well this time is that the entry is relevant to my interest area (jboss stuff with netbeans).

    RichFaces support in Netbeans is very welcome. Now what personally I would like to see is a Facelets support in Netbeans 6.1 since it would be nice step toward Seam support without the tedious extra work to get it setup. Visual Web project (along with wizards) for those frameworks would be great).

    One last thing, support for exploded archives (war files) so that any modification to a jsp file in the editor can be reflected to the server without redeploy (this work under Tomcat and JBoss AFAIK).

    Keep on the good work :)

  • David Sunday, May 4, 2008

    Hi Geertjan,

    Excellent plugin. Is there anyway that this could work on a Free-Form project so it could work with seamgen generated projects? Failing that support for Facelets would be an excellent plugin to aid Seam development.


  • finc Sunday, May 4, 2008

    to Geertjan:

    Sorry, I have own library "RichFaces", which is in version 3.1.4 (3.2.0 cannot use because this version have important bugs).

    Your plugin wants create library with name: RichFaces, which I have :)

    to David:

    When you use facelets plugin, you can checkout cvs project from https://nbfaceletssupport.dev.java.net/

    and build & create \*.nbms against Netbeans Platform 6.1. Now, you can load this plugins to Netbeans 6.1 ;)

  • Daoud AbdelMonem Faleh Monday, May 5, 2008

    Hey Finc,

    The 3.2.0SR is a bug fix release for the 3.2.0. It's very stable and usable. Geertjan plugin bundle this library, it's a library wrapper plugin, you can continue to use your own or simply rename it :). What's great about this plugin is the palette one. What I'd love to see about this one is an integration with visual web project.

    Thx for your tip about the facelets plugin :), I've never thought it would build against 6.1, since now I can't dare the time going in a troubles shooting process for my IDE.

    Well thought things will be easier when the Web Bean jsr will be adopted in the upcoming JEE6. We will get jsf 2.0 with it's templating facility ala facelets + jsftemplating, web beans ala Seam, ejb lite, ejb 3.1, that would be a great release!


    Daoud AbdelMonem Faleh

  • Thomas Zillinger Monday, May 5, 2008

    can you create a link to http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html_single/index.html

    in the popup? or even a direct link to each component in the page?

  • Thomas Zillinger Monday, May 5, 2008

    Maybe you could even use links to the live demo: https://www.redhat.com/apps/WebForm/richfaces_demo.html Maybe you could also use icons for each component as they are used in the component tree of the demo

  • finc Monday, May 5, 2008

    to Daoud AbdelMonem Faleh: It's true, but in this version is bug still (about utf-8 request in ajax).

    This bug will by repair in 3.2.1 :(

    New features Java EE 6 are very good, but now I must develop apps and I can use only JSF 1.2. I use Seam because this framework doing things right :)

  • Sean Connolly Friday, May 9, 2008

    Hi Geertjan,

    Great work, the plugin looks great. However, are you worried at all about having duplicate jars included in projects? If you open a JSF 1.2 project in NetBeans 6.1, it includes the 'JSF 1.2' library by default. Looking in the Libraries menu, you can see that 'JSF 1.2' includes not only jsf-api.jar and jsf-impl.jar (which define all of JSF 1.2), but also the Apache Commons jars (commons-beanutils.jar, commons-collections.jar, commons-digester.jar, and commons-logging.jar).

    At first glance it would seem clear that we just need to leave the commons-\*.jars out of the RichFaces plugin; but I'm sure you noticed as I did that the commons-\*.jars included in the 'JSF 1.2' library are quite different than those needed to run RichFaces.

    I've had a lot of trouble getting the NetBeans plugins OUT cleanly and am just curious what your thoughts on the situation are.

    Keep up the good work,


  • John Doe Tuesday, May 20, 2008

    Long article

  • Joe Ersinghaus Friday, May 30, 2008

    Hi Geertjan,

    David, in a previous comment, asked if this plugin could be added to a free-form seam gen project but I apologize, I did not understand your response to him.

    Could you show me what steps are necessary to add the plugin to this type of project? It seems like your instructions were the general method of building the nbm for use in a web based application and not for a free-form.



  • Geertjan Friday, May 30, 2008

    I have no idea how it would work with a freeform project, Joe, sorry. I'm not very familiar with that project type, myself.

  • david Monday, June 23, 2008

    Never mind support for the visual editor right now... how can I simply avoid the component error?

  • Hung Nguyen Sunday, May 8, 2011
    thanks, but in my palette, the components is *.xml, so i can not drag and drop it. how can i solved this?
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.