jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-132) BindableRepositoryFactory requires exact resource type
Date Fri, 10 Jun 2005 12:11:47 GMT
     [ http://issues.apache.org/jira/browse/JCR-132?page=all ]

Jukka Zitting updated JCR-132:
------------------------------

      Component: config
        Summary: BindableRepositoryFactory requires exact resource type  (was: Too BindableRepositoryFactory)
    Description: 
The org.apache.jackrabbit.jndi.BindableRepositoryFactory class requires the exact class name
org.apache.jackrabbit.jndi.BindableRepository to be specified for the JNDI resource that the
factory is responsible for. However the current deployment model 2 howto document suggest
that the more generic interface name javax.jcr.Repository be used instead. Currently this
suggested configuration results in a null JNDI resource .

This issue should be fixed by either fixing the documentation (I can do this) or by relaxing
the code in BindableRepositoryFactory. I'll attach a patch that does the latter, please comment
on what you think is the best solution.

This issue was detected during the mailing list thread
http://www.mail-archive.com/jackrabbit-dev@incubator.apache.org/msg01324.html


  was:

    Environment: JNDI  (was: )
       Priority: Trivial  (was: Major)

> BindableRepositoryFactory requires exact resource type
> ------------------------------------------------------
>
>          Key: JCR-132
>          URL: http://issues.apache.org/jira/browse/JCR-132
>      Project: Jackrabbit
>         Type: Wish
>   Components: config
>  Environment: JNDI
>     Reporter: Jukka Zitting
>     Priority: Trivial

>
> The org.apache.jackrabbit.jndi.BindableRepositoryFactory class requires the exact class
name org.apache.jackrabbit.jndi.BindableRepository to be specified for the JNDI resource that
the factory is responsible for. However the current deployment model 2 howto document suggest
that the more generic interface name javax.jcr.Repository be used instead. Currently this
suggested configuration results in a null JNDI resource .
> This issue should be fixed by either fixing the documentation (I can do this) or by relaxing
the code in BindableRepositoryFactory. I'll attach a patch that does the latter, please comment
on what you think is the best solution.
> This issue was detected during the mailing list thread
> http://www.mail-archive.com/jackrabbit-dev@incubator.apache.org/msg01324.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message