i have an application running on JBoss Seam 2, which uses rich faces as its presentation layer.
My question is can I do away with rich faces and use gwt.
what are the stuff that must take into account ?
Is it possible ?
You can use gwt instead of richfaces if you would like to. You can start by reading Chapter 22 of the seam reference guide.
Related
I am looking for a library similar to MetaWidget which can derive an application form from a bean and vice versa for Vaadin 8. MetaWidget is on the state of Vaadin 6 and a little complicated to use.
If there isn't any library then I consider to create one myself but I don't wanted to recreate the wheel.
As noted in the comments, Vaadin 8 has built-in data binding supported with the Binder class. Especially, the bindInstanceFields maybe of interest for you to simplify binding bean properties to field components. Layouting is simplified by FormLayout.
However, I am not aware of an add-on or library that automatically picks the right field components and lays them out.
References:
Blog: Vaadin 8 Binder, Section "Declarative Binding"
Documentation: Forms
This Vaadin add-on may help. It generates CRUD UI from entity beans:
https://vaadin.com/directory/component/crud-ui-add-on/
errai-uibinder is no more available for errai 4.0 (4.0.0.Beta1) but using uibinder without the specific treatment seems to be the cause of some runtime problems at startup in my application.
Has anyone successfully used UiBinder views with Errai 4.0 ?
Thanks,
S.
I think, Errai 4.0 will no longer support UiBinder. That's because generators will not be part of GWT 3.0. And because as long as no one will rewrite the Uibinder generators and replace them with APT, it will not work.
Take a look at the blog:
http://errai-blog.blogspot.de/2016/04/errai-400beta1-released.html
Errai offers an alternative way to create UIs.
I'm developing enterprise web application which is using JSF with Eclipse IDE. But i'n not experienced at JSF web application architect, just not familiar with name classes ,projects,packages,web pages, template pages etc.. , is it possible to name packages like following:
CompanyName.systemName.controller (there would be controllers in it )
CompanyName.systemName.Model (there would be managed beans and other things in it )
even how to choose best structure for my project(mean Architecture of folders,classes,packages,web pages, template pages etc). if anyone has an idea ? i'd be glad if have sample project.
thanks
Those are fine package names. Some people like to group packages by purpose:
org.mycompany.myapp.controller
org.mycompany.myapp.dao
org.mycompany.myapp.service
etc...
For larger applications, I like to group them by feature:
org.mycompany.myapp.billing
org.mycompany.myapp.signup
org.mycompany.myapp.webservices
etc...
As for folder structure, a good Maven archetype can be very helpful. Here's a web page that gives a good walkthrough of setting up a few types of JSF projects using Maven archetypes: http://www.javaserverfaces.org/get-started
If you look from architecture point of view, your JSF application should mirror very much like any other well architected Java-Web application.
For packaging I like to break first by functionality (like core, gui) and then by business unit level.
Something like:
com.comp.core.db.beans
com.comp.extension.ui.extension //If my application is going to give extension point for others to implement, extend the functionality.
com.comp.core.ui.controller
On a similar note pages, config files can be broken into separate logical units.
I have a complicated Apache Wicket application.I want to convert that application as a Wicket Portlet application. I got some information from https://cwiki.apache.org/WICKET/portal-howto.html. But doesnt so clear . So wanted to know the simple steps to convert an wicket Application into Wicket Portlet Application
I have done the exact opposite of you, I converted a lot of Wicket Portlet to a single Wicket Application. What portlet container are you going to use ? What Wicket version are you using ? I think Portlet support has been dropped in 1.5, so be warned that you will be stuck with 1.4 unless you provide your patches. The Wiki page you're talking explains everything you have to know. I suggest you try an hello-world before converting your application.
I'm looking to setup the GWT-Validation Framework (client side for now) in our application, but I'm not clear from the docs what pieces I need and what goes where?
We are using GWT 2.1 and MVP. I have the inherits entry for Validation in the gwt.xml, but what goes actually goes into the View, Activity, etc... I'm not aware of any tutorials available.
Any help would be appreciated!
Aftermath:
At the time when I was trying to use it, GWT 2.1 wasn't compatible with the GWT-Validation framework. After doing more reading I found this out. I don't know if that is still the case.
I assume you are referring to the validation framework in GWT and not the gwt-validation library? If that's the case, here is a page that describes how you can do bean validation: http://code.google.com/p/google-web-toolkit/wiki/BeanValidation. If you are actually referring to the gwt-validation library, here is a page that describes how to use it:
http://code.google.com/p/gwt-validation/wiki/ConceptOfOperations
Here is a link that gives some information about the GWT Validation Framework, GWT-Validator and the authors solution, the GWT-Validation library. It is a good synopsis of the issues and why he wrote the new library with some code snippets.
The GWT Validation Library.