<!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: Load on startup is ignored - JaxWS webservice is always initialized first
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/asoldano">Alessio Soldano</a> in <i>JBoss AS7 Development</i> - <a href="http://community.jboss.org/message/617824#617824">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Hi rushead,</p><p>the WS endpoints is actually started during the deployment phase, which ends with rewriting (for POJO endpoints) [1] or creation (for EJB3 endpoints) of the webapp web.xml descriptor and start of the web transport layer. The servlet stuff is indeed just the transport layer/view of the webservice endpoint and is just the mean for serving HTTP requests to the webservice endpoints. The endpoint is thus created regardless of / independently from the servlet layer and the jbossws endpoint servlet delegates to the actual ws endpoints at runtime.</p><p>Expecting the servlet context to be available when the POJO endpoint bean is instanciated if unfortunately a wrong assumption here. Similarly, I bet you would not expect to have the servlet stuff available when an EJB3 WS endpoint is created in the case of EJB3 endpoints.</p><p>So unless there's a specification requirement (and I really believe there's not such req) mandating actually creating the endpoint after the web transport is up, this is not going to be modified, as this a design decision and it granted multiple benefits. Btw, AS6 was already based on this afair.</p><p>This said, you can probably achieve the behaviour you need differently, below are a couple of idea:</p><p>- you can modify your ws endpoint impl to call a given method when the first invocation comes; if your endpoint is being served on HTTP transport only, the servlet context and such will for sure be available</p><p>- you could also provide a configuration lookup mechanism that do not rely on the servlet init params (for instance lookup/read a conf or prop file in the deployment, use the ServiceLoader API, etc) and read your configuration in a @PostConstruct annotated method of the endpoint implementation</p><p>- if you still need to bound your endpoint creation to the servlet, you can have a custom servlet that programmatically starts a WS endpoint, either by the JAXWS Enpdoint.publish(..) API or through the EndpointPublisher API that is included in the current AS 7.1.0.Alpha1-SNAPSHOT version (that's still to be released, sorry)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>[1] your web.xml is rewritten by replacing the reference to the ws endpoint bean with the actual jbossws endpoint servlet; the endpoint bean class is passed to the endpoint servlet as a parameter</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/617824#617824">going to Community</a></p>
        <p style="margin: 0;">Start a new discussion in JBoss AS7 Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>