Re: [jira] Resolved: (JCR-1672) Adding Event interface and isLocal()

2008-07-17 Thread Carsten Ziegeler
Thanks Marcel for applying the patch. Is there any chance to get this into the 1.4.x branch as well? Carsten Marcel Reutegger (JIRA) wrote: [ https://issues.apache.org/jira/browse/JCR-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved

[jira] Assigned: (JCR-1678) NullPointerException in constructor of JcrDavException

2008-07-17 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela reassigned JCR-1678: --- Assignee: angela i will take care of this as soon as possible. thanks in advance for the patch and for the

[jira] Updated: (JCR-1679) dir with same name as repository has incorrect behavior

2008-07-17 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCR-1679: Affects Version/s: (was: core 1.4.4) 1.4 Assignee: angela i will take a look

[jira] Updated: (JCR-1679) Simple Webdav: dir with same name as repository has incorrect behavior

2008-07-17 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCR-1679: Component/s: (was: jackrabbit-webdav) jackrabbit-jcr-server Summary: Simple Webdav: dir

Re: Connection pooling

2008-07-17 Thread Alexander Klimetschek
I think we do need a pooling for all the jdbc connections in Jackrabbit. But that should be possible without managing DataSources within Jackrabbit. DataSource management itself is clearly a task of the container or servlet engine and would create too much additional code that needs to be

[jira] Created: (JCR-1682) Session returned does not offers transaction support

2008-07-17 Thread Douglas Jose (JIRA)
Session returned does not offers transaction support Key: JCR-1682 URL: https://issues.apache.org/jira/browse/JCR-1682 Project: Jackrabbit Issue Type: Bug Components:

[jira] Updated: (JCR-1682) Session returned does not offers transaction support

2008-07-17 Thread Douglas Jose (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Douglas Jose updated JCR-1682: -- Attachment: jcr-1682.diff Here is a patch which I believe can fix the problem. Session returned does

Re: Connection pooling

2008-07-17 Thread Matej Knopp
This assumes that you are running jackrabbit in environment that manages DataSources. I think that's a bit far fetched assumptions. So far I didn't notice jackrabbit having any dependencies on the environment you are running it within. And I'm also not really sure about the servlet engine being

[jira] Commented: (JCR-1663) REFERENCE properties produce duplicate strings in memory

2008-07-17 Thread Antonio Carballo (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614369#action_12614369 ] Antonio Carballo commented on JCR-1663: --- Thank you Roman for the java file and

Re: Need Help !

2008-07-17 Thread Stefan Guggisberg
On Thu, Jul 17, 2008 at 7:13 AM, KÖLL Claus [EMAIL PROTECTED] wrote: hi marcel, thanks for the infos. with the bundle db persistence manager it works fine. i think also that bundle fs pm are not for production environements but we have 3 stages (dev,pre-production and production) and in our

Re: Connection pooling

2008-07-17 Thread Thomas Müller
Hi, I am trying to understand both Matej and Alexander / Marcel... In my view Jackrabbit should be able to obtain database connections using a JDBC URL as well as a data source name. If Jackrabbit requires some kind of connection pooling, that should be integrated in Jackrabbit - otherwise it is

Re: Connection pooling

2008-07-17 Thread Matej Knopp
Well, i think the easiest solution would be if jackrabbit instantiated and maintained DataSource instances. This gives the most flexibility. If someone wants to get a data source from JNDI it would be only matter of using the right (proxied) data source. DataSource id=ds1

Re: Connection pooling

2008-07-17 Thread Alexander Klimetschek
On Thu, Jul 17, 2008 at 7:07 PM, Matej Knopp [EMAIL PROTECTED] wrote: Well, i think the easiest solution would be if jackrabbit instantiated and maintained DataSource instances. This gives the most flexibility. If someone wants to get a data source from JNDI it would be only matter of using

Re: Connection pooling

2008-07-17 Thread Matej Knopp
If you get database connection pooling in Jackrabbit without DataSources (using the aforementioned commons-dbcp for example), why do you need a explicit DataSource configuration inside the repository.xml then? I don't really understand the question. What exactly do you mean by database

Re: Connection pooling

2008-07-17 Thread Thomas Müller
Hi, I think there is a misunderstanding. It is already possible to use data sources in Jackrabbit as described here: http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ As of Jackrabbit 1.4, the connection can be created using a JNDI Data Source as well. To do that, the driver class name

Re: Connection pooling

2008-07-17 Thread Matej Knopp
What if you want to use C3P0 or commons dbcp or anything else for that matter but you don't want to obtain it through JNDI because you use spring/guice/hivemind or any other IoC container? Or what if you don't use a IoC container at all, nor you deploy to an application server but you still want

Re: Connection pooling

2008-07-17 Thread Matej Knopp
On Thu, Jul 17, 2008 at 6:47 PM, Thomas Müller [EMAIL PROTECTED] wrote: Hi, I am trying to understand both Matej and Alexander / Marcel... In my view Jackrabbit should be able to obtain database connections using a JDBC URL as well as a data source name. If Jackrabbit requires some kind of