You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2006/03/29 01:52:19 UTC
[jira] Created: (AXIS2-532) Session Management
Session Management
------------------
Key: AXIS2-532
URL: http://issues.apache.org/jira/browse/AXIS2-532
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Versions: 0.95
Reporter: Rajith Attapattu
Session Management
-------------------------------
This patch containes transport independent session mgt using WS-Addressing EPRs
Interfaces
--------------
All interfaces are located in the core module
Main interfaces useful for users
org.apache.axis2.session.Session
org.apache.axis2.session.SessionManager
org.apache.axis2.session.SessionIdFactory
There is a Null impl for these interfaces within core
Implementation
------------------------
All implementation specific classes are located in the session module
Clustering impl
----------------------
Clustering impl is located within the clustering module
(only empty classes so far)
Examples (located in the samples module)
-----------------
ATM example
sample.session.atm.*
Echo example
sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (AXIS2-532) Session Management
Posted by Rajith Attapattu <ra...@gmail.com>.
Hey Deepal,
Thanks for the reply and no misunderstandings at all.
I am defintely +1 for the module approach. (As I mentioned to you before)
As long as I can add the config to the axis2 system module approach is
great. Well infact module is the best approach.
>And I think adding a method to get session manager from AxisService and
AxisConfiguration is not sound good to me , we have some other >alternatives
as you know even service implementation class we store as a parameter
Actually currently it gets the Global session manager from
AxisConfiguration.
I was thinking about allowing to define a session manager on a per service
level, hence the AxisService
for instance you want only certain services to be clustered.
However if there is an alternative way of handling this, then I am happy to
do that.
Can u please elaborate on these alternatives. I can quickly change the code
to support that.
>I dont know whether I am missing something , can you please explain how do
you plan to do clustering with your session management >proposal.
No my mistake on not explaning this. We cluster the sessions using WADI or
maybe richochet or JGroups.
The idea is to carry the simple conversation to another node if the primary
node fails.
How clustering is done depends on what we use. In side Axis2 we will only
have the glue code to wire to the underlying infrastructure.
Currently an effort in WADI is in full swing.
> And adding session management related stuff into Message receivers not
going to be work , since ppl can write their own message receivers, > so in
that case he has to aware of session management.
You are absolutely right.
This is totally a hack and temporary messure untill I figure out the propoer
solution.
I need help in figuring out how to pass the session object between the
inpipeline and the out pipeline. (thats one issue)
the other is for me to figure out a way to capture the start and end of a
message processing.
the sync case is good, but the async case is tricky as the real work is
happening in the back ground thread and I need to figure out when the
processing ends.
I am sure there is a way. Lets brain storm and find a way.
Thanks a lot for the feedback.
Regards,
Rajith
On 6/21/06, Deepal Jayasinghe (JIRA) <ji...@apache.org> wrote:
>
> [
> http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12417068]
>
> Deepal Jayasinghe commented on AXIS2-532:
> -----------------------------------------
>
> Hi Rajitha
>
> I wen through your patch + documents and they are great. But I have few
> concern about the patch and the proposal (please please dont misunderstand
> me).
>
> From your patch I realized that you are trying to do a number of changes
> to Axis2 to support session management. As you know we have session
> management in Axis2 and it has limitation too. As described in your
> proposal we can not manage session across services groups , so the ideal
> solution would be to add a way to change service group at the runtime.
>
> And I really want to rename the servicegroupId into something else :)
>
> I dont know whether I am missing something , can you please explain how do
> you plan to do clustering with your session management proposal.
>
> As I suggested sometimes ago you can implement the proposal as Axis2
> module (like Sandesha , Rampart) , since what you want is to add two handles
> in the flows and share some data across invocations.
>
> Any way from the patch I found following can be change nicely to implement
> Session management as a module.
>
> You dont need to add two handlers into axis2.xml , what you can do is to
> add a module.xml and add the handlers there what do you think
>
> +<handler name="SessionHandler"
> + class="org.apache.axis2.session.SessionHandler">
> + <order phase="PreDispatch" phaseLast="true"/>
> + </handler>
>
>
> <phase name="MessageOut">
> + <handler name="EndOfRequestHandler"
> + class="org.apache.axis2.session.EndOfRequestHandler
> ">
> + <order phase="MessageOut" phaseFirst="true"/>
> + </handler>
> </phase>
>
>
> Do we need to support by default , so having default session management
> stuff in axis2.xml is not good to me , what I suggest is to have them as
> parameters then you dont need to do any modifications to AxisConfigBuilder
> or any other core axis2 classes. Still I am thinking to implement session
> management as a module like Sandesha.
>
> + <!-- ================================================= -->
> + <!-- Session Management and Clustering -->
> + <!-- Comment this section on client side, no session management is
> needed for client side -->
> + <!-- ================================================= -->
> + <sessionManagerFactory class="
> org.apache.axis2.session.DefaultSessionManagerFactory">
> + <sessionManager class="
> org.apache.axis2.session.Axis2SessionManager">
> Do you really need to have separate field to store session object in
> Message context , you can store that as a property.
>
> And adding session management related stuff into Message receivers not
> going to be work , since ppl can write their own message receivers, so in
> that case he has to aware of session management.
>
> AxisService service = msgContext.getAxisService();
> + if (service !=null && service.getSessionManager() !=
> null){
> + return service.getSessionManager();
> + }
>
>
> And I think adding a method to get session manager from AxisService and
> AxisConfiguration is not sound good to me , we have some other alternatives
> as you know even service implementation class we store as a parameter
>
> // first check if there is a session manager for the service
> + AxisService service = msgContext.getAxisService();
> + if (service !=null && service.getSessionManager() !=
> null){
> + return service.getSessionManager();
> + }
>
>
> So please comment on this and I am very sorry for my delay to reply
>
>
> > Session Management
> > ------------------
> >
> > Key: AXIS2-532
> > URL: http://issues.apache.org/jira/browse/AXIS2-532
> > Project: Apache Axis 2.0 (Axis2)
> > Type: New Feature
>
> > Versions: 0.95
> > Reporter: Rajith Attapattu
> > Attachments: session_march_28.patch, session_mgt_march29.patch,
> session_mgt_march30.patch, session_mgt_march31.patch
> >
> > Session Management
> > -------------------------------
> > This patch containes transport independent session mgt using
> WS-Addressing EPRs
> > Interfaces
> > --------------
> > All interfaces are located in the core module
> > Main interfaces useful for users
> > org.apache.axis2.session.Session
> > org.apache.axis2.session.SessionManager
> > org.apache.axis2.session.SessionIdFactory
> > There is a Null impl for these interfaces within core
> > Implementation
> > ------------------------
> > All implementation specific classes are located in the session module
> > Clustering impl
> > ----------------------
> > Clustering impl is located within the clustering module
> > (only empty classes so far)
> > Examples (located in the samples module)
> > -----------------
> > ATM example
> > sample.session.atm.*
> > Echo example
> > sample.session.echo.*
>
> --
> 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
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
Re: [jira] Commented: (AXIS2-532) Session Management
Posted by Rajith Attapattu <ra...@gmail.com>.
Dims,
Wasn't it in the patch I submitted?? maybe there is something wrong with the
patch.
Can you please verify?
I will create a fresh copy of trunk and will try to apply my patch.
Regards,
Rajith.
On 3/30/06, Davanum Srinivas (JIRA) <ji...@apache.org> wrote:
>
> [
> http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12372462]
>
> Davanum Srinivas commented on AXIS2-532:
> ----------------------------------------
>
> could u please upload the new classes?
>
> example:
> org.apache.axis2.session.NullSessionManager;
> org.apache.axis2.session.SessionManager;
>
> thanks,
> dims
>
> > Session Management
> > ------------------
> >
> > Key: AXIS2-532
> > URL: http://issues.apache.org/jira/browse/AXIS2-532
> > Project: Apache Axis 2.0 (Axis2)
> > Type: New Feature
> > Versions: 0.95
> > Reporter: Rajith Attapattu
> > Attachments: session_march_28.patch
> >
> > Session Management
> > -------------------------------
> > This patch containes transport independent session mgt using
> WS-Addressing EPRs
> > Interfaces
> > --------------
> > All interfaces are located in the core module
> > Main interfaces useful for users
> > org.apache.axis2.session.Session
> > org.apache.axis2.session.SessionManager
> > org.apache.axis2.session.SessionIdFactory
> > There is a Null impl for these interfaces within core
> > Implementation
> > ------------------------
> > All implementation specific classes are located in the session module
> > Clustering impl
> > ----------------------
> > Clustering impl is located within the clustering module
> > (only empty classes so far)
> > Examples (located in the samples module)
> > -----------------
> > ATM example
> > sample.session.atm.*
> > Echo example
> > sample.session.echo.*
>
> --
> 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
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
[jira] Commented: (AXIS2-532) Session Management
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12372663 ]
Deepal Jayasinghe commented on AXIS2-532:
-----------------------------------------
I tried to apply the patch , but it seems to me that patch is old and there were few conflicting so I did not do that.
So please re-create the patch using current SVN head and send that back.
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-532) Session Management
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=all ]
Rajith Attapattu updated AXIS2-532:
-----------------------------------
Attachment: session_mgt_march31.patch
Deepal,
I took the time to make some improvemets.
Please let me know how it goes
Regards,
Rajith
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch, session_mgt_march30.patch, session_mgt_march31.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-532) Session Management
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=all ]
Rajith Attapattu updated AXIS2-532:
-----------------------------------
Attachment: session_march_28.patch
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-532) Session Management
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12417068 ]
Deepal Jayasinghe commented on AXIS2-532:
-----------------------------------------
Hi Rajitha
I wen through your patch + documents and they are great. But I have few concern about the patch and the proposal (please please dont misunderstand me).
>From your patch I realized that you are trying to do a number of changes to Axis2 to support session management. As you know we have session management in Axis2 and it has limitation too. As described in your proposal we can not manage session across services groups , so the ideal solution would be to add a way to change service group at the runtime.
And I really want to rename the servicegroupId into something else :)
I dont know whether I am missing something , can you please explain how do you plan to do clustering with your session management proposal.
As I suggested sometimes ago you can implement the proposal as Axis2 module (like Sandesha , Rampart) , since what you want is to add two handles in the flows and share some data across invocations.
Any way from the patch I found following can be change nicely to implement Session management as a module.
You dont need to add two handlers into axis2.xml , what you can do is to add a module.xml and add the handlers there what do you think
+<handler name="SessionHandler"
+ class="org.apache.axis2.session.SessionHandler">
+ <order phase="PreDispatch" phaseLast="true"/>
+ </handler>
<phase name="MessageOut">
+ <handler name="EndOfRequestHandler"
+ class="org.apache.axis2.session.EndOfRequestHandler">
+ <order phase="MessageOut" phaseFirst="true"/>
+ </handler>
</phase>
Do we need to support by default , so having default session management stuff in axis2.xml is not good to me , what I suggest is to have them as parameters then you dont need to do any modifications to AxisConfigBuilder or any other core axis2 classes. Still I am thinking to implement session management as a module like Sandesha.
+ <!-- ================================================= -->
+ <!-- Session Management and Clustering -->
+ <!-- Comment this section on client side, no session management is needed for client side -->
+ <!-- ================================================= -->
+ <sessionManagerFactory class="org.apache.axis2.session.DefaultSessionManagerFactory">
+ <sessionManager class="org.apache.axis2.session.Axis2SessionManager">
Do you really need to have separate field to store session object in Message context , you can store that as a property.
And adding session management related stuff into Message receivers not going to be work , since ppl can write their own message receivers, so in that case he has to aware of session management.
AxisService service = msgContext.getAxisService();
+ if (service !=null && service.getSessionManager() != null){
+ return service.getSessionManager();
+ }
And I think adding a method to get session manager from AxisService and AxisConfiguration is not sound good to me , we have some other alternatives as you know even service implementation class we store as a parameter
// first check if there is a session manager for the service
+ AxisService service = msgContext.getAxisService();
+ if (service !=null && service.getSessionManager() != null){
+ return service.getSessionManager();
+ }
So please comment on this and I am very sorry for my delay to reply
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch, session_mgt_march30.patch, session_mgt_march31.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-532) Session Management
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=all ]
Rajith Attapattu updated AXIS2-532:
-----------------------------------
Attachment: session_mgt_march29.patch
oops forgot to svn add before making patch.
Sorry for the mistake
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-532) Session Management
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=all ]
Deepal Jayasinghe resolved AXIS2-532.
-------------------------------------
Resolution: Won't Fix
as I know we are going with different approach, so no need to keep this open
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: New Feature
> Affects Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch, session_mgt_march30.patch, session_mgt_march31.patch
>
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-532) Session Management
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12373076 ]
Deepal Jayasinghe commented on AXIS2-532:
-----------------------------------------
I went though the patch and understood that you have done a great job , thx for doing all those. I have few question to clarify.
We have transport independent session management called SOAP session , so if you deploy a service in a SOAP session scope then service will have transport independent session management. So there what will happen is ;
when you deploy a service in SOAP session , when a service get a request it will send a serviceGroupID (which is the session ID) back , so if user send that back (in the next request) then user will be able to come back to the same session.
In the meantime we have transport dependent session as well , both in simple HTTP server case and AxisServlet case we do support transport dependent session management.
I think I am missing something please explain to me , the difference between what we have right now and what you have done.
One other thing I understood from your path is that you can achieve the same goal by adding an axis2 module (.mar) , since what you have done is getting the session at the in handler and adding session id into outgoing message. So the best thing you should do is get the session by In handler and populate MessageContext using that.
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch, session_mgt_march30.patch, session_mgt_march31.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-532) Session Management
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12372462 ]
Davanum Srinivas commented on AXIS2-532:
----------------------------------------
could u please upload the new classes?
example:
org.apache.axis2.session.NullSessionManager;
org.apache.axis2.session.SessionManager;
thanks,
dims
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-532) Session Management
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=all ]
Rajith Attapattu updated AXIS2-532:
-----------------------------------
Attachment: session_mgt_march30.patch
Deepal,
I checked to see before uploading the patch and there are no conflicts and and was upto date with the HEAD revision at that time.
So I hope we can get it going this time.
Regards,
Rajith
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch, session_mgt_march30.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-532) Session Management
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-532?page=comments#action_12372568 ]
Rajith Attapattu commented on AXIS2-532:
----------------------------------------
Dims,
Sorry it looks like I didn't do and svn add before doing making the patch.
So it didn't contain any new files :-)
Sorry about the mix up.
Regards,
Rajith
> Session Management
> ------------------
>
> Key: AXIS2-532
> URL: http://issues.apache.org/jira/browse/AXIS2-532
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Versions: 0.95
> Reporter: Rajith Attapattu
> Attachments: session_march_28.patch, session_mgt_march29.patch
>
> Session Management
> -------------------------------
> This patch containes transport independent session mgt using WS-Addressing EPRs
> Interfaces
> --------------
> All interfaces are located in the core module
> Main interfaces useful for users
> org.apache.axis2.session.Session
> org.apache.axis2.session.SessionManager
> org.apache.axis2.session.SessionIdFactory
> There is a Null impl for these interfaces within core
> Implementation
> ------------------------
> All implementation specific classes are located in the session module
> Clustering impl
> ----------------------
> Clustering impl is located within the clustering module
> (only empty classes so far)
> Examples (located in the samples module)
> -----------------
> ATM example
> sample.session.atm.*
> Echo example
> sample.session.echo.*
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira