<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body 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 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>
</body>
</html>