[
http://jira.jboss.com/jira/browse/JBREM-496?page=comments#action_12339413 ]
Tom Elrod commented on JBREM-496:
----------------------------------
No longer have InvokerRegistry:
public static synchronized void registerInvoker(String transport, String clientClassName,
String serverClassName)
public static synchronized void registerInvoker(String transport, Class client, Class
server)
public static synchronized void unregisterInvoker(String transport)
but instead have been replaced with:
public static synchronized void registerInvokerFactories(String transport, Class
clientFactory, Class serverFactory)
public static synchronized void unregisterInvokerFactories(String transport)
since invokers are created via factories now (for both client and server invokers)
restructure service providers for remoting
------------------------------------------
Key: JBREM-496
URL:
http://jira.jboss.com/jira/browse/JBREM-496
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need a way to package and identify transport implementations for remoting. The idea is
that anyone would be able to create their own transport implementation and drop it in and
be "deployed" (where deployed means can just automatically discovered and used
during runtime).
A few ideas of how to do this are:
1. Use service provider from jar metadata -
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider
(e.g. URL[] urls = new
Class().getResources("META-INF/services/org.jboss.remoting/Transport") ; )
2. Follow jndi pattern for package name.
(e.g. org.jboss.remoting.plugins.http.TransportFactory).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira