It wasnt the namespace ( i cleaned that up now, same error still ). If I
insert the Code:
-----------------------------
if (reader.getState() == XMLReader.START) {
if (elementName.equals(ns1_getJobStateReturn_QNAME)) {
..... Original DeSerialize Code ( ns1_getJobStateReturn_QNAME =
"getJobStateReturn" )
}
// New hacked deserialze Part
else if(elementName.equals(nsMADDI_JobState_QNAME)) //
(nsMADDI_JobState_QNAME == JobState)
{
member =
ns2_myJobState_SOAPSerializer.deserialize(nsMADDI_JobState_QNAME, reader,
context);
if (member instanceof SOAPDeserializationState) {
if (builder == null) {
builder = new
DobbinStub.Dobbin4Web_getJobState_ResponseStruct2_SOAPBuilder();
}
state = registerWithMemberState(instance, state, member,
myGETJOBSTATERETURN_INDEX, builder);
isComplete = false;
} else {
instance.setGetJobStateReturn((DobbinStub.JobState)member);
}
reader.nextElementContent();
}
---------
in Dobbin4Web_getJobState_ResponseStruct2_SOAPSerializer::doDeserialize(...)
Everything works, but thats a hack.
Thx
Marcus
----- Original Message -----
From: "Marcus Tillmanns" <m.tillmanns_at_cube-tec.de>
To: <users_at_jax-rpc.dev.java.net>
Sent: Monday, August 23, 2004 1:33 PM
Subject: Re: Axis and Java WSDP WebServices
> Good Point, Ill check that out now.
>
> But the error Message from Java sais:
> java.rmi.RemoteException: Runtime exception; nested exception is:
> unexpected element name: expected=getJobStateReturn, actual=JobState
> at
>
com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(Streami
> ngSender.java:248)
> at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:230)
> at
>
DobbinStub.Dobbin4Web_PortType_Stub.getJobState(Dobbin4Web_PortType_Stub.jav
> a:120)
> (....)
>
> Thx,
> Marcus
>
>
> ----- Original Message -----
> From: "Anne Thomas Manes" <anne_at_manes.net>
> To: <users_at_jax-rpc.dev.java.net>
> Sent: Monday, August 23, 2004 1:27 PM
> Subject: RE: Axis and Java WSDP WebServices
>
>
> > The namespace in the response message doesn't match the WSDL definition.
> > This is probably what's causing your problem.
> >
> > The WSDL says it should be "http://localhost/axis/Dobbin4Web", but the
> > response message uses "http://localhost/Dobbin4Web".
> >
> > I'm assuming that JWSDP is giving you an error that it doesn't
understand
> > how to parse {http://localhost/Dobbin4Web}getJobStateResponse?
> >
> > The problem isn't with the wrapper element's local name
> (getJobStateResponse
> > versus getJobStateReturn -- the local name doesn't matter); it's with
the
> > namespace qualifier.
> >
> > There must be something wrong with the way you configured the service,
> > because the service response doesn't correspond to the published WSDL.
> >
> > Anne
> >
> > -----Original Message-----
> > From: Marcus Tillmanns [mailto:m.tillmanns_at_cube-tec.de]
> > Sent: Monday, August 23, 2004 4:00 AM
> > To: users_at_jax-rpc.dev.java.net
> > Subject: Re: Axis and Java WSDP WebServices
> >
> > Sure,
> >
> > Im not sure if its all copliant, But I somehow expect Axis to be a
little
> > compliant :) Anyway, here is the request (not from Java but php nuSoap,
I
> > don't think that matter greatly, cause request works always):
> >
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> > <SOAP-ENV:Envelope
> > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> > 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:nu="http://dobbin/axis/Dobbin4Web">
> > <SOAP-ENV:Body>
> > <nu:getJobState xmlns:nu="http://dobbin/axis/Dobbin4Web">
> > <jobid xsi:type="xsd:string">TestJob</jobid>
> > </nu:getJobState>
> > </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
> >
> > and the response
> >
> > <?xml version='1.0' encoding='utf-8' ?>
> > <SOAP-ENV:Envelope
> > 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:env="http://www.w3.org/2003/05/soap-envelope"
> > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/">
> > <SOAP-ENV:Body>
> > <ns1:getJobStateResponse
> > xmlns:ns1="http://localhost/dobbin4web"
> > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
> > <JobState xsi:type="ns2:JobState"
> xmlns:ns2="http://soapinterop.org/xsd">
> > <state xsi:type="xsd:int">0</state>
> > <message xsi:type="xsd:string">Noch nicht Implemementiert</message>
> > </JobState>
> > </ns1:getJobStateResponse>
> > </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
> >
> > The wsdl part looks like this:
> >
> > <wsdl:message name="getJobStateRequest">
> > <wsdl:part name="jobid" type="xsd:string"/>
> > </wsdl:message>
> >
> > <wsdl:message name="getJobStateResponse">
> > <wsdl:part name="getJobStateReturn" type="s:JobState"/>
> > </wsdl:message>
> >
> > <wsdl:operation name="getJobState" parameterOrder="jobid">
> > <wsdl:input message="tns:getJobStateRequest"
> > name="getJobStateRequest"/>
> > <wsdl:output message="tns:getJobStateResponse"
> > name="getJobStateResponse"/>
> > </wsdl:operation>
> >
> > <wsdl:operation name="getJobState">
> > <soap:operation soapAction="Dobbin4Web#getJobState"/>
> > <wsdl:input name="getJobStateRequest">
> > <soap:body
> >
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> > namespace="http://localhost/axis/Dobbin4Web"
> > use="encoded"/>
> > </wsdl:input>
> > <wsdl:output name="getJobStateResponse">
> > <soap:body
> >
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> > namespace="http://localhost/axis/Dobbin4Web"
> > use="encoded"/>
> > </wsdl:output>
> > </wsdl:operation>
> >
> > I already thought that its an Axis failure, not generating a compliant
> > response, but since php nuSoap understands the response, I thought that
at
> > least the SOAP Implementation should be able to handle this. And a guy
> from
> > Sun told me that there is a place to configure how the response shall be
> > formatted, but didn't said where this could be done.
> >
> > Thx for your time,
> > Marcus
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Doug Kohlert" <Doug.Kohlert_at_Sun.COM>
> > To: <users_at_jax-rpc.dev.java.net>
> > Sent: Friday, August 20, 2004 8:50 PM
> > Subject: Re: Axis and Java WSDP WebServices
> >
> >
> > > Marcus,
> > > Wscompile generates stubs based on what is in the WSDL file. Are you
> > > sure that the return message is formatted in compliance with
> > > the WSDL? Can you include the WSDL and the response SOAP message you
> > > are getting?
> > >
> > > Marcus Tillmanns wrote:
> > >
> > > >Hi guys,
> > > >
> > > >Im new to java and WSDP, I normaly worked with C++ and Axis. I have
> > written
> > > >a WebService using Axis C++ wich works fine with Axis Clients. But
now
> I
> > (or
> > > >the customer) wan't to call this Service via Jwsdp / j2ee. The
problem
> is
> > > >that Axis doens't encloses its response Messages as the jwsdpstubs
> think
> > (
> > > >it omits the funcNameReturn MessageName ). I was told that I can
alter
> > the
> > > >Typemapping wscompile uses, but I can't find where I should do it and
> how
> > to
> > > >tell wscompile to use this alternate typemapping. Could you point me
> > towards
> > > >the right location for this kind of stuff ?
> > > >
> > > >Thx in advance
> > > >Marcus Tillmanns
> > > >
> > > >
> > > >---------------------------------------------------------------------
> > > >To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > > >For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > -------------------------------
> > > Doug Kohlert
> > > Sun MicroSystems, Inc.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > > For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net