Re: AW: o.a.jr.c.p.db.DerbyPersistenceManager should be replaced with o.a.jr.c.p.bundle.DerbyPersistenceManager

Hi, I am ok with going to the pooled version. Just create a JIRA and do ;-) Am Donnerstag, den 09.12.2010, 16:46 +0100 schrieb Clemens Wyss: > > must be removed, too Hmm, I assume this parameter has been removed altogether, right ? Point is: Jackrabbit must IMHO not fiddle with the Derby stat

[jira] Created: (SLING-1891) Replace Cass.forName uses by ClassLoader.loadClass

Replace Cass.forName uses by ClassLoader.loadClass -- Key: SLING-1891 URL: https://issues.apache.org/jira/browse/SLING-1891 Project: Sling Issue Type: Bug Components: Extensions, JCR,

Re: sling@tomcat : howto communicate with Sling bundles/services?

Clemens- I have no idea if this will work, but you might want to look at the OSGi JNDI Services specification. It is more orientated around making JNDI services accessible, but it may be possible to use it to expose an OSGi service via JNDI outside the OSGi container. Logically, in order to make th

AW: o.a.jr.c.p.db.DerbyPersistenceManager should be replaced with o.a.jr.c.p.bundle.DerbyPersistenceManager

Jukka Zitting just replied: 'In fact go directly to pool while you're at it. In 2.2 we're also deprecating non-pooled bundle persistence, see JCR-2803 [1]. [1] https://issues.apache.org/jira/browse/JCR-2803 BR, Jukka Zitting' > -Ursprüngliche Nachricht- > Von: Clemens Wyss [mailto:cle

AW: o.a.jr.c.p.db.DerbyPersistenceManager should be replaced with o.a.jr.c.p.bundle.DerbyPersistenceManager

must be removed, too Should I JIRA this? Regards Clemens > -Ursprüngliche Nachricht- > Von: Clemens Wyss [mailto:clemens...@mysign.ch] > Gesendet: Donnerstag, 9. Dezember 2010 16:43 > An: dev@sling.apache.org > Betreff: o.a.jr.c.p.db.DerbyPersistenceManager should be replaced with > o.a

o.a.jr.c.p.db.DerbyPersistenceManager should be replaced with o.a.jr.c.p.bundle.DerbyPersistenceManager

Just had a discussion (see below) on the jackrabbit ml. Possibly before releasing the next release... Regards Clemens Von: Clemens Wyss [mailto:clemens...@mysign.ch] Gesendet: Donnerstag, 9. Dezember 2010 16:34 An: d...@jackrabbit.apache.org Betreff: AW: o.a.jr.c.p.pool.DerbyPersistenceManager n

Hudson build is back to stable : sling-trunk-1.6 #660

See

Hudson build is back to stable : sling-trun k-1.6 » Apache Sling Launchpad Testing #660

See

Re: [VOTE] Release Sling Parent 10, API 2.2, Adapter 2.0.8, Commons Classloader 1.2.2, and JCR Classloader 3.1.4

+1 Artifacts LGTM and also issues fixed make sense. Ian On 8 Dec 2010, at 16:48, Carsten Ziegeler wrote: > Hi, > > this is another set of releases for SLING-6 > > This vote is for the release of: > > - Apache Sling Parent POM 10 [1] > - Apache Sling Commons Classloader 1.2.2 [2] > - Apache Sli

Hudson build became unstable: sling-trunk-1.6 #659

See

Hudson build became unstable: sling-trunk -1.6 » Apache Sling Launchpad Testing #659

See

AW: SlingPOSTServlet : Auto Checkin Nodes

Looks like I got it, last but not least due to the integration tests ;-) Regarding the integration tests (in PostServletVersionableTests.java) I would apply two "extract method" refactorings (createVersionedNode and createNonVersionedNode, which differ only in the fact that params is submitted

[jira] Commented: (SLING-1482) Commons Log should not export OSGi Configuration Admin package but have a dynamic dependency

[ https://issues.apache.org/jira/browse/SLING-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969655#action_12969655 ] Felix Meschberger commented on SLING-1482: -- Committed a first version in Rev. 1043