Announcement Announcement Module
Collapse
No announcement yet.
why i don't need the stub and skleton class for spring RMI ? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • why i don't need the stub and skleton class for spring RMI ?

    why i don't need the stub and skleton class for spring RMI ?

  • #2
    Spring wraps your remote wannabe object in an adapter class that is a generic remote object, and registers it with the RMI registry. On the client side, Spring uses AOP to look up and invoke the remote wrapper object. The stub for the generic remote object is already generated and provided by Spring.

    Have a peek in org.springframework.remoting.rmi.RmiInvocationWrap per & org.springframework.remoting.rmi.RmiClientIntercep tor for more details. Clever stuff if I say so myself.

    Comment


    • #3
      Could RmiInvocationWrapper be used on the client side to create a RMI object from a POJO, which could be registered with the server, so the server can do callbacks?

      Take a look at my post on Bi-directional remoting

      Comment


      • #4
        Yes, this should be possible. See http://forum.springframework.org/showthread.php?t=14684. However, there seems to be a bug in Spring 1.2 which I've raised in Jira
        Last edited by robyn; May 16th, 2006, 04:35 AM.

        Comment

        Working...
        X