On Sep 1, 2006, at 9:22 AM, Raymond Feng wrote:
Hi,
Where do we stand for this topic?
Here are some questions to be confirmed:
1) Should we allow system/extension/application code on the same
classpath even it's not the best pratice? If not, should we get rid
of the "SCATestCase"?
People will do that so we need to define the behaviour when the
runtime is set up that way. That may include ignoring things from
that classpath.
I think SCATestCase in its current form is an aberration and should
be removed and replaced with an integration test framework.
2) Should we have different SCDL file naming conventions for
systems, extensions and applications?
No.
3) Should we use ClassLoader.getResource() to locate SCDL files?
That should be one way and we need to define the semantic on how it
works.
4) How do we support extension dependencies in the following cases?
* An extenasion depends on a 3rd party jar
* An extension depends on another extension
That depends on the type of dependency.
For class dependencies we should define how the classpath is
constructed, and code from any jar (extension or not) is just code on
that classpath.
For configuration dependencies we need to define how SCDL is located.
For component dependencies we need a mechanism to express them.
5) Do we have any plan to fully leverage OSGi to deal with bundle
isolations and dependencies?
We should be able to use that in an OSGi environment, but unless we
pre-req one then we need other mechanisms.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
