Hey Mark,
first of all thanks for the information but I disagree. I would see providing a
CRUD api as a helpful feature as this would provide a single place for asset
management. Having access via GIT is fine, but then I have to sync the repo
location (changes, renames, deletes) and the GIT
If you really need a programatic CRUD with a GIT access abstracted, you can use
the VFS API.
On Aug 13, 2013, at 8:40 AM, Alexander Herwix a...@herwix.com wrote:
Hey Mark,
first of all thanks for the information but I disagree. I would see providing
a CRUD api as a helpful feature as
Hey Alexandre,
I'm sorry but I don't really understand what you mean.
If you mean that I can implement a VFS in my own App then sure I could do this
but as I said that would introduce the problem of keeping the configuration of
both VFS in sync. Not insurmountable, but I still think that it
You can always take the Apache Chemistry project, and adapt that to our GIT
repository.
http://chemistry.apache.org
Mark
On 13 Aug 2013, at 12:40, Alexander Herwix a...@herwix.com wrote:
Hey Mark,
first of all thanks for the information but I disagree. I would see providing
a CRUD api as
Hey guys,
I really love the new wb-apps, but documentation is really pretty sparse right
now, so maybe you guys can help me out :)
Is there any documentation on the authoring REST-Api? I have already asked on
the jbpm forum, where they said that there should be one but that it's not
On 12 Aug 2013, at 18:28, Alexander Herwix a...@herwix.com wrote:
Hey guys,
I really love the new wb-apps, but documentation is really pretty sparse
right now, so maybe you guys can help me out :)
Is there any documentation on the authoring REST-Api? I have already asked on
the jbpm
