Ben,

Argh. This looks like a problem in mulgara-core-2.0.6.jar. It should 
include org.mulgara.client.jrdf but somewhere between 2.0.0 and 2.0.5 it 
disappeared. It looks like a typo in mulgara's build file, since the Ant 
target that builds the jar still depends on client-jrdf, but now no 
longer includes its contents.

I'm traveling for the next few days, but I can see about repackaging 
mulgara-core next week. In the meantime, if you grab Mulgara 2.0.6 and 
add the client-jrdf jar to Fedora's WEB-INF/lib dir, that might do the 
trick.

Eddie

On 10/30/2008 08:26 PM, Benjamin O'Steen is rumored to have said:
> I have the mulgara 3.0.0 instance running fine, using the "-s fedora" to
> give it the fedora servername. Fedora is set to run remote, and set the
> host param to localhost, and the servername to 'fedora'.
> 
> Both run fine, going to http://localhost:8080/fedora/risearch redirects
> me to the webui nicely, and this is functioning fine from what I can
> tell (I can create, drop and add rdf graphs and triples)
> 
> However, I am missing the bit of information about how fedora syncs to
> mulgara - what is the Graph URI? I have tried creating
> <rmi://localhost/fedora#rdfs and #ri> in case they are the intended
> graph uris, but this doesn't work. The fedora-rebuild.sh returns the
> following:
> 
> "NOTE: You must now manually re-initialize (clear) 
>       the existing triplestore.  The RI rebuilder
>       cannot yet automatically perform this step 
>       for this type of triplestore.  Press enter
>       when finished.
> 
> Initializing triplestore interface...
> Error: Failed to initialize new Resource Index
> 
> fedora.server.errors.ResourceIndexException: Failed to initialize new
> Resource Index
>         at
> fedora.server.resourceIndex.ResourceIndexRebuilder.start(ResourceIndexRebuilder.java:149)
>         at
> fedora.server.utilities.rebuild.Rebuild.<init>(Rebuild.java:81)
>         at
> fedora.server.utilities.rebuild.Rebuild.main(Rebuild.java:424)
> Caused by: org.trippi.TrippiException: Failed to create Client JRDF
> Graph.
>         at
> org.trippi.impl.mulgara.MulgaraSession.getElementFactory(MulgaraSession.java:180)
>         at
> org.trippi.impl.mulgara.MulgaraConnector.init(MulgaraConnector.java:165)
>         at
> org.trippi.TriplestoreConnector.init(TriplestoreConnector.java:24)
>         at
> fedora.server.resourceIndex.ResourceIndexRebuilder.start(ResourceIndexRebuilder.java:142)
>         ... 2 more
> Caused by: org.jrdf.graph.GraphException: Failed to create Client JRDF
> Graph.
>         at
> org.mulgara.server.driver.JRDFGraphFactory.newClientGraph(JRDFGraphFactory.java:186)
>         at
> org.trippi.impl.mulgara.MulgaraSession.getElementFactory(MulgaraSession.java:178)
>         ... 5 more
> Caused by: java.lang.ClassNotFoundException:
> org/mulgara/client/jrdf/RemoteGraphProxy
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:164)
>         at
> org.mulgara.server.driver.JRDFGraphFactory.getClassTypes(JRDFGraphFactory.java:266)
>         at
> org.mulgara.server.driver.JRDFGraphFactory.newClientGraph(JRDFGraphFactory.java:179)
>         ... 6 more
> 
> 
> Is there a step I am missing?
> 
> Ben
> 
> 
> On Wed, 2008-10-29 at 13:48 -0400, Greg Jansen wrote:
>> Hey, we've got Mulgara running in remote mode as described below, using 
>> Mulgara's default #server1 servername.  The fedora-rebuild scripts 
>> require Mulgara to be running, but not Fedora.  So what I did was create 
>> two /etc/init.d scripts, one to start both and one to just start Mulgara 
>> alone.
>>
>> I do think the architecture could be further decoupled by allowing 
>> fedora to run while also reindexing the resource index.  However, you've 
>> got to block or track all object changes while that the index process 
>> completes, something that seems more likely in the next release, which 
>> promises JTA support.  Edwin, do fedora developers have any plans or 
>> thoughts about that?
>>
>> thanks,
>> Greg Jansen
>> Carolina Digital Repository
>> UNC Chapel Hill
>>
>> Edwin Shin wrote:
>>> (moving to fedora users)
>>>
>>> On 10/29/2008 11:15 PM, Benjamin O'Steen is rumored to have said:
>>> <snip/>
>>>
>>>   
>>>> Some documentation on the limits/breadth of support would be most
>>>> appreciated, as the statement 'SPARQL support' might pose problems for
>>>> managing user expectations. 
>>>>     
>>> I'm not positive what the latest state of SPARQL support in Mulgara 
>>> is--it's either complete or just about. Mid-summer (before Mulgara 
>>> 2.0.0), about 95% of SELECT queries were supported, where the main thing 
>>> missing was ordering by expression instead of by a variable. Also at 
>>> that time, ASK, DESCRIBE and CONSTRUCT were not supported, but these are 
>>> now supported (or at least I see the code for it now).
>>>
>>>   
>>>> (So far, I have got the in-vm mulgara to understand a SELECT query, but
>>>> it fails to reply with any results. A person with only SPARQL experience
>>>> might be similarly stuck.)
>>>>     
>>> You'll still need to include a FROM clause in your SPARQL query if that 
>>> helps (e.g. "select * from <#ri> where { ?s ?p ?o }")--there's no 
>>> default model set, which come to think of it, we should consider doing.
>>>
>>>   
>>>> On a similar note, I was also interested in having an external Mulgara
>>>> store coupled to Fedora. If anyone has a walkthrough on how to set this
>>>> up, I'd love to read it. I have set the host param in the fedora.fcfg,
>>>> and have Mulgara's web UI happily running on /risearch. However, I
>>>> haven't been able to guess the process for creating the graph for Fedora
>>>> to use, mainly due to my inexperience with native mulgara, so rebuilding
>>>> fails, and Mulgara seems empty.
>>>>     
>>> In datastore configuration for Mulgara in fedora.fcfg, set "remote" to 
>>> "true", and set the "host" (and "port" if you're not using the default 
>>> 1099) parameter to the host Mulgara is running on (e.g. "localhost"). 
>>> You also need to ensure that the serverName parameter matches your 
>>> remote instance of Mulgara (e.g. start mulgara with "-s fedora" or 
>>> change serverName in fedora.fcfg to "server1", which is Mulgara's 
>>> default). I think that's it ;) Let me know if that works for you. Then 
>>> this should go up on the wiki.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to