Hey, I finally found this opportunity...

JAX-RPC vs. Axis

Guys,

Is it possible to use JAX-RPC with Axis web service? I tried a version 
that comes with Glassfish 3 and got some easy operations working but for 
more complicated some deserialization exceptions occur. With Apache Axis 
everything works just fine.

Exception in thread "main" java.rmi.RemoteException: Runtime exception; 
nested exception is:
deserialization error: deserialization error: unexpected XML reader 
state. expected: END but found: START: id
at 
com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:348)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:330)
at test.JiraSoapService_Stub.getIssue(JiraSoapService_Stub.java:376)
at rpcclient4.RPCClient4.main(RPCClient4.java:33)
Caused by: deserialization error: deserialization error: unexpected XML 
reader state. expected: END but found: START: id
at 
com.sun.xml.rpc.encoding.SOAPDeserializationContext.deserializeMultiRefObjects(SOAPDeserializationContext.java:107)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:256)
... 2 more
Java Result: 1

--

-- 
Best regards,
Alexander Kouznetsov

jax-rpc is now live

What is a messageContext?

I need to get a SOAPMessage and I think the solution is the following:

SOAPMessageContext soapContext = (SOAPMessageContext)messageContext;

// get SOAP message
SOAPMessage msg = soapContext.getMessage();

But, what is that messageContext??

I have created my proxy automatically with Netbeans using an wdsl file.
My Service Endpoint Interface is called "ManagementService"

Thank you to everyone
--

-- 
View this message in context: http://old.nabble.com/What-is-a-messageContext--tp28256780p28256780.html
Sent from the JAX-RPC - User mailing list archive at Nabble.com.

Java to WSDL nillable attributes?

Newbie Question,

When I generate my wsdl from Java code all of the attributes in my WSDL are
set to nillable="true".

I update the generated wsdl to have nillable="false" for the attributes that
must be populated but when the WAR file get's deployed the wsdl sets
everything back to nillable="true".

Is there a way to keep the WSDL file from getting changed? 

BTW, im using Eclipse IDE, JAX-RPC, AXIS in Tomcat environment.

Any help would be appreciated.
--

-- 
View this message in context: http://old.nabble.com/Java-to-WSDL-nillable-attributes--tp27461893p27461893.html
Sent from the JAX-RPC - User mailing list archive at Nabble.com.

Character Set Encoding

Hi !
I developed a web service, and a mobile client. On the Sun Wireless
Toolkit Emulator the mobile client works fine, but when it's deployed
on my nokia 5800, there is
an error when i send a char like á,é,ñ  :

Jan 21, 2010 10:31:23 PM
com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit handle
SEVERE: Couldn't create SOAP message due to exception: XML reader
error: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte
0x65 (at char #261, byte #37)

i found a solution for this problem but for the ibm implementation of jax-rpc :
set the javax.xml.soap.SOAPMessage.CHARACTER_SET_ENCODING property
but in the stub generated by netbeans ( netbeans impl of jax-rpc ?? )
i don't find this property

Thanks you in advance

jax-rpc - cyclical references

JAX-RPC - Parameter with Cyclical References

namespace help

I'm a novice (at best) at SOAP and Web Services in general.  I'm writing
a simple program to consume this web service. WSDL below.  The stubs and
stuff are generated by NetBeans 6.7.1

The code I am using to test:
    ToyboxService_Impl l_service = new ToyboxService_Impl();
    RTI l_rti = l_service.getRTI();
    ((Stub)l_rti)._setProperty(Stub.USERNAME_PROPERTY, "omitted");
    ((Stub)l_rti)._setProperty(Stub.PASSWORD_PROPERTY, "omitted");
    StringHolder l_cid = new StringHolder();
    StringHolder l_content = new StringHolder();
    StringHolder l_result = new StringHolder();
    l_rti.fetch_profile("me <at> you.com", l_cid, l_content, l_result);

The error I am getting:

unexpected element name:
expected={http://the.namespace.com/survey/}fetch_profileResponse,
actual=fetch_profileResponse

If I am reading that correctly, the generated code is expecting the
namespace but the server is not responding with one.  Is that what that
means?  Is there something I can tweak in the WSDL or the code to get
around this problem?

<wsdl:definitions
    targetNamespace="http://the.namespace.com/survey/"
    elementFormDefault="unqualified"
    attributeFormDefault="unqualified"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tbx="http://abc.stuff.com/"
    xmlns:rti="http://the.namespace.com/survey/">

  <wsdl:message name="create_profileParameters">
    <wsdl:part name="email" type="xsd:string" />
    <wsdl:part name="first_name" type="xsd:string" />
    <wsdl:part name="last_name" type="xsd:string" />
    <wsdl:part name="address1" type="xsd:string" />
    <wsdl:part name="address2" type="xsd:string" />
    <wsdl:part name="city" type="xsd:string" />
    <wsdl:part name="state" type="xsd:string" />
    <wsdl:part name="zip" type="xsd:string" />
    <wsdl:part name="age_range" type="xsd:string" />
    <wsdl:part name="home_phone_number" type="xsd:string" />
  </wsdl:message>

  <wsdl:message name="fetch_profileParameters">
    <wsdl:part name="email" type="xsd:string" />
  </wsdl:message>

  <wsdl:message name="rtiResult">
    <wsdl:part name="cid" type="xsd:string" />
    <wsdl:part name="content" type="xsd:string" />
    <wsdl:part name="result" type="xsd:string" />
  </wsdl:message>

  <wsdl:portType name="RTI">

    <wsdl:operation name="create_profile">
      <wsdl:input message="rti:create_profileParameters" />
      <wsdl:output message="rti:rtiResult" />
    </wsdl:operation>

    <wsdl:operation name="fetch_profile">
      <wsdl:input message="rti:fetch_profileParameters" />
      <wsdl:output message="rti:rtiResult" />
    </wsdl:operation>

  </wsdl:portType>

  <wsdl:binding name="SOAP" type="rti:RTI">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>

    <wsdl:operation name="create_profile">
      <soap:operation soapAction="#create_profile"/>
      <wsdl:input>
        <soap:body namespace="http://the.namespace.com/survey/"
use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body namespace="http://the.namespace.com/survey/"
use="literal"/>
      </wsdl:output>
    </wsdl:operation>

    <wsdl:operation name="fetch_profile">
      <soap:operation soapAction="#fetch_profile"/>
      <wsdl:input>
        <soap:body namespace="http://the.namespace.com/survey/"
use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body namespace="http://the.namespace.com/survey/"
use="literal"/>
      </wsdl:output>
    </wsdl:operation>

  </wsdl:binding>

  <wsdl:service name="ToyboxService">
    <wsdl:documentation>stuff</wsdl:documentation>
    <wsdl:port name="RTI" binding="rti:SOAP">
      <soap:address location="http://the.namespace.com/survey/"/>
    </wsdl:port>
  </wsdl:service>

</wsdl:definitions>

--

-- 

Mitch Claborn
972-954-7341
mitch <at> claborn.net

SOAP WSA Header with jwsdp-1.6

Does the WSDL validate the request, response and fault types in Document-literal type of webservices