Mixing ASP and Servlets/JSP

[Sankar Subbiramaniam]

Hi,
One of our company site is already developed running with ASP technologies. Now we want the new applications to be developed in JAVA technology.
Will this have any problems ? Will the session object created by ASP application accessible by JSP and java servlets ?
Please give your suggestions.
regards
Sankar

[dave kees]

Regarding the mixing of JSP and ASP, did you ever get any
feedback? I am working with a test case written in ASP.
The session attributes set by the ASP are NOT being
recognized when a JSP tries to accesses them.
Seems like the app must be ine or the other and no
mixing of ASP and JSP, expecially if they need to pass
data.

[Tim Holloway]

By itself, a web app doesn't require everything to be ASP, JSP, or even PHP. However each has its own idea of what a session object is.
If you want to migrate to JSP, the best thing to do is write/locate a JNI class that can access the IIS session info. This might be a little tricky, since the only way you might be able to get it is to do an internal HTTP request to IIS to an app that can get/set session variables.
At the next level out, you should consider storing session info in language-neutral objects on some sort of common storage medium such as a temp file. This will obviously require mods to the ASP code.
Finally, you could migrate session info to a Java environment and use a Java server app instead of a neutral object (tempfile). The ASPs could then store session info through that and the overhead for Java (and eventual conversion to Java sessions) would be reduced.

[dave kees]

So in other words, since the session object is different
between ASP and JSP, are you saying data CANNOT be passed
between ASP and JSP using the session object?
I have no idea how I would implement those other suggestions.

[Mike Curwen]

Yes, that's what he's saying.

Think about it this way: Would you be able to pass a Visual Basic variable of type Variant, to a Java program that expects an Object?

ASP and JSP are two different platforms that have (you can be fairly certain), radically different ideas about what makes an interface, and how objects should be constructed.

Just look at the differences between them:

// create a new Session variable to store the users name
Session ( 'Name' ) = 'James';
// display the name in any page on your site
Out ( 'Your name is ' + Session ( 'Name' ) );

The corresponding JSP would be something like:

// create a new Session variable to store the user's name
session.setAttribute("Name", "James");
// display the name in any page on your site
out.println("Your name is " + (String) session.getAttribute("Name"));

They sound alike (they're both called session), but these are obviously different objects with different interfaces.