Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 26189 invoked from network); 3 Mar 2010 23:44:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Mar 2010 23:44:22 -0000 Received: (qmail 37634 invoked by uid 500); 3 Mar 2010 23:44:13 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 37591 invoked by uid 500); 3 Mar 2010 23:44:13 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 37582 invoked by uid 99); 3 Mar 2010 23:44:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 23:44:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=6710e7ef3=Steven.Birmingham@itt.com designates 151.190.252.22 as permitted sender) Received: from [151.190.252.22] (HELO cip-fwa-c2.itt.com) (151.190.252.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 23:44:05 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIFAFqCjksKIBAN/2dsb2JhbACbfQa2aoR8BIMXHA X-IronPort-AV: E=Sophos;i="4.49,576,1262581200"; d="scan'208";a="16788316" Received: from unknown (HELO fwexedge3.itt.net) ([10.32.16.13]) by cip-fwa-c2.itt.com with ESMTP/TLS/RC4-MD5; 03 Mar 2010 18:31:07 -0500 Received: from fwexhub4.itt.net (10.32.76.114) by edge.itt.com (10.32.16.13) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 3 Mar 2010 18:44:43 -0500 Received: from IIWCBO-EHUB1.iiw.de.ittind.com (10.244.2.24) by fwexhub4.itt.net (10.32.76.114) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 3 Mar 2010 18:43:43 -0500 Received: from iiwcbo-emb1.iiw.de.ittind.com ([10.244.2.29]) by IIWCBO-Ehub1.iiw.de.ittind.com ([::1]) with mapi; Wed, 3 Mar 2010 18:43:43 -0500 From: "Birmingham, Steven" To: "users@jackrabbit.apache.org" Date: Wed, 3 Mar 2010 18:43:41 -0500 Subject: RE: NodeType creation Thread-Topic: NodeType creation Thread-Index: Acq7EFMAcSFyVY9GRPq6MNR8y7FTVwAGUSRg Message-ID: References: <90a8d1c01003030944s3e3f88eo8f8fba7a894a6ef0@mail.gmail.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I built and added jackrabbit-core-2.0.0.jar to the build path, but JackRabb= itNodeTypeManager is still unresolved. Yes, I was trying to do an evaluati= on on the standalone server. So, are you saying NodeType management in 2.0= is not available in the standalone server? I will download the 2.0 war file and see if things work differently on Tomc= at. I am a little confused as there is documentation on the 2.0 website fo= r NodeType management but I guess it is incomplete? Thanks for your help, Steve -----Original Message----- From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com]=20 Sent: Wednesday, March 03, 2010 1:30 PM To: users@jackrabbit.apache.org Subject: Re: NodeType creation On 03.03.2010, at 19:01, "Birmingham, Steven" =20 wrote: > Thanks for the response. > > JackrabbitNodeTypeManager is not on the class path either. I have =20 > all the 2.0 jars on the class path. > For jackrabbitNodeTypeManagerImpl I get three implementations on the =20 > classpath: > //import org.apache.jackrabbit.jcr2spi.nodetype.NodeTypeManagerImpl; > //import =20 > org.apache.jackrabbit.ocm.nodemanagement.impl.jackrabbit.NodeTypeManagerI= mpl; > import =20 > org.apache.jackrabbit.ocm.nodemanagement.impl.jeceira.NodeTypeManagerImpl= ; > > Does NodeType registration work for you in 2.0? > yes JackrabbitNodeTypeManager is included in jackrabbit-core, which is =20 missing from your dependencies list. are you accessing a stand-alone jackrabbit server? if yes, you might =20 be out of luck since the said method is only available on a local, =20 i.e. embedded instance. cheers stefan > Here are my dependencies. > > conf=3D"compile"/> > > commons" rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"2.0.0" conf=3D"compile"/> > commons" rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"2.0.0" conf=3D"compile"/> > server" rev=3D"2.0.0" conf=3D"compile"/> > rev=3D"3.0.1" conf=3D"compile"/> > conf=3D"compile"/> > conf=3D"compile"/> > conf=3D"compile"/> > conf=3D"compile"/> > conf=3D"compile"/> > > Steve > > -----Original Message----- > From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com] > Sent: Wednesday, March 03, 2010 10:44 AM > To: users@jackrabbit.apache.org > Subject: Re: NodeType creation > > On Wed, Mar 3, 2010 at 5:25 PM, Birmingham, Steven > wrote: >> Hello, >> >> I am trying to read a NodeType configuration from an xml file. The =20 >> example I used was from the ocm test classes. >> >> =20 >> jackrabbitNodeTypeManagerImpl.createNodeTypesFromConfiguration=20 >> (session, >> new FileInputStream("./resources/=20 >> Signal.xml")); >> >> Exception in thread "main" java.lang.NoClassDefFoundError: org/=20 >> apache/jackrabbit/core/nodetype/xml/NodeTypeReader >> >> I have jcr-2.0.jar and all the other jackrabbit bundles on the =20 >> class path. Am I somehow missing a jar or is this method not =20 >> supported anymore or changed? > > try this: > http://jackrabbit.apache.org/api/2.0/org/apache/jackrabbit/api/Jackrabbit= NodeTypeManager.html#registerNodeTypes(java.io.InputStream,%20java.lang.Str= ing) > > e.g. > > ((JackrabbitNodeTypeManager) > session.getNodeTypeManager()).registerNodeTypes(new > FileInputStream("./resources/Signal.xml"), > JackrabbitNodeTypeManager.TEXT_XML); > > cheers > stefan >> >> Thanks, >> Steve >> >> ________________________________ >> This e-mail and any files transmitted with it may be proprietary =20 >> and are intended solely for the use of the individual or entity to =20 >> whom they are addressed. If you have received this e-mail in error =20 >> please notify the sender. >> Please note that any views or opinions presented in this e-mail are =20 >> solely those of the author and do not necessarily represent those =20 >> of ITT Corporation. The recipient should check this e-mail and any =20 >> attachments for the presence of viruses. ITT accepts no liability =20 >> for any damage caused by any virus transmitted by this e-mail. >>