This web-based tool is based on plain JSF. It aims to provide support for all features of JCR-Repository including optional features like versioning.
The specification for JCR 1.0 can be found here , the work in progress for 2.0 can be found here: here .
For development the implementation Apache Jackrabbit is used, which can be found here: here .
[fleXive] is a JavaEE 5 open source (LGPL 2.1 or higher) framework for the development of complex and evolving (web-)applications. It speeds up development by easing many tedious and repetitive programming tasks and helping to keep your application(s) flexible during the development-cycle and in production.
Based on the latest industry-standards like EJB 3, JSF, etc. [fleXive] should be your choice for building up your own new application.
JSF Flex goal is to provide users capability in creating standard Flex components as JSF components. So users would create the components as normal JSF components and the project will create the necessary SWC, SWF files and etcetera and link the values of the components back to the managed beans using JSON+Javascript and Actionscript. {standard Flex components has been open sourced through MPL license}
Currently many of the standard rich flex widgets (buttons, sliders, inputs [richTextEditor, textArea, ...], progressbars, colorpickers, various panels [accordion, tabBar, ...], and etcetera) have been written as intention of support.
Exadel Flamingo provides a set of commands that help a developer to generate initial code. To bootstrap a project, a developer answers a few questions in a wizard. Based on these questions, a standard project is generated. Flamingo is based on Maven, therefore the new application is generated according to Maven conventions, making it easy for people familiar with Maven to navigate through the project.
The generated code provides all the necessary plumbing and connectivity from Flex or JavaFX to Seam or Spring. A developer only needs to focus on business functionality; Flamingo takes care of the rest. All communications between the user interface and Seam or Spring components are taken care of by Exadel Flamingo.
Exadel Flamingo also provides a set of Flex components that make it extremely convenient to support specific features of Seam on the client side.
This will be the first of a small series of blogs covering proposed new features in JSF 2.0.
Keep in mind that none of the features described are final, and may change, but
this is a good opportunity to show the features as they exist now and illicit feedback.
The traditional way to integrate JSF and Spring was to define JSF beans in faces-config as managed beans and refer to the spring beans using the managed-property configuration. With the help of the spring’s delegatingvariableresolver the managed property is resolved from spring application context and JSF’s IOC injects the bean to the JSF Managed bean instance. I’ve written an article it about this way before.First approach is modelled as follows
JSF-Spring-JPA is the popular stack of choice these days, mostly to be used in my consulting and training purposes I’ve created a base project called MovieStore demonstrating the annotation-driven integration of JSF-Spring-JPA. JSF backing beans, spring service level beans and DAO’s are configured and integrated with annotations. Only the core infrastructure like datasource, entityManagerFactory or transactionManager are configured with xml.
Maven Archetypes for Web Applications
This page contains maven archetypes to help you quickly and easily get started on a web project that uses the jetty plugin. Each archetype allows you to generate a template for your project based on the included sample web application. (This supposes that maven 2.x is already installed in your system)
Java framework for CRUD and Validation.
Crank Google Group for Questions and Such
Crank is a master/detail, CRUD, and annotation driven validation framework built with JPA, JSF, Facelets and Ajax. It allows developers to quickly come up with JSF/Ajax based CRUD listings and Master/Detail forms from their JPA annotated Java objects.
Crank uses a lot of the new JSF features from Facelets, Ajax4JSF, etc. that will be used in JSF 2.0. Crank is a use case analysis of what is possible with the new JSF 2.0 stack.
The validation piece does server-side validation, Ajax validation or just emitted JavaScript validation based on Java annotations, property files, XML files, or database tables. Currently works with JSF, Spring MVC and Spring Webflow.
Trying to combine JSF and JSP is like trying to shoehorn a foot into a glove: it's possible, but it's really just a stopgap measure until something better comes along. In this article, JSF enthusiast Rick Hightower introduces you to what he likes best about Facelets: easy HTML-style templating and reusable composition components.
this module makes the integration of spring-annotation and JSF really easy.
* It registers automatically a VariableResolver in the JSF stack to enable the use of the spring beans as managed beans
* it adds 2 (two) more scopes to spring framework: flash and conversation
* it registers a navigation handler in the JSF stack to enable you to write less code
* it adds some annotations to make it easier to write JSF code
Bestehende JavaServer Faces-Komponenten um Ajax-Funktionalität zu erweitern, das geht mittlerweile recht einfach. Und das, ohne sich in eine Ajax-Bibliothek einzuarbeiten, Umwege über Servlets zu machen oder sonstige, nicht auf den JSF-Lifecycle abgestimmte Techniken zu benutzen.
The Google Web Toolkit (GWT) has attracted a lot of attention lately as a way to make it easier for developers to add AJAX Web 2.0 features to their applications. Like other approaches, the designers of GWT have tried to insulate developers from having to deal with the underlying JavaScript, which implements these features. GWT achieves this goal of simplifying the creation of advanced client-side JavaScript widgets by generating them from Java code.