Re: passing param as part of URL path

Brian Lalor wrote: Hey, cool! The two books that I can find (of the 3 I own) only cover up to Struts 1.1. The link Laurie sent contains some more info on the wildcard mappings, but it appears that you've gotta use a custom ActionMapping class[1, 2], with the className property of the /> e

Re: passing param as part of URL path

On Fri, 2005-07-15 at 13:12 -0500, Brian Lalor wrote: > is there a way to specify a new default ActionMapping class? The "type" attribute of the element will set a default so you don't have to repeat it (or forget to repeat it) in all your elements: -Max --

Re: passing param as part of URL path

On Jul 15, 2005, at 1:12 PM, Brian Lalor wrote: Hey, cool! The two books that I can find (of the 3 I own) only cover up to Struts 1.1. The link Laurie sent contains some more info on the wildcard mappings, but it appears that you've gotta use a custom ActionMapping class[1, 2], with the c

RE: passing param as part of URL path

> is there a way to specify a new default ActionMapping class? ModuleConfig does indeed have a method for setting the default action mapping class, but I'm not sure how you would set this. - Dave - To unsubscribe, e-mail: [EM

Re: passing param as part of URL path

On Jul 15, 2005, at 12:50 PM, Durham David R Jr Ctr 805 CSPTS/SCE wrote: I think you could use a wildcard mapping like this: But I'm not sure how to retrieve this property in an action. Actually, I'm not even sure that this works. Maybe someone else can post more info a

RE: passing param as part of URL path

> I was thinking that I would somehow capture CATALOG1 and CATALOG2 > and stick them into the request, but I'm not sure how to go about it. > It this functionality that Struts already has, do I need to implement > a filter, or should I subclass the main ActionServlet? I think you could use a

Re: passing param as part of URL path

You can do this using wildcard action mapping paths: http://struts.apache.org/userGuide/building_controller.html#action_mapping_wildcards L. Brian Lalor wrote: I'm working on a product catalog display application that uses the same logic and code, but takes a common parameter for *every req

passing param as part of URL path

I'm working on a product catalog display application that uses the same logic and code, but takes a common parameter for *every request*, specifying the specific catalog to use. The application is a web service of sorts, and has no state stored between requests. I would like to use URLs of