I am developing an SSO application and we are using this kind of scenario
when one app calls some actions of the other app. We are picking those URLs
from DB and simply providing links to them.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 3:22 AM
To: Struts Users Mailing List
Subject: Re: Communicate between two struts apps

Hello All,

I believe Single Sign On will be able to share Session attributes between 
applications. Single Sign On is supported by many application servers like 
Oracle, BEA, IBM, etc

Thanks and regards,
Pazhanikanthan. P (Paz)

Consultant for AXA,
HCL Australia Services Pty. Ltd.
Off   : +61-3-9618-4085
Mob : +61-0411-354-838




Monkeyden <[EMAIL PROTECTED]>
23/06/2006 07:42 AM
Please respond to "Struts Users Mailing List"

 
        To:     "Struts Users Mailing List" <user@struts.apache.org>, 
[EMAIL PROTECTED]
        cc: 
        Subject:        Re: Communicate between two struts apps


>AFAIK, if the applications are in two separate contexts there is
>no way to share data between them using a common session

Not to mention, some of the Struts tags (form, link) derive context at
runtime, so you don't have the ability to specify an external context.

>You'll be forced to do something kludgy and authenticate to both systems
>and maintain two sessions.

I don't know if I'd refer to SSO as "something klugy"





On 6/22/06, Eric Dahnke <[EMAIL PROTECTED]> wrote:
>
>
> AFAIK, if the applications are in two separate contexts there is
> no way to share data between them using a common session. You'll
> be forced to do something kludgy and authenticate to both systems
> and maintain two sessions.
>
> I would love to see a thread started about this because it is a
> big shortcoming I come up against frequently in Java. That is,
> different wars and contexts are a great way to separate and manage
> different large scale projects, but when it comes time to piece it
> back together as part of a large possibly modular application, yr
> fcked.
>
> Siteminder (a proprietary product) is a way to get around this and
> is Java friendly, but don't know how it works.
>
>
>
> On Thu Jun 22 13:10:18 EDT 2006, Wen-Jung Chen
> <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > We have two struts applications which are planning to be created
> > as two war
> > files and deployed as one ear file on application server. We
> > develop one
> > struts app and other team develops another one. The requirement
> > for us is
> > their struts application will call our action method to invoke a
> > window on
> > our side. Does anyone know how their struts app can invoke our
> > action
> > method? I was told that they can use url redirect by using url we
> > provided
> > so we can popup a window for them. Is this right way to do it? Is
> > there any
> > other better way to handle this since we are located in two
> > different jvm?
> > And also if we want to  pass data back so they can display
> > message on their
> > screen, are we still use same way such as url direct to pass data
> > as request
> > parameter to them?
> >
> > Please help.
> >
> > Thanks,
> > Wen-Jung
> >
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


_____________________________________________________________________ 
This e-mail has been scanned for viruses by MCI's Internet Managed 
Scanning Services - powered by MessageLabs. For further information 
visit http://www.mci.com


****************************************************************************
*****
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA.   Thank you.
****************************************************************************
******



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to