Thanks for the interesting article. I'd heard about JSR-170 and Jackrabbit but hadn't had time to check it out. Looks like it could be very powerful. I've particularly thought that there is a great need for versioned data in more cases than not.

I also appreciate your keeping the article short, however, there are a couple things it seems you left out. In the introduction you say "the devil is in the details", but you never explain that statement. Is that just general pragmatism/cynicism or did you find any gotchas?

You also use the Jackrabbit API, but don't explain where our data is going. Does Jackrabbit just write to the file system by default? Is this configured in the "repository.xml" file you mentioned. Well, I suppose I can find the answers to these questions myself on the Jackrabbit site, but it would have been good to at least mention how that works.

For that matter, you mention that you can use Hibernate or JDBC with Jackrabbit, but then say that JSR-170 is almost the exact opposite of ORMs... but if your repository content is being put into a RDB, wouldn't you still need some sort of relational mapping?

Thanks again.

Hi
by refrence to the below paragraph of your article :

"The Jackrabbit code base contains not only the JCR API reference implementation, but also a fully functional repository as well as several contributed libraries for tasks, such as accessing a remote repository via RMI. There is even a JDBC persistence manager to allow plugging in a relational database as a persistent store, and an object-relational mapping tool that allows Hibernate applications to use the repository.
"
but as I knew jackrabbit does not support JDBC persistence manager till now !!!!!!!!!!!! it only support filesystem

Hi guys,

I'm studing the JSR 170, to evluate it for a project.
Also, I have read the Frank Sommers interesting article about the JackRabbit implementation.

I don't know very well XMLdatabases, such as exists or others. I'd like to know if JCR have some advantages vs. XMLdatabases, in other words why choose JCR in place of exists for example?

I see that JCR support versioning, Access Control and different backend ways, but there are more radical differences between they ?

Bye
Stefano

Hi,
My objective is to standardize the access (read/write or both) to data content in data sources like a database (MySQL) and any other content repository that is not JSR 170 compliant like Open CMS, live link or share point. By standardizing access I mean that the client program will no longer call the respository specific API like LAPI or JDBC but rather call JCR API methods to achieve common functions like, login, logout, read and write.

I want to clear my concepts by writing a kind of sample connector for MY SQL database which can be accessed by JCR API rather than JDBC. I understand that in order to do I need to write a wrapper around JDBC API which will perform the desired operations using JDBC (as My SQL understand JDBC) but for a developer the entry point will be JCR API.

I have confusion while writing this wrapper. I have taken an example of exportsystemview() of JCR API.

The client code to access this method in CRX using JCR API is

/*
public class ExportXMLFromCRX {
public static void main(String[] args) {
String propertyName = "";
Repository repository = null;
Session repSession = null;
FileInputStream fileInputStream = null;
FileOutputStream fileOutputStream = null;
try
{
ClientRepositoryFactory factory = new ClientRepositoryFactory();
// This is mandatory for rmi access to the CRX
System.setProperty("java.rmi.server.useCodebaseOnly", "true");
repository = factory.getRepository("//localhost:1234/crx");
if(repository != null)
{
userCredentials = new SimpleCredentials(userID,password);
repSession = repository.login(new SimpleCredentials(“admin”, “admin”.toCharArray(), “crx.default”);
if(repSession != null)
{
File outputFile = new File("C:/test1.xml");
FileOutputStream out = new FileOutputStream(outputFile);
repSession.exportSystemView("/MyRootNode", out, false, false);
}//end if(repSession != null)
}// end if(repository != null)
} //end try
catch (Exception Exc)
{
System.out.println(Exc.getMessage());
}//end catch
finally
{
repSession.save(); //save to update nodes created in the CRX Session
repSession.logout(); //duly log-out of the CRX session
}//end try
}// end finally
}
}
*/

What I want is to have a different implementation of the same method which will fetch data from database in an XML format & returns the XML the way the above method does

How should I write a wrapper class for my custom method which fetches record from DB and build an XML but exposed as JCR method? If I am able to do so then the above client code can be used as it is for my MYSQL wrapper code as well. The difference will be that it will no longer fetch data from CRX and build XML but will build an XML based on my database records.

Please suggest what are the steps I need to perform to achieve this?