-user@incubator.apache.org
Subject: Re: Spring, bus, confusion
Well, I guess my reaction is that anything you do in setup requires
an
explicit thing to reverse it in the tearDown. If you add a handler,
you should remove it in tearDown.
Dan
On Monday 01 October 2007, Benson Margulies
Hi Benson,
You can call bus.shutdown(true) in @After to tear down the server and the
jetty engine.
Willem.
bmargulies wrote:
Please forgive me for pasting a lot of code into here.
I'm trying to set up a unit test framework where the fixture sets up
jetty with an endpoint and some
I tried that. I still found my configuration changes to the server
'already present' when I create the next application context.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 9:11 AM
To: cxf-user@incubator.apache.org
Subject: Re: Spring
into a new app context. Yet, the server
on the bus still somehow has the extra handler.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 11:32 AM
To: cxf-user@incubator.apache.org
Subject: RE: Spring, bus, confusion
What do you mean
somehow has the extra handler.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 11:32 AM
To: cxf-user@incubator.apache.org
Subject: RE: Spring, bus, confusion
What do you mean the server's configuration is there?
Do you mean the jetty
No maven. These are tests in my product, run from Eclipse or ant.
-Original Message-
From: Freeman Fang [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 11:48 AM
To: cxf-user@incubator.apache.org
Subject: Re: Spring, bus, confusion
Hi Benson,
I assume you use mvn to run
