[
https://issues.apache.org/jira/browse/JCR-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270309#comment-16270309
]
Claus Köll commented on JCR-4195:
---------------------------------
These are my finidings after testing.
The RMI Server tells the client if it should use a proxy or to use a static
stub.
Clients from version 2.16/2.15.7 will not be able to connect to older servers.
(the stubs are missing)
On the other hand it is possible to connect with a older client (pre
2.16/2.15.7) to server starting with version 2.16/2.15.7. (a proxy will be used)
I think this is ok but as said we should document this fact.
I do not see any reason why we should phase out jackrabbit-rmi at the moment
because all things works as before beside this fact.
> jcr-rmi on java 9: Cannot use SUN rmic, as it is not available
> --------------------------------------------------------------
>
> Key: JCR-4195
> URL: https://issues.apache.org/jira/browse/JCR-4195
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 2.16, 2.15.7
>
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.8:run (rmic) on project
> jackrabbit-jcr-rmi: An Ant BuildException has occured: Cannot use SUN rmic,
> as it is not available. A common solution is to set the environment variable
> JAVA_HOME
> [ERROR] around Ant part ...<rmic verify="true"
> classpathref="maven.compile.classpath"
> base="C:\projects\apache\jackrabbit\trunk\jackrabbit-jcr-rmi\target\classes"/>...
> @ 4:140 in
> C:\projects\apache\jackrabbit\trunk\jackrabbit-jcr-rmi\target\antrun\build-main.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
