Comments for Rockhopper Blog

Comment on JUnit4, Selenium and Spring test context by Fran

Fran — Mon, 14 May 2012 15:46:48 +0000

Just as a comment,

By convention, a Spring bean name should start lowercase: “selenium” instead of “Selenium”

Cheers,

Fran

Comment on Learning Clojure: Leiningen by Learning Clojure: Setting up the Emacs on OSX | Rockhopper Blog

Learning Clojure: Setting up the Emacs on OSX | Rockhopper Blog — Wed, 18 Apr 2012 15:52:25 +0000

[...] Blog Technical Development Topics by Gene De Lisa Skip to content AboutResources « Learning Clojure: Leiningen Learning Clojure: Setting up the Emacs on OSX By Gene De Lisa | Published: April 12, [...]

Comment on Spring @MVC 3 cascading selects using jQuery by Danilo

Danilo — Wed, 21 Mar 2012 13:21:35 +0000

Excellent post. I was searching for something like that.

The good part is that i made some modifications in the code

$.ajax({
type: “POST”,
url: “${findStateCitiesURL}”,
success: function(data){
$.each(data, function(val, text){
$(‘#cboState’).append($(”).val(val).html(text));
});
}
});

And in the Controller:

@ResponseBody
@RequestMapping(value = “/cities/{state}”, method = RequestMethod.POST)
public List findStateCities(@PathVariable(“state”) String state, ModelMap map) {
logger.debug(“finding cities for state ” + state);
return this.geoService.findCitiesForState(state); // as a List or something like that
}

And of course, Jackson is in my pom.xml:

org.codehaus.jackson
jackson-mapper-asl
1.9.5

Comment on Spring @MVC 3 cascading selects using jQuery by Gene De Lisa

Gene De Lisa — Mon, 28 Nov 2011 18:07:18 +0000

Kamal,

You need a plugin for Eclipse to recognize Maven projects. Some versions of Eclipse, such as Spring’s STS, already have it in the bundle. If you’ve downloaded one of the distributions from eclipse.org, then you need to install it.

There is information on the plugin at the eclipse.org site on installing and using the m2e plugin.

Once you have the plugin installed, you simply unzip the projects I’ve provided and choose the Eclipse menu item “Import” then choose “Existing Maven Project”.

Comment on Spring @MVC 3 cascading selects using jQuery by Kamal

Kamal — Mon, 28 Nov 2011 03:36:27 +0000

Hi,
I am new here learning Spring, I like this tutorial, I am new to Maven to, please , I downloaded from the link :
Download Source as a Maven Project

Can you please show me the steps on how to import this project in eclipse.

your help is appreciated,
thanks

Comment on Spring @MVC 3 cascading selects using jQuery by david

david — Mon, 24 Oct 2011 06:50:51 +0000

thank you very much. using your example i solved my issue with ajax call in spring MVC which i was struggling for almost 2 weeks.

Comment on Spring @MVC 3 cascading selects using jQuery by Wijoata

Wijoata — Fri, 21 Oct 2011 19:44:45 +0000

Excelente POST.

Comment on Factory Design Pattern by Mozart and the Flyweight Design Pattern | Rockhopper Blog

Mozart and the Flyweight Design Pattern | Rockhopper Blog — Thu, 05 May 2011 13:45:19 +0000

[...] our friend the GoF Factory Design Pattern? Instead of being a micro-managing pointy haired boss (i.e. using the keyword “new”) a [...]

Comment on Eclipse 3.6 Helios arrives. Plugin update support still needs work by Bob

Bob — Mon, 14 Mar 2011 16:53:48 +0000

JSF 2.0 is designed to support Ajax. The above comment is only true for JSF 1.x

Comment on Eclipse 3.6 Helios arrives. Plugin update support still needs work by Yazilim Tasarim

Yazilim Tasarim — Thu, 02 Sep 2010 07:49:35 +0000

IceFaces is not actually a JSF implementation. It’s a JSF add-on (ajax component library and then some more). Apache MyFaces and Sun’s RI are the implementations.

I was consulting/contracting JSF full time for about two years, and saw relatively little evidence of IceFaces being used in the field. Thinking seemed to be: “JSF is complex enough as it is so we don’t want to add any extra stability-risking complexity on top”. This is not at all isolated to IceFaces, which may well be the best of the bunch, but all JSF Ajax stuff seems to be retrofits on top of a framework that simply was not designed for Ajax.

As of JSF itself; I’v moved to GWT about a year ago (and would NEVER move back to JSF), but to tell the truth JSF served me relatively well. Some architectural and design deficiencies are balanced by the wide industry adaptation.