<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Re: jbossws-native: Publish HttpContext via Endpoint API
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/sgt_pimenta">Pedro Correia</a> in <i>JBoss Web Services</i> - <a href="http://community.jboss.org/message/605913#605913">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>>>> When you published endpoint from such servlet using old endpoint publish API the JBossWS AS integration implementation</p><p>>>> called AS internals and was executing deployment chain once again</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>You have a point. I agree on the "hack" here in terms of <span style="text-decoration: underline;">lifecycle</span>.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>>>> This part of JAX-WS specification is completely broken an unclear and many pieces of it NOT PORTABLE!</p><p>>>> I'd call it experimental feature of JAX-WS spec.</p><p>  </p><p>I agree <strong>javax.xml.ws.Endpoint</strong> is far from clear. But despite its lack of typification, method <strong>publish(Object serverContext)</strong> indicates that «server context encapsulates the server infrastructure and addressing information for a particular transport». At least the purpose to provide control to the user was clear.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>In fact your colleague Alessio Soldano has promoted its use! <span> ;) </span></p><p><a class="jive-link-external-small" href="http://jbossws.blogspot.com/2010/08/comsunnethttpserver-transport-using.html" target="_blank">http://jbossws.blogspot.com/2010/08/comsunnethttpserver-transport-using.html</a><span> </span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Correct me if I'm wrong, but in the end it's all about providing a HTTP SPI (which has been broken for JBossWS) in order to plug any HTTP server implementation. In my opinion, apart from the server lifecyle (which appears to be the real issue), it makes sense to allow programmatic deployment in any compliant container.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I do not question the choice for Netty, Jetty, etc. as a <span style="text-decoration: underline;">default </span>implementation. But it seems like a step-back for JBossWS to have broken its HTTP SPI. The deployment chain issue could have been solved (or so I wished) by establishing rules for a given server context, e.g. indicating the server lifecycle and initialization was controlled externally. Just a suggestion of course, I have not a clear idea of the complexity involved.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Bottom-line is... Any luck for a revamped version of the SPI? <span> :) </span></p><p>  </p><p>Regards,</p><p>Pedro</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/605913#605913">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss Web Services at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2044">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>