Twitter got me

Title says it all, twitter finally got me.

http://twitter.com/cagataycivici

JSF-Spring-JPA-Security

I’ve written various articles about how to integrate JSF-Spring-JPA-SpringSecurity before which is based on JSF centric annotation based approach, the latest example I’ve created introduces PrimeFaces to provide rich client features to the stack. Application’s name is moviecollector and deployed online at here live for a test run.

MovieCollector demonstrates several uses cases of PrimeFaces components like Partial Page Rendering, Excel-PDF data exporter, datatable, autoComplete, dialog and more. Code is also available on subversion repository of PrimeFaces so it’d be a good reference if you need an example application for this stack.

I’ll be adding more use cases to the project in time probably after getting PrimeFaces 0.9.0 ready which will include flash based file upload, drag&drop, file download and more stuff.

PrimeFaces 0.8.3 is ready

PrimeFaces team is proud to announce that UI Components 0.8.3 is released, this release is mainly for maintenance. See the change log at http://primefaces.prime.com.tr/en/changelog. We’ve upgraded the YUI version 2.7.0 and added various bug fixes.

This is the last release of the 0.8.x line, next version would be 0.9.0 and many new features such as flash based fileupload and drag&drop are planned to be shipped with 0.9.0. PrimeFaces UI is marching towards 1.0 which would probably come out around autumn 2009.

Thanks to all members of PrimeFaces community for their contributions and support.

JSF Html Editor

PrimeFaces ships with a rich text editor allowing users to provide HTML text. Editor component is based on YUI editor with PrimeFaces extensions and the underlying javascript widget is of type PrimeFaces.widget.Editor.

The simplest example would be;

<p:editor value="#{bean.text}" />

In addition for Turkish users, Turkish is built-in.

<p:editor value="#{bean.text}" language="tr" />

Editor is also skinnable using CSS, following is just an example.

For the live examples, checkout the online demo.

RichFaces and PrimeFaces Integration

It is usually pain to merge two or more component suites in one project. If you’ve ran into some issues then you know what I’m talking about. One of the design goals of PrimeFaces is the compatibility with other JSF component libraries.

For example, RichFaces and PrimeFaces can work together well. Even the ajax integration would work. Both libraries has partial page rendering features, the cool thing is that no known conflict occurs even when using ajax stuff together.

Following a4j:commandButton reRender’s primefaces panel;

<a4j:commandButton value="Rich Update" reRender="primePanel" />
<p:panel id="primePanel" header="Visca el Barca">
	<h:outputText value="I hope Barca will kick Bayern's ass" />
</p:panel>

And the vice versa, primefaces button reRender’s rich:panel.

<p:button value="Prime Ajax Update" update="richPanel" async="true"/>

<rich:panel id="richPanel" header="Visca el Barca">
	<h:outputText value="I hope Barca will kick Bayern's ass" />
</rich:panel>

JSF 2.0 standardizes many things like ajax and resource loading but it’s still component library’s responsibility to follow the standard. Even before JSF 2.0, as of JSF 1.2 PrimeFaces is friendly to other component libraries, the idea is not to mess with JSF extension points a lot and use them as minimal as possible. That’s why PrimeFaces has no filter:)