t will only run A1.
When B is started, at the end of it's
ServletContextListener.contextinitialized(...),
it makes a call into A which causes A to run A2. Then when your
retrieval
components call into B, it is ready for them.
--Ken
On Dec 10, 2009, at 11:14 AM, Scot Hatt wrote:
> That is
e, or I am completely missing the forest through the
trees via the information you are providing.
-Scot
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, December 10, 2009 11:26 AM
To: Tomcat Users List
Subject: Re: Context Chicken & Egg Problem
On 10/12/2009 16:14, S
he final A segment
(which contains the call to B).
--Ken
On Dec 10, 2009, at 10:32 AM, Scot Hatt wrote:
> Thank you for the response.
>
> I understand the limitation I am up against and it is not a
> production level
> issue that I have to get around. I have a local VM, as I
0/12/2009 15:15, Scot Hatt wrote:
> Hello,
>
> I have spent a great deal of time scouring the bug list and trying to put
> together the right set of terms to find resolution for this but have been
> unsuccessful.
>
> I am dealing with a situation where webapp A is calling a ser
Hello,
I have spent a great deal of time scouring the bug list and trying to put
together the right set of terms to find resolution for this but have been
unsuccessful.
I am dealing with a situation where webapp A is calling a servlet in webapp
B during A's startup. I think I am dealing wit
