• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

RMI over JRMP

 
Ranch Hand
Posts: 442
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've worked through a few example tuts of RMI but I haven't been able to find one that makes it clear enough, even though my application is already running using RMI I'm not sure I've implemented it correctly, some examples are simple to implement but dont provide the required explanation regarding JRMP.
My requirements are as follows,
1) do not use HTTP server
2) do not require installation of security manager
3) provide all classes pre-installed, ie no dynamic class downloading
4) use RMI over JRMP(do not use IIOP)
so far I know I've not used HTTP server, and I also haven't installed a security manager, not sure if that only works on my network or not, especially seeing as I didn't make an instance of RMISecurityManager or use a policy file.
I can also jar the stub and relevant client classes, so that rules out 1, 2, and 3.
can someone perhaps briefly look at this implementation and tell me if its JRMP or not, please
javaworld rmi/adapter tut
my implementation is pretty much the same except that my client uses naming to lookup the host.
another implied restriction is that I cant use a policy file, because my command to execute has to take the following form
thanks alot in advance for any input
 
Cowgirl and Author
Posts: 1589
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy
If you're not using IIOP, then you *are* using JRMP. JRMP is simply Java's wire protocol for RMI. One simple way to know for sure, when you created your stubs and skeletons, if you didn't specifically make them IIOP (by using the -iiop flag with rmic), then you're JRMP all the way
cheers,
Kathy
 
Ta Ri Ki Sun
Ranch Hand
Posts: 442
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Kathy Sierra:
Howdy
If you're not using IIOP, then you *are* using JRMP. JRMP is simply Java's wire protocol for RMI. One simple way to know for sure, when you created your stubs and skeletons, if you didn't specifically make them IIOP (by using the -iiop flag with rmic), then you're JRMP all the way
cheers,
Kathy


thanks alot Kathy, it is JRMP then, because the only flag I use to compile my stubs is -v1.2 to exclude skeletons.
thanks again
 
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
and bundle the stub class with the client. which avoid dynamic downloading.stub class is needed at both ends(client and server)
 
reply
    Bookmark Topic Watch Topic
  • New Topic