Namespace Error when generating Client Proxy for Java Web Service

Hi.Experts:
    When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
    The error like this:
    "Incorrect value: Unknown Namespace http://sql.java
    Exception of class CX_SLIB "
   I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
Best Regards
Martin Xie

Hi Martin
I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
Maybe my version is different.
You say that you can select the file ou url.
Did you select the file or url?
If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
If was url, access this url, copy the xml and same in one file, then select this file in the step above.
I don't know if works, its only a suggestion.
regards
Marcos

Similar Messages

Generation Error - when trying to publish a Java web service

Hi All,
I keep getting the following Generation Error -- java.util.NoSuchElementException_ when I'm trying to create a Java Web Service using the jdeveloper wizard.
I have 2 entities and 2 stateless session beans acting as their facades. One entity has a One-One(FK) relationship with the other entity. I test out the entities and session beans using the test client and the OC4J embedded container and everything seems to work. When I try to generate a Java WebService from one of the entities I keep getting the "Generation Error". Could someone please provide me with some insight into why I'm facing this problem, because it seemed fine when I published J2EE web services previously and now this happens and I cant seem to publish web services anymore. Everytime I keep getting the same GenerationError. Thanks in advance.

Without going into any technical discussion about the code, my first question is what JDK version was used to create this which was imported into the form? Understand that Forms 10 runs on JDK 1.4.2, so if you used any newer JDK version, likely there will be problems.

Creating client proxy for calling web service

Hello,
I like to call a WebServce from our vendor. The vendor provides me no WSDL document.
Question: Is it possible to create a client proxy without WSDL? I have just the SOAP Request/Response.
SAP ECC 6.0
SAP_BASIS 700 0010
Thank you very much in advance for any helpful answer.
Kind regards
Axel

Hi Axel,
I am working on a program to connect to a external web-service from SAP (R/3 enterprise 4.7) and while searching all the available stuff for this I got this method.
But, I am still facing some other issues and hence doesn't have the whole solution. You have to probably try it out from your side once and see if it helps.
Please refer the following blog.
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/847. [original link is broken] [original link is broken] [original link is broken]
it describes a method which is not at all using any WSDL file. Instead it uses the CL_HTTP_CLIENT class to pass a SOAP request to the web-service and then get the response.
Regards
Barada

Help on Sun Certified Developer for Java Web Services (CX-310-220) exam

Hi,
I am planing for Sun Certified Developer for Java Web Services (CX-310-220) certification. Can anyone provide me the links for resouces? can anyone provide me books/publications/author best preparation material to score good marks in exam? can anyone provide me the download resources available over internet?
thanks in advance..!!!
regards
gaveesha

yes, that's the only decent book covering most of the exam curiculum (but NOT all of it, check the exam specs versus the book content to know what you are missing).
I'm working on the same material, and boy is it a lot...
Dry, boring stuff most of it.

Sun Certified Developer for Java Web Services (CX-310-220)

Hello All,
I'm planning to study for Sun Certified Developer for Java Web Services (CX-310-220). I really appreciate any help in suggesting the books and the material requiered for the above certification.
Thanks,
Greeshma...

yes, that's the only decent book covering most of the exam curiculum (but NOT all of it, check the exam specs versus the book content to know what you are missing).
I'm working on the same material, and boy is it a lot...
Dry, boring stuff most of it.

I am planing for Sun Certified Developer for Java Web Services (CX-310-220)

Hi,
I am planing for Sun Certified Developer for Java Web Services (CX-310-220) certification. Can anyone please provide me the resources for preparation?
Can anyone suggest me which books/author/publications best helps me to get good results in exam? Any books/author/publications available over internet to download and prepare?
regards
gaveesha

yes, that's the only decent book covering most of the exam curiculum (but NOT all of it, check the exam specs versus the book content to know what you are missing).
I'm working on the same material, and boy is it a lot...
Dry, boring stuff most of it.

Unknown namespace error when generating a client proxy

