You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Kishore <na...@techunified.com> on 2002/12/20 06:53:35 UTC
cocoon-session management.
Hi all,
I am using cocoon to apply XSL transformation
on XML files generated by my 'SERVLETS'. So, cocoon
intercepts the client request, calls the proper application servlet, then applies xsl mapping on the servlet's output and returns the result as a html file.
Now, the problem I am facing is, this way I am unable to maintain sessions among my servlet's clients. Each new request coming to my servlet is creating a session afresh because it's not the client directly, but cocoon that's making a request for my servlets.
Has anybody faced this problem or know the solution? Pl. let me know ASAP.
regards
nanda kishore.
Re: cocoon-session management.
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi Kishore:
I am using XSP. I am using the CVS 2.1 version of Cocoon that have a
better authentication framework.
The special thing I did was write a the <xsp-session:getxml> tag that
works as described in:
http://xml.apache.org/cocoon/developing/webapps/authentication.html
I understand you have a diferent problem. Since I am using just one huge
servlet called cocoon.
Antonio Gallardo.
Kishore dijo:
> Mr. Antonio Gallardo :
> You said you were using an
> application that is 100% cocoon based and that seems to preserve
> sessions.
> Now, could you let me know, if your content generators
> are
> servlets as is the case with me or JSP or XSPs. Also, whether you did
> something specially to be able to implement session management in your
> application.
>
> regards
> nanda kishore.
>
>
>
>
>
>
>
>> SAXESS - Hussayn Dabbous dijo:
>> > cocoon basically does not preserve session state in
>> > subrequests.
>> ? I dont think soo. I have currently running an application 100%
>> Cocoon based that works with the authentication framework. And it
>> looks like the sessions are preserved.
>>
>> Can you explain more why you told that?
>>
>> Antonio Gallardo
>>
>> >
>> > i'm currently working together with another developer on a
>> > general solution. We are investigating severeal approaches.
>> >
>> > Currently we are looking at the idea to add another
>> > protocol to cocoon, or enhance the http protocol. There
>> > was the idea to enhance the new webproxy generator, but
>> > we want to check out first, if the protocol enhancement
>> > would do a better job here. It may be a more general
>> > approach...
>> >
>> > I made some basic tests and things work fine. I expect to
>> > write some preliminary results tonight or tomorrow.
>> >
>> > As i see multiple requests on this theme i get convinced
>> > there is severe need for this feature.
>> >
>> > I want to inform you, that this enhancement is a commercially
>> > triggered work. The participants in the project are beeing
>> > payed for their work but the results are kept open source...
>> >
>> > I'd like to see more projects of this kind. So also individual
>> programmers could can benefit ...
>> >
>> > regards, hussayn
>> >
>> > Kishore wrote:
>> >> Hi all,
>> >> I am using cocoon to apply XSL transformation
>> >> on XML files generated by my 'SERVLETS'. So, cocoon
>> >> intercepts the client request, calls the proper application
>> servlet, then applies xsl mapping on the servlet's output and
>> returns the result as a html file.
>> >> Now, the problem I am facing is, this way I am
>> unable
>> >> to
>> >> maintain sessions among my servlet's clients. Each new request
>> coming to my servlet is creating a session afresh because it's not
>> the client directly, but cocoon that's making a request for my
>> servlets.
>> >> Has anybody faced this problem or know the
>> solution?
>> >> Pl.
>> >> let me know ASAP.
>> >>
>> >> regards
>> >> nanda kishore.
>> >
>> >
>> > ---------------------------------------------------------------------
>> Please check that your question has not already been answered in
>> the FAQ before posting.
>> <http://xml.apache.org/cocoon/faq/index.html>
>> >
>> > To unsubscribe, e-mail:
>> <co...@xml.apache.org> For additional commands,
>> e-mail: <co...@xml.apache.org>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>> To unsubscribe, e-mail: <co...@xml.apache.org>
>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by Kishore <na...@techunified.com>.
Mr. Antonio Gallardo :
You said you were using an
application that is 100% cocoon based and that seems to preserve sessions.
Now, could you let me know, if your content generators are
servlets as is the case with me or JSP or XSPs. Also, whether you did
something specially to be able to implement session management in your
application.
regards
nanda kishore.
> SAXESS - Hussayn Dabbous dijo:
> > cocoon basically does not preserve session state in
> > subrequests.
> ? I dont think soo. I have currently running an application 100% Cocoon
> based that works with the authentication framework. And it looks like the
> sessions are preserved.
>
> Can you explain more why you told that?
>
> Antonio Gallardo
>
> >
> > i'm currently working together with another developer on a
> > general solution. We are investigating severeal approaches.
> >
> > Currently we are looking at the idea to add another
> > protocol to cocoon, or enhance the http protocol. There
> > was the idea to enhance the new webproxy generator, but
> > we want to check out first, if the protocol enhancement
> > would do a better job here. It may be a more general
> > approach...
> >
> > I made some basic tests and things work fine. I expect to
> > write some preliminary results tonight or tomorrow.
> >
> > As i see multiple requests on this theme i get convinced
> > there is severe need for this feature.
> >
> > I want to inform you, that this enhancement is a commercially
> > triggered work. The participants in the project are beeing
> > payed for their work but the results are kept open source...
> >
> > I'd like to see more projects of this kind. So also individual
> > programmers could can benefit ...
> >
> > regards, hussayn
> >
> > Kishore wrote:
> >> Hi all,
> >> I am using cocoon to apply XSL transformation
> >> on XML files generated by my 'SERVLETS'. So, cocoon
> >> intercepts the client request, calls the proper application servlet,
> >> then applies xsl mapping on the servlet's output and returns the
> >> result as a html file.
> >> Now, the problem I am facing is, this way I am unable
> >> to
> >> maintain sessions among my servlet's clients. Each new request coming
> >> to my servlet is creating a session afresh because it's not the
> >> client directly, but cocoon that's making a request for my servlets.
> >> Has anybody faced this problem or know the solution?
> >> Pl.
> >> let me know ASAP.
> >>
> >> regards
> >> nanda kishore.
> >
> >
> > ---------------------------------------------------------------------
> > Please check that your question has not already been answered in the
> > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
> >
> > To unsubscribe, e-mail: <co...@xml.apache.org>
> > For additional commands, e-mail: <co...@xml.apache.org>
>
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: [Question] Re: cocoon-session management.
Posted by Conal Tuohy <co...@paradise.net.nz>.
See the WebServiceProxyGenerator:
http://outerthought.net/wiki/Wiki.jsp?page=WebServiceProxyGenerator
> -----Original Message-----
> From: Emmanuil Batsis (Manos) [mailto:mbatsis@humanmarkup.org]
> Sent: Saturday, 21 December 2002 00:24
> To: cocoon-users@xml.apache.org
> Subject: Re: [Question] Re: cocoon-session management.
>
>
>
>
> SAXESS - Hussayn Dabbous wrote:
> > Maybe HTTPClient supports proxy functionalities?
> > That may help getting things done...
>
> I agree that the ideal situation is the ability to forward cookies
> between the remote application and the real client (i.e. a browser
> requesting from Cocoon) and vice versa. Additionally, those cookies
> should be readable *and* modifyable by logic inside Cocoon.
>
>
> > If you are interested, we can get into a discussion.
> > Maybe we should wait until our preliminary results are
> > available?
>
>
> Unfortunatelly I just started with HttpClient and haven't found any
> related functionality in the documentation. I posted a question on
> commons-users (see [1]).
>
> Let's wait a bit and see what happens :-)
>
>
> [1]
> http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=104038254206245&w=2
>
>
> Manos
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: [Question] Re: cocoon-session management.
Posted by "Emmanuil Batsis (Manos)" <mb...@humanmarkup.org>.
SAXESS - Hussayn Dabbous wrote:
> Maybe HTTPClient supports proxy functionalities?
> That may help getting things done...
I agree that the ideal situation is the ability to forward cookies
between the remote application and the real client (i.e. a browser
requesting from Cocoon) and vice versa. Additionally, those cookies
should be readable *and* modifyable by logic inside Cocoon.
> If you are interested, we can get into a discussion.
> Maybe we should wait until our preliminary results are
> available?
Unfortunatelly I just started with HttpClient and haven't found any
related functionality in the documentation. I posted a question on
commons-users (see [1]).
Let's wait a bit and see what happens :-)
[1]
http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=104038254206245&w=2
Manos
>
> regards, hussayn
>
> Emmanuil Batsis (Manos) wrote:
>
>>
>> I'm in a similar situation (but without cocoon) and investigating the
>> HttpClient [1](from commons). HttpClient can hadle cookies which makes
>> it a session-able HTTP client.
>>
>> My question here is, does it make sense to try and build a generator
>> for Cocoon with the above? I am under the impression that sitemap
>> logic is not session-aware (as a client of remote applications).
>>
>> [1] http://jakarta.apache.org/commons/httpclient/
>>
>> Thanks,
>>
>> Manos
>>
>>
>>
>> SAXESS - Hussayn Dabbous wrote:
>>
>>> I am talking about following setup:
>>>
>>> You have two separate webapplications not necessaryly
>>> running in the same container! One app is the cocoon
>>> application. The other app is a session based webapp.
>>>
>>> Now you setup a pipeline, which gathers data from the
>>> other webapp. Here you are lost.
>>>
>>> What basically is missing: The session state is
>>> usually preserved within cookies, or by URL-rewriting.
>>> If sessions are cookie based, we need to pass the session
>>> cookie through cocoon. And this is definitely not implemented
>>> yet. Or my understanding of the cocoon code is absolutley
>>> wrong ;-)
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>> To unsubscribe, e-mail: <co...@xml.apache.org>
>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: [Question] Re: cocoon-session management.
Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
Yes, in principle you are right. You could use
HTTPClient to organise the session management.
But you will have to consider other points:
1.) Your subsession may be authenticated. Thus you
will have to maintain interactions between the
cocoon-client and the far-application server to
get logged into your subsystem. Then you would
be faced with flow control iussues...
This may be a problem, since your cocoon-client
operates silently in the background...
2.) Besides this, your subsession might want to
pass permanent cookies to it's client. This may
be possible with HTTP-Client, but then you will
have to maintain a cookie-database for your
cocoon clients... (No problem if your app runs
only for yourself ;-)
Both points are from my point of view problematic.
In certain cases the approach work. In other cases
you might run into complexity problems.
I would rather keep the interaction at the browser
site, thus it is the browser who keeps the cookies
and it is the cocoon-client, who acts as a proxy and
passes the cookies to the underlying subsystem...
OK, here you face other problems, but these problems
can at least be solved in general without getting
too mutch complexity into the game...
Maybe HTTPClient supports proxy functionalities?
That may help getting things done...
If you are interested, we can get into a discussion.
Maybe we should wait until our preliminary results are
available?
regards, hussayn
Emmanuil Batsis (Manos) wrote:
>
> I'm in a similar situation (but without cocoon) and investigating the
> HttpClient [1](from commons). HttpClient can hadle cookies which makes
> it a session-able HTTP client.
>
> My question here is, does it make sense to try and build a generator for
> Cocoon with the above? I am under the impression that sitemap logic is
> not session-aware (as a client of remote applications).
>
> [1] http://jakarta.apache.org/commons/httpclient/
>
> Thanks,
>
> Manos
>
>
>
> SAXESS - Hussayn Dabbous wrote:
>
>> I am talking about following setup:
>>
>> You have two separate webapplications not necessaryly
>> running in the same container! One app is the cocoon
>> application. The other app is a session based webapp.
>>
>> Now you setup a pipeline, which gathers data from the
>> other webapp. Here you are lost.
>>
>> What basically is missing: The session state is
>> usually preserved within cookies, or by URL-rewriting.
>> If sessions are cookie based, we need to pass the session
>> cookie through cocoon. And this is definitely not implemented
>> yet. Or my understanding of the cocoon code is absolutley
>> wrong ;-)
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
[Question] Re: cocoon-session management.
Posted by "Emmanuil Batsis (Manos)" <mb...@humanmarkup.org>.
I'm in a similar situation (but without cocoon) and investigating the
HttpClient [1](from commons). HttpClient can hadle cookies which makes
it a session-able HTTP client.
My question here is, does it make sense to try and build a generator for
Cocoon with the above? I am under the impression that sitemap logic is
not session-aware (as a client of remote applications).
[1] http://jakarta.apache.org/commons/httpclient/
Thanks,
Manos
SAXESS - Hussayn Dabbous wrote:
> I am talking about following setup:
>
> You have two separate webapplications not necessaryly
> running in the same container! One app is the cocoon
> application. The other app is a session based webapp.
>
> Now you setup a pipeline, which gathers data from the
> other webapp. Here you are lost.
>
> What basically is missing: The session state is
> usually preserved within cookies, or by URL-rewriting.
> If sessions are cookie based, we need to pass the session
> cookie through cocoon. And this is definitely not implemented
> yet. Or my understanding of the cocoon code is absolutley
> wrong ;-)
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi Hussayn:
I agree with you. In that case you lost the session tracking. Apparently
Cocoon manages his own sessions.
I think we need to make Cocoon to work with the Tomcat Sessions or (to be
more general) with the Servlet Container Session Management. In that way
all will be OK accross multiple web applications.
Yesterday I was reading about the new persistent session management in
Tomcat 4.1.x. I think we can make use of it. But, since Cocoon works with
the Java Servlet Specification 2.2 and not 2.3, this can be an issue to
resolve. I feel like you in that the session management is weak at the
current development of Cocoon. We need some improvement here to help
webapplication development. The best approach is try to be the most
closest to the specification 2.3.
At the end, for session management in only one application, the current
authentication framework is OK.
Sorry for the incoveniences. :-D
Antonio Gallardo.
SAXESS - Hussayn Dabbous dijo:
> Maybe there is a missunderstanding here?
>
> cocoon preserves session when you keep within your
> webapplication. But i am talking about another
> problem:
>
> If you are specifying a source over the http: protocol,
> cocoon simply opens another HTTPClient request. This
> request does NOT preserve the session state!
>
> I am talking about following setup:
>
> You have two separate webapplications not necessaryly
> running in the same container! One app is the cocoon
> application. The other app is a session based webapp.
>
> Now you setup a pipeline, which gathers data from the
> other webapp. Here you are lost.
>
> What basically is missing: The session state is
> usually preserved within cookies, or by URL-rewriting.
> If sessions are cookie based, we need to pass the session
> cookie through cocoon. And this is definitely not implemented
> yet. Or my understanding of the cocoon code is absolutley
> wrong ;-)
>
>
> regards, hussayn
>
>
> Antonio Gallardo wrote:
>> SAXESS - Hussayn Dabbous dijo:
>>
>>>cocoon basically does not preserve session state in
>>>subrequests.
>>
>> ? I dont think soo. I have currently running an application 100%
>> Cocoon based that works with the authentication framework. And it
>> looks like the sessions are preserved.
>>
>> Can you explain more why you told that?
>>
>> Antonio Gallardo
>>
>>
>>>i'm currently working together with another developer on a
>>>general solution. We are investigating severeal approaches.
>>>
>>>Currently we are looking at the idea to add another
>>>protocol to cocoon, or enhance the http protocol. There
>>>was the idea to enhance the new webproxy generator, but
>>>we want to check out first, if the protocol enhancement
>>>would do a better job here. It may be a more general
>>>approach...
>>>
>>>I made some basic tests and things work fine. I expect to
>>>write some preliminary results tonight or tomorrow.
>>>
>>>As i see multiple requests on this theme i get convinced
>>>there is severe need for this feature.
>>>
>>>I want to inform you, that this enhancement is a commercially
>>>triggered work. The participants in the project are beeing
>>>payed for their work but the results are kept open source...
>>>
>>>I'd like to see more projects of this kind. So also individual
>>>programmers could can benefit ...
>>>
>>>regards, hussayn
>>>
>>>Kishore wrote:
>>>
>>>>Hi all,
>>>> I am using cocoon to apply XSL transformation
>>>>on XML files generated by my 'SERVLETS'. So, cocoon
>>>>intercepts the client request, calls the proper application servlet,
>>>> then applies xsl mapping on the servlet's output and returns the
>>>> result as a html file.
>>>> Now, the problem I am facing is, this way I am unable
>>>>to
>>>>maintain sessions among my servlet's clients. Each new request coming
>>>> to my servlet is creating a session afresh because it's not the
>>>> client directly, but cocoon that's making a request for my servlets.
>>>> Has anybody faced this problem or know the solution?
>>>>Pl.
>>>>let me know ASAP.
>>>>
>>>>regards
>>>>nanda kishore.
>>>
>>>
>>>---------------------------------------------------------------------
>>> Please check that your question has not already been answered in the
>>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>>
>>>To unsubscribe, e-mail: <co...@xml.apache.org>
>>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>> To unsubscribe, e-mail: <co...@xml.apache.org>
>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
maybe there is a chance, if the following holds:
1.) your servlets run within your cocoon based webapp
2.) you access the servlets over "context:" or
"cocoon:" protocol.
I was previously talking only about the "http:"
protocoll. For the other two protocols i might
be wrong in the use case described above.
regards, hussayn
SAXESS - Hussayn Dabbous wrote:
> Maybe there is a missunderstanding here?
>
> cocoon preserves session when you keep within your
> webapplication. But i am talking about another
> problem:
>
> If you are specifying a source over the http: protocol,
> cocoon simply opens another HTTPClient request. This
> request does NOT preserve the session state!
>
> I am talking about following setup:
>
> You have two separate webapplications not necessaryly
> running in the same container! One app is the cocoon
> application. The other app is a session based webapp.
>
> Now you setup a pipeline, which gathers data from the
> other webapp. Here you are lost.
>
> What basically is missing: The session state is
> usually preserved within cookies, or by URL-rewriting.
> If sessions are cookie based, we need to pass the session
> cookie through cocoon. And this is definitely not implemented
> yet. Or my understanding of the cocoon code is absolutley
> wrong ;-)
>
>
> regards, hussayn
>
>
> Antonio Gallardo wrote:
>
>> SAXESS - Hussayn Dabbous dijo:
>>
>>> cocoon basically does not preserve session state in
>>> subrequests.
>>
>>
>> ? I dont think soo. I have currently running an application 100% Cocoon
>> based that works with the authentication framework. And it looks like the
>> sessions are preserved.
>>
>> Can you explain more why you told that?
>>
>> Antonio Gallardo
>>
>>
>>> i'm currently working together with another developer on a
>>> general solution. We are investigating severeal approaches.
>>>
>>> Currently we are looking at the idea to add another
>>> protocol to cocoon, or enhance the http protocol. There
>>> was the idea to enhance the new webproxy generator, but
>>> we want to check out first, if the protocol enhancement
>>> would do a better job here. It may be a more general
>>> approach...
>>>
>>> I made some basic tests and things work fine. I expect to
>>> write some preliminary results tonight or tomorrow.
>>>
>>> As i see multiple requests on this theme i get convinced
>>> there is severe need for this feature.
>>>
>>> I want to inform you, that this enhancement is a commercially
>>> triggered work. The participants in the project are beeing
>>> payed for their work but the results are kept open source...
>>>
>>> I'd like to see more projects of this kind. So also individual
>>> programmers could can benefit ...
>>>
>>> regards, hussayn
>>>
>>> Kishore wrote:
>>>
>>>> Hi all,
>>>> I am using cocoon to apply XSL transformation
>>>> on XML files generated by my 'SERVLETS'. So, cocoon
>>>> intercepts the client request, calls the proper application servlet,
>>>> then applies xsl mapping on the servlet's output and returns the
>>>> result as a html file.
>>>> Now, the problem I am facing is, this way I am unable
>>>> to
>>>> maintain sessions among my servlet's clients. Each new request coming
>>>> to my servlet is creating a session afresh because it's not the
>>>> client directly, but cocoon that's making a request for my servlets.
>>>> Has anybody faced this problem or know the solution?
>>>> Pl.
>>>> let me know ASAP.
>>>>
>>>> regards
>>>> nanda kishore.
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> Please check that your question has not already been answered in the
>>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>>
>>> To unsubscribe, e-mail: <co...@xml.apache.org>
>>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>> To unsubscribe, e-mail: <co...@xml.apache.org>
>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
Maybe there is a missunderstanding here?
cocoon preserves session when you keep within your
webapplication. But i am talking about another
problem:
If you are specifying a source over the http: protocol,
cocoon simply opens another HTTPClient request. This
request does NOT preserve the session state!
I am talking about following setup:
You have two separate webapplications not necessaryly
running in the same container! One app is the cocoon
application. The other app is a session based webapp.
Now you setup a pipeline, which gathers data from the
other webapp. Here you are lost.
What basically is missing: The session state is
usually preserved within cookies, or by URL-rewriting.
If sessions are cookie based, we need to pass the session
cookie through cocoon. And this is definitely not implemented
yet. Or my understanding of the cocoon code is absolutley
wrong ;-)
regards, hussayn
Antonio Gallardo wrote:
> SAXESS - Hussayn Dabbous dijo:
>
>>cocoon basically does not preserve session state in
>>subrequests.
>
> ? I dont think soo. I have currently running an application 100% Cocoon
> based that works with the authentication framework. And it looks like the
> sessions are preserved.
>
> Can you explain more why you told that?
>
> Antonio Gallardo
>
>
>>i'm currently working together with another developer on a
>>general solution. We are investigating severeal approaches.
>>
>>Currently we are looking at the idea to add another
>>protocol to cocoon, or enhance the http protocol. There
>>was the idea to enhance the new webproxy generator, but
>>we want to check out first, if the protocol enhancement
>>would do a better job here. It may be a more general
>>approach...
>>
>>I made some basic tests and things work fine. I expect to
>>write some preliminary results tonight or tomorrow.
>>
>>As i see multiple requests on this theme i get convinced
>>there is severe need for this feature.
>>
>>I want to inform you, that this enhancement is a commercially
>>triggered work. The participants in the project are beeing
>>payed for their work but the results are kept open source...
>>
>>I'd like to see more projects of this kind. So also individual
>>programmers could can benefit ...
>>
>>regards, hussayn
>>
>>Kishore wrote:
>>
>>>Hi all,
>>> I am using cocoon to apply XSL transformation
>>>on XML files generated by my 'SERVLETS'. So, cocoon
>>>intercepts the client request, calls the proper application servlet,
>>>then applies xsl mapping on the servlet's output and returns the
>>>result as a html file.
>>> Now, the problem I am facing is, this way I am unable
>>>to
>>>maintain sessions among my servlet's clients. Each new request coming
>>>to my servlet is creating a session afresh because it's not the
>>>client directly, but cocoon that's making a request for my servlets.
>>> Has anybody faced this problem or know the solution?
>>>Pl.
>>>let me know ASAP.
>>>
>>>regards
>>>nanda kishore.
>>
>>
>>---------------------------------------------------------------------
>>Please check that your question has not already been answered in the
>>FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>>To unsubscribe, e-mail: <co...@xml.apache.org>
>>For additional commands, e-mail: <co...@xml.apache.org>
>
>
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
SAXESS - Hussayn Dabbous dijo:
> cocoon basically does not preserve session state in
> subrequests.
? I dont think soo. I have currently running an application 100% Cocoon
based that works with the authentication framework. And it looks like the
sessions are preserved.
Can you explain more why you told that?
Antonio Gallardo
>
> i'm currently working together with another developer on a
> general solution. We are investigating severeal approaches.
>
> Currently we are looking at the idea to add another
> protocol to cocoon, or enhance the http protocol. There
> was the idea to enhance the new webproxy generator, but
> we want to check out first, if the protocol enhancement
> would do a better job here. It may be a more general
> approach...
>
> I made some basic tests and things work fine. I expect to
> write some preliminary results tonight or tomorrow.
>
> As i see multiple requests on this theme i get convinced
> there is severe need for this feature.
>
> I want to inform you, that this enhancement is a commercially
> triggered work. The participants in the project are beeing
> payed for their work but the results are kept open source...
>
> I'd like to see more projects of this kind. So also individual
> programmers could can benefit ...
>
> regards, hussayn
>
> Kishore wrote:
>> Hi all,
>> I am using cocoon to apply XSL transformation
>> on XML files generated by my 'SERVLETS'. So, cocoon
>> intercepts the client request, calls the proper application servlet,
>> then applies xsl mapping on the servlet's output and returns the
>> result as a html file.
>> Now, the problem I am facing is, this way I am unable
>> to
>> maintain sessions among my servlet's clients. Each new request coming
>> to my servlet is creating a session afresh because it's not the
>> client directly, but cocoon that's making a request for my servlets.
>> Has anybody faced this problem or know the solution?
>> Pl.
>> let me know ASAP.
>>
>> regards
>> nanda kishore.
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon-session management.
Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
cocoon basically does not preserve session state in
subrequests.
i'm currently working together with another developer on a
general solution. We are investigating severeal approaches.
Currently we are looking at the idea to add another
protocol to cocoon, or enhance the http protocol. There
was the idea to enhance the new webproxy generator, but
we want to check out first, if the protocol enhancement
would do a better job here. It may be a more general
approach...
I made some basic tests and things work fine. I expect to
write some preliminary results tonight or tomorrow.
As i see multiple requests on this theme i get convinced
there is severe need for this feature.
I want to inform you, that this enhancement is a commercially
triggered work. The participants in the project are beeing
payed for their work but the results are kept open source...
I'd like to see more projects of this kind. So also individual
programmers could can benefit ...
regards, hussayn
Kishore wrote:
> Hi all,
> I am using cocoon to apply XSL transformation
> on XML files generated by my 'SERVLETS'. So, cocoon
> intercepts the client request, calls the proper application servlet,
> then applies xsl mapping on the servlet's output and returns the result
> as a html file.
> Now, the problem I am facing is, this way I am unable to
> maintain sessions among my servlet's clients. Each new request coming to
> my servlet is creating a session afresh because it's not the client
> directly, but cocoon that's making a request for my servlets.
> Has anybody faced this problem or know the solution? Pl.
> let me know ASAP.
>
> regards
> nanda kishore.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>