Comments on: Using the Sun Java BluePrints AJAX JSF Components in your own JSF Web Application

By: Kedar Mhatre

Kedar Mhatre — Sat, 21 Mar 2009 07:05:00 +0000

My Jdeveloper version is 11g TP4 (5188 build)

By: Kedar Mhatre

Kedar Mhatre — Sat, 21 Mar 2009 07:02:40 +0000

Lucas, bpcatalog-ee5-ea-0.8-installer.jar is for Java EE 5 and JSF 2.1 compliant. Lib folder contains bp-ui-14.jar which for older version. When I use these jars in JDeveloper 11g (ADF BC RC) it fails with Illegal state exception.
Have you worked with this application on 11g?

By: Neeraja

Neeraja — Tue, 28 Aug 2007 12:48:01 +0000

hi,
In my application,I want a pop-up calendar.
For that I downloaded AJAX JSF Components – along with the entire Blueprints Catalog.
I placed these under WEB-INF/lib folder of my project.
and I rebuild the project.But I am getting the error like

Error(342): Unable to instantiate tag: ui:popupCalendar (class: com.sun.j2ee.blueprints.ui.popupcalendar.PopupCalendarTag) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.
Error(342): Unable to find class for bean: null defined by tag with class: com.sun.j2ee.blueprints.ui.popupcalendar.PopupCalendarTag

but the bp-ui-14.jar(for the class PopupCalendarTag.class) is there under WEB-INF/lib folder.
what is the solution to my problem.
Can anyone pls suggest me the solution

By: K

Wed, 18 Apr 2007 14:37:34 +0000

Yeah, after looking into it a bit more, I also narrowed it down to the render kit. It seems that once you place a component that requires the render kit (ie, just about anything), your BluePrint (or other library) ceases to function. Looking at the rendered HTML, I can see that the scripts that BluePrint relies on are no longer included, so someone must be overriding their inclusion (for whatever reason). Disappointing is, I think, a very mild way of putting it. Standardization really needs to be worked out to avoid this type of frustration. Thanks for your reply and information!

By: Lucas

Lucas — Wed, 18 Apr 2007 11:24:18 +0000

K: you most certainly have a point. I have recently done a lot of investigation into various JSF implementations and I was very disappointed at the lack of interoperability. Very few implementations can actually work together. For example ICEFaces, Backbase, ADF Faces and Trinidad are all mutually exclusive. MyFaces Tomahawk on the other hand can be used in conjunction with many other implementations, at least ADF Faces and Trinidad. I had no luck so far mixing ADF Faces with the SUN Java BluePrint JSF Components – so that is not good news – although I am not ready to give up yet. I have not done an extensive analysis of the issues. Using Project Woodstock together with ADF Faces also seems to be a problem. I have not yet tried the JBoss Rich Ajax components. I did try RichFaces, without success. I cannot say for sure where the issues stem from. One issue is that some JSF implementations require their very own render kit and these requirements clash.

By: K

Tue, 17 Apr 2007 21:37:09 +0000

Very handy….except…

If you try using these components on a page with an “af:panelPage,” they stop working. I’m fairly new to ADF, so I wouldn’t be surprised if there’s a good reason for this, but, since I know of no such “good reason,” I have to say: unless there’s a way to work around this, the functionality of these components seems rather limited.

If I’m wrong, then, please, correct me. I’d love to make use of this functionality, but would also like the layout ease provided by “panelPage.”

By: sebnoumea

sebnoumea — Sat, 14 Apr 2007 03:07:38 +0000

Hi Lucas,

Could you provide the resources please ?

Thanks,
Seb.