<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>I'd think it should be enough to make the necessary changes to
the embedded server and osgi subsystem (if there are any). <br>
The FrameworkFactory that uses the embedded server and stuff
related to the TCK setup should live in <a
href="https://github.com/jbosgi/jbosgi">jbosgi</a>.<br>
<br>
cheers<br>
--thomas<br>
<br>
</tt>
<div class="moz-cite-prefix">On 11/21/2012 10:45 AM, David
Bosschaert wrote:<br>
</div>
<blockquote cite="mid:50ACA2CC.8040904@redhat.com" type="cite">
<pre wrap="">As many know - AS7 is also an OSGi Framework meaning that it implements
the OSGi Core Specifications.
Additionally native JBoss support for more and more OSGi Enterprise
Specifications is being added. Examples are:
* The OSGi HttpService Specification (as7-5083)
* The OSGi WebApplication Specification (as7-5235)
* OSGi JPA support (as7-5476)
* other specs are also looked at
For everything that implements an OSGi spec there is also an OSGi TCK
testsuite. Over the past while I've been looking at getting AS7 to run
under the OSGi TCK. This is specifically needed when you want to check
that the above implementations are actually compliant with the specs.
To be able to run AS7 under the OSGi TCK 2 things had to be done:
* OSGi in AS7 had to be enhanced to support the OSGi Launcher API [1].
This is what the TCK uses to launch a framework.
* The TCK configuration files need to be tweaked so that it runs with
AS7 (instead of the RI).
I've implemented these two in
<a class="moz-txt-link-freetext" href="http://github.com/bosschaert/jboss-as/commit/8de4742e3f7bef059c2d12137c360ffb4d0a5780">http://github.com/bosschaert/jboss-as/commit/8de4742e3f7bef059c2d12137c360ffb4d0a5780</a>
I've added the TCK integration to the jboss-as/osgi/tck subtree. It's
fairly small as its mostly configuration and having it in jboss-as means
that we can easily kick off a tck run in hudson or from the commandline
for any AS build. It effectively gets us an additional bunch of system
tests for the (Enterprise) OSGi compliant components.
No changes to the product (build directory). The launcher API is not yet
included in the product, although we could decide to include it if we
think that makes sense.
I would like to file a pull request for this soon. Hope this works for
others. The associated JIRA is <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/AS7-5639">https://issues.jboss.org/browse/AS7-5639</a>
Thanks,
David
[1]
<a class="moz-txt-link-freetext" href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/launch/package-summary.html">http://www.osgi.org/javadoc/r4v42/org/osgi/framework/launch/package-summary.html</a>
_______________________________________________
jboss-as7-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</pre>
</body>
</html>