Re: AW: Anyone using JCR Browser???

Thu, 15 Feb 2007 00:42:48 -0800 

Hi Avim,


Can't wait to hear more details:)
currently I'm creating a concept for the successor project of the JCR Browser. As soon as I have an up to date proposal I will post it also here in the users mailing list to align the requirements of the project. 

Bye,

Sandro



Sandro Böhme wrote:

Hi Avim,


it looks good. I think that can work. In the next version that I will 
release the shutdown() method will not be used anymore. There is a 
solution to use the Jackrabbit functionality that shuts down the 
repository as soon as the last session logged out.


 > Are there any plans to add write functionalities?

Not to add write functionality but to create a new project with writing 
capabilities.


Regards,

Sandro

avim schrieb:

I've just refactored the local Jackrabbit "connector" plugin to work with
1.2.1. Seems fine.
The attached plugin doesn't include some large jars, please add them
manually.

http://www.nabble.com/file/6482/plugins.zip plugins.zip 
Are there any plans to add write functionalities?


Sandro Boehme wrote:

Hi,

the UI-Plugin of the JCR Browser does not depend on a JCR implementation
like Jackrabbit. It does not even know the Jackrabbit jar files. This
means the JCR Browser is "pure JCR". It uses some kind of "connector"
architecture that is based on Eclipse Plugins. At the moment there are
three connectors. There is one for the jLibrary DMS, one for a RMI
connection and one local Jackrabbit connection. It is also possible to
create a connector for Alfresco, Exo or other JCR implementations. The
local Jackrabbit connection contains the Jackrabbit jar's. In earlier
days
I explicitly called the shutdown() method in the local Jackrabbit
connection because for some reason it did not work in an other way. I
will
try to only call the "logout" method. As this logs out the only
javax.jcr.Session it should automatically shutdown the repository. I
will
try that when I have the time.

Bye,

Sandro

-----Ursprüngliche Nachricht-----

Von: avim [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 6. Februar 2007 14:27

An: [email protected]
Betreff: Re: Anyone using JCR Browser???


It's not gonna work, cause jackrabbit's api and hierarchy(CD) has been
slightly changed.
Unfortunately these tools are not "pure JCR" and have code dependencies
on
jackrabbit...


Sandro Böhme wrote:

Glaucio Scheibel schrieb:

I change the jars from JCR browser and it works, only disconnecting 
is still freezing (I have to quit eclipse to do this).

I'm already in the process to test the update of the local repository 
connector to Jackrabbit 1.2.1 and experienced the same behavior. The 
call to repository.shutdown()

(http://jackrabbit.apache.org/api-1/org/apache/jackrabbit/core/Reposit

oryImpl.html#shutdown()) never comes back. I will go into the details 
to find out, what the reason is as soon as I have the time.


Regards,

Sandro


Glaucio

avim wrote:

The reason is lucene & indexes.

If the repository was touched by 1.2.1, in order to access it by JCR 
browser or jackrabbit viewer you must delete the indexes 
manually(every time!):

repository/index, workspaces/default/index etc.
Not such a good idea, but it works...
I hope these tools will be upgraded soon...
Does any one know alternative tools?


Nithya Mani wrote:

 

Hi,


I am using JCR browser 0.9 Eclipse plug-in with 
jackrabbit-core-1.0.jar. I tried with the local jackrabbit 
repository. There is a problem during login.
I have set only 'userid' as user name for Simple Credentials of JCR 
browser.

It doesn't throw any error message. It just says '-1:-1:-1'.
It was not possible to login. Please check the credentials.
-1: -1: -1


What does the meaning of this message? Here is the repository.xml 
file I am using.

<Repository>
    <FileSystem
class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
        <param name="path" value="${rep.home}/repository"/>
    </FileSystem>
      <Security appName="Jackrabbit">
        <AccessManager
class="org.apache.jackrabbit.core.security.SimpleAccessManager">

        </AccessManager>

        <LoginModule
class="org.apache.jackrabbit.core.security.SimpleLoginModule">
                  </LoginModule>
    </Security>

    <Workspaces rootPath="${rep.home}/workspaces"
defaultWorkspace="default"/>
    <Workspace name="${wsp.name}">
        <FileSystem
class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
            <param name="path" value="${wsp.home}"/>
        </FileSystem>
        <PersistenceManager
class="org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager">
           <param name="driver"
value="oracle.jdbc.driver.OracleDriver"/>
           <param name="url"
value="jdbc:oracle:thin:@xxxx:1521:orcl"/>
           <param name="user" value="nithya"/>
           <param name="password" value="nithya"/>
           <param name="schema" value="oracle"/>
           <param name="schemaObjectPrefix" value="${wsp.name}_"/>
           <param name="externalBLOBs" value="false"/>
       </PersistenceManager>
        <SearchIndex
class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
            <param name="path" value="${wsp.home}/index"/>
        </SearchIndex>
    </Workspace>

    <!--
        Configures the versioning
    -->

    <Versioning rootPath="${rep.home}/version">               
<FileSystem

class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
            <param name="path" value="${rep.home}/version" />

        </FileSystem>       
        <PersistenceManager

class="org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager">
           <param name="driver"
value="oracle.jdbc.driver.OracleDriver"/>
           <param name="url"
value="jdbc:oracle:thin:@blizzard:1521:orcl"/>
           <param name="user" value="nithya_registry"/>
           <param name="password" value="nithya"/>
           <param name="schema" value="oracle"/>
           <param name="schemaObjectPrefix" value="version_"/>
           <param name="externalBLOBs" value="false"/>
       </PersistenceManager>

    </Versioning>

    <SearchIndex
class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
        <param name="path" value="${rep.home}/repository/index"/>
    </SearchIndex>
</Repository>

Am I missing anything?
Regards,

Nithya Mani
Senior Developer, webMethods
[EMAIL PROTECTED]
IM: nithya_infravio (Yahoo)

    
    
       


-----Original Message-----

From: Sandro Boehme [mailto:[EMAIL PROTECTED] Sent: 
Thursday, January 25, 2007 3:14 PM

To: [email protected]
Subject: Re: Anyone using JCR Browser?

Hi Waldemar,


you are right the local repository (deployment model 1) connection 
of the JCR Browser uses the Jackrabbit 1.0 libraries in the Eclipse 
classpath. But the Eclipse plugin classpath is not configurable at 
runtime. This means you cannot change to a newer Jackrabbit version 
by design while using the local repository connection of the JCR

Browser.


But you can use the remote repository (deployment model 3) 
connection method of the JCR Browser to connect to a repository 
version of your choice. You will find a short how-to in the 
ReadMeFirst.txt file of the JCR Browser distribution. If I can help 
you any further you can either ask in the mailing list of the JCR 
Browser or here and I will help you get it running.


Best regards,

Sandro

--
https://www.xing.com/profile/Sandro_Boehme
http://www.linkedin.com/in/sandroboehme
http://www.wingsuit.de


    

  



--
View this message in context:
http://www.nabble.com/RE%3A-Anyone-using-JCR-Browser----tf3172922.html#a8825896
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
































					Reply via email to