Another simple way to use tomcat with eclipse is to start tomcat with
remote debugging, and attach to it from eclipse. A couple of switches
in the tomcat startup script should do it.
-
To unsubscribe, e-mail: users-unsubscr...@tom
On the Eclipse question: Eclipse basically just starts your Tomcat
(which you configure
into Eclipse), using it's own startup script which maps all Tomcat
output into the Eclipse
console. As such, JNDI (or whatever else) works just like it does
when start Tomcat
from it's own startup.sh in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
I'm bringing this back onto the list in case it helps anyone. Also
marking OT.
On 12/15/2009 1:42 PM, David Fisher wrote:
> We designed things during the Tomcat 3 timeframe. I will need to push my
> developer to do it the JNDI way, I'll likely
Hi Chris,
Current architecture is to share a jar in shared/lib between the main
webapps, an admin webapps and a localhost only management webapps.
This
was originally in Tomcat 3. New architecture will separate each, drop
the management webapps and we'll control contexts via multicasting,
j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
On 12/14/2009 11:58 AM, Christopher Schultz wrote:
> FWIW, we recently moved from 5.5 to 5.0 in our development environment
Thanks, Ken.
s/5\.0/6.0/
:)
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using Gnu
Now that's really retro. :-)
On Dec 14, 2009, at 11:58 AM, Christopher Schultz wrote:
FWIW, we recently moved from 5.5 to 5.0 in our development environment
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 12/11/2009 3:39 PM, David Fisher wrote:
>> Finally, you might consider using a ServletContextListener instead of a
>> Servlet, as this is the recommended practice for context setup. You can
>> still provide a servlet to report on the status
Hi Chris,
public class UniverseLoader extends HttpServlet {
protected long timeLoaded;
public void init() throws ServletException {
new Thread(new LoadUniverseTask()).start();
}
public void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletExcept
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 12/10/2009 9:08 PM, David Fisher wrote:
> public class UniverseLoader extends HttpServlet {
>
> protected long timeLoaded;
>
> public void init() throws ServletException {
> new Thread(new LoadUniverseTask()).start();
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scot,
> Original Message
> Subject: RE: Context Chicken & Egg Problem
> From: "Caldarale, Charles R"
> Date: Thu, December 10, 2009 6:24 pm
> To: Tomcat Users List
>
>> From: sh...@radiant
s,
Dave
On Dec 10, 2009, at 5:34 PM, sh...@radiantblue.com wrote:
Thank you Chuck. That is exactly what I was looking for.
Original Message ----
Subject: RE: Context Chicken & Egg Problem
From: "Caldarale, Charles R"
Date: Thu, December 10, 2009 6:24 pm
To: Tomc
Thank you Chuck. That is exactly what I was looking for.
Original Message
Subject: RE: Context Chicken & Egg Problem
From: "Caldarale, Charles R"
Date: Thu, December 10, 2009 6:24 pm
To: Tomcat Users List
> From: sh...@radiantblue.com [mailto:sh...@radiantbl
> From: sh...@radiantblue.com [mailto:sh...@radiantblue.com]
> Subject: RE: Context Chicken & Egg Problem
>
> just a curiosity as to what is happening under the Tomcat
> covers during this scenario.
Tomcat initialization is single-thread, so if webapp A happens to get
initia
Thanks for your reply Chris.
I mentioned in one of the replies that this is only a question regarding
why an app in the initialization phase should or should not make an HTTP
call, for whatever reason, to a "yet to be initialized" context in the
same container. This is a case of "I want to run the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scot,
On 12/10/2009 12:45 PM, Scot Hatt wrote:
> So either I am just not able to adequately describe what I am seeing, nobody
> has dealt with this issue, or I am completely missing the forest through the
> trees via the information you are providing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scot,
On 12/10/2009 10:32 AM, Scot Hatt wrote:
> I was curious if there is a specific reference on this problem that I can
> point to for my fellow devs that try to run everything on a single Tomcat
> instance.
Not on a single Tomcat instance, but yo
at Users List
Subject: Re: Context Chicken & Egg Problem
It still seems like a simple issue to me.
Split your initialization of A into A1 and A2.
A2 is no longer part of immediate initialization for A.
Put your Scheduler launches, with their Data retrieve components, into
A2.
When A is started, i
- ...
- Data retrieval component n fires and calls
"http://localhost:8080/B/servlet/HereIsData";
- /A dies
Does this make more sense?
-Scot
-Original Message-
From: Ken Bowen [mailto:kbo...@als.com]
Sent: Thursday, December 10, 2009 10:47 AM
To: Tomcat Users List
Subject: Re: Context
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
n fires and calls
> "http://localhost:8080/B/servlet/HereIsData";
> - /A dies
>
> Does this make more sense?
> -Scot
>
> -Original Message-
> From: Ken Bowen [mailto:kbo...@als.com]
> Sent: Thursday, December 10, 2009 10:47 AM
> To: Tomcat Users List
> Su
cot Hatt
Subject: Re: Context Chicken& Egg Problem
On 10/12/2009 15:32, 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 stated, that
solves
the issue
10, 2009 10:47 AM
To: Tomcat Users List
Subject: Re: Context Chicken & Egg Problem
If I understand you correctly, your problem is that B needs to be
initialized before A.
(I don't understand what running locally as to do with it. ??)
If that is correct, why can't you organize the in
ssage-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, December 10, 2009 10:22 AM
To: users@tomcat.apache.org
Subject: Re: Context Chicken & Egg Problem
On 10/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
a specific reference on this problem that
I can
point to for my fellow devs that try to run everything on a single
Tomcat
instance.
-Scot
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, December 10, 2009 10:22 AM
To: users@tomcat.apache.org
Subject: Re: Conte
this problem that I can
point to for my fellow devs that try to run everything on a single Tomcat
instance.
-Scot
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, December 10, 2009 10:22 AM
To: users@tomcat.apache.org
Subject: Re: Context Chicken & Egg Problem
On 1
On 10/12/2009 15:22, Pid wrote:
On 10/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
On 10/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 servlet in webapp
B during A's
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
28 matches
Mail list logo
