Hi Melanie, Sorry, I could not answer you as I was in holiday. I will start to work on August 27. In my demonstration, I was using CRX CMS. But to connect CRX, I have and additional bundle to be added to the OSGi environment. I can provide you that bundle when I'm back.
I did not access to the repo via HTTP. In my demonstration, a session is obtained together with a session key after giving the necessary credentials e.g username, password, rmi endpoint. And that session key is used by CMS Adapter to access to the repo. Best, Suat On Mon, Aug 20, 2012 at 12:11 PM, Melanie Reiplinger < [email protected]> wrote: > Hi Suat, > > I cannot access my jackrabbit repo via xmlhttp either (although curl works > fine), so this might as well be a CORS access problem. In your demo, did > you have to somehow provide access to the repo (by setting headers etc)? > > Best, > Melanie > > Am 15.08.2012 11:15, schrieb Melanie Reiplinger: > > Hi Suat, >> >> Am 13.08.2012 13:35, schrieb Suat Gonul: >> >>> In any case, I guess that you >>> need to configure a RDF Bridge through the >>> {stanbol}/system/console/**configMgr interface. There you should find >>> the >>> "Apache Stanbol CMS Adapter Default RDF Bridge Configurations". In that >>> configuration you specify the root path in the CMS to be exported to the >>> RDF. >>> >>>> by that you mean the content repository path? This means that I set >>>> there the path to my content repository? >>>> >>> Yes, you set there a path residing in the content repository. >>> >>> I have set up a jackrabbit workspace with some toy nodes in it. To >>>> access it remotely, I'd configure something like >>>> http://[myserver]/server/ >>>> <http://lnv-89012.dfki.uni-sb.**de:9002/server/default/node1<http://lnv-89012.dfki.uni-sb.de:9002/server/default/node1>>, >>>> but then >>>> I can work with this repository exclusively, right? >>>> >>> I cannot access the URL you gave, but I guess you should give /node1 >>> path to export it as RDF. I didn't get your question about working >>> exclusively with the repository. But, you already seem to work on the >>> default repository of Jackrabbit running on your server. >>> >>> >> I tried with several paths, none will work. >> My remote repository stub is >> http://lnv-89012.dfki.uni-sb.**de:9002/rmi<http://lnv-89012.dfki.uni-sb.de:9002/rmi> >> . >> (you cannot access those URIs because they are in a closed network) >> For accessing the content repository, I should use (according to my >> jackrabbit guidelines): >> http://lnv-89012.dfki.uni-sb.**de:9002/server<http://lnv-89012.dfki.uni-sb.de:9002/server>to >> access all workspaces of myJCR repository >> http://lnv-89012.dfki.uni-sb.**de:9002/server/default/jcr:**rootto<http://lnv-89012.dfki.uni-sb.de:9002/server/default/jcr:rootto>access >> a single workspace (example with workspace named 'default'). -> this >> one is also where I can navigate to with my browser, so this should then be >> the correct path I guess. >> >> >> But I always get the same error about >> org.apache.stanbol.cmsadapter.**jcr.mapping.JCRRDFMapper Failed to >> retrieve node having path: <thePath> or its childr >> >> I'm an absolute beginner with content repositories, using jackrabbit for >> the first time and I'm really unsure of what would have to work if >> everything was correct, but I can see my repository in the jackrabbit >> console and I also can see that my nodes are existing, and the info command >> tells me that everything looks like I would expect: >> >> >> >> >> >> Repository: >> http://lnv-89012.dfki.uni-sb.**de:9002/rmi<http://lnv-89012.dfki.uni-sb.de:9002/rmi> >> User : admin >> Workspace : default >> Node : / >> >> I looked at your paper ("Semantic Content Management with Apache >> Stanbol") and saw that you used jackrabbit in the demo, too. Is there some >> publicly accessible repository I could use for testing (so that I see what >> the path I have to specify looks like in a working example)? >> >> best, >> melanie >> >> >
