axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1009) Client session objects are shared by a multiple call object
Date Thu, 22 Apr 2004 12:19:54 GMT
The following comment has been added to this issue:

     Author: Toshiyuki Kimura
    Created: Thu, 22 Apr 2004 5:19 AM
       Body:
  I apologize for the delay in replying to you.
I think I'd like to take care of it later. Sure,
any helps are very appreciated, though. :)

Thanks,

  Toshi (Toshiyuki Kimura)
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1009?page=comments#action_35208

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1009

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1009
    Summary: Client session objects are shared by a multiple call object
       Type: Bug

     Status: Open

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             current (nightly)

   Assignee: Axis Developers Mailing List
   Reporter: Toshiyuki Kimura

    Created: Thu, 14 Aug 2003 9:40 AM
    Updated: Thu, 22 Apr 2004 5:19 AM
Environment: Operating System: All
Platform: All

Description:
If a user application creates two call objects from one service
object with setMaintainSession(true), all of session info (including
ids, objects) are shared among the two client unintentionally.

Expected combination:

  [         JVM : Service ojb ] = one-to-many
  [ Service obj : Call obj    ] = one-to-many
  [    User app : Call obj    ] = one-to-many

.........*.........*.........*.........*.........*.........*.........*
          +------------+                +------------+  +------------+ 
4th Layer | User app-1 |                | User app-2 |  | User app-3 |
          +------+-----+                +------+-----+  +-----+------+ 
                 +-------------+               |              |
                 |             |               |              |
          +------+-----+ +-----+------+ +------+-----+ +------+-----+
3rd Layer |Call obj.A-1| |Call obj.A-2| |Call obj.B-1| |Call obj.B-2|
          +------+-----+ +-----+------+ +------+-----+ +------+-----+
                 |             |               |              |
          +------+-------------+------+ +------+-------------------+
2nd Layer |       Service obj. A      | |      Service obj. B      |
          +---------------------------+ +--------------------------+
          +--------------------------------------------------------+
1st Layer |                    JVM (Java Virtual Machine)          |
          +--------------------------------------------------------+
.........*.........*.........*.........*.........*.........*.........*

 - The 1st Layer will be coverd by
   System.setProperty("javax.xml.rpc.session.maintain","true/false").
 - The 2nd Layer will be coverd by
   service.setMaintainSession(true/false).
 - The 3nd Layer will be coverd by
   call.setMaintainSession(true/false).

 Finally, the order of priority would be better off processing
"3rd layer" -> "2nd layer" -> "1st layer".

Thanks,

  Toshi (Toshiyuki Kimura) <kimuratsy@nttdata.co.jp>
  R&D Headquarters
  NTT DATA Corporation


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message