that's a lot, let me be brief in my answers :-)
1. setting up your webapp project should go fairly quickly, just follow the getting started guide, use the maven andromdapp:generate plugin and generate a web-only application 2. select Spring+Hibernate, you'll have bpm4struts enabled 3. make sure to enable web services if you think you're going to need them the estimates are for someone who is familiar with AndroMDA, that is, who read the docs and studied the examples a) should take about 20 minutes if you take your time, generated: hibernate POJOs, *.hbm files, .. everything you need b) you don't need to model those CRUD pages, just use the <<Manageable>> stereotype on your entities (See a demo here: CRUD demo (http://galaxy.andromda.org:8080/crud/Home/Manage.do)) .. the Spring + Bpm4Struts cartridges will do the rest c) this is a typical scenario (aka the master-detail usecase), it features advanced bpm4struts feature .. will take a day to complete and perhaps a few questions to the forum before you get it right the first time (although everything is explained in the bpm4struts howto , in the 'tables' section) so far you'll not need to customize any pages d) then model this small use-case, if you know exactly what you want to have you'll be able to learn how you need to model it x) you seem to be missing services, that might also take a moment to do: think about what you need and where you will use it this would take about 2 days for a prototype, 3 weeks or more for a functionally complete, implementation .. attention: doing style/layout is another thing, use a gfx artist for that job, not a Java developer it's not just about code-generation, it's also about (1) maintainability, (2) extensibility and (3) extendability .. AndroMDA helps in all those aspects it's over a longer period of time that making the AndroMDA choice pays off, in the beginning too, but it's even more after a while the reason is that hand-coders waste time maintaining things, they make errors where the code generator does not also: updates to the cartridges will improve your project too, new features become available, etc... summary: 1) 3 weeks with AndroMDA vs. 2 months using classical development 2) customize the templates or the generated code, whatever fits best, in your case I would customize the templates .. here you'll lose some time getting to know bpm4struts templates it's true that customization requires you to understand what is generated: you'll need to understand the generated code and you'll need to understand where it is coming from, this might seem frightening at first, but you should be productive after a short period of time though asking questions in this forum will get you all the information you need, most of the time during the day you'll get an answer withing 30 minutes 3) security can be modeled both for bpm4struts and spring, but only JASS compatible though, there's no support for more complicated security constraints i) 10 minutes ii) yes, 10 minutes to draw the associations and creating the actors iii) there is a login page generated for you, just customize it, alternatively you can model a login use-case (this is what I'm currently doing on my project at work) adding security will take you 2-3 days more if you know what you're doing (this includes building + modeling + running + testing + etc...) anyway, that's what it would take me, obviously I can't speak for anyone else getting to know AndroMDA will require you to invest time and effort, so you might want to try a little minimalistic sample demo, just to see how far you can go, I tried to simulate that with the online store for bpm4struts, using spring+hibernate is more straightforward -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3771#3771 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
