[jboss-jira] [JBoss JIRA] Closed: (JBPM-839) Can't store JSR170 node.

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-839?page=all ]

Tom Baeyens closed JBPM-839.
----------------------------

    Fix Version/s: jBPM jPDL 3.2
       Resolution: Done

improved the JCR documentation:

<chapter id="docmgmt">
  <title>Document management</title>
  
  <para>This is still an experimental feature.
  </para>

  <para>To enable this feature, you need to 
  uncomment the following line in the hibernate.cfg.xml:
  </para>
  
  <programlisting>&lt;mapping resource="org/jbpm/context/exe/variableinstance/JcrNodeInstance.hbm.xml"/&gt;</programlisting>
  
  <para>The document management support of jBPM is based on 
    <ulink url="http://www.jcp.org/en/jsr/detail?id=170">Java Content Repository</ulink>.
    That is a standard java specification for integrating document management
    systems into Java.  The basic idea is that jBPM supports storage of JCR nodes 
    as process variables.
  </para>
  
  <para>To store a node, the session, repository and path are extracted from the node 
  like this:
  </para>
  
  <programlisting>Session session = node.getSession();
Repository repo = session.getRepository();
Workspace wspace = session.getWorkspace();

// THE NODE REPOSITORY AND WORKSPACE NAME GOT TO CORRESPOND WITH A JBPM SERVICE NAME
repository = repo.getDescriptor(Repository.REP_NAME_DESC);
workspace = wspace.getName();
path = node.getPath();
  </programlisting>

  <para><emphasis role="bold">IMPORTANT NOTE:</emphasis> The name of the jbpm context service 
    MUST correspond with the name of the repository (repository.getDescriptor(Repository.REP_NAME_DESC)).
    This is to make the match between the reference stored in the jbpm process variables and 
    the repository when a node-variable is being loaded from the jBPM DB. When the JCR node process 
    variable is retrieved, each service name in the jbpm context will be matched against the 
    repository and workspace name stored.  The matching between jbpm context service and the 
    JCR session/repository names will go like this:
  </para>
  
  <itemizedlist>
    <listitem>if there is a jbpm context service named 'jcr' (lower case) that one will be 
    taken
    </listitem>
    <listitem>a service name that is equal to the repository name matches
    </listitem>
    <listitem>a service that starts with the repository name and ends with the workspace 
    name matches and takes preference over a service with the repository name
    </listitem>
  </itemizedlist>
  
  <para>The typical use case for this feature is a document approval process.  A document 
    needs to be approved and updated.  That document (e.g. a word document), can be 
    stored in a JCR-content-repository-node.  The node contains all the versions of the 
    document.  So that later in the process, people still can consult the historical 
    versions of the document.
  </para>

  <para>This feature was only tested with Jackrabbit.  Please refer to the JCR 
  implementation documentation for more information about library dependencies.
  </para>  
</chapter>


> Can't store JSR170 node.
> ------------------------
>
>                 Key: JBPM-839
>                 URL: http://jira.jboss.com/jira/browse/JBPM-839
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2 beta 2
>         Environment: windows XP english version
> JDK 1.5.10
> jackrabbit 1.2.1
>            Reporter: David Chan
>         Assigned To: Tom Baeyens
>             Fix For: jBPM jPDL 3.2
>
>         Attachments: jsr-cannot-persistent.txt
>
>
> when I run the test case org.jbpm.jcr.JcrDbTest ,  hibernate session can't be committed.
> see below key lines:
> ....deploy process.
> ....
>  ProcessInstance processInstance = jbpmContext.newProcessInstanceForUpdate("document approval");
> .....
> Node documentNode = processInstanceNode.addNode("document");
> .....
> contextInstance.setVariable("document", documentNode);
> //comment the line above, there's no exception.
> ....
> According to the chapter 12 titled 'Document management' of user guide,  it said:
> "Next, JCR Node's can be stored in the process variables"
> that seems doesn't work!
> I also viewed  the class file 'JcrNodeInstance'  and found it extends class 'VariableInstance',  
> the node-type variable ought support persistent.
> something else wrong?
> Details please see the attachment 'jsr-cannot-persistent.txt'

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira