3 Replies Latest reply on Jun 26, 2002 4:10 AM by derry

    sorry,deryy.I can not reply your message.

    cjacker

      I have replyed twice but can not see it,so I have to post a new topic.

      in catalina.jar (or in tomcat's source under catalina/src/share/org/apache/catalina/session/")
      there is a file named "LocalStrings.properties",
      but it defined "standardSession.setAttribute.ise" twice and no definition for "standardSession.setAttribute.iae".
      so have the "can not find message for key"standardSession.setAttribute.iae" exception.

      i think first definition for "ise" should be changed as "iae" then it can give me a "Non-serializable" exception.
      from here I got an idea and solve the problem.

      thank you for your reply:-)



        • 1. Re: sorry,deryy.I can not reply your message.
          joao.clemente

          As I see that my messages have the same behaviour you reported, it seems JBoss forum no longer work like they previously did. Maybe posting is now submited to "moderator aprouval" or there was a decision to commit changes to forum list only periodically or something.
          Maybe for performance/server load reasons?

          Joao Clemente
          IST - Portugal

          • 2. Re: sorry,deryy.I can not reply your message.
            joao.clemente

            Well, better seen, it seems like a bug.

            If you notisted, your post will be reported in forum list (check the posting date and the message ordering, it is updated when you post), but either your message, the message counter and the last sender name keep the same was they were before...

            Hey, you guys that have upgraded the forum machine, maybe you know something about this?

            Joao Clemente
            IST - Portugal

            • 3. Re: sorry,deryy.I can not reply your message.
              derry

              > i think first definition for "ise" should be changed
              > as "iae" then it can give me a "Non-serializable"
              > exception.
              > from here I got an idea and solve the problem.

              Fixed in HEAD and Branch_3_0 (so it will be in 3.0.1)...

              CU
              Thomas