Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <1558206138.1111049661988.JavaMail.jira@ajax.apache.org>
Date: Thu, 17 Mar 2005 09:54:21 +0100 (CET)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Assigned: (JCR-71) WorkspaceConfig.init() throws
 NullPointerException if Search configuration is missing
In-Reply-To: <1487214042.1111044380551.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-71?page=history ]

Jukka Zitting reassigned JCR-71:
--------------------------------

    Assign To: Jukka Zitting

> WorkspaceConfig.init() throws NullPointerException if Search configuration is missing
> -------------------------------------------------------------------------------------
>
>          Key: JCR-71
>          URL: http://issues.apache.org/jira/browse/JCR-71
>      Project: Jackrabbit
>         Type: Bug
>   Components: config
>  Environment: Jackrabbit SVN Rev. 156527
>     Reporter: Felix Meschberger
>     Assignee: Jukka Zitting

>
> When the search configuration is missing from the repository.xml configuration, the WorkspaceConfig.sc field is null and consequently the WorkspaceConfig.init() method throws a NullPointerException.
> This is by itself a bug, especially since missing search configuration is perfectly ok resulting in Jackrabbit not building the search index (which is - believe it or - what really want).
> On that matter, since the configuration file structure seems to be implied by the configuration framework but the DTD is inlined into the configuration file, the configuration framework should act very gracefully to missing or wrong or unexpected configuration elements. Thus, for example, if the file system configuration (WorkspaceConfig.fsc) would be missing, the WorkspaceConfig should probably hint at this point and not throw a NullPointerException without further explanations (of course throwing anything at all is still better than going wild).

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira