<div class="gmail_quote">Hi,</div><div class="gmail_quote"><br></div><div class="gmail_quote">On 28 October 2011 09:03, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">So all JARs must be OSGi-ified before they can be used? Is there any way to keep this information outside? </div></blockquote><div><br></div><div><font face="arial, helvetica, sans-serif">Right, all JARS </font>must be OSGi-ified before they can be deployed in an OSGi container. By the way, it's also possible to embed jars in a bundle, but that's not in the OSGi spirit. <font face="arial, helvetica, sans-serif">AFAIK, there is no way to put these information outside the jar (JBoss Modules is less intrusive here).</font></div>
<div><font face="arial, helvetica, sans-serif"><br></font></div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<font face="arial, helvetica, sans-serif"><span style="font-family:arial">Do you know of any other JSR published JAR that also expose its OSGi headers? </span></font></blockquote>
<div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">JAX-RS (JSR-311) </font><font face="arial, helvetica, sans-serif"><span style="font-family:arial">expose </span>the OSGi headers in its <a href="http://grepcode.com/file/repo1.maven.org/maven2/javax.ws.rs/jsr311-api/1.1.1/META-INF/MANIFEST.MF" target="_blank">Manifest</a>. </font></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I'm asking because declaring dependencies means that all dependent JSRs (and the JDK) will need to be OSGi-ified as well. I'd rather see that coordinated by the Java EE expert group. There is also the problem of supporting them forever(tm).</div>
</div></blockquote><div><br></div><div>No need to OSGi-ified the JDK, by default it's part of every Bundle classloader. </div><div><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">
</span></div><div><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">Currently, for BV there is no dependencies, so all packages just need to be exported (like JAX-RS).</span><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)"> I agree that if a dependency, non OSG</span>i-ified<span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">, is added to BV the interest is limited. I see two cases:</span></div>
<div><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)"><br></span></div><div><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">* the dependency can be </span><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">OSG</span>i-ified by the user -> OK</div>
<div>* the<span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)"> dependency cannot be </span><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)">OSG</span>i-ified -><span style="font-family:arial, helvetica, sans-serif;line-height:16px;white-space:pre-wrap;background-color:rgb(249, 249, 249)"> BV cannot be deployed as a bundle (but can be embedded in the user bundle)</span></div>
<div><br></div><div>--Kevin</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div><div><div></div><div>
<div>
On 27 oct. 2011, at 22:52, Kevin Pollet wrote:</div>
<br></div></div><blockquote type="cite"><div><div></div><div>
<div>
Hi experts,
</div><div><br></div><div>IMHO, making Bean Validation ready for the modular world is a great thing! </div><div><br></div><div>A first step might be to provide the module meta-datas (OSGi headers, …). For OSGi, those meta-datas can be added to the jar Manifest within the maven build with the <a href="http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html" target="_blank">maven-bundle-plugin</a>. The advantage is that the api can be deployed in an OSGi container out of the box. For JBoss Modules the descriptor <span style="color:rgb(51, 51, 51);font-family:Arial, Helvetica, FreeSans, sans-serif;line-height:17px">reside alongside its content but we can provide it.</span></div>
<div><br></div>
<div>WDYT?</div><div><br>--Kevin<br><br></div></div></div>
_______________________________________________<br>beanvalidation-dev mailing list<br><a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
<br></blockquote></div><br>