Hi, In the future, for other implementation specific extensions, we could maybe use a wrapper mechanism like the one from JDBC 4.0, as described here:
http://java.sun.com/javase/6/docs/api/java/sql/Wrapper.html This mechanism was invented for JDBC drivers, but it can be used for other APIs as well (as far as I see). For Jackrabbit, probably we should remove the 'generic' part of it. Thomas On 10/5/06, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
hi eknath, i create a jira issue for this: http://issues.apache.org/jira/browse/JCR-585 regards, toby On 10/4/06, Eknath Kadam <[EMAIL PROTECTED]> wrote: > > On 10/4/06, Thomas Mueller <thomas.tom.mueller <at> gmail.com> wrote: > > > - For those interfaces that need to be extended, create new interfaces as > > > part of Jackrabbit, and let them extend the JCR API. Then use those > > > interfaces instead of the JCR API for the RMI API and the log/trace wrapper. > > > The application then just casts to the new interfaces instead of the > > > implementation. > > Thanks Thomas for the idea. > I modified RemoteWorkspace.java ServerWorkspace.java and > ClientWorkspace.java and added new method > void createWorkspace(String name), rebuild the project and > used the new jar in project. > Now I use following code create new workspace remotely > ((ClientWorkspace)workspace).createWorkspace("newWorkspace"); > > I am sure this approach would work for rest the issue also. > I would recommand if standard jackrabbit-rmi > also provides such functionality. > > Thanks, > Eknath > > -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
