On 15.02.2007, at 12:03, Oliver Lietz wrote:
Hello all,
I try to find a solution for accessing repositories remotely from a
3rd party
application. My preferred approach is to use pojo service(s) with
different
remote interfaces on top (SOAP, AMF, plain XML over HTTP, ...).
I found two issues which are related to this:
Admin interface: XML-RPC vs SOAP
http://jira.magnolia.info/browse/MAGNOLIA-589
commands: expose them as services
http://jira.magnolia.info/browse/MAGNOLIA-1335
In my opinion we should complete the set of commands (move, delete,
copy, create ,....) and expose them as simple services. The benefit
of this approach is, that this simple commands can be used in any
command chain and in workflows.
Looks like access to repositories is scattered over many different
classes,
sometimes using workspace, sometimes using session. It would be
nice to have
We are removing the direct workspace operations (expect import/
export): http://jira.magnolia.info/browse/MAGNOLIA-1225.
a single class with a well defined api. What should I consider when
I start
working on this topic? Is there any work in progress which could be
interesting for me?
in 3.1 the triple HierarchyManager, Content and NodeData will be
interfaces.
Thanks in advance for any useful advices.
We are thinking about using XFire (http://xfire.codehaus.org/)
O.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
