[Duplicate of an email to axkit-users]

This release finally puts the pieces of the puzzle in place for being able
to build dynamic web sites with AxKit. No longer will I be saying "AxKit
is best for static sites".

The key piece is major updates to the XSP engine, which allows taglibs to
become a workable reality. Taglibs allow you to do things like:

 <except:try>
  <mail:send-mail>
   <mail:to>[EMAIL PROTECTED]</mail:to>
   <mail:from>[EMAIL PROTECTED]</mail:from>
   <mail:subject>AxKit Rocks!</mail:subject>
   <mail:body>
   Matt, I just wanted to say that I think AxKit is really cool! Thanks!
   </mail:body>
  </mail:send-mail>
  <except:catch>
  Sending Mail failed: <except:message/>
  </except:catch>
 </except:try>

Kip Hampton has put a lot of work in with me to make sure we have a good
range of taglibs to get you started, so we've got Param, ESQL, Exception,
Sendmail and Util to get you started. We'll build more as the need
arises. Of course XSP doesn't limit you to taglibs, and to demonstrate
that I'll be releasing the Take23 CMS shortly, which is just 4 XSP pages
and a module, and some stylesheets.

All of the taglibs have been uploaded to CPAN, which will be the prefered
location for them. If people think they would be better on
axkit.org/download then we'll put them there too.

Other updates include:

 - Much better dependencies checking
 - XPathScript adds import_template() function and other minor changes
 - Better shared memory usage when using directives in httpd.conf
 - All XSP namespaces updated to Apache normalised versions (these are
   http://apache.org/xsp/<module>/<version> although these may well
   change again shortly)

Enjoy, and keep those bug reports coming.

If you have any questions about XSP/taglibs please don't hesitate to ask.

-- 
<Matt/>

    /||    ** Director and CTO **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // **     Personal Web Site: http://sergeant.org/     **
     \\//
     //\\
    //  \\

Reply via email to