yeah I was thinking not so much from a JCR point of view (as it is a implementation detail not to be exposed), but more from the fact that you could use WebDAV to save/load resources. I have see this done with a document templating system - where business analsyts used an RCP app which talked WebDAV to the content store.
<br><br>MS and Open Office can also save to WebDAV URLs. Just another way to poke around in the repo - I have heard cries of pain from WebDAV, so I don't think I will do it for now.<br><br><div><span class="gmail_quote">
On 2/19/07, <b class="gmail_sendername">James Williams</b> <<a href="mailto:james.williams@redhat.com">james.williams@redhat.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Most of the Drools prospects could care less about JCR. I haven't heard<br>any direct prospect desire anything JCR related. But, the prospect<br>profiles look like:<br><br>Group #1: Want a way to expose business rules authoring/mgmt to
<br>analysts. Are talking to ILog and Fair Isaac but don't wan to pay for<br>expensive, proprietary stuff.<br><br>Group #2: They are bread/butter savvy Java dev groups looking to<br>de-couple rules from biz logic code. I wish we had more of these calls.
<br>Maybe a white paper/article blitz is warranted.<br><br>Group #3: They want to do workflow, not rules.<br><br>Group #4: They want an ESB that supports workflow, rules, messaging,<br>tranformation, service registry, provides robust management and
<br>something that'll wash their car too.<br><br>I had to beef up my insurance-quote demo to use decision tables in<br>addition to DRL/DSL to support group #1 (still haven't updated the wiki<br>but will do it soon b/c the demo works w/out svn now and is packaged
<br>mostly as an EAR). JCR has come up in 1 of my ISV calls, but I think it<br>was more of a "nice to have" than anything else.<br><br>So, prospects are not clamoring for it now, but we are speaking to a lot<br>
of rules ignorant folks that don't really know what the underlying<br>architecture should look like. This is more of a prospect breakdown than<br>anything else, but I think it highlights that the field is telling us to
<br>focus on knobs/switches that hide what's underneath the hood.<br><br>HTH,<br>James<br><br>On Mon, 2007-02-19 at 11:00 +1000, Michael Neale wrote:<br>> For anyone who knows anything about JCR/JSR-170, there is a "node
<br>> type" called nt:file, which represents a file type resource.<br>><br>> We have a "asset" type node at the moment, which is kind of analagous<br>> to a file (and it is stored in folders).<br>
><br>> As the repository is kind of like a filesystem (ine one sense, in<br>> another its queryable like a database and presented like one) it is<br>> possible, if we choose, to expose things via WebDAV for applications
<br>> like Excel to save into. This opens up a lot of possibilities.<br>><br>> I wanted to get peoples thoughts on making our "asset" node be an<br>> "nt:file" type - from an API point of view most of this can and will
<br>> be hidden, more of a small structural change to allow future<br>> flexability. At the moment the asset type just stored content as a<br>> string or byte[] as needed - with an nt:file it would be slightly more
<br>> formally defined to be closer to a file.<br>><br>> Is it worth the effort? Is this something that excites or interests<br>> people:<br>><br>> FYI, if one was to browser the repo as a (virtual) file system, it
<br>> would look something like:<br>><br>> /root<br>> /packages<br>> /package name<br>> /assets<br>> /Rule1.drl<br>> /Rule2.drl....<br>> /Something.xls
<br>> /another package ....<br>> /categories ...<br>> /statuses<br>> /configuration ...<br>><br>><br>> _______________________________________________<br>> rules-dev mailing list<br>> <a href="mailto:rules-dev@lists.jboss.org">
rules-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>--<br>James Williams <<a href="mailto:james.williams@redhat.com">
james.williams@redhat.com</a>><br>Red Hat<br><br>_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev">
https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br>