Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of ijonas.kisselbach@gmail.com
 designates 209.85.132.244 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=fQbcca5e/11iiGqZnIn9sCoRCNG3HSF29dOvAlHaCOZThMOG+xVIeot72IHjZavkh+N148f6I34nffnaLLWGvyNkZRagu6HtxjvKQw71U4HcwCBT9eoB/BNy2wjXqUO7ITbmYt8AaMR14twzjOxCkMbZY9lnfE0fKNrr8NAQSWQ=
Message-ID: <510d57f60705310432q503b6de0he464f5370bda31bb@mail.gmail.com>
Date: Thu, 31 May 2007 12:32:45 +0100
From: "Ijonas Kisselbach" <ijonas.kisselbach@gmail.com>
To: users@jackrabbit.apache.org
Subject: Jackrabbit+WebDAV under JBoss 4.0.5 problem (solved)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_11543_32352832.1180611165962"

------=_Part_11543_32352832.1180611165962
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

You may remember me from last week... I'm the one trying to deploy a Model-2
JCA-based Jackrabbit on JBoss 4.0.5 and then get the WebDAV servlets
connecting via JNDI to the shared repository.

After sifting through the Jackrabbit source code I think I've solved the
WebDAV deployment problem... If you take a look at

http://svn.apache.org/repos/asf/jackrabbit/tags/1.3/jackrabbit-webapp/src/main/java/org/apache/jackrabbit/j2ee/JNDIConfig.java

it contains a method:

    public void init(ServletConfig ctx) throws ServletException  {
        super.init(ctx);
        // add all params whose name starts with 'java.namming.' to the env
        Enumeration enum = ctx.getInitParameterNames();
        while (enum.hasMoreElements()) {
            String name = (String) enum.nextElement();
            if (name.startsWith("java.naming.")) {
                jndiEnv.put(name, ctx.getInitParameter(name));
            }
        }
        // enable jndi if url is specified
        jndiEnabled = jndiEnv.containsKey("java.naming.provider.url");
    }

The last statement "activates" the JNDI configuration IF AND ONLY IF the "
java.naming.provider.url" parameter has been specified.

I've add the solution to http://wiki.apache.org/jackrabbit/JackrabbitOnJBoss

But it seems odd needing to specify the JNDI environment variables when
deployed __inside__ JBoss.

Hope it helps,
Ijonas Kisselbach.

------=_Part_11543_32352832.1180611165962--