We are using WAS 7.0 and I'm trying to generate a client proxy for an inhouse webservice via Object Navigator (SE80). When using the Wizard I get an error message from the Librabry Handler saying: "Unknown namespace: http://schemas.xmlsoap.org/soap/encoding".
A check by the colleagues who provide this Webservice says that the wsdl is ok.
Any idea for this error message?
Many Thanks.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:intf="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
   <complexType name="SAPHRMitarbeiterDatenMitarbeiter">
    <sequence>
     <element name="Bukrs" nillable="true" type="xsd:string"/>
     <element name="Werks" nillable="true" type="xsd:string"/>
     <element name="Kostl1" nillable="true" type="xsd:string"/>
     <element name="Kostl2" nillable="true" type="xsd:string"/>
     <element name="Persk" nillable="true" type="xsd:string"/>
     <element name="Pernr" nillable="true" type="xsd:string"/>
     <element name="Nachn" nillable="true" type="xsd:string"/>
     <element name="Vorna" nillable="true" type="xsd:string"/>
     <element name="Eintr" nillable="true" type="xsd:string"/>
     <element name="Austr" nillable="true" type="xsd:string"/>
     <element name="Sacha" nillable="true" type="xsd:string"/>
     <element name="Sachn" nillable="true" type="xsd:string"/>
     <element name="IAKen" nillable="true" type="xsd:string"/>
     <element name="IABeg" nillable="true" type="xsd:string"/>
     <element name="IAEnd" nillable="true" type="xsd:string"/>
     <element name="Level" nillable="true" type="xsd:string"/>
     <element name="Stelle" nillable="true" type="xsd:string"/>
     <element name="Abtlg" nillable="true" type="xsd:string"/>
     <element name="Mgr_Pernr" nillable="true" type="xsd:string"/>
     <element name="Mgr_Name" nillable="true" type="xsd:string"/>
    </sequence>
   </complexType>
   <complexType name="ArrayOfSAPHRMitarbeiterDatenMitarbeiter">
    <complexContent>
     <restriction base="soapenc:Array">
      <attribute ref="soapenc:arrayType" wsdl:arrayType="impl:SAPHRMitarbeiterDatenMitarbeiter[]"/>
     </restriction>
    </complexContent>
   </complexType>
</schema>
</wsdl:types>
   <wsdl:message name="ReadDataResponse">
      <wsdl:part name="ReadDataReturn" type="impl:ArrayOfSAPHRMitarbeiterDatenMitarbeiter"/>
   </wsdl:message>
   <wsdl:message name="ReadDataRequest">
      <wsdl:part name="in0" type="xsd:string"/>
      <wsdl:part name="in1" type="xsd:string"/>
      <wsdl:part name="in2" type="xsd:string"/>
      <wsdl:part name="in3" type="xsd:string"/>
   </wsdl:message>
   <wsdl:portType name="SAPHRMitarbeiterDatenRead">
      <wsdl:operation name="ReadData" parameterOrder="in0 in1 in2 in3">
         <wsdl:input message="impl:ReadDataRequest" name="ReadDataRequest"/>
         <wsdl:output message="impl:ReadDataResponse" name="ReadDataResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="SAPHRMitarbeiterDatenReadSoapBinding" type="impl:SAPHRMitarbeiterDatenRead">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="ReadData">
         <wsdlsoap:operation soapAction=""/>
         <wsdl:input name="ReadDataRequest">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:input>
         <wsdl:output name="ReadDataResponse">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="SAPHRMitarbeiterDatenReadService">
      <wsdl:port binding="impl:SAPHRMitarbeiterDatenReadSoapBinding" name="SAPHRMitarbeiterDatenRead">
         <wsdlsoap:address location="http://194.55.55.58:7001/SAPHRMitarbeiterDatenWebservice/services/SAPHRMitarbeiterDatenRead"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Hi Michael,
the use of soapenc:Array is not supported. There are other ways to declare arrays:
-In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type.
-In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration.
-In a DESCRIPTION, array declaration wrapper elements SHOULD NOT be named using the convention ArrayOfXXX.
-A MESSAGE containing serialized arrays MUST NOT include the soapenc:arrayType attribute.
So you need to copy the WSDL file to a local file and edit it, afterwards, use it to generate the proxy.
Maybe you should have a look at the following url:
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272
I hope this will help you to solve the problem.
Edited by: Duhan Bernhard on Nov 7, 2008 12:29 PM

Security-role for java web services developed using j-developer 10.1.2.1

