I really have only basic crud stuff and the database I am using is Neo4J, which is a No SQL database.
What I am really looking for is a really clean separation of client from serverside. I really would like all the communications from client to server be done via REST calls with JSON. I am not quite sure how to handle an empty form, then submitting the json to the server side which then generates my domain object, I know how to map and use Jackson, but the form will have 4 fields but not the overall main domain object that the 4 fields come from, so I am not sure if I have to wrap the 4 fields with one map holding one map. Anyway, that is the least of my worries.
Not sure exactly what you're looking for. I seem to attain what you are looking for with jQuery on the client and Play or Front Man on the server. Complete separation aside from agreement on the web API. What more are you looking for?
Bear Bibeault wrote:Not sure exactly what you're looking for. I seem to attain what you are looking for with jQuery on the client and Play or Front Man on the server. Complete separation aside from agreement on the web API. What more are you looking for?
I have never looked at your frontman, maybe that will work for me. But how much coupling happens in using frontman. Any classes I have to extend or implement?
(Assuming Scala is ok as the programming language of choice).
Bowler has you extend classes, so those classes are too coupled to Bowler. Plus I don't know Scala, don't want to learn another language, I know Java and Groovy, and shouldn't need to learn a whole new language first.
I like EmberJS, very much like an approach I was thinking about. I also heard of extjs, nodejs, and Spring has one being created by a friend of mine. I think at some point I might get up to this level, but right now, my site is really simple, just can't get the UI and server side connected nicely.