Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of chadmichaeldavis@gmail.com
 designates 209.85.218.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=x7LTzO7YwC0anbajv/Rrjqo0LhRXOFuZiAt6AihB0lOcg8stKD1Su+Q3j1hVwYYxWN
         uwaTUO2lAA9mgMCAd8scz9sBH2198SryTHYBkQfON25S9w8X2sWkmLEwXXUokteg94Qg
         mcYOmBHdAIoH6pDWKoVO/+Cj35IDWC0x/5zFs=
MIME-Version: 1.0
In-Reply-To: <v2nca38d6911004281225q205fd546qde84286fa8c53f35@mail.gmail.com>
References: <v2nca38d6911004281225q205fd546qde84286fa8c53f35@mail.gmail.com>
Date: Wed, 28 Apr 2010 13:32:23 -0600
Message-ID: <q2z4fe4c4f51004281232u3f5e2a0cw291f0f5f87cfa4cb@mail.gmail.com>
Subject: Re: Mixing deployment models
From: ChadDavis <chadmichaeldavis@gmail.com>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 28, 2010 at 1:25 PM, Dario Louzado <louzadod@gmail.com> wrote:
> Hi, I=B4m testing jackrabbit 2.0.0 (and soon 2.1.0). We are using a mixed
> deployment model:
> =A0 - Model 2 - shared J2EE resource
> =A0 - Model 3 - repository server accessed by another app using JCR on to=
p of
> WevDav.
>
> I user Model 2 for administrative tasks like registering new node types. =
I
> use model 3 for my content app (creating nodes, connecting nodes and so o=
n).
> Both are pointing to the same "default" workspace.
>
> What is happening:
>
> 1) I register a new NodeType "X" via web app accessing repository using
> Model 2. Thats OK. Nodetype "X" is there in the repository.
> ...
> InputStream is =3D
> getClass().getClassLoader().getResourceAsStream(CND_DOCUMENTO);
> Reader cnd =3D new InputStreamReader(is);
> CndImporter.registerNodeTypes(cnd, s);
> s.save();
> ....
>
>
> 2) Content app tries to access NodeType "X" (via JCR on top of WebDav/mod=
el
> 3), but it is not accessible after connecting to the same repository and
> workspace. The new nodetype simply is not there.
>
> ....
> =A0 =A0@Override
> =A0 =A0public NodeTypeIterator getAllNodeTypes() throws RepositoryExcepti=
on {
> =A0 =A0 =A0 =A0NodeTypeIterator result =3D this.jcrSession.getWorkspace()=
.
> =A0 =A0 =A0 =A0 =A0 =A0getNodeTypeManager().getAllNodeTypes();
> =A0 =A0 =A0 =A0return result;
> =A0 =A0}
>
> =A0 =A0// connect to model 3 server using the following URL:
> =A0 =A0// http://myserver:8080/jackrabbit/server
> ....
>
>
> Is there any limitation with WebDav access concerning custom nodetypes?

I've used custom node types on SPI/davex remoting stack in both 2.0
and 2.1.  I doubt that this is the problem.


Or
> is there any limitation with mixing deployment models?
>