JAX-WS web service - "Cannot find dispatch method"

I'm getting the same error response every time I send a request to my JAX-WS web service:
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>I've tried using JAX-WS RI 2.1.7 and 2.2 on my Tomcat server, but both return the same error response. It will return the WSDL just fine (when "?wsdl" is appended to the endpoint URL). I used "wsimport" to generate the necessary Java classes from my WSDL--it used JAX-WS RI 2.1.6 (the one included with the JDK I guess) to generate the Java source files.
Other people online have had similar problems, but never with the SOAP element "{http://www.w3.org/2003/05/soap-envelope}Envelope", always with things specific to their WSDLs like "{}reqParams" or "{http://www.telekom.at/eai/WSToCramerCSIRead}CSIRead". I set a debug breakpoint at the start of my SIB method and it doesn't even get that far.
Any ideas? Thanks for your help.
WSDL:
<?xml version="1.0" encoding="utf-8"?>
<!-- This wsdl file is for an XDS-I.b Imaging Document Source Actor
     It can be used 'as is' to support Imaging Document Source Retrieve Imaging Document Set Transaction
     using Synchronous Web Services. 
     -->
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
  xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:ihe="urn:ihe:iti:xds-b:2007" xmlns:iherad="urn:ihe:rad:xdsi-b:2009" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
  targetNamespace="urn:ihe:rad:xdsi-b:2009" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
  xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" name="ImagingDocumentSource">
  <documentation>IHE XDS-I.b Imaging Document Source</documentation>
  <types>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:iti:xds-b:2007"
      xmlns:ihe="urn:ihe:iti:xds-b:2007">
      <!-- Include the message schema -->
      <xsd:include schemaLocation="../schema/IHE/XDS.b_DocumentRepository.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:rad:xdsi-b:2009"
      xmlns:ihe="urn:ihe:iti:xds-b:2007"
      xmlns:iherad="urn:ihe:rad:xdsi-b:2009">
      <!-- Include the message schema -->
      <xsd:include schemaLocation="../schema/IHE/XDSI.b_ImagingDocumentSource.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
      xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0">
      <!-- Include the message schema -->
      <xsd:include schemaLocation="../schema/ebRS/rs.xsd"/>
    </xsd:schema>
    <!-- While no elements are directly used from these schema in the WSDL,
      they need to be present here in order for
      code generating toolkits to work properly -->
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0">
      <!-- Include the message schema -->
      <xsd:include schemaLocation="../schema/ebRS/lcm.xsd"/>
    </xsd:schema>
   <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
      <!-- Include the message schema -->
      <xsd:include schemaLocation="../schema/ebRS/rim.xsd"/>
    </xsd:schema>
  </types>
  <message name="RetrieveImagingDocumentSetRequest_Message">
    <documentation>Retrieve Imaging Document Set</documentation>
    <part name="body" element="iherad:RetrieveImagingDocumentSetRequest"/>
  </message>
  <message name="RetrieveDocumentSetResponse_Message">
    <documentation>Retrieve Document Set Response</documentation>
    <part name="body" element="ihe:RetrieveDocumentSetResponse"/>
  </message>
  <portType name="ImagingDocumentSource_PortType">
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <input message="iherad:RetrieveImagingDocumentSetRequest_Message"
        wsaw:Action="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <output message="iherad:RetrieveDocumentSetResponse_Message"
        wsaw:Action="urn:ihe:iti:2007:RetrieveDocumentSetResponse"/>
    </operation>
  </portType>
  <binding name="ImagingDocumentSource_Binding" type="iherad:ImagingDocumentSource_PortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <soap12:operation soapAction="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <input>
        <soap12:body use="literal"/>
      </input>
      <output>
        <soap12:body use="literal"/>
      </output>
    </operation>
  </binding>
  <service name="ImagingDocumentSource_Service">
    <port name="ImagingDocumentSource_Port_Soap12" binding="iherad:ImagingDocumentSource_Binding">
      <soap12:address location="http://localhost:8080/webservice-test/ridsService"/>
    </port>
  </service>
</definitions>
Request:
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:urn="urn:ihe:rad:xdsi-b:2009"
xmlns:urn1="urn:ihe:iti:xds-b:2007"
xmlns:a="http://www.w3.org/2005/08/addressing">
   <soap:Header>
     <a:Action soap:mustUnderstand="1">urn:ihe:rad:2009:RetrieveImagingDocumentSet</a:Action>
     <a:MessageID>urn:uuid:0fbfdced-6c01-4d09-a110-2201afedaa02</a:MessageID>
     <a:ReplyTo soap:mustUnderstand="1">
          <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
     </a:ReplyTo>
     <a:To>http://localhost:8080/webservice-test/ridsServer</a:To>
   </soap:Header>
   <soap:Body>
      <urn:RetrieveImagingDocumentSetRequest>
         <!--1 or more repetitions:-->
         <urn:StudyRequest studyInstanceUID="test1">
            <!--1 or more repetitions:-->
            <urn:SeriesRequest seriesInstanceUID="test2">
               <!--1 or more repetitions:-->
               <urn1:DocumentRequest>
                  <!--Optional:-->
                  <urn1:HomeCommunityId>test3</urn1:HomeCommunityId>
                  <urn1:RepositoryUniqueId>test4</urn1:RepositoryUniqueId>
                  <urn1:DocumentUniqueId>test5</urn1:DocumentUniqueId>
               </urn1:DocumentRequest>
            </urn:SeriesRequest>
         </urn:StudyRequest>
         <urn:TransferSyntaxUIDList>
            <!--1 or more repetitions:-->
            <urn:TransferSyntaxUID>?</urn:TransferSyntaxUID>
         </urn:TransferSyntaxUIDList>
      </urn:RetrieveImagingDocumentSetRequest>
   </soap:Body>
</soap:Envelope>
Response (HTTP 500):
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>

I posted here to benefit anybody who is looking for a solution.
The solution is to use WebServiceContext to get ServletContext, then use ServletContext to get parameters defined in web.xml.
@Resource private WebServiceContext m_wsCxt;
Then in method
SOAPMessageContext soapCxt = (SOAPMessageContext) m_wsCxt.getMessageContext();
ServletContext servletCxt = (ServletContext) soapCxt.get(javax.xml.ws.handler.MessageContext.SERVLET_CONTEXT);
}

