What I wrote to initiate this discussion may confuse things a little, but I do realise that I do not have to use Spring Roo. I was simply too lazy to micro-manage that detail.
I must confess that I am confused by Spring's use of Maven. When I tried Spring Roo, perhaps, I was confused with all the entrails that Maven was spewing out. There were error messages and I had no idea what to do with those diagnostics. Imagine using Ant to write a web app - of course you could do that. But wouldn't be better if I wrote it in Java or Python? May be, Spring was attempting to build the Maven project for me by dynamically constructing the pom for me. Alright, perhaps, the intertwining of Maven is to provide and escape- path flexibility for people to choose to use or not to use GWT for presentation. Ok, then forget it, because I am intent on using GWT or SmartGWT and uibinder with them. Giving me the flexibility not to use them is introducing dependency and consequently points of failure I do not wish to deal with. Alright again, perhaps, the intertwining of Maven is to provide an opportunity for me to insert a process to inspect a database schema and then automate the production of the data model and then automate the production of data stream template. When I use Microsoft Visual Studio with ADO.NET life is simple. I don't have command line statements to type in. Why can't it be as simple as using Visual Studio? Why can't all this complexity be hidden behind Eclipse? Oh yes, I remember now, you are providing me with yet another flexibility - the option not to use Eclipse. What I need is a smooth spontaneous path from my data model to view/ presentation. I just do the JPA/JDO objects and their interaction with the data repository, then I present the objects to the client which autonomously and spontaneously decides how to present the data or solicit inputs at the GWT client. How complicated can that be? Why do you need involving a dependency tool like Maven or Ant to do that? Like a sledge hammer on a nail? Oh, oops, I missed this one - that Maven is involved because it is trying to template the auto-build process for me, which I could pick and stick by my own to improve it. If I have to manually pick and stick an automation template - is that even called automation because I don't even know what to pick and where to stick on the template that Spring Roo has created for me. Trying to achieve so much flexibility with such unsuitable a tool like Maven. That is too ambitious to do everything with Maven. My lack of understanding of how to use Spring Roo "properly" finds it a monolithic fascistic tool that tries to be a socialist grand-daddy to every entity in the build process. Well defined autonomous modular steps can flexibly build the world. The general rule of industrial practice - A tool that introduces more complexity in an attempt at simplification, or introduces more point of failures requiring manual intervention, in an attempt at automation is NOT to be used at all. It is highly probable that I don't know how to use Spring Roo "properly". In fact, I don't know what it does within that food chain ... Why do you even bother to construct the pom for me? Just help me construct the pathway from schema to model to presentation and let me decide if I wish to and how to use Maven. Can't it be done the way DataNucleus does it for me? Why involve Maven? Decouple Maven from that pre-build process and leave the Maven glue-ification decision to me. I consider DataNucleus a very usable tool. The guys who wrote it have my every accolade as professionals. Every diagnostic it spews out, I know what to do with them - even when the first time I used it. The usability of Spring Roo is no where near DataNucleus'. Couldn't Spring Roo be architected to be operated like DataNucleus? Actually, couldn't GWT team recommend something else that is operated like DataNucleus? Sorry for the outburst, and perhaps to Maven mavens and Spring havens I sound like an incompetent programmer - so my apologies about that, but ... So I am considering a project where the utility would inspect an entity class and its annotation, builds uibinder template. we could write a GWT client-side code that runs similarly to SmartGWT datasource, which inspects the RPC'd objects and decides what widgets to use to present them. The client-side datasource would also be fed with a json config where we would specify preferences to affect the data presentation. It's that simple - why get Spring or Maven involved? On Jun 7, 3:49 am, Thomas Broyer <[email protected]> wrote: > You are confusing many things: -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
