RE: Where to put non action associated data

lnew...@gmail.com] Sent: 01 August 2011 14:39 To: Struts Users Mailing List Subject: Re: Where to put non action associated data Yep, a service is the canonical solution--my impression was that the OP was trying to avoid *any* knowledge of the additional search stuff, but composing capabilities

Re: Where to put non action associated data

Yep, a service is the canonical solution--my impression was that the OP was trying to avoid *any* knowledge of the additional search stuff, but composing capabilities via services sure seems like the easiest thing to do. Dave On Mon, Aug 1, 2011 at 9:32 AM, Aaron Brown wrote: > If I were coding

Re: Where to put non action associated data

If I were coding the search part, I'd probably place the secondary piece inside a searching business service. Your action would instantiate a search business service and ask it to get search results based on a query string. The business service would do that and also (based on whatever business log

Re: Where to put non action associated data

Meh, while I think turning this into something event-based is way overkill, I wouldn't turn to chaining, either. I'd probably just use an interceptor, AOP, or any other "around"-type solution. I view actions as something a user can hit (insert mom-joke here), not as a chunk of general-purpose func

Re: Where to put non action associated data

This sounds like one of the very few legitimate uses of the chain result type. Check out http://struts.apache.org/2.0.14/docs/chain-result.html (*Chris*) On Jul 31, 2011 9:50 AM, "Marcus Bond" wrote: > Hi, > > > > Say I have a form where user can carry out a product search which hits an > action