Sweet is a web application framework for building dynamic web content that runs on any Java servlet server. The framework is made with Scala, a more advance and easier to write programming language compared to Java. Since Sweet applications can run on a Java Virtual Machine, it can take advantage of all the Java libraries, servers, and large communities.
Our visions and goals for Sweet is SWEET itself:
* Simplicity - Sweet needs to keep complex things simple.
* Works - Sweet needs to be practical and functional.
* Efficient - Sweet needs to be efficient.
* Extensible - Sweet needs to be extensible by developers.
* Testable - Sweet needs to be testable.
Vaadin is a Java web application framework. It is designed for creating rich and interactive applications that run in the browser, without any plugins. A server-driven architecture together with reusable component model is used to simplify programming of applications and for better web application security. No HTML, XML or JavaScript necessary and all Java libraries and tools are at your disposal.
Hannibal is a code generator that can generate scaffolding for web projects in different languages, including Java, PHP, SQL, and JavaScript. The code it generates follows Restful considerations.
[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 Fiji
Exadel Fiji is an extension to JavaServer Faces to fully encapsulate Flex.
Exadel Fiji extends JSF by allowing the use of Flex with JSF components and within a JSF page. When using Fiji Flex components, developers can use Flex with the same familiar JSF component-based approach to building user interfaces.
Welcome to Project SocialSite, an open source (CDDL/GPL2) project building Widgets and Web Services that make it easy for you to add social networking features to your existing web sites, including the ability to run OpenSocial Gadgets and have them backed by the same social graph.
Here are some of the key features we're developing:
* A complete end-to-end user interface for Social Networking in the form of JavaScript widgets that can be embedded into any site (Java, Ruby, PHP-based and more).
* A flexible Social Graph repository that can work in a wide variety of social networking scenarios. With configurable profile properties and relationship types.
* Comprehensive JavaScript and REST API access to that Social Graph repository: OpenSocial plus conforming extensions.
* Scalability via support for running in distributed configuration, table partitioning technologies, master and slave databases and distributed caching.
Gracelets is a view/controller technology layered on top of Facelets/JSF. It complements the Facelets templating technology by allowing Groovy scripts to replace or be used in connection with normal Facelets source files and views.
The name came from combining the Gr in Groovy and replacing the F in Facelets with Gr, Groovy Facelets, or Gracelets (yeah, a no-brainer).
One of the inspirations behind Gracelets was the desire to use Groovy scripts, which have many practical applications for many java developers these days, and yet have all the power of Facelets and JSF behind the groovy script. Another inspiration was to at least have the option to develop quick solutions in a single file. Of course the Model-View-Controller concept is marvillous and it is important to keep things seperate, which can also be easily done with Gracelets. But sometimes it is nice not to be forced to do so just to prototype or develop some quick solution that one wants or needs, and Gracelets gives you that option. In other words, Gracelets works fine as simply a view technology in the MVC flow, but also allows you to do more in a single script if you so desire.
The main goal of Gracelets is to complement Facelets and provide more options, flexibility and efficiency to Facelets and JSF users and component developers. Since you can still use normal Facelet XHTML views and everything else you already have invested in JSF/Facelets, you are not forced to use Gracelets even though it is installed/configured. Thus you can choose exactly where you want to use Groovy Facelets/Gracelets in your application. Even inside Gracelet scripts, you can still access the full component/tag set already available in JSF/Facelets. Some of the possible practical uses of Gracelets could be (but is not limited to) the following: