Hi Sten,
I'd recommend to create a SOAP API based on the Jackrabbit SPI effort because it
is much easier to implement. In contrast to the JCR API the Jackrabbit SPI is
less object oriented (e.g. there are no methods to navigate between items, etc.)
and better suited for protocols.
See:
http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/11221/
http://article.gmane.org/gmane.comp.apache.jackrabbit.user/2463/
If you are interested in building a SOAP API based on the Jackrabbit SPI
interfaces you may want to have a look at the SPI-RMI implementation. It simply
remotes the SPI interfaces using RMI. Using SOAP instead should be straight forward.
regards
marcel
Sten Roger Sandvik wrote:
Hi all!
I have searched the archives in this mailing list and "googled" about
JCR+SOAP and I am puzzled that it does not exist a SOAP api on top of JCR
yet. I know that the WebDAV "and friends" is a platform neutral way of
accessing the JCR api, but recently I have been in need of a SOAP api. Have
anyone else need for such a api?
If anyone has done something here or have ideas, please let me know. If
nobody has done something here, I am considering to begin development of a
generic SOAP mapping on top of JCR. The reason is that I need to access the
JCR functionality via ActionScript (or Flex) without using Flex Data
Services.
Regards,
Sten Roger Sandvik