process - A more agile alternative to Java EE -

in nutshell, i'm trying find process/technology stack web applications development, easy/fast/flexible prototype, has clear upgrade path robust production platform.

i apologize lengthy description below, problem between tech , process , can't find easy/short way express it. , yes read "good subjective, bad subjective" article.

currently using java ee blows , whistles (agile, continuous integration, issue tracking, unit testing, hibernate/spring/stripes/jquery stack ...). use flexible project definition/analysis process feature gathering in parallel gui mockups (kudos balsamiq mockups) creation , later html static pages prototype. during development, frequent intermediate builds client reviews. once testing phase functionality 90% on target , needed bugfixing , final robustness polish.

for our traditional clients ie banks , pharmaceuticals, above process/technology stack works charm.

lately though, developing internet startups. in case process quite different. start basic mockups, first raw prototype made (lots of static pages + basic functionality cover core scenarios). start developing full blown application.

critical step here! when application goes public, marketing/business guys receive feedback birds, observe competition, make conclusions , want change application. a lot! @ point not in prototype mode more, have nice robust, production quality java ee application hundreds of unit test built in. can evolve it, neither easy nor agile.

1) on process side, tried nail down spec visual , formal tools available, in vain; nobody able fix spec before market speaks.

2) tried more "flexible" environments rubyonrails , php.

2.a) production grade quality, still seem little bit week compared java ee (yes, know of important services/apps written in php)

2.b) if use them in "flexible" way, great prototyping, obtain code difficult rise production quality.

2.c) if implement best practices (layering, unit testing ...), complexity becomes comparable standard java ee's complexity have.

3) when app goes live, has polished , robust, easy make prototype no option.

4) if propose make throwaway prototype, client refuses see throwaway , asks bring production quality (not willing pay start-from-scratch development).

so basically, putting "quality" (intending structure, robustness) in process, when not needed , when stays in way of change , flexibility.

any ideas?

become flexible.

seriously, need @ , team, rather 'technology stack'.

many have stood are, take leap , take on 'flexible' alternative.

you'll surprised power can yield. know power comes responsibility not knowing how use tool. lot more that.

it may don't need alternative, need dig deep current troubles , fix them. isn't we're supposed do? improve our craftsmanship?

oh, not internet start ups, banks , pharmaceuticals mention moving flexible alternatives.