Hi Wolfgang,
Yes - it is using Axis 1.4. I have attached the wsdl file for you to review.
The server sends error message to the client if something is wrong. That is
the error message I sent you. The client I am using is a C# client. So the
error was not generated on the client. I think the error is happening during
the marshaling process on the server side. Please let me know what you think.
Thanks again for all the help.
Best Regards!
Raihan
--- On Tue, 7/1/08, WJ Krpelan <[EMAIL PROTECTED]> wrote:
> From: WJ Krpelan <[EMAIL PROTECTED]>
> Subject: Re: Questions regarding Axis1.4
> To: [email protected]
> Date: Tuesday, July 1, 2008, 6:41 AM
> ok,
>
> The errors you are getting are caused by the client java
> app trying to deserialize the soap/xml-response and getting
> something unexpected
> I.E. the SERVER is sending some response the CLIENT cant
> make sense of.
> Notice the various instances of "response" within
> these error-messages.
>
> the next step would be to have a look at the actual
> SOAP-XML-Response on the wire, which could be done e.g. by
> using the microsoft-tool fiddler or some soap-monitor like
> tcpmon which is being shipped with AXIS 1.4
>
> My guess at this moment would be the
> Webservice-Implementation on the SERVER side doesnt do what
> you would expect. Is the server built on AXIS 1.4? What does
> the WSDL-document look like?
>
> I dont think the responsibility lies with the code you sent
> me,
> maybe with the code which reassembles the image out of the
> base64-data (improbable)
>
> HTH
> Wolfgang
>
>
>
>
>
>
> --- On Mon, 6/30/08, Raihan Ahmed
> <[EMAIL PROTECTED]> wrote:
>
> > From: Raihan Ahmed <[EMAIL PROTECTED]>
> > Subject: Re: Questions regarding Axis1.4
> > To: [email protected]
> > Date: Monday, June 30, 2008, 5:27 PM
> > Hi,
> > Yes, this document causes the error. But dumping it
> into a
> > string, you might not be able to reproduce the error
> since
> > the image data won't be base64 string dynamically
> > generated from inside the code. But please try for
> me!
> >
> > Also, if you can't reproduce the error, could you
> write
> > a small WS to send a small xml document where one node
> will
> > have base64 data generated by reading an image file to
> see
> > if you can reproduce error? I know I am asking too
> much!
> > But I need your expertise/knowledge badly to shed some
> > lights on this issue.
> > I have attached the code to generate base64 from an
> image
> > file to save you time in case you decide to try the
> second
> > approach.
> >
> > And here is the error we are getting -
> > ERROR:
> > System.Web.Services.Protocols.SoapException:
> > java.lang.reflect.InvocationTargetException
> > at
> >
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> > message, WebResponse response, Stream responseStream,
> > Boolean asyncCall)
> > at
> >
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at
> > GuruWebServiceImpService.getArrestBookingReport(String
> in0,
> > String in1) in
> >
> C:\TestCourtWS\TestCourtWS\TestCourtWS\GuruWebServiceImpService.cs:line
> > 334
> > at TestCourtWS.Form1.btnAB_Click(Object sender,
> > EventArgs e) in
> >
> C:\TestCourtWS\TestCourtWS\TestCourtWS\Form1.cs:line
> > 269
> >
> > Thanks so much!
> > Raihan
> >
> > --- On Mon, 6/30/08, WJ Krpelan
> > <[EMAIL PROTECTED]> wrote:
> >
> > > From: WJ Krpelan <[EMAIL PROTECTED]>
> > > Subject: Re: Questions regarding Axis1.4
> > > To: [email protected]
> > > Date: Monday, June 30, 2008, 10:35 AM
> > > Ahmed,
> > > this xml document is looking alright
> > > could you verify that exactly this example
> document
> > causes
> > > an error too so that I could try to reproduce it
> by
> > putting
> > > it into a string. pls give me the exact error
> message
> > if
> > > applicable
> > > Cheers, Wolfgang
> > >
> > >
> > >
> > > --- On Mon, 6/30/08, Raihan Ahmed
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > From: Raihan Ahmed
> <[EMAIL PROTECTED]>
> > > > Subject: Re: Questions regarding Axis1.4
> > > > To: [email protected]
> > > > Date: Monday, June 30, 2008, 3:09 PM
> > > > Hi Wolfgang,
> > > > I am sending you an attachment with an
> example
> > xml
> > > document
> > > > that we output to the client. I will send
> you
> > the
> > > > attachment to your personal account in
> Apache has
> > any
> > > > restrictions on attachments.
> > > > I hope this will help you see what I am
> doing
> > wrong.
> > > > I again thank you sincerely for taking the
> time
> > out to
> > > look
> > > > at this issue.
> > > > Raihan
> > > >
> > > >
> > > > --- On Mon, 6/30/08, WJ Krpelan
> > > > <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > From: WJ Krpelan
> > <[EMAIL PROTECTED]>
> > > > > Subject: Re: Questions regarding
> Axis1.4
> > > > > To: [email protected]
> > > > > Date: Monday, June 30, 2008, 5:17 AM
> > > > > Ahmed,
> > > > > its difficult to follow because I cant
> tell
> > when
> > > are
> > > > you
> > > > > speaking of the overall xml-document
> and
> > when of
> > > an
> > > > > included xml-document. btw the
> > > xml-schema-datatype is
> > > > named
> > > > > "base64Binary" and not
> base64. so
> > > whereever
> > > > you
> > > > > use base64 data you should discover a
> > > > > "base64Binary" datatype
> within
> > your
> > > > > xml-schema-document for your
> > > xml-instance-document.
> > > > > I assume here that your xml-documents
> are
> > all
> > > > > xml-schema-based?
> > > > > Still I think an (anonymized) example
> > document
> > > would
> > > > say
> > > > > more than a thousand words,
> > > > > Wolfgang
> > > > >
> > > > >
> > > > > --- On Mon, 6/30/08, Raihan Ahmed
> > > > > <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > From: Raihan Ahmed
> > > <[EMAIL PROTECTED]>
> > > > > > Subject: Re: Questions regarding
> > Axis1.4
> > > > > > To: [email protected]
> > > > > > Date: Monday, June 30, 2008, 1:36
> AM
> > > > > > Hi Wolfgang,
> > > > > > Thanks a bunch for your email. I
> know
> > it is
> > > very
> > > > > unusual
> > > > > > having xml document inside xml
> > document. It
> > > was
> > > > one
> > > > > of the
> > > > > > requirement of the client that the
> > output
> > > has to
> > > > be in
> > > > > xml
> > > > > > document. It has data from
> multiple
> > > different
> > > > sources
> > > > > and
> > > > > > uses Justice xml for law
> enforcement
> > > agencies as
> > > > its
> > > > > > standard. So far we have not run
> into
> > any
> > > issues
> > > > (as
> > > > > long
> > > > > > as we didn't use base64 data)
> with
> > this
> > > even
> > > > > though it
> > > > > > seems weird considering that SOAP
> > response
> > > itself
> > > > is
> > > > > an xml
> > > > > > document. Can you think of any
> other
> > way we
> > > > could do
> > > > > this?
> > > > > > As far as the hard-coded base64
> string
> > goes,
> > > this
> > > > is
> > > > > what
> > > > > > is happening -
> > > > > > after a client request, I query
> > database
> > > with
> > > > input
> > > > > data,
> > > > > > and parse the query result and put
> them
> > in
> > > the
> > > > xml
> > > > > > document. During this process, I
> have
> > to
> > > check
> > > > if the
> > > > > > record has an image associated
> with it.
> > If
> > > it
> > > > does,
> > > > > then I
> > > > > > get the image file, convert it
> into
> > base64
> > > and
> > > > stick
> > > > > that
> > > > > > base64 string into the image tag.
> And
> > it
> > > fails.
> > > >
> > > > > > I also print this xml document out
> for
> > > debugging
> > > > > purposes.
> > > > > > From this output, if I copy and
> paste
> > the
> > > base64
> > > > > string into
> > > > > > the image tag (that is I am
> sending a
> > > hard-coded
> > > > > output),
> > > > > > then it works. That is, my output
> sent
> > to
> > > client
> > > > > always
> > > > > > has the same image data.
> > > > > > I am not sure if I was able to
> explain
> > this
> > > at
> > > > all.
> > > > > Please
> > > > > > let me know if you need any more
> info
> > to
> > > help me
> > > > out
> > > > > with
> > > > > > this problem.
> > > > > > Thanks again!
> > > > > > Raihan
> > > > > >
> > > > > >
> > > > > > --- On Sun, 6/29/08, WJ Krpelan
> > > > > > <[EMAIL PROTECTED]>
> wrote:
> > > > > >
> > > > > > > From: WJ Krpelan
> > > > <[EMAIL PROTECTED]>
> > > > > > > Subject: Re: Questions
> regarding
> > > Axis1.4
> > > > > > > To: [email protected]
> > > > > > > Date: Sunday, June 29, 2008,
> 5:32
> > PM
> > > > > > > Hi
> > > > > > > what you are doing (putting
> xml
> > > documents
> > > > within
> > > > > xml
> > > > > > > documents as strings)
> > > > > > > is not considered usual
> practice.
> > > I'm
> > > > not
> > > > > > surprised
> > > > > > > that you are running into
> problems
> > with
> > > AXIS
> > > > 1
> > > > > using
> > > > > > this
> > > > > > > approach.
> > > > > > > I dont understand exactly
> what you
> > mean
> > > by
> > > > > putting it
> > > > > > > hardcoded vs generated into
> the
> > > response.
> > > > could
> > > > > you
> > > > > > provide
> > > > > > > an example?
> > > > > > > Cheers,
> > > > > > > Wolfgang
> > > > > > >
> > > > > > >
> > > > > > > --- On Sun, 6/29/08, Raihan
> Ahmed
> > > > > > > <[EMAIL PROTECTED]>
> > wrote:
> > > > > > >
> > > > > > > > From: Raihan Ahmed
> > > > > <[EMAIL PROTECTED]>
> > > > > > > > Subject: Questions
> regarding
> > > Axis1.4
> > > > > > > > To:
> [email protected]
> > > > > > > > Date: Sunday, June 29,
> 2008,
> > 6:00
> > > AM
> > > > > > > > Hello,
> > > > > > > > I am sorry to email in
> this
> > > manner.
> > > > But I
> > > > > have
> > > > > > run
> > > > > > > into an
> > > > > > > > issue that I just
> can't
> > figure
> > > out.
> > > > I
> > > > > have
> > > > > > > searched the
> > > > > > > > Internet without any
> luck.
> > > > > > > > I have a web service
> running
> > under
> > > > Axis1.4.
> > > > > One
> > > > > > of
> > > > > > > the
> > > > > > > > methods returns an array
> of
> > string
> > > to
> > > > the
> > > > > client.
> > > > > >
> > > > > > > Each
> > > > > > > > string in the array is
> > actually an
> > > XML
> > > > > document
> > > > > > with
> > > > > > > data
> > > > > > > > from database tables.
> And
> > each of
> > > > these XML
> > > > > > documents
> > > > > > > has
> > > > > > > > a node that has image
> data in
> > > Base64
> > > > string.
> > > > >
> > > > > > > > Now the problem is this
> -
> > > > > > > > Without the Base64, it
> works
> > fine.
> > > But
> > > > soon
> > > > > I
> > > > > > add the
> > > > > > > > base64 data in the node,
> I
> > get the
> > > > > SoapException
> > > > > > on
> > > > > > > the
> > > > > > > > server side. If I copy
> the
> > base64
> > > > string
> > > > > and
> > > > > > > hard-code it
> > > > > > > > in the response, it
> works.
> > But
> > > when
> > > > the
> > > > > base64
> > > > > > is
> > > > > > > > generated, it does not
> work.
> > > > > > > > I can't figure out
> the
> > reason
> > > -
> > > > base64
> > > > > is
> > > > > > simple
> > > > > > > ascii
> > > > > > > > characters. Why
> can't I
> > put a
> > > > string
> > > > > like
> > > > > > that in
> > > > > > > the
> > > > > > > > response?
> > > > > > > > I am desperate. Please
> help!
> > If
> > > I am
> > > > in
> > > > > the
> > > > > > wrong
> > > > > > > place,
> > > > > > > > please point to the
> right
> > people
> > > so
> > > > that I
> > > > > can
> > > > > > get an
> > > > > > > > answer.
> > > > > > > > Best Regards!
> > > > > > > > Raihan U. Ahmed
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> > > > > > >
> [EMAIL PROTECTED]
> > > > > > > > For additional commands,
> > e-mail:
> > > > > > > >
> [EMAIL PROTECTED]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail:
> > > > > > [EMAIL PROTECTED]
> > > > > > > For additional commands,
> e-mail:
> > > > > > > [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > > > > [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail:
> > > > > > [EMAIL PROTECTED]
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > [EMAIL PROTECTED]
> > > > > For additional commands, e-mail:
> > > > >
> > > >
> > >
> >
> [EMAIL PROTECTED]
> > > > To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > > For additional commands, e-mail:
> > > > [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > >
> >
> [EMAIL PROTECTED]
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
<wsdl:definitions targetNamespace="urn:RMSDataExchange">
-
<!--
WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)
-->
-
<wsdl:types>
-
<schema targetNamespace="urn:RMSDataExchange">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
-
<complexType name="ArrayOf_soapenc_string">
-
<complexContent>
-
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]"/>
</restriction>
</complexContent>
</complexType>
</schema>
</wsdl:types>
-
<wsdl:message name="getCitationResponse">
<wsdl:part name="getCitationReturn" type="impl:ArrayOf_soapenc_string"/>
</wsdl:message>
-
<wsdl:message name="getArrestBookingReportRequest">
<wsdl:part name="in0" type="soapenc:string"/>
<wsdl:part name="in1" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getArrestBookingReportResponse">
<wsdl:part name="getArrestBookingReportReturn"
type="impl:ArrayOf_soapenc_string"/>
</wsdl:message>
-
<wsdl:message name="getIncidentReportByStringResponse">
<wsdl:part name="getIncidentReportByStringReturn" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getJail24HrReportResponse">
<wsdl:part name="getJail24HrReportReturn" type="impl:ArrayOf_soapenc_string"/>
</wsdl:message>
-
<wsdl:message name="getCitationRequest">
<wsdl:part name="in0" type="soapenc:string"/>
<wsdl:part name="in1" type="soapenc:string"/>
</wsdl:message>
<wsdl:message name="getJailListReportRequest">
</wsdl:message>
-
<wsdl:message name="putArrestWarrantResponse">
<wsdl:part name="putArrestWarrantReturn" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getNewlyServedWarrantsResponse">
<wsdl:part name="getNewlyServedWarrantsReturn"
type="impl:ArrayOf_soapenc_string"/>
</wsdl:message>
-
<wsdl:message name="recallWarrantResponse">
<wsdl:part name="recallWarrantReturn" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getNewlyServedWarrantsRequest">
<wsdl:part name="date" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="recallWarrantRequest">
<wsdl:part name="warrantNumber" type="soapenc:string"/>
<wsdl:part name="recallDate" type="soapenc:string"/>
<wsdl:part name="recallReason" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getIncidentReportByStringRequest">
<wsdl:part name="incidentID" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="getJailListReportResponse">
<wsdl:part name="getJailListReportReturn" type="impl:ArrayOf_soapenc_string"/>
</wsdl:message>
-
<wsdl:message name="getJail24HrReportRequest">
<wsdl:part name="date" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:message name="putArrestWarrantRequest">
<wsdl:part name="warrantXML" type="soapenc:string"/>
</wsdl:message>
-
<wsdl:portType name="GuruWebServiceImp">
-
<wsdl:operation name="getIncidentReportByString"
parameterOrder="incidentID">
<wsdl:input message="impl:getIncidentReportByStringRequest"
name="getIncidentReportByStringRequest"/>
<wsdl:output message="impl:getIncidentReportByStringResponse"
name="getIncidentReportByStringResponse"/>
</wsdl:operation>
-
<wsdl:operation name="putArrestWarrant" parameterOrder="warrantXML">
<wsdl:input message="impl:putArrestWarrantRequest"
name="putArrestWarrantRequest"/>
<wsdl:output message="impl:putArrestWarrantResponse"
name="putArrestWarrantResponse"/>
</wsdl:operation>
-
<wsdl:operation name="getNewlyServedWarrants" parameterOrder="date">
<wsdl:input message="impl:getNewlyServedWarrantsRequest"
name="getNewlyServedWarrantsRequest"/>
<wsdl:output message="impl:getNewlyServedWarrantsResponse"
name="getNewlyServedWarrantsResponse"/>
</wsdl:operation>
-
<wsdl:operation name="recallWarrant" parameterOrder="warrantNumber
recallDate recallReason">
<wsdl:input message="impl:recallWarrantRequest" name="recallWarrantRequest"/>
<wsdl:output message="impl:recallWarrantResponse" name="recallWarrantResponse"/>
</wsdl:operation>
-
<wsdl:operation name="getJailListReport">
<wsdl:input message="impl:getJailListReportRequest"
name="getJailListReportRequest"/>
<wsdl:output message="impl:getJailListReportResponse"
name="getJailListReportResponse"/>
</wsdl:operation>
-
<wsdl:operation name="getJail24HrReport" parameterOrder="date">
<wsdl:input message="impl:getJail24HrReportRequest"
name="getJail24HrReportRequest"/>
<wsdl:output message="impl:getJail24HrReportResponse"
name="getJail24HrReportResponse"/>
</wsdl:operation>
-
<wsdl:operation name="getArrestBookingReport" parameterOrder="in0 in1">
<wsdl:input message="impl:getArrestBookingReportRequest"
name="getArrestBookingReportRequest"/>
<wsdl:output message="impl:getArrestBookingReportResponse"
name="getArrestBookingReportResponse"/>
</wsdl:operation>
-
<wsdl:operation name="getCitation" parameterOrder="in0 in1">
<wsdl:input message="impl:getCitationRequest" name="getCitationRequest"/>
<wsdl:output message="impl:getCitationResponse" name="getCitationResponse"/>
</wsdl:operation>
</wsdl:portType>
-
<wsdl:binding name="RMSDataExchangeSoapBinding"
type="impl:GuruWebServiceImp">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
-
<wsdl:operation name="getIncidentReportByString">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getIncidentReportByStringRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getIncidentReportByStringResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="putArrestWarrant">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="putArrestWarrantRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="putArrestWarrantResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="getNewlyServedWarrants">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getNewlyServedWarrantsRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getNewlyServedWarrantsResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="recallWarrant">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="recallWarrantRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="recallWarrantResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="getJailListReport">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getJailListReportRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getJailListReportResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="getJail24HrReport">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getJail24HrReportRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getJail24HrReportResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="getArrestBookingReport">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getArrestBookingReportRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getArrestBookingReportResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
-
<wsdl:operation name="getCitation">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getCitationRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:input>
-
<wsdl:output name="getCitationResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:RMSDataExchange" use="encoded"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
-
<wsdl:service name="GuruWebServiceImpService">
-
<wsdl:port binding="impl:RMSDataExchangeSoapBinding"
name="RMSDataExchange">
<wsdlsoap:address
location="http://172.16.1.180:8080/axis/services/RMSDataExchange"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
