Sadly, I won't have time to develop this for the momen, but I found another way : I deploy the JCA adapter and expose it through the remoting servlets in jackrabbit-webapp. While working on this, I ran through two issues, I wonder weither these are "by design" or real issues : 1. org.apache.jackrabbit.servlet.remote.RemoteBindingServlet expects the repository to be exposed via a servlet context attribute only and doesn't make use of org.apache.jackrabbit.j2ee.RepositoryAccessServlet ; 2. The JCA adapter brings its own slf4j implementation (logback), shouldn't this be a user choice ?
Let me know if I should fill these issues in JIRA. Btw, I work with the latests 2.3 snapshots. Regards, Edouard On Mon, Jun 6, 2011 at 2:23 PM, Jukka Zitting <[email protected]>wrote: > Hi, > > On Mon, Jun 6, 2011 at 1:06 PM, Edouard Hue <[email protected]> wrote: > > Do you think it would be feasible to enable remote RMI access with the > JCA > > adapter ? > > We could add an option for that. Though I'm not sure how remote access > would interact with the transaction manager. It would be interesting > to discuss this further if someone comes up with an initial patch. > > BR, > > Jukka Zitting >
