The new feature of specifying an external-to-war mav.xml file works great. My dream of separation of engine (war) and content is one step closer to reality!! The strength of a war is that everything can be bundled together, but in an application where you want to have one engine with multiple personalities or skins, it doesn't quite work.
Thanks so much, Dan
At 02:52 PM 2/19/2003 -0800, you wrote:
The separated param collections and the absolute config path features are checked in. Take a look.
I'll get to the remaining issues soon.
Jeff
> From: "Schnitzer, Jeff" <[EMAIL PROTECTED]> > > Separating the three different param collections (controller, view, > transform). > > Allowing file:, http:, ftp: in the maverick config file (and config > transform) path. Need to check to see if I can detect absolute vs > relative URLs just by creating a URL and checking for > MalformedURLException. Oterhwise just explicit checks for those strings > will work. > > Review John-Mason's controller chaining code and figuring out how this > can be morphed into a pluggable Controller framework. > > Adding a link to Roman's Tiers sample. > > Sorry about the lag. Both work and life switched into high-gear at the > same time. > > Jeff Schnitzer > [EMAIL PROTECTED]
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge [INVALID FOOTER]
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf [INVALID FOOTER]
