File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Servlets and the fly likes Applet-Servlet communication. Jdk version conflicts Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "Applet-Servlet communication. Jdk version conflicts" Watch "Applet-Servlet communication. Jdk version conflicts" New topic
Author

Applet-Servlet communication. Jdk version conflicts

Wolfgang Stein
Greenhorn

Joined: Mar 26, 2001
Posts: 11
Our application uses applet-servlet communication
through serialized java objects.
On the server side we have to use jdk 1.2 or higher.
On the client browser we are restricted to jdk 1.1
since most browsers support it w/o plug-in.
Problem 1: Servlet to applet communication
Objects generated and serialized by the jdk 1.2 VM on the server
are read and used successfully in our jdk 1.1 applet *so far*.
It's understood the receiving applet is restricted to 1.1 methods
(e.g. using 'compareToIgnoreCase()' of class String would be illegal).
Problem 2: Applet to servlet communication
Certainly a jdk 1.3 servlet receiving serialized objects should
not try to use any jdk 1.1 methods on it that vanished in jdk 1.3.
Question:
Are there more restrictions or potential problems on this?
Any experiences with larger projects?

I know this is in prinicpal no solely servlet related
question since it might be based on jdk version conflicts
and serialisation in general.
But i suppose people running servers that require
jdk 1.2 or later could also have faced that problem.
Wolfgang Stein
 
Don't get me started about those stupid light bulbs.
 
subject: Applet-Servlet communication. Jdk version conflicts
 
Similar Threads
DISABLE PUT DELETE TRACE OPTIONS on TOMCAT
JQ + Question ID :958011966030
compiling code using different versions (jdk 1.3 and jdk 1.4)
From JDK 1.1 to JDK 1.3
question for author Aaron Mudler