In one of my projects the user has to select a customer from a dropdown list. Problem is that the number of customers they have is much to big to prefill. So I used dwr to build a solution. The user has a dropdown from which he can choose the field he wants to query (let’s say street), he than fills in a streetname, presses the button and the list gets prefilled with the list of customers who match.<\/p>\n
How does it work. Wel really simple \ud83d\ude42<\/p>\n
In my backend I have a simple POJO Search with a method getCustomers(String searchField,String searchValue). This calls a service layer, who in turn calls a dao layer,… you know the drill. In the end the method will return a List of Customer objects. I exposed these objects in the dwr.xml configuration file. (that’s it for the java backend stuff) (nice isn’t it \ud83d\ude42 )<\/p>\n
Now the javascript part is also small and handy. I had to include the dwr engine and my exposed object as javascript objects. When the user presses the button this small piece of code gets executed<\/p>\n
When the javascript gets a response back, the CustomerCallBackHandler will be executed. That looks like this<\/p>\n Where data is an array of Customer JSON objects. This means that in my java Customer object I have the getter\/setter getId(),getName(). In javascript I can simply do data[0].id and data[0].name.<\/p>\n Now isn’t that nifty?! \ud83d\ude1b<\/p>\n \/me like<\/p>\n","protected":false},"excerpt":{"rendered":" In one of my projects the user has to select a customer from a dropdown list. Problem is that the number of customers they have is much to big to prefill. So I used dwr to build a solution. The user has a dropdown from which he can choose the field he wants to query … <\/p>\n
\nSearch.getCustomers(searchField,searchValue,CustomerCallBackHandler);
\n<\/code><\/p>\n
\nfunction CustomerCallBackHandler(data){
\n<\/code><\/p>\n