Thanks for providing this module, I was able to use it to auto-post and/or replace new pages.
The confluence api allows you to post confluence wiki markup into newer versions of confluence (i.e., >4.x). The xml-rpc api seems to be the only way to do it.
Inline::Java makes many things possible. I have used it in conjunction with JDBC.pm to write a portable sql command line application (search for sqlpj on github). Writing the interface in Perl was a breeze, and allowed a much more feature rich environment, like dynamically generating calls to explore the JDBC metadata for virtually any database, and generating XML output for query results. Patrick has been a big help and helped me track down a problem in JDBC caused by a change in the way Perl handles ISA (inheritance) in Perl 5.10.0.
Highly recommended for anyone who needs to take advantage of the thousands of Java api's out there in the wild. In the case of JDBC, just drop the vendor's jar in your classpath and you're off and running.
The only problem I've had is in catching interrupts on the Perl side and dealing with the disconnect with the Java server, interrupting the server in mid stream. However, that is a minor problem and perhaps an area for future enhancement.
Great module from Tim Bunce. It wraps the JDBC library for ease of use with Inline::Java.
Enables perl to access any database that has a JDBC interface. I have written two programs that use it, search for sqlpj or ecdump on github.
Cpanm is just awesome!
First, the installation is brilliant (painless, flexible, just works!)
Second, it just does the right thing - you can install any package from cpan or backpan just by pasting the url, or have it look up the module for you.
No complicated arguments, just install it already.
I doubt if I will ever use cpan again.
Nicely done in every way.
This is a wonderfully well-written module that is very reliable and saved me loads of time.
If you have to deal with any SCCS conversion, this is the module to use!
I used this library to process 65K SCCS files with over 2.5 million revisions, and it worked flawlessly. It is one to two orders of magnitude faster than other solutions, because it does not rely on SCCS native tools. (Note: check heirloom.sourceforge.net if you need SCCS tools and you don't have a native install).
The author has generously provided very useful examples - which were the starting point for my own back-end to convert a major SCCS source repository to CVS. Once you have converted to CVS, you can use the feature-rich tools hosted on svn2cvs.tigris.org to do further conversions, or you can use the git conversion provided as an example by this author.