Re: how to Connect to the Repository

Hi, HI, Can you help me about the demo just with jcr-1.0.jar. Sorry, I don't understand what you with demo just with jcr-1.0.jar. Regards, Thomas

Re: how to Connect to the Repository

Hi, I don't want to use Jackrabbit source code. I want to write code by myself. OK I understand. Do you have the simple demo? What kind of demo are you looking for? Regards, Thomas

Re: Component releases, proposed solution

Hi, If done correctly, major new development can be done in the trunk without risk. Sure, if it only concerns a single location or limited set of locations. If it touches multiple places, this is not that easy. USE_DATA_STORE is used in multiple places, I don't think it's a big problem. And

Re: Component releases, proposed solution

Hi, Alternatively, how about if the modified component always got the top level version number? That way we'd have gaps in the component version numbers, but it would always be easy to correlate the component version number with the top-level release that first contained it. +1 for the 'gap

Re: Connection pooling

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

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: AW: AW: Need Help !

Hi, Thanks, but now I'm even more confused because BundleFSPersistenceManager is listed in the wiki as mature and very fast but in your earlier email you say it is not recommended for a production environment. Not trying to create an argument but it would be very helpful to Jackrabbit users

Re: Repository locked by one server in clustered mode

Hi, When using clustering, the cluster nodes can not share the repository. Each cluster node must have its own repository configuration. See http://wiki.apache.org/jackrabbit/Clustering for details. Regards, Thomas On Sat, Jun 28, 2008 at 3:44 PM, Balak Dev [EMAIL PROTECTED] wrote: Dear All,

Re: Java 5 in Jackrabbit 2.0?

Hi, I am for using Java 1.5. Another option would be to switch to Java 1.5 and provide some documentation or a build profile that uses Retroweaver if Java 1.4 is still required. I have never used it and I don't have an opinion on it, just to list the option: http://retroweaver.sourceforge.net/

Re: Documentation

Hi, better documentation for Jackrabbit. many things are missing, also for some very basic descriptions. One can see that by the type of questions coming up on the users list. I agree. Having bad documentation is bad because: - Many users don't use the mailing list and just move on. - There

Re: BundleDbPersistanceManager

Hi, externalBlobs problem with a clustered deployment Anyway the blob store doesn't work in a clustered environment. As of Jackrabbit 1.4, there is an alternative to the blob store: the data store. http://wiki.apache.org/jackrabbit/DataStore There are two variants: the file data store (better

Re: DataStore Garbage Collector Performance

Hi, We have a working background GC. Well, the current released GC implementation can run in the background as well. Or can it not? What is the difference between your and the current implementation? Regards, Thomas

Re: Memory use of item states

Hi, I support memory optimizations. The YourKit Java Profiler could help to find out what takes how much memory. If done correctly, memory optimizations will improve performance (because more items fit in the cache). In addition to what Jukka proposed I would like to implement a value cache

Re: DataStore Garbage Collector Performance

Hi, i have testet it with the option set to true and it takes about 3,2 hours ... This is about what I have expected. what do you think how long will it take to improve the gc process much more ? I don't know. And I don't know if it's important: garbage collection can run in the background.

Re: DataStore Garbage Collector Performance

Hi, Did you use the 'persistence manager scan' option? GarbageCollector.setPersistenceManagerScan(true); That should improve the performance. I have added a idea how to speed up garbage collection in the future at http://wiki.apache.org/jackrabbit/DataStore (at the very bottom). Regards, Thomas

Re: Bad OOTB experience with 1.4

Hi, I fully agree with Carsten. We have already discussed this, see http://www.nabble.com/Why-there's-no-jcr-1.0.jar-in-1.4-war-dist--td15216240.html Until Sling is released, what about if we create a .zip file (instead of the .war file) that includes the current .war file and the jcr-api.jar,

Re: JNDI + BundleDbPersistenceManager

Hi, Instead of using BundleDbPersistenceManager you probably need to use the OraclePersistenceManager. Unfortunately this will not work with JNDI at the moment (because default user name and password are used). However you could patch the OraclePersistenceManager with the current one from the

Re: extending the jackrabbit-api

Hi, I would not create a 'temporary project'. A 'temporary package' is enough. Regards, Thomas On Fri, May 9, 2008 at 1:09 PM, Angela Schreiber [EMAIL PROTECTED] wrote: yes, that was the idea. alternatively we could also create an interim project module, jackrabbit-jsr283-api and drop that

Re: Problems indexing pdf file with DBDatastore

Hi, This is a bug in TempFileInputStream. I will log a bug and fix the problem. Thanks for reporting this issue. Regards, Thomas On Wed, May 7, 2008 at 10:25 AM, KÖLL Claus [EMAIL PROTECTED] wrote: hi, if i import a pdf file into my repository configured with a dbdatastore i get following

Apache SVN down?

Hi, It looks like svn.apache.org is down again. I can't connect to the jackrabbit svn at the moment. Regards, Thomas

Re: remove JackrabbitRepository.shutdown()

Hi, I have no concerns about shutdown being in an interface as such I just object to putting it in a client-level interface. We should have discussed that earlier... For example the idea of a separate RepositoryManager interface that covers both repository startup and shutdown is IMHO

Re: remove JackrabbitRepository.shutdown()

Hi, But we're diverging from the shutdown() issue. Yes. I propose create a new public interface JackrabbitManagedRepository extends Repository { void shutdown(JackrabbitSession session); } This would have the following advantages: - Developers can write applications against an interface.

Re: remove JackrabbitRepository.shutdown()

Hi, What about the other points? I repeat them here and I hope I get an answer on them as well: - Developers can write applications against an interface. - Developers can use Javadocs. Also, the autocomplete feature in the IDE would list relevant methods. - Access right checking can be

Re: remove JackrabbitRepository.shutdown()

Hi, RepositoryManagement mgmgt = new JackrabbitRepositoryMgmt(); Repository mgmt.createRepository() mgmt.shutdown(Repository rep) This looks good as well, as long as RepositoryManagement is an interface. There are some advantages compared to having shutdown on the

<    1   2   3