Java ME 3.0 Web Services Stub Generator Inheritance problem

Hello,
I have a problem with that relates to inheritance.
Suppose I have abstract class User and class Member that extends class User.
Suppose I have web service MyService:
@WebService
public class MyService {
public User getUser(int id) {
// do something
When the server returns a Member instance instead of User I receive a MarshalException at the Client.
The reason is " Invalid Element in Response:" + Member field that isn't part of User.
I am using Java Me SDK 3.0 wscompile stub generator.
I have also checked it with GlassFish stub generator wsimport and there the problem didn't appear.
Ideas ?
Thanks in advance,
Raanan

Seems like you are missing a necessary jar-file in your forms-classpath. Check the libraries attached to your project in Jdeveloper and add them to the path.

Similar Messages

FlexBuilder Generated Web Service Stubs and requestTimeout

I generated webservice stubs from a WSDL using Flexbuilder and during an operation I would like the request to timeout after a certain amount of time (say 5 seconds). How would I get the generated web service stub to generate a timeout fault? I tried setting the requestTimeout property in the autogenerated BaseService class, but it seems to have no effect

Can you point me to any documentation that gives more information about this ? Because I came across a scenerio's once wher if I provide Ties it will accept them and it will not re-create them .........
Both are tow scenerio with "server" = true option :
Here's when it won't do it :
If I run wscompile on a config file that provide's "service" tag and include all those ties generated in deployement file it won't re-create the ties.
Bur here's when it will :
If I run wscompile on config file that provides "wsdllocation" tag and than include those genertaed files in the deployement than it will re-create the ties again .
Any idea about that ?
Prashant

Using Oracle AS Web Services stub in portlet?

I have built a portlet using the jdeveloper plugin wizard, and added a web service stub using the jdeveloper wizard for that. I have added no other code to the portlet than the stub. When running the portlet the classloader throws an class format exception. When using the same stub in a standalone application it runs fine. The libraries mentioned in jdevelopers under the system library "Oracle SOAP" has all been added to the webapplication web-inf/lib. How do I fix it?

(coworker)
We have solved the problem. It turned out that the auto generated stub contained code not compatible with the OC4J class loader (but compatible with normakl JVM classload). By modifying the stub a little we got it working. Here is the an extract from one method in the stub. The two line that work comes first and the two next lines contains the auto generated code
public Integer dispatchFile(byte[] fileContent, Integer programID) throws Exception {
params.addElement(new Parameter("fileContent", fileContent.getClass(), fileContent, null));
params.addElement(new Parameter("programID", programID.getClass(), programID, null));
// params.addElement(new Parameter("fileContent", byte[].class, fileContent, null));
// params.addElement(new Parameter("programID", Integer.class, programID, null));
The two original lines compiles into some static class members and a static method that fails to load.
The new code does not produce any static content.
We consider this behaviour to be an OC4J error.

Access user inside of web service stub (or web service)

i am trying to access the current portal user from inside a web service and/or a web service stub. (note, ws is generated using xslt)...
i found in an otn document (http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/articles/understanding.web.services.for.portlets.html) the following:
*** begin
By using information specified in the XML provider definition (provider.xml), the renderers allow inputs to a web service to be "wired up" declaratively to any of the following sources of information.
Portlet render request parameters, such as the username, locale and authentication level
*** end
it continues, but the above section seems relevant to me. it indicates that i should be able to get this information to my web service (through the renderer???). can someone please explain how? are there examples of this?
thank you very much.
chris

found it...
http://portalcenter.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/ARTICLES/HOW.TO.BUILD.WEB.SERVICES.PORTLETS.HTML

Converting a java file to a web service

How can i convert a java file to a web service,And then invoke that service by making my other java file.

You can convert your java file into a WSDL with the WSDL2Java utility in Axis. This will create a definition that will be accessible by potential clients.
To deploy your java class, you can use Axis in a Web Server of your choice (Tomcat, Apache). All you need to do is run the Axis Admin Client for a deploy.wsdd file and point your client to the IP:PORT.
Very straightforward.
http://ws.apache.org/axis/java/user-guide.html
Hope it helps.
SBO

Document Literal Web Service Stub Error

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

Flex Builder 3 - Web Service Proxy Generator

Hi guys,
I am investigating the web service proxy generator that is part of FB3. I can't seem to get it working properly and wondered if anyone else has managed to succeed.
I am using WSDL files that are generated from RFC-enabled function modules using the web service browser on a WAS ABAP.
I have chosen two quite simple function modules. RFC_SYSTEM_INFO and BAPI_USER_GETLIST.
The WSDL files are retrieved from the URLs /sap/bc/soap/wsdl11?services=RFC_SYSTEM_INFO and /sap/bc/soap/wsdl11?services=BAPI_USER_GETLIST on my server.
I am following the Adobe documentation at http://livedocs.adobe.com/flex/3/html/help.html?content=data_4.html#151327
Anyway, I generate the proxies and then try to use them.
First I call the RFC_SYSTEM_INFO web service like this...
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns:ws="au.com.yelcho.*">
    <ws:RFC_SYSTEM_INFOService id="myWebService" />
     <mx:Button label="Call Web Service" labelPlacement="top" click="myWebService.rFC_SYSTEM_INFO_send()" x="97" y="10"/>
     <mx:Label x="60" y="43" text="Current Resources"/>
     <mx:Text id="txNameOutput1" text="{myWebService.rFC_SYSTEM_INFO_lastResult.CURRENT_RESOURCES}" x="185" y="43"/>
     <mx:Label x="54" y="69" text="Maximal Resources"/>
     <mx:Text id="txNameOutput" text="{myWebService.rFC_SYSTEM_INFO_lastResult.MAXIMAL_RESOURCES}" x="185" y="69"/>
     <mx:Label x="105" y="95" text="RFC HOST"/>
     <mx:Text id="txNameOutput2" text="{myWebService.rFC_SYSTEM_INFO_lastResult.RFCSI_EXPORT.RFCHOST}" x="185" y="95"/>
</mx:Application>
At first glance this seems to work, but on closer inspection it turns out that not all the returned XML payload has been extracted properly.
Attributes at the top level, like CURRENT_RESOURCES work fine. Attributes at a lower level, like RFCSI_EXPORT.RFCHOST are empty.
It is even more difficult when I try and call the BAPI_USER_GETLIST service because it requires input parameters. Testing with XMLSpy I found that I need to pass the MAX_ROWS and USERLIST parameters to get the SOAP call to work.
I have been unable to figure out how to pass these parameters so that the web service call takes place properly. I have tried using both the MXML and ActionScript methods.
It is entirely probably that, as I haven't played with Flex for some months, I have forgotten some vital piece of information on how to do this.
Any help would be appreciated.
Cheers
Graham Robbo

Hi Raja,
thanks for your ongoing help with this, but you have confused me again - notr a hard this to do.
When I generate the proxies from BAPI_USER_GETLIST I get the following .as files created..
BAPIRET2.as
BAPIUSNAME.as
BAPIUSSEXP.as
BAPIUSSRGE.as
BAPI_USER_GETLISTResultEvent.as
BAPI_USER_GETLISTService.as
BAPI_USER_GETLIST_request.as
BaseBAPI_USER_GETLISTService.as
BaseBAPI_USER_GETLISTServiceSchema.as
FIELD_type0.as
FIELD_type1.as
FIELD_type2.as
FIELD_type3.as
FIELD_type4.as
FIELD_type5.as
FIRSTNAME_type0.as
FIRSTNAME_type1.as
FULLNAME_type0.as
FULLNAME_type1.as
HIGH_type0.as
HIGH_type1.as
HIGH_type2.as
HIGH_type3.as
IBAPI_USER_GETLISTService.as
ID_type0.as
ID_type1.as
LASTNAME_type0.as
LASTNAME_type1.as
LOGOP_type0.as
LOGOP_type1.as
LOG_MSG_NO_type0.as
LOG_MSG_NO_type1.as
LOG_NO_type0.as
LOG_NO_type1.as
LOW_type0.as
LOW_type1.as
LOW_type2.as
LOW_type3.as
MESSAGE_type0.as
MESSAGE_type1.as
MESSAGE_V1_type0.as
MESSAGE_V1_type1.as
MESSAGE_V2_type0.as
MESSAGE_V2_type1.as
MESSAGE_V3_type0.as
MESSAGE_V3_type1.as
MESSAGE_V4_type0.as
MESSAGE_V4_type1.as
NUMBER_type0.as
NUMBER_type1.as
OPTION_type0.as
OPTION_type1.as
OPTION_type2.as
OPTION_type3.as
PARAMETER_type0.as
PARAMETER_type1.as
PARAMETER_type2.as
PARAMETER_type3.as
PARAMETER_type4.as
PARAMETER_type5.as
RETURN_type0.as
RETURN_type1.as
SELECTION_EXP_type0.as
SELECTION_EXP_type1.as
SELECTION_RANGE_type0.as
SELECTION_RANGE_type1.as
SIGN_type0.as
SIGN_type1.as
SYSTEM_type0.as
SYSTEM_type1.as
TYPE_type0.as
TYPE_type1.as
USERLIST_type0.as
USERLIST_type1.as
USERNAME_type0.as
USERNAME_type1.as
WITH_USERNAME_type0.as
WITH_USERNAME_type1.as
So my question is where do the datatypes...
              TABLE_OF_BAPIRET2;
               TABLE_OF_BAPIUSSEXP;
               TABLE_OF_BAPIUSSRGE;
               TABLE_OF_BAPIUSNAME;
               TABLE_OF_BAPIUSNAME;
...come from?
Is your proxy generator creating something mine isn't or did you create these yoursefl?
Cheers
Graham Robbo

The Proper way to go - Passing Serialized Java Objects vs. Web Services?

The team which I am apart of in our little "community" is trying to convince some "others" (management) that we should not use web services to communicate (move large data) within the same application (allbeit a huge application spanning across many servers).
Furthermore these "others" are trying to tell us that in this same application when two small apps. inside of this large app. are both java we should not communicate via serialized java objects but instead we should use Web Services and XML. We are trying to convince them that the simplest way is best.
They have asked us to provide them with proof that passing serialized java objects back and forth between two smaller java applications inside of a larger one is an Industry Standard. Can anyone help either straighten my fellow workers and I out or help us convince the "others" of the proper way to go?

When I was a consultant we always gave the client what they wanted. Even if it was the wrong choice. Suck it up.
I'm glad I wasn't one of those customers. Although I agree that a customer is the one who decides what to do, when I pay someone for consultancy, I expect them to consult me. If they know I'm trying to do something that I shouldn't be doing, I expect a good consultant to be able to show me that there's a better way (not just tell me I'm not doing it right, mind you).
We pass a lot of data using XML and we don't have any transmission or processing speed issues.
Then you either have a much better network than our customer did, or we're not talking about the same amounts of data here.
I used the JAX-RPC RI ...
That's cool... our customer was, unfortunately, infected with Borland products, so we had to use BES. The web services on BES were run by Axis.
How large were these messages?
Huge... each element had about 15 attributes, so 1,200 elements would require 19,200 XML nodes (envelope not included). By comparison, the serialized messages weren't even a quarter that size. It's not just about what you send across the network; it's also the effort of parsing XML compared to desrializing Java objects. Our web service wasn't exactly the only process running at the server.
Anyone who understand the fundamental difference between ASCII (XML) and binary (serialized) formats realizes that no web service can possibly achieve the performance of binary Java services. Why do you think that work is being put into binary web services? I'm not saying XML is never a good thing; just that it's not The Holy Grail that a lot of people are making it look like.
http://issues.apache.org/jira/browse/AXIS-688
Ouch.

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.

WEB SERVICE PROXY GENERATED USING 11.1.1.5.0 WSDL FAILS WITH 11.1.1.6.0

I have created a Web Service Proxy project in Jdev using BI Publisher 11.1.1.5.0 WSDL (ReportService). Generated ReportService_Service method uses following QName to get the port:
namespaceURI = "http://xmlns.oracle.com/oxp/service/v2"
localPart = "*v2/ReportService*"
Reports are generated successfully via Web Services when using BI Publisher 11.1.1.5.0 but when I use BI Publisher 11.1.1.6.x, it fails with this exception:
+'javax.el.ELException: javax.xml.ws.WebServiceException: {http://xmlns.oracle.com/oxp/service/v2}v2/ReportService is not a valid port. Valid ports are: {http://xmlns.oracle.com/oxp/service/v2}ReportService'+
I noticed that if the Web Service Proxy project is created using BI Publisher 1.1.1.1.6.0 WSDL (ReportService), the generated ReportService_Service method uses following QName to get the port:
namespaceURI = "http://xmlns.oracle.com/oxp/service/v2"
localPart = "*ReportService*"
We are supporting both 11.1.1.5.0 and 11.1.1.6.x, so is there a way to make it work with both.
FYI, I have tried removing v2 but then it only works with 11.1.1.6.0 and fails with 11.1.1.5.0.
+Caused By: javax.xml.ws.WebServiceException: {http://xmlns.oracle.com/oxp/service/v2}ReportService is not a valid port. Valid ports are: {http://xmlns.oracle.com/oxp/service/*v2}v2/*ReportService+

Dear,
found the solution (after trying last 1-2 days ...).
I was already using java 1.7 update 7.
I had to start java settings and to deselect Java 1.7.0_07.
Instead I selected latest Java version from Apple: 1.6.0_35-b10-428.
With these settings the installer finishes without crash.
Kind regards
Lorenz
Edited by: Lorenz on Oct 4, 2012 1:47 PM

Modifying properties with a file for Web Service Stub used for Oracle Forms

I have created a stubbed-out web service in JDeveloper (10.1.3.4) and imported into Oracle Forms.
However, I would like to use a properties file to call the appropriate endpoint based on if the environment is dev, test, UAT or prod. I see that a properties file is referenced in the _Stub class. Here is a snippet of code from that class file:
public CriticalChangeWS_Soap11_Stub(HandlerChain handlerChain) {
super(handlerChain);
setProperty(ENDPOINTADDRESS_PROPERTY, "http://epw-01.gds.graebel.com:8087/CriticalChange.svc/Soap11");
setSoapVersion(SOAPVersion.SOAP_11);
setServiceName( new QName("http://tempuri.org/","CriticalChangeService"));
setPortName( new QName("http://tempuri.org/","CriticalChangeWS_Soap11"));
setupConfig("wsquery/proxy/runtime/CriticalChangeWS_Soap11_Stub.xml");
How can I use the XML file to set the ENDPOINT_ADDRESS_PROPERTY?
Thanks.
Jim O

Hi Frank,
I got the following two lines of code just to check if WebServiceConnection was able to read the connections file alright.
            String urlString = wsc.getWsdlUrlStr();
            System.out.println("WSDL URL: "+urlString);
I am not using urlString for further processing.
The output is
WSDL URL: http://<host>/PSIGW/PeopleSoftServiceListeningConnector/MyService.1.wsdl
java.lang.NullPointerException
        at java.lang.Class.isAssignableFrom(Native Method)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:97)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:118)
The WSDL Url pointed to is the one that I configure in the connection while deploying the App.
Ran a test and WSDL Url is accessible by the app.

Web Service stub code different in FB4 than in Flex Builder 3

We have an application that was initially developer in Flex Builder 3 and used the Import Web Service wizard to generate all the webservice stub code we needed. We then upgraded to using Flash Builder 4 and importing the wsdl using the Connect to Data/Service wizard writes different stub code than what we had in Flex Builder 3.
What happened and is there a way to have the Flash Builder 4 wsdl importer write the stub code the way the Flex Builder 3 importer did?

I figured out the RDS issue - check the web.xml file in the
WEB-INF folder of cfroot and webroot. I uncommented the
<servlet-name> and the <servlet-mapping> tags which
referenced RDS Servlet, restarted the server, and that took care of
the RDS issue.

Adding security to a web service then generating a proxy [SOLVED]

Hi
I generated a web service based on a very simple java program. I have deployed it to a local oc4j install and successfully called it from a proxy generated from jdev. I am using 10.1.3.3.0.
I added security to the web service and regenerated the proxy. I wanted to see the difference in the SOAP messages sent to the web service. However the proxy does not seem to have changed to take account of the new security settings on the web service.
The security options I set were:
On main security dialog: Ticked the port and "Text Password"
On Authentication: Ticked "Expect Username ti Authenticate"
"Password Required"
Password Type = "Plain Text"
"Nonce Required in Token"
"Creation Time Required in Token"
I have 2 questions:
1. How do I get the proxy to send SOAP messages that contain the security headers required to run the web service. Here is the main method from my proxy. I thought adding setUsername and setPassword would be the solution
    public static void main(String[] args) {
        try {
            gpn3.Getphonenum3SoapHttpPortClient myPort = new gpn3.Getphonenum3SoapHttpPortClient();
            System.out.println("calling " + myPort.getEndpoint());
            // Add your own code here
            myPort.setUsername("oc4jadmin");
            myPort.setPassword("welcome");
            myPort.getNum("Lisa");
        } catch (Exception ex) {
            ex.printStackTrace();
2. When the web service receives a user name and password what does it check them against? I assume the oc4jadmin user will be allowed access but how do I set up other users?
many thanks
paul schweiger
Message was edited by:
[email protected]

I have figured this out now
1. I needed to set the same security settings in my proxy as I did for my web service. I had assumed that the proxy would generate the necessary security settings from the web service.
2. For some reason my web service application is using the system level jazn-data xml file
oc4j_extended_101330/j2ee/home/config/system-jazn-data.xml
This does include the oc4jadmin user and I am now able to use that account to call the web service. I also managed to add another user and use that account to call the web service successfully.
Thanks for the help
paul

How to code in java to use the web services of CRM

Hi,
I am new to CRM on demand web services. I want to develope a java J2EE application to insert some lead data into CRM on demand. But i have no idea of how the wsdl provided by CRM can be converted to a java class so that i can use the API's provided by them in my program. I am using Eclipse Galileo IDE for my java application development. Can any one tell me the way to reference the wsdl in my program or any other way to build my application.
Please help me out.
Thanx in advance.

May be it's the 'stub' you should be looking for.
Any Account related queries/creations - AccountStub
--> Query : Populate AccountQuery, populate AccountQueryPage_Input, call accountStub.accountQueryPage(input);
--> Creation: Populate AccountData, populate AccountInsert_Input, call accountStub.accountInsert(input)
It's the same procedure for other objects like Contact, Lead, Opportunity.
I worked on other web-services using Axis2, and 'Stub' has been the one which we use to connect to the web-service.
Edited by: 838315 on Mar 30, 2011 11:17 PM
Edited by: 838315 on Mar 30, 2011 11:59 PM

Java exception when invoking web service

I am using JDeveloper 10.1.3.04 to deploy a PL/SQL function as a web service to 10gIAS. I can deploy the service, but when invoking it from the endpoint my SOAP output looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>java.lang.NullPointerException</faultstring>
<faultactor>/GetAmountContextRoot/MyWebService1</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Deploying what is essentially the same web service to the OC4J instance that comes with JDeveloper, my SOAP returns the expected value:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns: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:ns0="http://devl29ieda/MyWebService2.wsdl/types/"><env:Body><ns0:returnAmountResponseElement><ns0:result>305249</ns0:result></ns0:returnAmountResponseElement></env:Body></env:Envelope>
I believe the problem is within the Java code created by the Web Service Wizard, but I do not know where.
Any help would be greatly appreciated.
Steven

Hi Steven,
You may want to look at the log on the server side to see if you have any hint that may help you track down where the NPE is comming from.
As you are using PL/SQL function, the other think you want to check is that the datasource information are properly defined in both environment.
Hope it helps,
-eric

Java ME 3.0 Web Services Stub Generator Inheritance problem

Similar Messages

Maybe you are looking for