You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Paul Dennis (JIRA)" <ji...@apache.org> on 2006/04/28 22:35:37 UTC
[jira] Created: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Request for other RMI binding options in RepositoryStartupServlet
-----------------------------------------------------------------
Key: JCR-419
URL: http://issues.apache.org/jira/browse/JCR-419
Project: Jackrabbit
Type: Improvement
Components: rmi
Versions: 1.1
Environment: Weblogic 8.1 T3
Reporter: Paul Dennis
Priority: Minor
The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
Context ctx = new InitialContext();
ctx.bind(repositoryName + "Remote", remote);
This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
Object ref = ctx.lookup(repositoryName + "Remote");
LocalAdapterFactory laf = new ClientAdapterFactory();
Repository remote = laf.getRepository((RemoteRepository) ref);
>From the initial tests I have done this appears to work well inside the Weblogic container.
- Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-419?page=all ]
Jukka Zitting updated JCR-419:
------------------------------
Fix Version/s: (was: 1.1)
> Request for other RMI binding options in RepositoryStartupServlet
> -----------------------------------------------------------------
>
> Key: JCR-419
> URL: http://issues.apache.org/jira/browse/JCR-419
> Project: Jackrabbit
> Issue Type: Improvement
> Components: rmi
> Affects Versions: 1.0, 1.0.1
> Environment: Weblogic 8.1 T3
> Reporter: Paul Dennis
> Assigned To: Jukka Zitting
> Priority: Minor
>
> The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
> The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
> I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
> For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
> Context ctx = new InitialContext();
> ctx.bind(repositoryName + "Remote", remote);
> This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
> Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
> Object ref = ctx.lookup(repositoryName + "Remote");
> LocalAdapterFactory laf = new ClientAdapterFactory();
> Repository remote = laf.getRepository((RemoteRepository) ref);
> From the initial tests I have done this appears to work well inside the Weblogic container.
> - Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-419?page=all ]
Jukka Zitting updated JCR-419:
------------------------------
Fix Version: 1.1
Version: 1.0
1.0.1
(was: 1.1)
> Request for other RMI binding options in RepositoryStartupServlet
> -----------------------------------------------------------------
>
> Key: JCR-419
> URL: http://issues.apache.org/jira/browse/JCR-419
> Project: Jackrabbit
> Type: Improvement
> Components: rmi
> Versions: 1.0, 1.0.1
> Environment: Weblogic 8.1 T3
> Reporter: Paul Dennis
> Priority: Minor
> Fix For: 1.1
>
> The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
> The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
> I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
> For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
> Context ctx = new InitialContext();
> ctx.bind(repositoryName + "Remote", remote);
> This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
> Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
> Object ref = ctx.lookup(repositoryName + "Remote");
> LocalAdapterFactory laf = new ClientAdapterFactory();
> Repository remote = laf.getRepository((RemoteRepository) ref);
> From the initial tests I have done this appears to work well inside the Weblogic container.
> - Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-419?page=all ]
Jukka Zitting reassigned JCR-419:
---------------------------------
Assignee: Jukka Zitting
> Request for other RMI binding options in RepositoryStartupServlet
> -----------------------------------------------------------------
>
> Key: JCR-419
> URL: http://issues.apache.org/jira/browse/JCR-419
> Project: Jackrabbit
> Issue Type: Improvement
> Components: rmi
> Affects Versions: 1.0, 1.0.1
> Environment: Weblogic 8.1 T3
> Reporter: Paul Dennis
> Assigned To: Jukka Zitting
> Priority: Minor
> Fix For: 1.1
>
>
> The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
> The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
> I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
> For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
> Context ctx = new InitialContext();
> ctx.bind(repositoryName + "Remote", remote);
> This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
> Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
> Object ref = ctx.lookup(repositoryName + "Remote");
> LocalAdapterFactory laf = new ClientAdapterFactory();
> Repository remote = laf.getRepository((RemoteRepository) ref);
> From the initial tests I have done this appears to work well inside the Weblogic container.
> - Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-419.
-------------------------------
Resolution: Fixed
Implemented alternative JNDI binding and access servlets in revision 543821. See JCR-956 for related information.
> Request for other RMI binding options in RepositoryStartupServlet
> -----------------------------------------------------------------
>
> Key: JCR-419
> URL: https://issues.apache.org/jira/browse/JCR-419
> Project: Jackrabbit
> Issue Type: Improvement
> Components: rmi
> Environment: Weblogic 8.1 T3
> Reporter: Paul Dennis
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 1.4
>
>
> The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
> The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
> I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
> For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
> Context ctx = new InitialContext();
> ctx.bind(repositoryName + "Remote", remote);
> This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
> Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
> Object ref = ctx.lookup(repositoryName + "Remote");
> LocalAdapterFactory laf = new ClientAdapterFactory();
> Repository remote = laf.getRepository((RemoteRepository) ref);
> From the initial tests I have done this appears to work well inside the Weblogic container.
> - Paul.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-419) Request for other RMI binding options in
RepositoryStartupServlet
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-419:
------------------------------
Fix Version/s: 1.4
Affects Version/s: (was: 1.0.1)
(was: 1.0)
> Request for other RMI binding options in RepositoryStartupServlet
> -----------------------------------------------------------------
>
> Key: JCR-419
> URL: https://issues.apache.org/jira/browse/JCR-419
> Project: Jackrabbit
> Issue Type: Improvement
> Components: rmi
> Environment: Weblogic 8.1 T3
> Reporter: Paul Dennis
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 1.4
>
>
> The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry.
> The LocateRegistry mechanism does not appear to work by default in a Weblogic environment.
> I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI().
> For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository:
> Context ctx = new InitialContext();
> ctx.bind(repositoryName + "Remote", remote);
> This allows for easy remote access using weblogic's native T3 protocol using the following on the client with:
> Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set
> Object ref = ctx.lookup(repositoryName + "Remote");
> LocalAdapterFactory laf = new ClientAdapterFactory();
> Repository remote = laf.getRepository((RemoteRepository) ref);
> From the initial tests I have done this appears to work well inside the Weblogic container.
> - Paul.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.