No idea if there is a RMI interface, but it seems whatever interfaces
are provided by default in Confluence are available in the Apache
installed instance.... Of course, any of these interfaces could be
disabled by infra in the future, if security issues or DoS attacks
become a problem.
-Donald
Pinaki Poddar wrote:
Thanks Donald for the references. I had browsed few of them earlier.
The references mainly show perl based scripting. I just played around with a
Java/JCR based API on Jackrabbit implementation. That provides an rmi based
access out of the box. So I was looking for details such as
i) does confluence installation open to an autheticated rmi based access?
ii) if yes, what is the URL?
I could not find it in the above references.
But reading through them, it appears that perl scripting comes more natural
in this environment for the current purpose.
DWoods wrote:
For webdav -
http://cwiki.apache.org/confluence/plugins/servlet/confluence/default
and use your cwiki uid/pwd.
Confluence docs -
http://confluence.atlassian.com/display/CONFEXT/WebDAV+Client+Setup#WebDAVClientSetup-WebDAVClientSetupOtherClients
For XMLRPC, I don't know if that is enabled, but try -
http://cwiki.apache.org/confluence/rpc/xmlrpc
Confluence docs -
http://confluence.atlassian.com/display/CONFEXT/Scripts
-Donald
Pinaki Poddar wrote:
Dnald/Craig,
Do you know the RMI URL to connect to confluence content repository
using
jackrabbit or anyy other JCR compatible client?
[1] http://cwiki.apache.org/confluence/administrators.action
DWoods wrote:
and adding some date substitution of when the last rsync ran would be
great too, so anyone could tell how old the static content is and if the
scripts are not running again....
That would also be helpful for search engines, to know which pages have
changed by updating the meta-data during the copy....
-Donald
Michael Dick wrote:
Hi Pinaki,
The upload.xml and the wiki updater are separate entities.
Upload.xml runs more or less nightly - I have build profile on our
continuous integration server that runs at 2:00 AM if there have been
changes. It lays down the documentation, and pre-compiled binaries into
a
'staging directory' on people.apache.org. Naturally others are free to
run
it at any time and deploy to other locations if they choose.
The wiki / homepage gets updated by confluence. After an update to the
wiki
confluence exports the site to our page on people.apache.org. The page
is
then 'skinned' by a cron job / script of some sort that Donald owns
which
adds the logo and some other customizations.
Doing what you want is a bit involved. The place to do it is in the
cron
job
/ script that gets executed after confluence updates the site. That
script
will have to unzip the openjpa binaries and run OpenJPAVersion (or just
read
the properties file) and do the substitution for you.
There may be some tweaking we can do to make the confluence export do
the
work for us, but that's beyond my knowledge. Also I only have a passing
familiarity with the cron job / script that adds the logo to the site,
so
I
my understanding might be out of date (this is how it worked when Marc
set
it up). Donald is the expert and can correct me if I'm wrong :-)
It's all doable, but might require some coordination to make this part
of
the 'main' cron job that inserts the logo.
Regards,
-mike
On Wed, Nov 25, 2009 at 3:28 PM, Pinaki Poddar <[email protected]>
wrote:
Hi,
I am looking for a way to display the SVN revision number of the
nightly
snapshot build in the confluence Wiki page. Looks like the upload ant
script (./openjpa-project/upload.xml) is the right place to
a) extract the revision number form the OpenJPA build
b) make some text substitution in the Wiki page that displays nightly
snapshot download in a table.
Comments/Suggestions/Alternatives?
-----
Pinaki
--
View this message in context:
http://n2.nabble.com/Adding-varaible-content-in-Confluence-from-OpenJPA-Builds-tp4067796p4067796.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
-----
Pinaki
-----
Pinaki
