See the WebServiceProxyGenerator:
http://outerthought.net/wiki/Wiki.jsp?page=WebServiceProxyGenerator
-Original Message-
From: Emmanuil Batsis (Manos) [mailto:[EMAIL PROTECTED]]
Sent: Saturday, 21 December 2002 00:24
To: [EMAIL PROTECTED]
Subject: Re: [Question] Re: cocoon-session
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
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
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
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,
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
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
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
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
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
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.
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
12 matches
Mail list logo