headers
imadhusudhanan | 2 Jan 2009 12:44
Favicon

New to JackRabbit ..

Dear All,

    I m new to JackRabbit. I would like to webdav enable my webapps which currently serves a web document
management system and the webdav feature would be an added feature. Pls do refer http://docs.zoho.com

    This is my setup do guide me in case I m wrong ,

    1) Wrote a WebDAVServlet extending SimpleWebdavServlet and implemented the getRepository method which
bears the FirstHops.java code as mentioned in the jackrabbit home.
    2) an entry in webdav make for accessing the WebdavServlet done !!
    3) Tried to access the servlet thru the Linux webdav client cadaver as below,

    Observations ::

    1) as soon as the server is started a repository is created with repository.xml in the same directory. Also
the default workspace and security workspaces are created. 

    
[test <at> localhost ~]$ cadaver http://localhost:8080/webdav
Authentication required for Jackrabbit Webdav Server on server `localhost':
Username: test
Password:
Could not open collection:
500 Internal Server Error
dav:/webdav/? 

    I also get this exception .. 

                    java.lang.NullPointerException
        at org.apache.jackrabbit.server.SessionProviderImpl.getSession(SessionProviderImpl.java:55)
(Continue reading)

Permalink | Reply | 1 comment |
headers
jira | 4 Jan 2009 08:20
Picon
Favicon

Subscription: open issues

Issue Subscription
Filter: open issues (294 issues)
Open Issues for Apache Jackrabbit
Subscriber: jackrabbitdev

Key         Summary
JCR-1918    DbDataStore keeps ResultSets open
            https://issues.apache.org/jira/browse/JCR-1918
JCR-1916    Inconsistent primary type / definition if adjusting child items fails
            https://issues.apache.org/jira/browse/JCR-1916
JCR-1915    Node.setPrimaryNodeType should only redefine child-definitions that are not covered by the
new effective nt
            https://issues.apache.org/jira/browse/JCR-1915
JCR-1914    Inconsistent jcr:mixinTypes if removing a mixin type failes upon clean-up
            https://issues.apache.org/jira/browse/JCR-1914
JCR-1911    missing test case for creating a binary property of length 0
            https://issues.apache.org/jira/browse/JCR-1911
JCR-1909    Property collectionClassName of  CollectionDescriptor is never used 
            https://issues.apache.org/jira/browse/JCR-1909
JCR-1908    Add lifecycle callback feature
            https://issues.apache.org/jira/browse/JCR-1908
JCR-1906    Make observation polling time configurable
            https://issues.apache.org/jira/browse/JCR-1906
JCR-1905    Occasional OCM test failures
            https://issues.apache.org/jira/browse/JCR-1905
JCR-1897    java.lang.NoSuchMethodError: org.apache.jackrabbit.value.ValueFactoryImpl.getInstance()Ljavax/jcr/ValueFactory
            https://issues.apache.org/jira/browse/JCR-1897
JCR-1895    Different behaviors between insert and update of a collection
            https://issues.apache.org/jira/browse/JCR-1895
JCR-1894    Word doc extraction problem
(Continue reading)

Permalink | Reply | 0 comments |
headers
imadhusudhanan | 5 Jan 2009 12:06
Favicon

Collection Not Found ..

Dear All,

    I have a problem while accessing the repository via cadaver. 
    I configured the repository manually and this is all the repository.xml

    
<?xml version="1.0" encoding="ISO-8859-1"?>
<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"/>
                <LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule">
                        <param name="anonymousId" value="anonymous"/>
                </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.xml.XMLPersistenceManager" />
                <SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
                        <param name="path" value="${wsp.home}/index" />
                </SearchIndex>
        </Workspace>
        <Versioning rootPath="${rep.home}/versions">
                <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
                        <param name="path" value="${rep.home}/versions"/>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jukka Zitting (JIRA | 5 Jan 2009 16:59
Picon
Favicon

Created: (JCR-1919) Update copyright year to 2009

Update copyright year to 2009
-----------------------------

                 Key: JCR-1919
                 URL: https://issues.apache.org/jira/browse/JCR-1919
             Project: Jackrabbit
          Issue Type: Improvement
            Reporter: Jukka Zitting
            Priority: Trivial

Our normal license headers don't contain copyright years, but the NOTICE.txt files do. We should update
the year to 2009 where appropriate.
Permalink | Reply | 1 comment |
headers
Alexander Klimetschek | 5 Jan 2009 17:07
Favicon

Re: New to JackRabbit ..

On Fri, Jan 2, 2009 at 12:44 PM, imadhusudhanan
<imadhusudhanan <at> zohocorp.com> wrote:
>    I also get this exception ..
>
>                    java.lang.NullPointerException
>        at org.apache.jackrabbit.server.SessionProviderImpl.getSession(SessionProviderImpl.java:55)

I have no exact idea about this error, but from looking at the code
[1], it seems the repository instance used by the webdav servlet is
null. Maybe there are other errors in the log before that indicate
some problem with the repository startup...

[1] https://svn.apache.org/viewvc/jackrabbit/tags/1.5.0/jackrabbit-jcr-server/src/main/java/org/apache/jackrabbit/server/SessionProviderImpl.java?view=annotate

Regards,
Alex
Permalink | Reply | 0 comments |
headers
Alexander Klimetschek | 5 Jan 2009 17:37
Favicon

Re: Collection Not Found ..

On Mon, Jan 5, 2009 at 12:06 PM, imadhusudhanan
<imadhusudhanan <at> zohocorp.com> wrote:
>            bash> cadaver http://localhost:8080/webdav/repository/default
>                Authentication required for Jackrabbit Webdav Server on server `localhost':

