On Thu, 5 Dec 2002, Ken Fitzpatrick wrote:
> Date: Thu, 05 Dec 2002 20:11:46 -0600
> From: Ken Fitzpatrick <[EMAIL PROTECTED]>
> To: Craig R. McClanahan <[EMAIL PROTECTED]>
> Cc: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: Re: Communication Between
On Thu, 28 Nov 2002, Ken Fitzpatrick wrote:
> Date: Thu, 28 Nov 2002 22:12:32 -0600
> From: Ken Fitzpatrick <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Communi
t: Re: Communication Between WebApps
I'm hearing more and more about real-world requirements for sharing
information between WebApps -- not just the authentication thing, but
entire business object graphs.
Consider the user's choice for the web site Skin. Wouldn't it make
sense for
I'm hearing more and more about real-world requirements for sharing
information between WebApps -- not just the authentication thing, but
entire business object graphs.
Consider the user's choice for the web site Skin. Wouldn't it make
sense for subsequently visited WebApps to honor the choice
You can send them to a different machine, url, etc. But, sounds as if you
are looking for the sort of thing that Struts 1.1 does so well, and is
outlined in Struts in Action, a new book.
At 11:19 PM 11/26/2002 +, you wrote:
I'm trying to develop a Struts feasibility example for my project a
... looked into container-managed authentication yet? Tomcat (and
others, I believe) will let you do single sign-on among different apps.
With CMA you don't have to worry about how the authentication gets
invoked ... the container takes care of that.
Jonathan Holloway wrote:
I'm trying to dev
6 matches
Mail list logo