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 javaservlets ? Please give your suggestions. regards Sankar
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.
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.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Dec 28, 2001
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.
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:The corresponding JSP would be something like:They sound alike (they're both called session), but these are obviously different objects with different interfaces.