3 Replies Latest reply on Mar 9, 2012 2:38 PM by Randall Hauch

    Sequencing of new content added through SVN connector

    Michael Matthee Newbie

      Hi guys,


      I have been attempting to get SVN commits to be sequenced by JCR.

      The XmlSequencerIntegrationTest only seems to test files published directly to the node-graph structure (via the API).


      Does modeshape support sequencing of content sourced from SVN ?

      Or am I missing an essential configuration setting somewhere ?




      Using Modeshape 2.7.0-FINAL.


      If I use a simple JpaSource sequencing works out fine.

      However, when I attempt the very same sequencing using SVN, it fails.


      Here is my sequencer:


              <mode:sequencer jcr:name="XML File Sequencer" mode:classname="org.modeshape.sequencer.xml.XmlSequencer">
                  <mode:description>Sequences XML files loaded under '/files', extracting the contents into the equivalent JCR graph structure.</mode:description>    
                  <mode:pathExpression>//(*.(xml)[*])/jcr:content[@jcr:data] => /sequenced/xml/$1</mode:pathExpression>


      And here is my source configuration:


      <mode:sources jcr:primaryType="nt:unstructured">
        <mode:source jcr:name="test-data"
           mode:description="14592 The ModeShape SVN repository (anonymous access)"
           mode:username="michael" mode:password="michael"
           mode:defaultWorkspaceName="trunk" />


      And then my repository:


       <mode:repository jcr:name="test-data-repository">
        <mode:nodeTypes jcr:primaryType="mode:nodeTypes" />
        <namespaces jcr:primaryType="mode:namespaces" />
        <mode:options jcr:primaryType="options">
          <mode:option jcr:name="projectNodeTypes" mode:value="true"/>
          <mode:option jcr:name="jaasLoginConfigName" mode:value="modeshape"/>
          <mode:option jcr:name="systemSourceName" mode:value="system@store"/>
          <mode:option jcr:name="queryIndexDirectory" mode:value="${jboss.server.data.dir}/modeshape/repositories/store/indexes"/>                        <mode:option jcr:name="queryIndexesRebuiltSynchronously" mode:value="true"/>
          <mode:option jcr:name="rebuildQueryIndexOnStartup" mode:value="ifMissing"/>


      Would appreciate your help, as I really like Modeshape and I'm pushing and motivating for its adoption in our organisation.


      Thank you,


        • 1. Re: Sequencing of new content added through SVN connector
          Randall Hauch Master

          The ModeShape SVN connector does not currently monitor SVN for changes (made by other clients) and publish those changes as ModeShape events. As a result, ModeShape does not "see" these changes made by other clients.


          It is possible to add this functionality to the SVN connector, but that simply hasn't been high enough priority for the current contributors.

          • 2. Re: Sequencing of new content added through SVN connector
            Michael Matthee Newbie

            Thanks Randall,


            Ok ... I will have to add that functionality then ...

            you can consider me a fellow contributor for the time being


            I have decided to build a custom SVN connector that contains the sequencing feature.

            I've also logged a feature request MODE-1415


            If you guys consider my connector worthwile,

            then perhaps we could add it to the "built-in" connectors list.


            • 3. Re: Sequencing of new content added through SVN connector
              Randall Hauch Master

              We'd be very happy to have you contribute.


              Regarding the SVN connector, our recent 2.8.0.Final release was our last planned minor release on the 2.x branch. We have been planning to release a patch release (e.g., 2.8.1.Final, since we're only fixing bugs) sometime in late March or early April. Instead, we could consider issuing another minor release (e.g., 2.9.0.Final) to include the bug fixes and your improvements to the SVN connector.


              All new feature development has switched to the 3.0 branch (the 'master' branch in Git), and in 3.0 the connector API/SPI will be changing. We can talk more about that if you want, but it's not clearly defined yet as we've been focusing mostly on the core JCR TCK functionality. We'll obviously port the SVN connector, and we'd love to have it watch/poll for changes in the SVN repository and generate the corresponding events within ModeShape.