Installing Axkit - Where to Go for Help (Page 7 of 7 )
If you get stuck at any point during the installation process, do not despair. There are still other resources available to help you get up and running. In addition to this book, there are other sources of AxKit documentation, as well as a strong AxKit user community that is willing and able to help.
Installed AxKit documentation
Most Perl modules that comprise the AxKit distribution include a level of documentation. In many cases, these documents are quite detailed. You can access this information using the standard perldoc utility typically installed with Perl itself. Just type perldoc <modulename>, in which <modulename> is the package name of the module that you want to read the docs from. The following list provides a general overview of the information you can find in the various modules.
AxKit
The documentation in AxKit.pm provides a brief overview of each AxKit configuration directive, including simple examples.
Example: perldoc AxKit
Apache::AxKit::Language::*
The modules in this package namespace provide support for the various XML processing and transformation languages such as XSLT, XSP, and XPathScript.
Example: perldoc Apache::AxKit::Language::XSP provides an XSP language reference.
Apache::AxKit::Provider::*
The modules in this namespace provide AxKit with the ability to fetch and read the sources for the XML content and stylesheets that it will use when serving the current request.
Example: perldoc Apache::AxKit::Provider::Filter shows the documentation for a module that allows an upstream PerlHandler (such as Apache::ASP or Mason) to generate content.
Apache::AxKit::Plugin::*
Modules in this namespace provide extensions to the basic AxKit functionality.
Example: perldoc Apache::AxKit::Plugin::Passthru offers documentation for the Passthru plug-in, which allows a “source view” of the XML document being processed based on the presence or absence of a specific query string parameter.
Apache::AxKit::StyleChooser::*
The modules in this namespace offer the ability to set the name of a preferred transformation style in environments that provide more than one way to transform documents for a given media type.
Example: perldoc Apache::AxKit::StyleChooser::Cookie shows the documentation for a module that allows stylesheet transformation chains to be selected based on the value of an HTTP cookie sent from the requesting client.
Additional user-contributed documentation is also available from the AxKit project’s web site at http://axkit.org/. Not only does the project site offer several useful tutorials, it also provides a user-editable Wiki that often contains the latest platform-specific installation instructions, as well as many other AxKit tips, tricks, and ideas.
Mailing lists
The AxKit project sports a lively and committed user base with lots of friendly folks who are willing to help. Even if you are not having trouble, I highly recommend joining the axkit-users mailing list. The amount of traffic is modest, the signal-to-noise ratio is high, and topics range from specific AxKit installation questions to general discussions of XML publishing best practices. You can subscribe online by visiting http://axkit.org/mailinglist.xml or by sending an empty email message to mailto:axkit-users-subscribe@axkit.org.
You can find browsable archives of axkit-users at:
Topics relating specifically to AxKit development are discussed on the axkit-devel list. Generally, you should post most questions, bug reports, patches, etc., to axkitusers. If you want to contribute to the AxKit codebase, then axkit-devel is the place for you. You can subscribe to the development list by sending an empty message to mailto: axkit-dev-subscribe@xml.apache.org.
In addition to the mailing lists, the AxKit community also maintains an #axkit IRC channel for discussing general AxKit topics. The IRC server hosting the channel changes periodically, so check the AxKit web site for details.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
|
 This article is taken from chapter two of the book XML Publishing with AxKit by Kip Hampton (O'Reilly, 2004; ISBN: 0596002165). Check it out at your favorite book store. Buy this book now.
|
|
