Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of rosenberg.leon@googlemail.com
 designates 64.233.162.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=uejxSWzScoOLbd78qwBwUr3Vam3mgfUx/sHr+6kWjX69SRRrzGW0WXeGG+JIAj/Mf0AdPGktGvkChejGItNW88f85XfglOG0Ge9CO9vMg4FkAdwb/83d9zNrdLlKYsEnEQBiEiTtVWRuitHPg++/3tXFhROLUDzgFkE7BFm59Oc=
Message-ID: <327858f40606231404g36be6b33qf9fc6b66ffc5dcbf@mail.gmail.com>
Date: Fri, 23 Jun 2006 23:04:24 +0200
From: "Leon Rosenberg" <rosenberg.leon@googlemail.com>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Re: Communicate between two struts apps
In-Reply-To: <399023580606231337r4a35e7fasa1afe31cac603c1e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <OF957E7B71.BB70A019-ONCA257195.00780030-CA257195.00781705@axa.com.au>
	 <0J1B00BIZ9NNA9I3@vms115.mailsrvcs.net>
	 <399023580606231337r4a35e7fasa1afe31cac603c1e@mail.gmail.com>

On 6/23/06, Madhav Bhargava <unmarshall@gmail.com> wrote:
> From your original mail the entire concept of having 2 war files bundled in
> one EAR file is a bit strange. You can totally avoid this by using different
> struts-config files and SwitchActions in struts.
>
> The two different teams can have their own set of actions, form beans,
> action mapping and whole lot of other stuff and still you can easily
> integrate the two into just one war file and package it in ear file.
>
> I would really like to know the benefit in having 2 war files.

Separate release processes?
Leon

>
> On 6/23/06, Mukta <mukta@amsoft.net> wrote:
> >
> > 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: paz.periasamy@axa.com.au [mailto:paz.periasamy@axa.com.au]
> > 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 <monkeyden@gmail.com>
> > 23/06/2006 07:42 AM
> > Please respond to "Struts Users Mailing List"
> >
> >
> >         To:     "Struts Users Mailing List" <user@struts.apache.org>,
> > edahnke@messagesmith.net
> >         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 <edahnke@messagesmith.net> 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
> > > <wenjungchen@gmail.com> 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: user-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: user-help@struts.apache.org
> > >
> > >
> >
> >
> > _____________________________________________________________________
> > 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: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>
>
> --
> When I tell the truth, it is not for the sake of convincing those who do not
> know it, but for the sake of defending those that do
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org