I have developed a java web service using j-developer 10.1.2.1, I have deployed this web service to oracle 10g (10.1.2.1) application server successfully. Now I want to add security-role to my web service deployment descriptor so that only a group of users that belong to a group can access my web service.
How can I do this? Can any one please let me know.
Thanks,
SC.

Hi.
I suspect you have a proxy server between your localhost and the
drive-app1.drivesoftwaresolutions.com
Probably in Jdev that proxy is setup nicely in Tools->Preferences->Web Browser and Proxy
But maybe your OC4J container running BPEL on localhost does not have that proxy setup.
You need to add startup parameters to the JVM. In 10.1.3 you can do this via the "AS Control" administration pages (there is a link on the SOA suite welcome page). Go to JVM, click on the container and switch to the "Administration" tab.
The properties are proxySet, proxyHost, proxyPort and nonProxyHosts
When deploying from JDev, the compilation in JDev works fine (uses the proxy). But when the JAR is transferred to the server, it is compiled again. This fails because the proxy is not used on the server side and it cannot read the wsdl.

Good books for java web services

hi.. i want to learn java web services. can anyone pls tell me the good books or material if any to start with. I have exp in core java.

http://www.soabook.com/ The Good Book for modern web service development in Java.
http://www.amazon.com/J2EE-Web-Services-SOAP-JAX-RPC/dp/0321146182 The Bible about all things web services.
Get them both, use the first to learn and the second as a reference.

Dev Env Setup for Java Web Services

Where can I find some good documentation that clear shows how to setup CR Server XI2 and my Java dev environment so I can deploy and run the Java Web Services samples and do develoment of my own. I can only find bits and pieces about Java Web Services but so far cannot get anything to work.

The XI Release 2 Service Pack 2 Web Services Developer guide is found here:
http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2
/en/en/WS_SDK/wssdk_consumer/default.htm
Sincerely,
Ted Ueda

Error while generating client proxy

Hi All,
I have got a WSDL file for which I am generating the client proxy. It is giving me a dump saying that, memory is not sufficient while generating the proxy.
I have also contacted the basis team, even after increasing the memory... we are facing the same issue. Can anyone suggest any solution or SAP Note if there are any???
Thanks in advance.
Bhargava.

Hi,
Please find the dump details below:
ST22 DUMP:
Short text
    No storage space available for FORM stack.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement
Error analysis
    You attempted to extend a stack, but the required storage spac
    not available.
    Storage request..............: 8450048 bytes.
How to correct the error
    Please check whether uncontrolled recursive calls caused this
    runtime error.
    Try to decide by analysis whether this request is
    reasonable or whether there is a program error. You should pay
    particular attention to the internal table entries listed belo
System environment
    SAP-Release 701
    Application server... "dcr"
    Network address...... "10.1.105.112"
    Operating system..... "AIX"
    Release.............. "6.1"
    Hardware type........ "00C834224C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 4

Error when create client proxy in ABAP

hi all
when I tried to create a client proxy through wsdl: http://www.webservicex.net/geoipservice.asmx?wsdl , I got and error message "Exception occurred in library handler", what's the really matter with this error ?
thanks very much!

You need to copy the WSDL file to a local file and edit it. The WSDL file contains non-SOAP bindings and that's what the generator is choking on. Use the 'Local file' option to generate the proxy class after editing the file.

Problem in creating a java proxy for PHP web service

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

How to setup Proxy for Java Web Start App ?

I'm having trouble getting Java Web Start to work.
at... http://java.sun.com/docs/books/tutorial/uiswing/14start/compile.html
It tell me...
To test whether your browser can launch an application using Java Web Start, click this link.
http://java.sun.com/docs/books/tutorialJWS/uiswing/14start/example-1dot4/HelloJWS.jnlp
I do that & see Java Web Start try to start but get message...
Java Web Start - Invalid Argument
Unable to launch specified application
An error occurred while launching/running the application.
Category: Invalid Argument error
Could not load file/URL specified: C:\Documents and Settings\Will\Local Settings\Temporary Internet Files\Content.IE5\OP8RSBCV\HelloJWS[1].jnlp
Then... http://java.sun.com/docs/books/tutorial/information/javawebstart.html tells me...
"This situation usually happens when your browser and your copy of Java Web Start have different proxy settings."
I click Start | Programs | Java Web Start | Java Web Start,,, then click File | Preferences | General
My choices are... Proxies: None User Browser _ Manual (User Browser grayed out)
If _ Manual checked then I get...
HTTP Proxy ______
HTTP Port _______
I'm running XP Pro via Wi Fi to a Linksys Wi Fi router to a cable modem... I'm also running Zone Alarm (tried turning it off but no luck)
I don't know how to set up the Proxy stuff... can any one please help me get this set up.
thanks - Will

