On Fri, Jun 24, 2011 at 7:29 AM, Patrick McCourt <pa...@mc-court.com> wrote: > The RequestsManager then passes off to the 2nd application, a > RequestHandler which will gather the details of the request, the > reason this is external is they want to be able to add in new request > types by simply building the struts for and deploying it rather than > redeploying everything.
I'm not convinced there'd need to be anything static at all yet: so far it sounds like there's a layer of abstraction that hasn't been discovered yet. That layer could be a DSL, or simply a dynamic language layer, meaning no hard deploys at all. > Since the RequestsHandler is the form for gathering the details I'm > not sure that it could be a UI-less API. There's no reason this can't be handled dynamically based on what information the request actually needs though, no? > Apologies if I've confused you more I didn't find it terribly clear after two readings. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
