> I guess there's probably not much of AxKit you'd be using, so might be > easier to just use an XSLT transformer inside Catalyst... > > Alternatively if there's bits of AxKit you want to use (stylechoosers, > etc) then a Catalyst Provider would be a good idea.
I had been thinking about this whole process and came to the conclusion that the only way to really do it would be a Catalyst::View::AxKit which AxKit saw as a Provider. AxKit's Caching would be nifty for Cat apps from what I've seen. > On 16 Dec 2005, at 07:37, <[EMAIL PROTECTED]> wrote: > >> Interested in this too. However, this is with an application build in >> axkit but switching to catalyst instead of taglibs (more or less same >> pipeline as yours example). >> >>> So I was wondering if anyone here had any experience using AxKit for >>> presentation side (front end) of an application build using Catalyst? >>> I've done some preliminary googling and haven't been able to find >>> much. >>> >>> I'm thinking of doing something with a pipeline like this: >>> Request -> Apache (AxKit) -> Catalyst -> XML -> AxKit -> XSLT -> >>> Response >>> If someone here could point me in the right direction or shout out a >>> couple of pointers/pitfalls it be greatly appreciated. >>> >>> Thanks, >>> - Jason Mills >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
