Amending my prior post, the spec is probably the best reference for the
on-parent-version values.
On 8/15/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
I can't answer all of your questions, and I'm looking for a some decent
docs in this area that bridge the gap between the Jackrabbit CND docs an
I can't answer all of your questions, and I'm looking for a some decent docs
in this area that bridge the gap between the Jackrabbit CND docs and the
specification, but in regards to whether the new version of NodeA will have
child nodes NodeB and NodeC, this depends on how the child nodes are
dec
I have a question about versioning.
NodeA has 2 child nodes NodeB and NodeC
NodeA and NodeC is versionable. NodeB is not.
If I check out NodeA, can I start making changes to NodeA and all of its
children, including NodeC? Then save and checkin NodeA? If so, will I get
a Version that includes
I'm looking for something in Jackrabbit that is like Slide's
ContentAdapter that lets you modify a document's properties or storage
location, or veto a document as it put into the repository. Is
something like that available?
Specifically, I'd like to have someone drop a document into one
locati
As a different option, on a project a few years back we built a web-based
XML editor using chiba[1] to transform XML documents stored in a CMS
(Documentum) to XHTML forms via XForms. Since chiba does the transformation
server-side, performance was pretty good, completely cross-browser, and we
coul
