Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-1109

Deployers should have openrdf on classpath before bigdata

    Details

      Description

      Per BLZG-1090 (RDR RDF parsers not always found), if the bigdata jar does not appear after the openrdf jar on the classpath then the openrdf parsers/writers can be registered after the bigdata specific classes with the result that certain functionality is lost.

      This is currently only an issue for the bigdata-specific extensions of the json data interchange for RDR (both RDF data and SPARQL result sets).

        Issue Links

          Activity

          Hide
          bryanthompson bryanthompson added a comment -

          @brad: please update me on the status of this ticket.

          Show
          bryanthompson bryanthompson added a comment - @brad: please update me on the status of this ticket.
          Hide
          bradbebee bradbebee added a comment -

          I validated this only occurs with the WAR deployment. The test is to start a Blazegraph instance, create an RDR-enabled KB, and load the example from the Wiki.

          @prefix : <http://bigdata.com> .
          @prefix foaf: <http://xmlns.com/foaf/0.1/> .
          @prefix dct:  <http://purl.org/dc/elements/1.1/> .
          
          :bob foaf:name "Bob" .
          <<:bob foaf:age 23>> dct:creator <http://example.com/crawlers#c1> ;
                               dct:source <http://example.net/homepage-listing.html> .
          
          Show
          bradbebee bradbebee added a comment - I validated this only occurs with the WAR deployment. The test is to start a Blazegraph instance, create an RDR-enabled KB, and load the example from the Wiki . @prefix : <http://bigdata.com> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix dct: <http://purl.org/dc/elements/1.1/> . :bob foaf:name "Bob" . <<:bob foaf:age 23>> dct:creator <http://example.com/crawlers#c1> ; dct:source <http://example.net/homepage-listing.html> .
          Hide
          bryanthompson bryanthompson added a comment -

          While it might only occur with the WAR, there is nothing about the "ant stage" target that ensures that this does not occur. The classpath is actually assembled using "find" as I recall and there is no intrinsic ordering guarantee.

          Show
          bryanthompson bryanthompson added a comment - While it might only occur with the WAR, there is nothing about the "ant stage" target that ensures that this does not occur. The classpath is actually assembled using "find" as I recall and there is no intrinsic ordering guarantee.
          Hide
          bradbebee bradbebee added a comment -

          TODO:

          1. Fix WAR file
          2. Fix deployers for explicit classpath reference

          Show
          bradbebee bradbebee added a comment - TODO: 1. Fix WAR file 2. Fix deployers for explicit classpath reference

            People

            • Assignee:
              beebs Brad Bebee
              Reporter:
              bryanthompson bryanthompson
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: