×

Loading...

Topic

This topic has been archived. It cannot be replied.
  • 工作学习 / IT技术讨论 / Does session work in WebSphere Test Environment of VisualAge for Java 3.5? -marcow(UserMarco); 2000-10-26 {477} (#12153@0)
    I am trying to write a servlet which creates session and a jsp
    component will use this session. But when I test them in WebSphere Test Environment, it seems that jsp component can't get the session object. Does the session instance disappear so quickly? Who can tell me how long a inactive session object will stay in WTE?

    Environment I am using:
    VisualAge for Java 3.5 (support JDK1.2.2)
    WebSphere Studio 3.5
    WebSphere Test Environment

    Thanks in advance.

    Marco
    • Suggest you abandon visual age for Java and use Jakarta-tomcat -jabber(jabber); 2000-10-26 {90} (#12181@0)
      Since you are testing servlet and jsp, I suggest you use Tomcat. It is really a nice tool.
    • I made a mistake -marcow(UserMarco); 2000-10-26 {161} (#12208@0)
      When I called method request.getSession () instead of request.getSession (true);
      So stupid!
      Now, it's working.
      I don't like WebSphere, but I have to use it.
      • IBM Websphere Suite is clumpsy. -jabber(jabber); 2000-10-26 {892} (#12214@0)
        IBM is also slow in supporting Java API. If I am not wrong here, Visual Age for Java only support JSP1.0. Only recently, Wehsphere began to support JDK1.2.

        By the way, I tried several time to install Webspehere at home but I did not have luck.

        However, familiarity with IBM products is a big plus for us to junt jobs in Canada. In Canada, IBM products is very influential.
        If a Java guy does not have experiences in WebSphere, Visual Age, and DB2, he/she will lose a lot of opportunities.

        In USA, small companies prefer to use Weblogic or some other not-so-famous application servers. My understanding is that using IBM products does mean vendor lock-in. Of course, big companies, especially Fortune 500 companies, trust IBM only.

        As for requestion.getSession method, if you use higher version API, you may get a deprecation warning if you use its no-argument variant.
枫下论坛主坛 /  工作学习 /  IT技术讨论