Ensure family safety with coverage

Start driving securely.





============================================================================================================================ Great news and thanks for the work. Do you have any estimate for when the Workspace.deleteWorkspace method will be implemented? Thanks Rakesh On 27 Jan 2010, at 03:53, Jukka Zitting wrote: The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit 2.0.0. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release. Release Notes -- Apache Jackrabbit -- Version 2.0.0 Introduction ------------ This is Apache Jackrabbit 2.0.0, a fully compliant and production-ready implementation of the Content Repository for Java Technology API, version 2.0 (JCR 2.0, http://jcp.org/en/jsr/summary?id=283 ). Changes in this release ----------------------- Jackrabbit 2.0 is a major upgrade from the earlier 1.x releases. The most notable changes in this release are: * Upgrade to JCR 2.0. This Jackrabbit release implements and is based on the official JCR 2.0 API. All of the features required by the JSR 283 specification have been implemented. Note that the remote access layers (RMI and WebDAV) only support a subset of JCR 2.0. * Upgrade to Java 5. All of Jackrabbit (except the jcr-tests component) now requires Java 5 as the base platform. Java 1.4 environments are no longer supported. * Separate JCR Commons components. Many of the general-purpose JCR components like OCM are now developed and released separately from the Jackrabbit content repository. See the individual components for their most recent releases. * Database connection pooling is now available for all database backends. Non-pooled versions of the bundle persistence managers are still available in the org.apache.jackrabbit.core.persistence.bundle package. To enable connection pooling in an existing Jackrabbit repository, replace the package name with org.apache.jackrabbit.core.persistence.pool in your repository and workspace configuration files. * Data store feature enabled in the default repository configuration. * Full text indexing with Apache Tika. Jackrabbit can now extract and index the full text content of many new types of documents, including the Office Open XML files produced by Microsoft Office 2007 and higher. * Apache Commons Collections, Apache Derby, Jetty, SLF4J and Apache Xerces dependencies have been upgraded to more recent versions. * OracleFileSystem class does not use special blob handling anymore as it is not required for Oracle versions since 10R1. Use the Oracle9FileSystem class if you need support for Oracle 9 or earlier. For more detailed information about all the changes in this and other Jackrabbit releases, please see the Jackrabbit issue tracker at https://issues.apache.org/jira/browse/JCR Backwards compatiblity ---------------------- Jackrabbit 2.0 is designed to be compatible with existing Jackrabbit 1.x clients and repositories. The main exceptions to this goal are: * Removal of deprecated classes and features. Jackrabbit 2.0 is not backwards compatible with client code that used classes or features that had been deprecated during the 1.x release cycle. Most notably the temporary org.apache.jackrabbit.api.jsr283 interfaces have been removed in favor of the official JCR 2.0 API in javax.jcr. * Repositories that have used the new JSR 283 security features included as a development preview in Jackrabbit 1.5 and 1.6 may face problems when upgrading to Jackrabbit 2.0. See especially JCR-1944 and JCR-2313 for more details. * The JCR-RMI layer no longer implements the Jackrabbit API extensions. Code that uses JCR-RMI with distributed transactions or for administration operations like creating workspaces or registering node types needs to be updated accordingly. * The JCR-RMI layer in Jackrabbit 2.0 only supports JCR 2.0 repositories. To access a JCR 1.0 repository implementation like Jackrabbit 1.x over RMI, you need to use the 1.x versions of JCR-RMI. Please contact the Jackrabbit user mailing list or issue tracker for more information on how to handle the upgrade if you face some of these issues. Contributors ------------ The following people have contributed to this release by submitting bug reports or by participating in the issue resolution process. Alexander Klimetschek Dietmar Gräbner Marcel Reutegger Alexandre Capt Dominique Pfister Martijn Hendriks Angela Schreiber Esteban Franqueiro Matej Knopp Attila Király Felix Meschberger Matt Johnston Bart van der Schans Frederic Esnault Michael Dürig Bertrand Delacretaz Jared Roberts Michael Xue Brian Topping Jeremy Anderson Philipp Bunge Carsten Ziegeler Jervis Liu Philipp Koch Charles Brooking Johann Sorel Rory Douglas Christian Jörg Hoh Sascha Theves Christian Trutz Jukka Zitting Sébastien Launay Claus Köll Julian Reschke Sridhar Raman Dan Diephouse Kadir Alaca Stefan Guggisberg Dave Brosius Lars Michele Sunil D'Monte Dave Marion Luca Tagliani Thomas Müller David Purpura Lutz Horn Tobias Bocanegra Manfred Bädke Thank you to everyone involved! Release Contents ---------------- This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.txt file for instructions on how to build this release. The source archive is accompanied by SHA1 and MD5 checksums and a PGP signature that you can use to verify the authenticity of your download. The public key used for the PGP signature can be found at https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS . About Apache Jackrabbit ----------------------- Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more. For more information, visit http://jackrabbit.apache.org/ About The Apache Software Foundation ------------------------------------ Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 100 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property framework limits the legal exposure of its 2,500+ contributors. For more information, visit http://www.apache.org/ Rakesh Vidyadharan President & CEO Sans Pareil Technologies, Inc. http://sptci.com/ | 100 W. Chestnut, Suite 1305 | Chicago, IL 60610-3296 USA | | Ph: +1 (312) 212 3933 | Mobile: +1 (312) 315-1596 (US), +91 949 611 0873 (IN) | Fax: +1 (312) 276-4410 | E-mail: rak ... @sptci.com Hi, They're called qt-dotnet and kde-dotnet. There are also other assemblies for other bindings, like plasma-dll for the plasma ones and qtuitools for the Qt UI Tools Module. All the Qt classes are in the namespace Qyoto, the KDE ones in Kimono . The C++ namespaces are the same in C#, so KIO stays KIO and Plasma stays Plasma. Otherwise the API is pretty much the same as in C++. Q_PROPERTYs are converted to .NET properties and all methods start with a capital letter - otherwise the API is identical. We have some examples in the sources - they should explain most of it. We really need to have some docs for the C# bindings.. Seems like more and more people are getting interested in them =) On Sunday 21 December 2008 02:47:56 Lindsay Mathieson wrote: I could really do with some beginner help/pointers here :) I'm using Kubuntu 8.10 with KDE 4.2 Beta 2 installed. kdebindings-kde4 is installed. I can't figure out what the Qyoto and Kimono assemblies are called, nor where they could be. Monodevelop has no references to them. And once I locate them - can't seem to find any docs on how to use them. Thanks, -- Arno Rehn ar ... @arnorehn.de _______________________________________________ Kde-bindings mailing list Kde- ... @kde.org https://mail.kde.org/mailman/listinfo/kde-bindings