I see. The ideal solution here would be to discover that one of the @-injectors would indeed hand you something that could be followed to the Service or Endpoint, JAX-WS-wise. Now we have to wait for someone who knows to tell us.
On Thu, Feb 19, 2009 at 9:28 AM, Andrew Clegg <[email protected]> wrote: > 2009/2/19 Benson Margulies <[email protected]>: >> Right. To get a running provider, someone had to call >> Endpoint.publish. I was suggesting that whomever that is would hang >> onto the returned Endpoint and pass it into the provider, or walk the >> trail to the schema and store that somewhere the provider could find >> it. > > At the moment that's done for me by CXF. So I have an endpoint defined > in cxf-servlet.xml: > > <jaxws:endpoint id="FrontEndService" > implementor="info.cathdb.funcnet.impl.FrontEndServiceProviderFacade" > endpointName="funcnet:FrontEndPort" > serviceName="funcnet:FrontEndService" > address="/FrontEndService" > wsdlLocation="WEB-INF/wsdl/Services.wsdl"> > </jaxws:endpoint> > > I want to be able to get at WEB-INF/wsdl/Services.wsdl to retrieve its > schema, from within FrontEndServiceProviderFacade, without having to > provide FrontEndServiceProviderFacade with the path to the WSDL > separately to load and parse it (because that's a violation of DRY). > > Obviously I understand that CXF is calling Endpoint.publish somewhere > behind the curtain -- is there a simple way to hook into that process? > Perhaps this is easier for Spring experts but I've never done any > apart from in configuring CXF. > > Thanks again, > > Andrew. > > -- > :: http://biotext.org.uk/ :: >
