<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Yes, I totally agree. In the long run the webapp subsystem
should be able to process WAB deployments. <br>
Here is an entry point <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBAS-8956">https://issues.jboss.org/browse/JBAS-8956</a><br>
<br>
Currently, we deploy WABs on PAX-Web, which internally uses Jetty.
<br>
<br>
cheers<br>
-thomas </tt><br>
<br>
On 03/16/2011 10:22 AM, Ales Justin wrote:
<blockquote
cite="mid:7731D87C-58CE-4E97-8811-266320FFC98A@gmail.com"
type="cite">As I already commented on the JIRA issue, this
approach just won't fly in the long run.
<div>Imagine every similar sub-system as OSGi that would need to
be excluded all over the place.</div>
<div><br>
</div>
<div>I'm also not saying this should be done immediately,</div>
<div>but I hope you have a long term vision where this kind of
approach won't be needed.</div>
<div>Imo, this is what OSGi EE should be all about, to be able to
run side-by-side, properly integrated, not explicitly excluded.</div>
<div>
<div><br>
<div>
<div>On Mar 16, 2011, at 10:11 AM, Thomas Diesler wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
<div class="moz-text-flowed" style="font-family:
-moz-fixed; font-size: 12px;" lang="x-western">Folks,
<br>
<br>
an OSGi bundle deployment is fundamentally different
from an EE deployment and must be handled by the OSGi
subsystem. DUPs that are not targeted for OSGi bundle
deployments must ignore these. Currently the
recommended approach to ignore an OSGi deployment in a
DUP is <br>
<br>
DeploymentUnit deploymentUnit =
phaseContext.getDeploymentUnit(); <br>
if(deploymentUnit.hasAttachment(Attachments.OSGI_MANIFEST))
{ <br>
return; <br>
} <br>
<br>
If you work on some other type of marker attachment,
make sure that this marker is not attached for an OSGi
deployment. For the above check to work, the OSGi
manifest processor must come early in the chain. I
changed the order of structure processors to <br>
<br>
// STRUCTURE <br>
public static final int
STRUCTURE_MOUNT = 0x0000;
<br>
public static final int
STRUCTURE_MANIFEST = 0x0100;
<br>
public static final int
STRUCTURE_OSGI_MANIFEST = 0x0200;
<br>
public static final int
STRUCTURE_RAR = 0x0300;
<br>
... <br>
<br>
This relates to a bug related to WAB (Webapp Bundle)
deployments <br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://issues.jboss.org/browse/JBAS-8940">https://issues.jboss.org/browse/JBAS-8940</a>
<br>
<br>
cheers <br>
-thomas <br>
<br>
<br>
<div class="moz-txt-sig"><span class="moz-txt-tag">-- <br>
</span>xxxxxxxxxxxxxxxxxxxxxxxxxxxx <br>
Thomas Diesler <br>
JBoss OSGi Lead <br>
JBoss, a division of Red Hat <br>
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </div>
</div>
<br>
</div>
_______________________________________________<br>
jboss-as7-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br>
<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><br>
</blockquote>
</div>
<br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>