-
1. Re: About to land GWTJSF support for GWT 1.4
robjellinghaus Jun 22, 2007 3:57 AM (in response to robjellinghaus)I have just landed this code at revision 274 of the ajax4jsf trunk. If this causes any problems to anyone in any way, please let me know immediately. I performed the integration locally using Perforce, so I'm confident I didn't miss any files.
The gwtjsf library is now one of the included modules in the main ajax4jsf POM, and it builds successfully in that configuration.
I have an updated a4j-gwtKickStart sample, but I am not sure how or whether to land it, since it is not mavenized. I am considering landing it as an Ant build, in something like ajax4jsf/trunk/samples/gwtjsf/a4j-gwtKickStart -- not part of the main Maven build, but available in the tree. Since the gwtjsf samples aren't anywhere in the tree at all now, this doesn't seem too bad. I'll do this over the weekend (or early next week) if no one objects.
Cheers!
Rob -- http://robjsoftware.org -
2. Re: About to land GWTJSF support for GWT 1.4
robjellinghaus Jun 26, 2007 1:15 AM (in response to robjellinghaus)I've now checked in the a4j-gwtKickStart sample, as originally written up by Sergey on TheServerSide, then modified by me to exercise the new GWT 1.4-based features of the GWTJSF library.
This is in the ajax4jsf trunk, in the samples/gwtjsf directory. There's a readme.txt that is hopefully fairly explanatory.
This sample still uses ant for its build, not maven. This is because I haven't the time to finish the maven conversion here. Anyone who wants to handle that part is welcome :-)
I will also not be checking in the other, previous samples from the GWTJSF tree on ajax4jsf.dev.java.net. Again, contributions here would be welcome.
This is the last contribution I currently plan to make to the Ajax4JSF tree, though I will stay in touch with the project.
Cheers!
Rob