On 8-Aug-06, at 10:48 AM, Stuart Brown wrote:
Is this XSP taglibs? They will work out of the box (only I haven't
ported that functionality yet). If they're XSLT-style taglibs yes I'm
sure those will work too. The big change will be that you will have
to write new config files, and maybe some very small plugins to hang
everything together. I can certainly help you with that if you post
some of your current config.
As far as our usage of AxKit1 goes we have a taglib written for
mod_perl
that uses TaglibHelper offer its functionality within our xsp pages.
These xsp pages then follow a xsl pipeline that delivers the final
mark-up.
AxKit holds the whole thing together for us.
So this should be easy, once I've got TaglibHelper (and SimpleTaglib)
working. And I need to make that happen as the wiki code depends on
it (which I intend to port next, as it will force me to get parsing
POST params working).
I read on a previous post that you can sit AxKit2 behind mod_perl
and
Apache, but will this be the best way migrate our setup?
Apologies my
Apache2, mod_perl2 knowledge is non existent at present.
The answer is "it depends" :-) What do you do currently? Do you have
a front-end proxy?
Currently we have a number of app servers running AxKit/mod_perl
that back
onto our Database proxy to deliver our dynamic content, our web
proxy is
under used at the mo. We could easily re-arrange so that AxKit sits
on the
proxy in front of mod_perl if that's what's required...
Yes, if you've got a front-end proxy right now this should be very
easy. In fact you can gradually port parts into AxKit2 as time
permits, just by deciding which bits to proxy where.
That's exactly what I've done on my server - where I'm now running
the AxKit2 gallery at http://home.sergeant.org/ but the rest of the
server is still proxied to my old AxKit1 installation.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
