Cleanser RMI.


94 views
Uploaded on:
Description
needs basic convention: SOAP. making C and Java cooperate ... Naming = <name, remote ... Similarity with non-RMI SOAP usage (stage unbiased) ...
Transcripts
Slide 1

A New-Old Programming Model for Web Services SOAP RMI Aleksander Slominski, Madhusudhan Govindaraju, Randall Bramley, Dennis Gannon Indiana University Extreme! Lab

Slide 2

Outline Web Services and RMI (Triangle) RMI and SOAP RMI framework for Java and C++ Is XML enough for interoperability? Could RMI/XML be (sufficiently quick)? Further Steps Conclusions

Slide 3

Web Services Today Apache SOAP, MS SOAP, … Optionally: WSDL or IDL Optionally: Create IDL.. Customer Interact Service

Slide 4

Web Services Tomorrow Registry Publish Lookup Client Interact Service

Slide 5

Classical RMI Overview RMI Registry Lookup Publish Client Remote Reference Server Remote Object Interact Skeleton Stub Transport Layer

Slide 6

Improving RMI Reusing as opposed to developing … Language free RMI display needs normal convention: SOAP making C++ and Java cooperate … Naming = <name, remote reference> understood naming administration: LDAP Working with future guidelines UDDI, WSDL, …

Slide 7

Implementation Goals: Compatibility with non-RMI SOAP executions (stage nonpartisan) more than 40 accessible now Minimal overhead on application essayist Easier Naming Service (JNDI, LDAP) Multi-convention fall flat over (prototyped) Allow membership to administrations from behind firewall (prototyped)

Slide 8

SoapRMI and Java/C++ SOAP is wire convention Binding to dialect builds For C++ Stub Skeleton XML related classes (mapping) For Java Can be static: as in C++ Or element: Only interfaces and XML mapping information

Slide 9

Dynamic versus Static Stubs Static stubs: exemplary stubs arranged from IDL – speedier yet should be recovered every time IDL changes Dynamic stubs: made with utilization of cutting edge appearance in JDK 1.3 (java.lang.reflect.Proxy) – runtime overhead Good to have both (and have the capacity to keep running in JDK 1.2 also – perhaps … )

Slide 10

SoapRMI/Java Design Subset of RMI like API Transport Layer RPC administrations Pluggable customer and server conventions XML mapping

Slide 11

Design: RMI API RMI Server API UnicastRemoteObject Naming.bind RMI Client API Remote, RemoteException Naming.lookup()

Slide 12

Design: Transport Layer RMI Server API UnicastRemoteObject Naming.bind RMI Client API Remote, RemoteException Naming.lookup() HTTP SoapEmbeddedServer HTTP java.net.HttpURLConnection

Slide 13

Design: RPC Layer RMI Server API UnicastRemoteObject Naming.bind RMI Client API Remote, RemoteException Naming.lookup() SOAP RPC SoapServices HTTP SoapEmbeddedServer HTTP java.net.HttpURLConnection

Slide 14

Design: Protocol Providers RMI Server API UnicastRemoteObject Naming.bind RMI Client API Remote, RemoteException Naming.lookup() SOAP RPC SoapServices Dispatcher (dynamic-skeleton) Invoker (dynamic-stub) HTTP SoapEmbeddedServer HTTP java.net.HttpURLConnection

Slide 15

Design: SOAP/XML layer RMI Server API UnicastRemoteObject Naming.bind RMI Client API Remote, RemoteException Naming.lookup() SOAP RPC SoapServices Dispatcher (dynamic-skeleton) Invoker (dynamic-stub) SOAP Encoding with Mapping HTTP SoapEmbeddedServer HTTP java.net.HttpURLConnection

Slide 16

XML mapping goals interoperability on the wire supporting multi-ref, xsi:type, … simple to process mapping depicted in XML and article model sufficiently adaptable XML construction sorts IDL port sorts (interfaces) sufficiently effective to permit code era dynamic stubs SOAP serialization, deserialization

Slide 17

Performance and past XML is not intended for execution our paper in SC \'00 … yet for strength!!! Intranet/Internet: Java RMI/IIOP/SOAP – straightforwardness is essential yet our take: Simple Open Access Protocol RMI reflection layer Multi-convention approach conceivable

Slide 18

Further work Standardized remote references dynamic WSDL or future norms Multi convention choice (prototyped) Security angles (under thought) Exception model (needs more work) Fail-over (prototyped) Routing Transactions …

Slide 19

Conclusions Web Services pervasive and Internet prepared RMI model basic however regularly just Java Coexistence of New and Old Systems Open Source SoapRMI 1.1 is accessible at this point! http://www.extreme.indiana.edu/cleanser

Recommended
View more...