On Sep 21, 2006, at 4:13 PM, Raymond Feng wrote:
Please see my comments below.
----- Original Message ----- From: "Jeremy Boynes"
<[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Thursday, September 21, 2006 12:09 PM
Subject: Re: SCATestCase fails if there are extensions with META-
INF/sca/default.scdl on the classpath
On Sep 21, 2006, at 11:38 AM, Raymond Feng wrote:
Hi,
I'm trying to fix a problem reported by JIRA TUSCANY-739 (http://
issues.apache.org/jira/browse/TUSCANY-739). Basically, it was to
require that an extension module declare the SCDL in META-INF/
sca/ default.scdl. But the fix conflicts with a known issue that
we have discussed before. With quite a few samples extending
from SCATestCase, the build will fail because now the extension
code is on the application classpath and there are more than one
META-INF/ sca/default.scdl and the Launcher may pick the wrong
default.scdl for the application.
What can we do here?
Don't pick extensions up from the application classpath.
SCATestCase should work
a) with an installed version of Tuscany and it should boot the
runtime in the same way the launcher does, or
I understand this case.
b) in the integration test phase of the build using a plugin that
loads extensions into its own runtime
Can you elaborate a bit here? Did you mean to have a maven plugin
to load extensions into its own classloader? What about running
them inside IDEs?
Yes.
How do you run/debug a J2EE application inside an IDE? That's
basically rhetorical, all the IDEs I know need integration code to
talk to application frameworks and SCA fits in the same mode. Without
that, you have the option of running the launcher with debug on, or
running some other command and connecting with remote debug.
Remember, the SCA programming model is designed to let you test
application code without needing a full SCA runtime booted. Most
tests can be done that way, with just a few integration tests to
validate full functionality and typically you wouldn't run those from
an IDE anyway.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