OK, on my XP Pro system I went to...
Start IE -> Control Panel -> Internet Options -> Connections -> Lan Settings -> Proxy Settings
This is my 'Local Area network (LAN) Settings panel...
- user Proxy server for LAN is checked
- Address is blank
- Port is blank
So do I plug something in here... the ip address of my linksys wi-fi router and a port number or what?
My Java Web Start Preferences won't let me click 'Use Browser' only None or Manual
If I click Manual, I don't know what to plug into the HTTP Proxy and HTTP Port fields...
I tried the ip address of my router... thinking it may have a built in Proxy Server... and port 8080 as indicated by the Help page for the Java Web Start... but no luck.
I really appriceate any help on this...
thanks - Will

Error when trying to access a secured web service from Forms 10g 10.1.2.3

Hello,
I'm trying to access a secured web service from Forms10g 10.1.2.3 but i'm getting the next error when pressing the button the first time:
java.rmi.RemoteException: ; nested exception is: HTTP transport error: javax.xml.soap.SOAPException:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 401 UnauthorizeWhen i press the button a second time i got this error:
javax.xml.rpc.soap.SOAPFaultException: The SOAP request is invalid. The required node 'Envelope' is missingThis is the code i have in my button:
DECLARE
jo ora_java.jobject;
pdfObject ora_java.jobject;
pdf     varchar2(900);
rv varchar2(100);
ex ora_java.jobject;
BEGIN
JO := SEARCHSOAPCLIENT.new;
SEARCHSOAPCLIENT.setUsername(JO,'weblogic');
SEARCHSOAPCLIENT.setPassword(JO,'welcome1');
pdfObject := SEARCHSOAPCLIENT.quicksearch(JO,'1234',NULL);
pdf := SEARCHSOAPCLIENT.tostring(pdfObject);
message(pdf);
message(' ');
EXCEPTION
WHEN ORA_JAVA.JAVA_ERROR then
message('Unable to call out to Java, ' ||ORA_JAVA.LAST_ERROR);
WHEN ORA_JAVA.EXCEPTION_THROWN then
ex := ORA_JAVA.LAST_EXCEPTION;
:error := Exception_.toString(ex);
END;When i run it from JDeveloper it works, this is a portion of java code the proxy web service has:
import oracle.webservices.transport.ClientTransport;
import oracle.webservices.OracleStub;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Stub;
public class SearchSoapClient {
    private webservicesproxywebcontent.proxy.SearchSoap _port;
    public SearchSoapClient() throws Exception {
        ServiceFactory factory = ServiceFactory.newInstance();
        _port = ((webservicesproxywebcontent.proxy.Search)factory.loadService(webservicesproxywebcontent.proxy.Search.class)).getSearchSoap();
        this.setUsername("weblogic");
        this.setPassword("welcome1");
        System.out.println("callling from _port "+ _port.quickSearch("1234234", null));
     * @param args
    public static void main(String[] args) {
        try {
            webservicesproxywebcontent.proxy.SearchSoapClient myPort = new webservicesproxywebcontent.proxy.SearchSoapClient();
            System.out.println("calling " + myPort.getEndpoint());
        } catch (Exception ex) {
            ex.printStackTrace();
     * delegate all operations to the underlying implementation class.
    public QuickSearchResult quickSearch(String queryText, IdcPropertyList extraProps) throws java.rmi.RemoteException {
        return _port.quickSearch(queryText, extraProps);
    }Also the secured web service was generated from Webcenter Content 11.1.1.6 that is why it's a secured web service.
Kind Regards
Carlos

Without going into any technical discussion about the code, my first question is what JDK version was used to create this which was imported into the form? Understand that Forms 10 runs on JDK 1.4.2, so if you used any newer JDK version, likely there will be problems.

Namespace Error when generating Client Proxy for Java Web Service

Similar Messages

Maybe you are looking for