You can always take the Apache Chemistry project, and adapt that to our GIT repository.
Mark
On 13 Aug 2013, at 12:40, Alexander Herwix <alex(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 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 VFS implementation is touted to be pluggable, so asset management
with a custom VFS provider could become a real pain. This might be an edge use case as not
everyone needs to provide a custom-ui and run the wb at the same time, however, I still
think it's a valid one, especially if you think about native mobile apps.
Anyway, keep up the good work.
Cheers, Alex
Am 12.08.2013 um 19:42 schrieb Mark Proctor <mproctor(a)codehaus.org>:
>
> On 12 Aug 2013, at 18:28, Alexander Herwix <alex(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 forum, where they said that there should be one but that it's not documented yet.
I have found some repository, group stuff exposed (drools-wb-rest), process-execution
(jbpm) but no real asset authoring.
>
>>
>> The reason I need this access, is to use the kie-wb in parallel to my own gui
with the kie-wb as admin interface. I know there have been improvements with
user-extendable editors via uberfire and GWT but with the level of documentation as it is
right now, I can't make that dive now. But with my data already in the wb it should be
trivial to port my user-facing gui in the future if the need should arise.
> We will not being doing any rest CRUD apis; although there are other rest api's
for administration stuff. As this is just git a variety of git apis exist for every
platform already. We have however done a java nio2 back port (api copy, with namespace
change), vfs that works with GIT remotely. But it is obviously java only.
>
> This should probably suffice any needs you have, for accessing and integrating with
content.
>>
>> What do you guys think? Is this possible with the upcoming droolsjbpm 6 release?
Could anyone provide at least rudimentary documentation of (all) the REST APIs? It would
really help if there would be at least a unified feature list of what to expect in open
APIs of the kie-wb (so for jbpm as well as drools).
> We don't ned to provide docs for how GIT works, but we will provide docs on the
rest apis we do support - just nothing yet. Still working over time on fixing critical
bugs.
>>
>> Thanks for any help on advance!
>>
>> Cheers, Alex
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users