Similar Messages

  • Error to invoke service by soap  : Cannot find dispatch method

    i m using jdevelopper 11g and oracle 10g , i write a fonction soap like that:
    -- create or replace function get_naissance(id in varchar2, url in varchar2) return varchar2 as soap_request varchar2(30000);
    declare
    soap_request varchar2(30000);
    soap_respond varchar2(30000);
    http_req utl_http.req;
    http_resp utl_http.resp;
    resp XMLType;
    begin
    soap_request:= '<?xml version = "1.0" encoding = "UTF-8"?>
    *<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://communes/"> <env:Header/>*
    *<env:Body> <ns1:getNaissanceFindById> <arg0>272001</arg0> </ns1:getNaissanceFindById> </env:Body> </env:Envelope> ';*
    http_req:= utl_http.begin_request ( 'http://localhost:7101/naissances-Naissances-webapp/naissanceWS' , 'POST' , 'HTTP/1.1' );
    utl_http.set_header(http_req, 'Content-Type', 'application/soap+xml');
    utl_http.set_header(http_req, 'Content-Length', length(soap_request));
    utl_http.set_header(http_req, 'SOAPAction', '');
    utl_http.write_text(http_req, soap_request);
    http_resp:= utl_http.get_response(http_req);
    utl_http.read_text(http_resp, soap_respond);
    utl_http.end_response(http_resp);
    resp:= XMLType.createXML(soap_respond);
    DBMS_OUTPUT.PUT_LINE ('naissance is : '||soap_respond);
    resp:= resp.extract('//ns2:getNaissanceFindByIdResponse/return' , 'xmlns:ns2="http://communes/"' );
    -- dbms_output.put_line('naissance: '||resp.getStringVal());
    -- return resp.getStringVal();
    end;
    there generate an error
    *naissance is : <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Body><S:Fault xmlns:ns4="http://schemas.xmlsoap.org/soap/envelope/"><S:Code><S:Value>S:Sender</S:Value></S:Code><S:Reason><S:Text xml:lang="fr">Cannot find dispatch method for {http://communes/}getNaissanceFindById</S:Text></S:Reason></S:Fault></S:Body></S:Envelope>*
    the method getNaissanceFindById is correctly implement , the web service run correctly :
    */** <code>select o from Naissance o where o.naissanceid like :id</code> */*
    *@RequestWrapper(className = "jaxws.overloaded.GetNaissanceFindById2")*
    *@ResponseWrapper(className = "jaxws.overloaded.GetNaissanceFindById2_Response")*
    *@WebMethod(operationName = "getNaissanceFindById_2")*
    *public Naissance getNaissanceFindById(String id) {*
    RETURN (Naissance)em.createNamedQuery("Naissance.findById").setParameter("id", id).getSingleResult();
    the result when i put id= 272001 when the service is running :
    *<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://communes/">*
    *<env:Header/>*
    *<env:Body>*
    *<ns1:getNaissanceFindById_2>*
    *<arg0>271002</arg0>*
    *</ns1:getNaissanceFindById_2>*
    *</env:Body>*
    *</env:Envelope>*
    *<?xml version = '1.0' encoding = 'UTF-8'?>*
    *<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">*
    *<S:Body>*
    *<ns2:getNaissanceFindById_2Response xmlns:ns2="http://communes/">*
    *<return>*
    *<addrid>1</addrid>*
    *<communeid>27100</communeid>*
    *<datnais>1962-11-09 00:00:00.0</datnais>*
    *<gender>f</gender>*
    *<idMere>270000</idMere>*
    *<idPere>270000</idPere>*
    *<naissanceid>271002</naissanceid>*
    *<nom>amamra</nom>*
    *<objectVersionId>0</objectVersionId>*
    *<prenom>zahia</prenom>*
    *</return>*
    *</ns2:getNaissanceFindById_2Response>*
    *</S:Body>*
    *</S:Envelope>*
    so i need your help to resolve this error it's amazing , if you want athers details i 'll give u
    thank you

    Please note you're on the SQL Developer forum, so I doubt you'll get answers here...
    Have fun,
    K.

  • Pi 7.1: Exception when contacting WS - "Cannot find dispatch method"

    Hi All,
    I have been receiving the following error message as shown in ICM log, where the trace level is set to 3, when a request is sent to a Web Server.
    ...<SOAP:Faultmlns:SOAP='htt//schemas.xmlsp.org/soap/envope/'><faultco>SOAP:Client</ultcode><faultring>Cannot find dispatch method for arg0</faultstring/SOAP:Fault>..
    No error message is returned using a soap client (as soapUI), after loading the same wsdl file.
    About the configuration of the SOAP Communication Channel, no conversion parameter have been set and no SOAP Action has been set because the seme exception is also raised by setting "arg0" as SOAP Action.
    The structure of the response message is like this.
    <Field1>
       <arg0>
           <field2>
           <field3>
    Any help will be well appreciated.
    Many thanks in advacne for your kind support.
    Regards,
           Giovanni

    Hi All !!
    This problem has been solved with the last SAP_XI* Patches.
    We install:
    SAP_XIESR  SP06 Patch 11
    SAP_XIAF   SP06 Patch 11
    SAP_XITOOL SP06 Patch 10
    and the problem...... SOLVED !!!
    Regards,
    Juan.

  • Cannot attach a WS-Policy to Jax-RPC Web Service

    I am having trouble trying to associate a WS-Security Policy with a BEA Jax-RPC Web Service?
    I am following the following procedure to try to associate a the policy:
    http://edocs.bea.com/wls/docs100/ConsoleHelp/taskhelp/webservices/ConfigureWSPolicyFile.html
    The problem is that when I navigate on the Administration Console to
    Deployments
    => AdapterAdminService (this is the name of my application)
    => com.gateway.admin.wsdl.v10.AdminImpl (this is the name of my Web Service)
    => Configuration
    => WS-Policy
    The Web console displays a stacktrace mentioning an "IndexOutOfBoundsException" :
    Error opening /jsp/webservice/WebServiceConfigurationWebServicePoliciesForm.jsp.
    The source of this error is java.lang.IllegalArgumentException: The property you provided 'contents' of form 'deploymentPlanForm' must not be set to null. at com.bea.console.taglib.html.TableTag.registerDataSet(TableTag.java:1588) at com.bea.console.taglib.html.TreeTableTag.doRegisterDataSet(TreeTableTag.java:49) at com.bea.console.taglib.html.TableTag.doStartTag(TableTag.java:1360) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag9(__webserviceconfigurationwebservicepoliciesform.java:498) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag8(__webserviceconfigurationwebservicepoliciesform.java:459) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag7(__webserviceconfigurationwebservicepoliciesform.java:416) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jspService(__webserviceconfigurationwebservicepoliciesform.java:265) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551) at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306) at com.bea.netuix.nf.UIControl.render(UIControl.java:578) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at
    I have this issue with both IE7 and Firefox 2. My domain is a WLS 10.0MP1 domain and is deployed on my Windows XP laptop.
    I am generating the WS from WSDL with the following ant command:
              <wsdlc srcWsdl="${wsdl.location.path}/AdapterAdministration.wsdl"
                   destJwsDir="${gen.compiled.wsdl.dir}"
                   packagename="com.gateway.admin.wsdl.v10.server"
                   destImplDir="server_impl_example" />
    then
                   <jwsc     srcdir="${src.dir}" destdir="${dist.dir}" classpathref="project.class.path" debug="true">
                             <jws file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                                  compiledWsdl="${gen.compiled.wsdl.dir}/AdapterAdministration_wsdl.jar" />
                        </jwsc>
    and finally, I deploy it with:
              <wldeploy action="deploy"
                   name="AdapterAdminService"
                   source="${dist.dir}/AdminImpl.war"
                   user="${wls.domain.user}"
                   password="${wls.domain.pwd}"
                   verbose="true"
                   stage="no"
                   upload="true"
                   adminurl="t3://${wls.domain.host}:${wls.domain.port}"
                   targets="${wls.domain.servername}" />
    Do you have any idea what might be wrong here?
    Thanks in advance,
    Svend

    Hi all,
    Some more information: I have created another very simple Jax-RPC Web Service, now using the @Policy annotation. The policy I specify is then correctly taken into account, but I still have the same symptom when I navigate to the Configuration => WS-Policy page on the Web Console (i.e., I cannot associate a WS-Policy to my WS with the Web Console)
    Beginning of the JWS file:
    @WebService(...)
    @WLHttpTransport(serviceUri = "", portName = "AdapterAdmin")
    @Binding(Binding.Type.SOAP12)
    @Policy(uri="Wssp1.2-Http-UsernameToken-Digest.xml")
    public class AdminImpl implements Admin {
    Ant task I use to build and deploy the service:
    <target name="build-service" depends="prepare">
              <mkdir dir="package"/>
              <mkdir dir="package/WEB-INF"/>
              <mkdir dir="package/WEB-INF/lib"/>
              <jwsc     
                   srcdir="${src.dir}"
                   destdir="package"
                   classpathref="project.class.path"
                   debug="true">
                   <jws
                        file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                        contextpath="/AdminImpl2"
                        explode="true"
                   />
              </jwsc>
              <move todir="package/WEB-INF">
                   <fileset dir="package/com/gateway/admin/wsdl/v10/AdminImpl/WEB-INF"></fileset>
              </move>
              <move todir="package/META-INF">
                   <fileset dir="package/xsize/gateway/admin/wsdl/v10/AdminImpl/META-INF"></fileset>
              </move>
              <copy todir="package/WEB-INF/lib">
                   <fileset dir="${lib.dir}"
                                  includes="client-1.0.jar,
                                       tools.jar />
              </copy>
              <delete dir="package/com" />
              <jar destfile="${dist.dir}/simpleWS2.war" >
                   <fileset dir="package" />
              </jar>     
              <wldeploy action="deploy"
                   name="AdminService-withPolicyAnnotation"
                   source="${dist.dir}/simpleWS2.war"
                   user="weblogic"
                   password="weblogic"
                   verbose="true"
                   stage="no"
                   upload="true"
                   adminurl="t3://localhost:9001"
                   targets="AdminServer" />
         </target>
    "

  • URGENT **** Need help for JAX-RPC Web Service Proxy deploy to OC4J 10.1.3.5

    Hi everyone!
    I’m really new to web services.
    I’m getting a *500 internal server error* while deploying my JAX-RPC web service Proxy to an Oracle AS, in an OC4J, v. 10.1.3.5.0.
    Running my client from my development environment (*jdeveloper 10g, 10.1.3.5.0*) everything functions correctly: from jdeveloper I can contact and use the web service defined by the following endpoint: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
    I created a "try_ws_client.jsp" file that runs correctly from my local development environment jdeveloper (that uses an embedded oc4j, v. 10.1.3.5.0) but fails when run from the test server (Oracle AS, in an OC4J, v. 10.1.3.5.0), getting, as I mentioned a 500 internal server error, a white page in IE but with FF the message says: The’s an error in the servlet .....
    Here's how I created the ws proxy and how I’m using it to consume the ws I mentioned.
    1. I used the jdeveloper “Create Web Service Proxy” wizard (File > New > Business Tier > Web Services > Web Service Prox) and in the WSDL document URL I put: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
    2. The operation ended without adding nothing to the web.xml file and creating the proxy files. One of them is: FederaMLOLSoapClient.java that have the WS exposed methods (es: public boolean createUser(String) ) + a “main” method with the example how to use this client to consume the WS.
    public static void main(String[] args) {
    try {
    it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
    System.out.println("calling " + myPort.getEndpoint());
    // Add your own code here
    } catch (Exception ex) {
    ex.printStackTrace();
    3. In FederaMLOLSoapClient.java I’ve create the method "tyIt":
    public String tryIt(String username) {
    try {
    it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
    if(myPort.createUser(String username)) {
    return “O.K”;
    } else {
    return “K.O”;
    } catch (Exception ex) {
    // logs error
    4. I created my try_ws_client.jsp file that creates FederaMLOLSoapClient object and calls the tryIt method, printing the “OK” or “KO” message.
    <%@ page import="it.reggiocity.provincia.biblioreggiane.*"%>
    <%
    String message = "";
    FederaMLOLSoapClient obj= new FederaMLOLSoapClient( );
    message = obj.tryIt(“AAAAAA70R10H226H”);
    %>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    <%@ page contentType="text/html;charset=windows-1252"%>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
    <title>prova</title>
    </head>
    <body><%=message%></body>
    </html>
    The situation is:
    My try_ws_client.jsp runs correctly from my jdeveloper and the user is created while creating app.ear and deploying it to my Oracle AS/OC4J as mentioned above, I get a 500 Internal Server Error.
    Any idea to find a solution to this problem?
    Please help.
    Take care.
    John M.

    Hi,
    you want to build the Web Service, or you want to consume the Service as a client? If the latter, Web client (ADF?) or Java client?
    Frank

  • JAXB unmarshaller error in JAX-WS web service

    Hi,
    We have a JAX-WS web service deployed to WLS 10.3.3.0 as an EAR file. The EAR file deploys without any problems, but the first time we attempt to call an operation we get a classloading problem when we run the following code snippet (I've put a comment after the failed line of code):
              Object jaxbObject = null;
              Unmarshaller unmarshaller = null;          
              try {
                   unmarshaller = JAXB_CTX.createUnmarshaller(); // JAXB_CTX is an instance of JAXBContext
                   jaxbObject = unmarshaller.unmarshal(new ByteArrayInputStream(xmlString.getBytes())); // this line fails
              } catch (JAXBException e) {
    If we update the EAR file or delete and re-install the EAR file in the WLS console then the problem doesn't go away, but if we restart the WL server that hosts the EAR file then the problem is resolved. The problem is consistently repeatable.
    The stacktrace for the error is:
    java.lang.ClassCastException: org.apache.xerces.parsers.XML11Configuration
         at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
         at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
         at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
         at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
         at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.createDocument(SAX2DOM.java:326)
         at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.<init>(SAX2DOM.java:85)
         at com.sun.org.apache.xalan.internal.xsltc.runtime.output.TransletOutputHandlerFactory.getSerializationHandler(TransletOutputHandlerFactory.java:187)
         at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getOutputHandler(TransformerImpl.java:392)
         at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerHandlerImpl.setResult(TransformerHandlerImpl.java:137)
         at com.sun.xml.bind.v2.runtime.unmarshaller.DomLoader$State.<init>(DomLoader.java:74)
         at com.sun.xml.bind.v2.runtime.unmarshaller.DomLoader.startElement(DomLoader.java:113)
         at com.sun.xml.bind.v2.runtime.unmarshaller.ProxyLoader.startElement(ProxyLoader.java:56)
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:456)
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:433)
         at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:138)
         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211)
         at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:184)
         at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
         at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:184)
         at com.northernrock.applicationdataservice.interaction.util.ServiceSoapPortUtil.generateJAXBObjectFromXML(ServiceSoapPortUtil.java:184)
         at com.northernrock.applicationdataservice.interaction.util.DataMapper.mapFullApplication(DataMapper.java:130)
         at com.northernrock.applicationdataservice.interaction.ServiceSoapPort.retrieveFullApplicationData(ServiceSoapPort.java:148)
         at com.northernrock.applicationdataservice.interaction.ServiceSoapPortImpl.retrieveFullApplicationData(ServiceSoapPortImpl.java:69)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
         at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
         at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
         at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:265)
         at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
         at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
         at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
         at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
         at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
         at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:373)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:524)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:255)
         at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:141)
         at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:210)
         at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:311)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:223)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:124)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    There seems to be something strange going on with the classloading, such that re-deploying the application causes the wrong Xerces parser classes to be loaded until the WL server is restarted. Once the restart is done then there is no problem until the next re-deployment.
    Does anyone know a fix for this issue?
    Any help is appreciated.
    Thanks,
    Jason

    Hi Jason,
    Below is the sample.....You can use this..
    JAXBElement<Task> root = null;
              try {
                   ByteArrayInputStream input = new ByteArrayInputStream(
                             xmlStr.getBytes());
                   JAXBContext jc = JAXBContext.newInstance(Task.class);
                   Unmarshaller u = jc.createUnmarshaller();
                   StreamSource sc = new StreamSource(new StringReader(
                             xmlStr.toString()));
                   root = u.unmarshal(new StreamSource(input), Task.class);
              } catch (Exception e) {
                   e.printStackTrace();
              }

  • Identity service cannot find user

    Installed BPEL 10.1.2
    added user using jazn.jar
    Now trying to log into worklist sample application
    and I get identity service cannot find user. Do I need to assign any role(s) to new user.
    Let me know.
    I am seeing simple questions not getting answers. Is this an Active Forum?
    Thanks
    Raghu

    closed
    for OAS 10.1.2.0.2. & BPEL PM 10.1.2.0.2
    I Install BPEL in MiddleTire
    1. ./runInstaller
    2. home = OAS home
    3. tea
    4. emctl stop em
    emctl start em
    5. Oracle_Home\opmn\bin\opmnctl stopproc ias-component=OraBPEL
    Oracle_Home\opmn\bin\opmnctl startproc ias-component=OraBPEL
    6. if OID working throw SSL, then 7,8 else 9
    7. edit file Oracle_Home\j2ee\OC4J_BPEL\config\jazn.xml
         <jazn provider="LDAP" location="ldap://host:636" default-realm="us">
              <property name="ldap.user" value="cn=orcladmin"/>
              <property name="ldap.password" value="!welcome1"/>
              <property name="ldap.protocol" value="ssl"/>
         </jazn>
    8. edit file Oracle_Home\integration\orabpel\system\services\config\is_config.xml
         <BPMIdentityServiceConfig
         xmlns="http://www.oracle.com/pcbpel/identityservice/isconfig">
              <provider providerType="JAZN" name="oid" >
                   <connection url="ldap://host:636" binddn="cn=orcladmin"
                        password="welcome1" encrypted="false">
                        <property name="securityProtocol" value="ssl" />
                   </connection>
              </provider>
         </BPMIdentityServiceConfig>
    then 11
    9. edit file Oracle_Home\j2ee\OC4J_BPEL\config\jazn.xml
         <jazn provider="LDAP" location="ldap://host:389" default-realm="us">
              <property name="ldap.user" value="cn=orcladmin"/>
              <property name="ldap.password" value="!welcome1"/>
         </jazn>
    10. edit file Oracle_Home\integration\orabpel\system\services\config\is_config.xml
         <provider providerType="JAZN" name="oid" >
              <connection url="ldap://host:389" binddn="cn=orcladmin"
                   password="welcome1" encrypted="false"/>
              </connection>
         </provider>
    11. edit file Oracle_Home\j2ee\OC4J_BPEL\application-deployments\hw_services\orion-application.xml
         <jazn provider="LDAP" location="ldap://host:389" default-realm="us" >
              <jazn-web-app auth-method="SSO"/>
         </jazn>
    12. Oracle_Home\opmn\bin\opmnctl stopproc ias-component=OraBPEL
    Oracle_Home\opmn\bin\opmnctl startproc ias-component=OraBPEL
    II Deploy BPEL portlets
    1. throw EM add EAR to OC4J_BPEL:
         fie: $ORACLE_HOME/integration/orabpel/system/services/lib/bpelportlet.ear
         &#1072;. Parent app = orabpel
         &#1073;. User Manager = Use JAZN LDAP User Manager
    2. edit file Oracle_Home\j2ee\OC4J_BPEL\application-deployments\bpelPortlet\orion-application.xml
         <jazn provider="LDAP" location="ldap://host:port" default-realm="us" >
              <jazn-web-app auth-method="SSO"/>
         </jazn>
    3.Oracle_Home\opmn\bin\opmnctl stopproc ias-component=OraBPEL
    Oracle_Home\opmn\bin\opmnctl startproc ias-component=OraBPEL
    4. Register BPEL provider
         http://bpel_host:bpel_port/BPELPortlet/providers
         &#1072;. Login Frequency = Once Per User Session
    636 - OID SSL port
    389 - OID non SSL port

  • JAX-WS Web Service with XFire Client

    I wrote a simple web service and client using XFire. However the server now needs to be JAX-WS. I wrote a simple service using NetBeans but I can't seem to get it to work with XFire. JAX-WS doesn't seem to like the SOAP XFire is sending it and the parameters passed into the web method are nulls instead of the intended values.
    Here is my web service:
    package org.me.hi;
    import javax.jws.WebMethod;
    import javax.jws.WebResult;
    import javax.jws.WebService;
    import javax.jws.soap.SOAPBinding;
    import javax.jws.soap.SOAPBinding.Style;
    import javax.jws.soap.SOAPBinding.Use;
    import javax.jws.soap.SOAPBinding.ParameterStyle;
    @WebService(name="HelloWS", targetNamespace="http://hi.me.org")
    @SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
    public class HelloWS {
        @WebMethod(operationName="add", action="")
        @WebResult(name="return", targetNamespace="http://hi.me.org")
        public Integer add(Integer a, Integer b) {
            if (a == null)
                System.out.println("a is null");
                return null;
            if (b == null)
                System.out.println("b is null");
                return null;
            System.out.println("a: " + a + " b: " + b);
            return a + b;
    }Here is the WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns:tns="http://hi.me.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://hi.me.org" name="HelloWSService">
      <types>
        <xsd:schema>
          <xsd:import namespace="http://hi.me.org" schemaLocation="http://localhost:8084/HelloWS/HelloWS?xsd=1"/>
        </xsd:schema>
      </types>
      <message name="add">
        <part element="tns:add" name="parameters"/>
      </message>
      <message name="addResponse">
        <part element="tns:addResponse" name="parameters"/>
      </message>
      <portType name="HelloWS">
        <operation name="add">
          <input message="tns:add"/>
          <output message="tns:addResponse"/>
        </operation>
      </portType>
      <binding type="tns:HelloWS" name="HelloWSPortBinding">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="add">
          <soap:operation soapAction=""/>
          <input>
            <soap:body use="literal"/>
          </input>
          <output>
            <soap:body use="literal"/>
          </output>
        </operation>
      </binding>
      <service name="HelloWSService">
        <port binding="tns:HelloWSPortBinding" name="HelloWSPort">
          <soap:address location="http://localhost:8084/HelloWS/HelloWS"/>
        </port>
      </service>
    </definitions>Here is my quick and dirty XFire client:
    package org.me.hi;
    import java.net.MalformedURLException;
    import java.net.URL;
    import org.codehaus.xfire.client.Client;
    public class HelloTest {
        public static void main(String[] args) {
            Client client;
            try {
                client = new Client(new URL("http://localhost:8085/HelloWS/HelloWS?wsdl"));
                Object[] results = client.invoke("add", new Object[] {1, 2});
                if (results.length != 0) {
                    System.out.println("result: " + (Integer)results[0]);
                } else {
                    System.out.println("null return");
            } catch (MalformedURLException e) {
                // TODO Auto-generated catch block
                e.printStackTrace();
            } catch (Exception e) {
                // TODO Auto-generated catch block
                e.printStackTrace();
    }Here is the SOAP I intercepted between the XFire client and the JAX-WS service:
    Calling the web method:
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soap:Body>
        <ns1:add xmlns:ns1="http://hi.me.org">
          <ns1:arg0>1</ns1:arg0>
          <ns1:arg1>2</ns1:arg1>
        </ns1:add>
      </soap:Body>
    </soap:Envelope>Response:
    <?xml version="1.0" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://hi.me.org">
      <soapenv:Body>
        <ns1:addResponse></ns1:addResponse>
      </soapenv:Body>
    </soapenv:Envelope>Console at the server side:
    a is nullConsole at the client side:
    null returnNot sure what I'm doing wrong, but I wrote a quick JAX-WS client using NetBeans and it works. We would like to keep using XFire if possible. Here is the SOAP between the JAX-WS client and the JAX-WS web service.
    <?xml version="1.0" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://hi.me.org/">
      <soapenv:Body>
        <ns1:add>
          <arg0>1</arg0>
          <arg1>2</arg1>
        </ns1:add>
      </soapenv:Body>
    </soapenv:Envelope>
    <?xml version="1.0" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://hi.me.org/">
      <soapenv:Body>
        <ns1:addResponse>
          <return>3</return>
        </ns1:addResponse>
      </soapenv:Body>
    </soapenv:Envelope>

    Result after navigating to: http://localhost:8084/HelloWS/HelloWS?xsd=1
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hi.me.org/" version="1.0">
      <xs:element xmlns:ns1="http://hi.me.org/" type="ns1:add" name="add"/>
      <xs:complexType name="add">
        <xs:sequence>
          <xs:element type="xs:int" minOccurs="0" name="arg0"/>
          <xs:element type="xs:int" minOccurs="0" name="arg1"/>
        </xs:sequence>
      </xs:complexType>
      <xs:element xmlns:ns2="http://hi.me.org/" type="ns2:addResponse" name="addResponse"/>
      <xs:complexType name="addResponse">
        <xs:sequence>
          <xs:element type="xs:int" minOccurs="0" name="return"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>

  • Polycom CX 600 - Certificate web service cannot be found

    Hi All,
    I know, there are some same issues in the forum, bot those are not helpful for me. My problem is the same, via network cable (using just DHCP) the Polycom CX 600 Lync Phone are not able to sign in (however 1 month ago it was), returning the error message:
    'Certificate web service cannot be found.'
    I've double checked the DHCP options and all of them are OK! We are not using Windows DHCP, but the options are right, the 43 option containing the proper hexa value, the sub-options are also valid. From the DHCP log I can verify that the device got the
    options, but the phone still not able to sign in.
    From the browser I cannot open the device, by it's IP, just with FTP:\\'IP'. There I could find a .clg1 log file, but it not containing useful information for me. 
    This is the link of the log file: http://speedy.sh/XAgMT/system.clg1
    If I run the DHCPUtil.exe -emulateclient on my workstation, I got the following:
    Starting Discovery ...
    Result: Failure =  -2147014848
    Or... sometimes it has a result:
    Starting Discovery ...
    Sending Packet (Size: 288, Network Adapter: 57.56.69.138, Attempt Type: Broadcas
    t + Unicast)
    --Begin Packet--
    DHCP: INFORM                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 0.0.0.0
    DHCP: Client HW Address (chaddr)  = E0DB55DE###--End Packet--
    Received Packet
    Sender:57.20.120.85:67, Size:408
    --Begin Packet--
    DHCP: ACK                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 57.56.69.131
    DHCP: Client HW Address (chaddr)  = E0DB55DE8993
    DHCP: Server Host Name  (sname)   =
    DHCP: Boot File Name    (file)    =
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) 57.20.120.85
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 18) enc:0 lync2013.dlh.de (00086C79
    6E633230313303646C6802646500)
        DHCP: Host Name(  12)         = (Length: 0)
        DHCP: Vendor Identifier(  60) = (Length: 0)
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
    3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
    572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
    31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
    36463736324634333635373237343530373236463736363937333639364636453639364536373533
    36353732373636393633363532453733373636335D)
        DHCP: End of this option field
    --End Packet--
    Received Packet
    Sender:57.20.120.85:67, Size:408
    --Begin Packet--
    DHCP: ACK                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 57.56.69.130
    DHCP: Client HW Address (chaddr)  = E0DB55DE8993
    DHCP: Server Host Name  (sname)   =
    DHCP: Boot File Name    (file)    =
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) 57.20.120.85
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 18) enc:0 lync2013.dlh.de (00086C79
    6E633230313303646C6802646500)
        DHCP: Host Name(  12)         = (Length: 0)
        DHCP: Vendor Identifier(  60) = (Length: 0)
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
    3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
    572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
    31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
    36463736324634333635373237343530373236463736363937333639364636453639364536373533
    36353732373636393633363532453733373636335D)
        DHCP: End of this option field
    --End Packet--
    Received Packet
    Sender:57.20.120.100:67, Size:408
    --Begin Packet--
    DHCP: ACK                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 0.0.0.0
    DHCP: Client HW Address (chaddr)  = E0DB55DE8993
    DHCP: Server Host Name  (sname)   =
    DHCP: Boot File Name    (file)    =
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) 57.20.120.100
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 18) enc:0 lync2013.dlh.de (00086C79
    6E633230313303646C6802646500)
        DHCP: Host Name(  12)         = (Length: 0)
        DHCP: Vendor Identifier(  60) = (Length: 0)
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
    3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
    572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
    31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
    36463736324634333635373237343530373236463736363937333639364636453639364536373533
    36353732373636393633363532453733373636335D)
        DHCP: End of this option field
    --End Packet--
    Received Packet
    Sender:57.20.120.100:67, Size:408
    --Begin Packet--
    DHCP: ACK                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 57.56.69.131
    DHCP: Client HW Address (chaddr)  = E0DB55DE8993
    DHCP: Server Host Name  (sname)   =
    DHCP: Boot File Name    (file)    =
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) 57.20.120.100
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 18) enc:0 lync2013.dlh.de (00086C79
    6E633230313303646C6802646500)
        DHCP: Host Name(  12)         = (Length: 0)
        DHCP: Vendor Identifier(  60) = (Length: 0)
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
    3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
    572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
    31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
    36463736324634333635373237343530373236463736363937333639364636453639364536373533
    36353732373636393633363532453733373636335D)
        DHCP: End of this option field
    --End Packet--
    Received Packet
    Sender:57.20.120.100:67, Size:408
    --Begin Packet--
    DHCP: ACK                (xid=5C1E8177)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 1545503095
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = 57.56.69.138
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 57.56.69.130
    DHCP: Client HW Address (chaddr)  = E0DB55DE8993
    DHCP: Server Host Name  (sname)   =
    DHCP: Boot File Name    (file)    =
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) 57.20.120.100
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 18) enc:0 lync2013.dlh.de (00086C79
    6E633230313303646C6802646500)
        DHCP: Host Name(  12)         = (Length: 0)
        DHCP: Vendor Identifier(  60) = (Length: 0)
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
    3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
    572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
    31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
    36463736324634333635373237343530373236463736363937333639364636453639364536373533
    36353732373636393633363532453733373636335D)
        DHCP: End of this option field
    --End Packet--
    Result: Failure =  1
    I don't know what is that Failure = 1
    Has anybody an idea???
    Many thanks,
    Tamás

    Hi,
    The DHCP options are good.
    Finally, I was able to run the test-csphonebootsrap cmdlet, and I got the following error:
    Result        : Failure
    Latency       : 00:00:01.2179659
    Error Message : No response received for getting root certificate chain.
                    Inner Exception:The remote server returned an unexpected respon
                    se: (417) Expectation Failed.
                    Inner Exception:The remote server returned an error: (417) Expe
                    ctation Failed.
    Diagnosis     :
                    Inner Diagnosis:Mime-Version : 1.0
                    X-Squid-Error : ERR_INVALID_REQ 0
                    Vary : Accept-Language
                    Content-Language : en
                    X-Cache : MISS from proxy.lsy.bud.dlh.de
                    X-Cache-Lookup : NONE from proxy.lsy.bud.dlh.de:3128
                    Connection : close
                    Content-Length : 3944
                    Content-Type : text/html
                    Date : Thu, 09 Jan 2014 13:24:47 GMT
                    Server : squid/3.1.10
                    Via : 1.0 proxy.lsy.bud.dlh.de (squid/3.1.10)
    VERBOSE: Workflow
    'Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow'
    started.
    Workflow
    'Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow'
    completed in '0.0001508' seconds.
    Target server Fqdn or web service Url not provided. Will have to do DHCP
    Registrar Discovery.
    An exception 'No response received for getting root certificate chain.'
    occurred during Workflow
    Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow
    execution.
    Exception Call Stack:    at
    Microsoft.Rtc.Admin.Authentication.WebServicesHelper.GetRootCertChains()
       at
    Microsoft.Rtc.SyntheticTransactions.Activities.GetRootCertChainsActivity.Intern
    alExecute(ActivityExecutionContext executionContext)
       at
    Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Ex
    ecute(ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity,
    ActivityExecutionContext executionContext)
       at
    System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRunti
    me workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()
    Server stack trace:
       at
    System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(
    HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory,
     WebException responseException, ChannelBinding channelBinding)
       at
    System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChanne
    lRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message,
    TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean
    oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan
    timeout)
       at
    System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessa
    ge methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
    message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
    reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
    msgData, Int32 type)
       at RootCertChainService.GetRootCertChains(GetRootCertChainsRequest request)
       at Microsoft.Rtc.Admin.Authentication.WebServicesHelper.GetRootCertChains()
    'DHCPDiscover' activity started.
    Starting DHCP registrar discovery...
    Constructing a DHCP packet.
    Adding DHCP option PARAMETER_REQUEST_LIST.
    Successfully added DHCP option.
    Adding DHCP option VENDOR_CLASS_IDENTIFIER.
    Successfully added DHCP option.
    Successfully constructed DHCP packet.
    Trying to open an udp connection.
    Remote IP : 255.255.255.255.
    Local IP : 10.150.7.33.
    \tCreating a new UDP client.
    Udp connection successfully created.
    Sending packet.
    Remote IP : 255.255.255.255.
    Remote Port : 67.
    Packet sent successfully.
    DHCP discovery message send. Waiting for DHCP servers to respond.
    Data received successfully.
    Remote IP : 57.20.120.85.
    Remote Port : 67.
    Response received for the DHCP Discovery message.
    Constructing a DHCP packet from received raw data.
    Extracting DHCP Options.
    Successfully constructed DHCP packet.
    Return value for DHCP option : SIP_SERVER.
    Found registrar Fqdn : lyncpool.dlh.de.
    Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.1.
    Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
    Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.1 - MS-UC-Client.
    Successfully extracted sub option value.
    Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.2.
    Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
    Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.2 - https.
    Successfully extracted sub option value.
    Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.3.
    Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
    Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.3 - lyncpool.dlh.de.
    Successfully extracted sub option value.
    Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.4.
    Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
    Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.4 - 443.
    Successfully extracted sub option value.
    Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.5.
    Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
    Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.5 -
    /CertProv/CertProvisioningService.svc.
    Successfully extracted sub option value.
    Found web service Url :
    https://lyncpool.dlh.de:443/CertProv/CertProvisioningService.svc.
    Disconnecting.
    DHCP registrar discovery activity completed successfully.
    'DHCPDiscover' activity completed in '1.2179659' seconds.
    'GetRootCertChains' activity started.
    Trying to download a certificate chain from web service.
    Web Service Url : http://lyncpool.dlh.de/CertProv/CertProvisioningService.svc
    Could not download certificate chain from web service.
    CHECK:
     - Web service Url is valid and the web services are functional.
    'UnRegister' activity started.
    'UnRegister' activity completed in '3.78E-05' seconds.
    VERBOSE: Workflow Instance ID 'a9313cfa-b82c-4bd2-9df6-81acca1bcbbc' completed.
    VERBOSE: Workflow run-time (sec): 1.5083016.
    It looks like the telephone are not able to download the root CA, but the webservice is available and reachable via port 80 and 443 too.... So, what is the reason? Why the Polycom CX600 is not able to download the root CA??

  • Simple JAX-WS web service does not work on WS7u6

    Hello,
    I am trying to deploy a very simple JAX-WS web service on WS7u6, but it is not working. The same service deployed on Tomcat 6.0.16 works fine.
    The service I'm trying to deploy is from a tutorial on the Netbeans website: [http://netbeans.org/kb/docs/websvc/jax-ws.html] - it is a simple calculator web service that adds two ints and returns an int.
    I follow the tutorial to the letter, but when I attempt to deploy on WS7, it fails as follows:
    [10/Dec/2009:21:21:44] info (25757): CORE3276: Installing a new configuration
    [10/Dec/2009:21:21:44] info (25757): WEB0118: SSO is enabled in virtual server [dadydude.qisc.com]
    [10/Dec/2009:21:21:44] info (25757): WEB0100: Loading web module in virtual server [dadydude.qisc.com] at [/wstest]
    [10/Dec/2009:21:21:44] info (25757): WSSERVLET12: JAX-WS context listener initializing
    [10/Dec/2009:21:21:44] info (25757): wsdl cannot be found from DD or annotation. Will generate and publish a new WSDL for SEI endpoints.
    [10/Dec/2009:21:21:44] failure (25757): WSSERVLET11: failed to parse runtime descriptor: class: org.me.calculator.jaxws.Add could not be found
    class: org.me.calculator.jaxws.Add could not be found
         at com.sun.xml.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.java:271)
         at com.sun.xml.ws.modeler.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:562)
         at com.sun.xml.ws.modeler.RuntimeModeler.processMethod(RuntimeModeler.java:509)
         at com.sun.xml.ws.modeler.RuntimeModeler.processClass(RuntimeModeler.java:355)
         at com.sun.xml.ws.modeler.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:251)
         at com.sun.xml.ws.server.RuntimeEndpointInfo.createSEIModel(RuntimeEndpointInfo.java:170)
         at com.sun.xml.ws.server.RuntimeEndpointInfo.init(RuntimeEndpointInfo.java:317)
         at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.createModelAndMetadata(WSServletContextListener.java:200)
         at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:120)
         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4456)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:5113)
         at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:235)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
         at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
         at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
         at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
         at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70)
         at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:491)
         at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304)
    [10/Dec/2009:21:21:44] failure (25757): WebModule[/wstest]PWC1275: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    WSSERVLET11: failed to parse runtime descriptor: class: org.me.calculator.jaxws.Add could not be found
         at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:131)
         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4456)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:5113)
         at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:235)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
         at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
         at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
         at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
         at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70)
         at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:491)
         at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304)
    Caused by: class: org.me.calculator.jaxws.Add could not be found
         at com.sun.xml.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.java:271)
         at com.sun.xml.ws.modeler.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:562)
         at com.sun.xml.ws.modeler.RuntimeModeler.processMethod(RuntimeModeler.java:509)
         at com.sun.xml.ws.modeler.RuntimeModeler.processClass(RuntimeModeler.java:355)
         at com.sun.xml.ws.modeler.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:251)
         at com.sun.xml.ws.server.RuntimeEndpointInfo.createSEIModel(RuntimeEndpointInfo.java:170)
         at com.sun.xml.ws.server.RuntimeEndpointInfo.init(RuntimeEndpointInfo.java:317)
         at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.createModelAndMetadata(WSServletContextListener.java:200)
         at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:120)
         ... 11 more
    [10/Dec/2009:21:21:44] failure (25757): PWC1306: Startup of context /wstest failed due to previous errors
    [10/Dec/2009:21:21:44] failure (25757): Null component com.sun.web-3:type=JspMonitor,name=jsp,WebModule=//localhost/wstest,J2EEApplication=null,J2EEServer=none
    [10/Dec/2009:21:21:44] info (25757): CORE3280: A new configuration was successfully installed
    [10/Dec/2009:21:21:44] info (25757): WSSERVLET13: JAX-WS context listener destroyedAm I simply missing something obvious here?
    Thanks,
    Bill

    OK, I've made significant progress.
    As I suspected, JAX-WS was indeed supposed to generate the missing class for me, but while it appears to do so automatically when deploying in Tomcat, it is necessary to hack your build.xml file to add the generated classes to your WAR file for WS7. Reference [http://developers.sun.com/webtier/reference/techart/websvcs_nb.html] for a (rather dated) description of how to deploy a JAX-WS service on WS7 (using Netbeans 5.0!).
    Note that as of NB6.7/6.8 much of the manual process is now done automatically by Netbeans, but curiously, not the part that actually causes the web service code to be generated. For that, we have to manually modify the build.xml to include a "-pre-dist" target that invokes the wsgen Ant task.
    This is the target I added to build.xml for this sample calculator service:
      <target name="-pre-dist">
        <taskdef name="wsgen" classname="com.sun.tools.ws.ant.WsGen">
          <classpath path="${javac.classpath}:${j2ee.platform.classpath}"/>
        </taskdef>
        <wsgen
          debug="true"
          keep="true"
          destdir="build/web/WEB-INF/classes"
          resourcedestdir="build/web/WEB-INF/classes"
          xendorsed="true"
          sei="org.me.calculator.CalculatorWS">
          <classpath>
            <pathelement path="${javac.classpath}:${j2ee.platform.classpath}"/>
            <pathelement location="${java.home}/../lib/tools.jar"/>
            <pathelement location="build/web/WEB-INF/classes"/>
          </classpath>
        </wsgen>
      </target>That will allow the project to build and deploy successfully, and I am now able to view my WSDL.
    However, at first the service itself was not working. After a bit of casting about, I determined that this was due to the fact that at some point I had added the METRO library to the project rather than simply the JAX-WS 2.2 library. After returning the configuration to just use JAX-WS and doing a clean build and deploy, the simple web service now works!
    One thought does emerge from all this, though: if the built in support for Tomcat runs wsgen for me when I deploy an app to that container, perhaps the Sun WS7 team needs to update their Netbeans plugin to do this for us, too. I should probably open a support case on that...
    OK, now on to real work. ;-)
    Bill

  • How to create JAX-WS web services using providers?

    I am looking at WebLogic web services, because we are investigating the possibility of migrating our web services from Apache CXF to WegLogic web services. Our web services are implemented using JAX-WS providers. However, I browsed through the Oracle Fusion Middleware document library, but I couldn't find any documents for implementing JAX-WS web services using providers.
    Is there any document, tutorial, or examples of that?
    Thanks in advance!
    Tao

    Ok just as I expected. So I guess I am left with the following two options
    1) either I switched to using JAXB in my apps instaed of xmlbeans....
    2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
    Programming Web Services for WebLogic Server (ant tasks)
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
    Getting Started With WebLogic Web Services Using JAX-RPC
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
    Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

  • Consuming Domino web service with JAXB encounters Method Response element

    I am able to consume a Domino R7 (Axis) web service with JAX-WS using Dispatch<SOAPMessage>. When I try using Dispatch<Object> however, JAXB throws an exception because it encounters an unexpected tag.
    The XML from the web service looks like this:
    <Envelope>
        <Body>
            <WebServiceMethodResponse>
                <WebServiceMethodReturn>
                    The meaning of life
                </WebServiceMethodReturn>
            </WebServiceMethodResponse>
        </Body>
    </Envelope>With Dispatch<SOAPMessage>, I can get to the meaning of life quickly using SOAPBody.getElementsByTagName( "WebServiceMethodReturn" ) but with Dispatch<Object>, it appears I must also create a class for the WebServiceMethodResponse element to make JAXB happy. I don't see this happening in other people's examples. Has the Return-element-within-Response-element design been eliminated in pure JAX-WS web services, or is this something that only IBM does?

    In case anyone's search leads them here, I've posted the solution at:
    *[http://www.pby.com/general.nsf/webarticles/dominowebservice01]*
    It is an exhaustive article (not "Hello World"!) that goes through several versions of the web service and client - hopefully explaining all+ pieces of the puzzle:
    ~ web service code,
    ~ WSDLs
    ~ schema
    ~ thoroughly-documented clients that do and do not use JAXB
    ~ ... that use generated artifacts
    ~ ... that customize existing POJOs
    ~ the SOAP messages generated in each direction
    ~ the necessary JAXB annotations
    ~ explanations of how the code works
    ~ explanations of how namespaces affect the code
    ~ on and on and on...
    My constant goal was to write an uncomplicated solution that uses as few artifacts (two) and annotations as possible. The end result is a small, fast JAX-WS 2.0 client that uses JAXB to invoke and consume a secured Domino 7 (1.4.2 JVM + AXIS) web service, using RPC/literal SOAP messages.

  • I cannot find the method in this interface!

    Is service an interface and query its method in the following scrips? But I cannot find the method query in this interface. What is the function of new?
    Map map = service.query(new FreeMemAgent(), null);
    Thank you
    Edited by: jetq on Jun 7, 2009 9:05 PM

    Hi Frank,
    service is a reference variable and refers to an instance of a class that implements the query() method that returns a reference to an instance of a class that implements the Map interface. If service happens to refer to an instance of a class that implements the InvocationService interface, you can find the Coherence 3.4.2 documentation of the method at InvocationService. The new keyword is a Java operator that creates an object. Continuing with the assumption that service refers to an instance of a class that implements the InvocationService interface, the FreeMemAgent class must implement the Invocable interface. A reference to a "new" FreeMemAgent object is being passed to the query() method.
    Regards,
    Harv

  • JAX-WS web service client and Windows integrated Security authentication

    I am currently developing a JAX-WS web service client running on WebLogic 10.3.2.0. The client is connecting to exchange web service running on IIS.
    Everything works well when EWS is configured with Http basic authentication.
    The problems started when I changed the autentication method on EWS from Http basic authentication to Windows integrated Security authentication.
    The client is then unable to authenticate to the web service. Every request made to EWS returns with the message : Invalid HTTP server response [401] - Unauthorized.
    I tried using an authenticator like this one:
    static class RetrieveWSDLAuthenticator extends Authenticator
    private String username, password;
    public RetrieveWSDLAuthenticator(String user, String pass)
    username = user;
    password = pass;
    @Override
    protected PasswordAuthentication getPasswordAuthentication()
    return new PasswordAuthentication(username, password.toCharArray());
    and setting it as the default authenticator :
    Authenticator.setDefault(new MyAuthenticator("username", "password"));
    but the method getPasswordAuthentication() was not even called.
    Is there a way to make a JAX-WS client works with Windows integrated Security ?

    WIS is not suppported on WLS JAX-WS. You'll need to use other authentication mechanisms such as http basic (which you tried already), or message-level security such as UNT, or SAML.
    Regards,
    Pyounguk

  • RIDC client using JAX-WS Web Service requires OWSM policy

    Hi
    For development purposes, I want to invoke the RIDC JAX-WS Web Service (I believe this to be the 11g idc native ws) but an error is thrown stating the various policies are invalid. The fact is my instance of Weblogic is not set up with OWSM and there are no security policies applied or configured.
    I was wondering if there was a way to invoke this web service using http basic authentication and bypass the requirement to have a policy attached.
    If not, does anyone have steps on how to enable OWSM and policies, and attach these to the IDC native web services).
    Thanks
    M

    Hi Ryan
    Yes, I have tried to use the JAX-WS with configuration that I was hoping would set Basic Auth on the request, however an error is thrown stating that the required policies are invalid on the server.
    In summary:
    I create a JaxWSClient client.
    I create a binder using the client.
    I create a IdcContext using a valid username and password.
    I set up the service details and params in the binder.
    I send the request by invoking the client and passing the binder and IdcContext.
    With this basic set-up, I get a SOAP fault from the server stating that policy 'oracle/no_authentication_service_policy' and oracle/no_messageprotection_service_policy are invalid. It makes sense that there are invalid as they are not present on my weblogic instance, and it seems that because I have not specified any other configuration, that these are treated as the default policies.
    Setting up basic auth would be ideal, as I do not have control of the Weblogic instances, and so getting OWSM would be a pain. There may be some way to set up the client to use Basic Auth, but unfortunately I cannot see how.
    Cheers

Maybe you are looking for