Try to enter a password for the login - any string except the empty
one should do it. The SimpleLoginModule has 3 access levels: anonymous
(if using the username given as "anonymousId") (lowest, only
read-access), normal users (any user/pw combination) and
administrative user (when using the username given as "adminId"
parameter in the SimpleLoginModule config).

Hope that helps,
Alex
Permalink | Reply | 1 comment |
headers
Jukka Zitting | 5 Jan 2009 17:51
Picon
Gravatar

Jackrabbit 1.5.1 release plan

Hi,

We already have some fixes for 1.5.0 and I'd like to push them out
quite soon as some of them (most notably the RMI behaviour of the
standalone server) affect the documentation I'm about to write.

Please let me know of any favourite fixes you'd like to see in 1.5.1
by tagging them appropriately in Jira by the end of this week. I'll
target to do the release next week.

BR,

Jukka Zitting
Permalink | Reply | 8 comments |
headers
David Izatt (JIRA | 5 Jan 2009 17:55
Picon
Favicon

Created: (JCR-1920) Upgrade from 1.4.5 to 1.5 creates exception for LDAP authentication

Upgrade from 1.4.5 to 1.5 creates exception for LDAP authentication
-------------------------------------------------------------------

                 Key: JCR-1920
                 URL: https://issues.apache.org/jira/browse/JCR-1920
             Project: Jackrabbit
          Issue Type: Bug
          Components: security
    Affects Versions: 1.5.0
         Environment: Windows XP SP2 & Java
            Reporter: David Izatt

Upgrading Jackrabbit from 1.4.5 to 1.5 has created an LDAP exception.  The configuration file which has not
changed (except for the adding the new SimpleSecurityManager as required) is the default with the
following substituted for the LoginModule:

        <LoginModule class="com.sun.security.auth.module.LdapLoginModule">
            <param name="userProvider" value="ldap://localhost/ou=people,dc=example,dc=com" />
            <param name="userFilter" value="(&amp;(uid={USERNAME})(objectClass=inetOrgPerson))" />
            <param name="authzIdentity" value="{USERNAME}" />
            <param name="debug" value="true" />
        </LoginModule>

This configuration worked correctly and I was able to authenticate properly with Jackrabbit 1.4.5
The same configuration with 1.5 throws the following exception:

javax.jcr.LoginException: com.sun.security.auth.module.LdapLoginModule does not support
'userProvider: com.sun.security.auth.module.LdapLoginModule does not support 'userProvider:
com.sun.security.auth.module.LdapLoginModule does not support 'userProvider
        at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1414)
(Continue reading)

Permalink | Reply | 16 comments |
headers
Alexander Klimetschek (JIRA | 5 Jan 2009 18:07
Picon
Favicon

Commented: (JCR-1920) Upgrade from 1.4.5 to 1.5 creates exception for LDAP authentication


    [
https://issues.apache.org/jira/browse/JCR-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660820#action_12660820
] 

Alexander Klimetschek commented on JCR-1920:
--------------------------------------------

The error message "com.sun.security.auth.module.LdapLoginModule does not support 'userProvider" is
coming from Sun's LdapLoginModule. Maybe there is a typo in the configuration file, ie. a superfluuous
single quote before "userProvider". Or the configuration of the login module changed with a new JVM version...

> Upgrade from 1.4.5 to 1.5 creates exception for LDAP authentication
> -------------------------------------------------------------------
>
>                 Key: JCR-1920
>                 URL: https://issues.apache.org/jira/browse/JCR-1920
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.5.0
>         Environment: Windows XP SP2 & Java
>            Reporter: David Izatt
>
> Upgrading Jackrabbit from 1.4.5 to 1.5 has created an LDAP exception.  The configuration file which has
not changed (except for the adding the new SimpleSecurityManager as required) is the default with the
following substituted for the LoginModule:
>         <LoginModule class="com.sun.security.auth.module.LdapLoginModule">
>             <param name="userProvider" value="ldap://localhost/ou=people,dc=example,dc=com" />
>             <param name="userFilter" value="(&amp;(uid={USERNAME})(objectClass=inetOrgPerson))" />
(Continue reading)

Permalink | Reply | 0 comments |
headers
Grégory Joseph (JIRA | 5 Jan 2009 19:07
Picon
Favicon

Commented: (JCR-1778) BindableRepositoryFactory doesn't handle repository shutdown


    [
https://issues.apache.org/jira/browse/JCR-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660836#action_12660836
] 

Grégory Joseph commented on JCR-1778:
-------------------------------------

Same goes if you replace {{repository.shutdown()}} by a call to
{{RegistryHelper.unregisterRepository}} which is even more worrying. The issue seems to be due to the
static cache of BindableRepositoryFactory.
I can reproduce this with 1.4.6 and 1.5.0, not with 1.4.5

> BindableRepositoryFactory doesn't handle repository shutdown
> ------------------------------------------------------------
>
>                 Key: JCR-1778
>                 URL: https://issues.apache.org/jira/browse/JCR-1778
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> The BindableRepositoryFactory class keeps a cached reference to a repository even after the repository
has been shut down.
> This causes the following code snippet to fail with an IllegalStateException:
>         Hashtable environment = new Hashtable();
>         environment.put(
>                 Context.INITIAL_CONTEXT_FACTORY,
(Continue reading)

Permalink | Reply | 0 comments |

Gmane