hi,
here it goes,
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="
http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:tns="http://xx.com/"; xmlns:s="http://www.w3.org/2001/XMLSchema";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace="
http://xx.com/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://xx.com/
">
<s:complexType name="ArrayOfReturnVo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="ReturnVo"
nillable="true" type="tns:ReturnVo" />
</s:sequence>
</s:complexType>
<s:complexType name="ReturnVo">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Message"
type="s:string" />
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfString">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="string"
nillable="true" type="s:string" />
</s:sequence>
</s:complexType>
<s:element name="SetCompanies">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SubType"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="SetCompaniesResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SetCompaniesResult"
type="tns:ArrayOfReturnVo" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="SetCompaniesSoapIn">
<wsdl:part name="parameters" element="tns:SetCompanies" />
</wsdl:message>
<wsdl:message name="SetCompaniesSoapOut">
<wsdl:part name="parameters" element="tns:SetCompaniesResponse" />
</wsdl:message>
<wsdl:portType name="Srv1Soap">
<wsdl:operation name="SetCompanies">
<wsdl:input message="tns:SetCompaniesSoapIn" />
<wsdl:output message="tns:SetCompaniesSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="Srv1Soap" type="tns:Srv1Soap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"; />
<wsdl:operation name="SetCompanies">
<soap:operation soapAction="http://xx.com/SetCompanies";
style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="Srv1Soap12" type="tns:Srv1Soap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http"; />
<wsdl:operation name="SetCompanies">
<soap12:operation soapAction="http://xx.com/SetCompanies";
style="document" />
<wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="Srv1">
<wsdl:port name="Srv1Soap" binding="tns:Srv1Soap">
<soap:address location="http://localhost:8090/Srv1.asmx"; />
</wsdl:port>
<wsdl:port name="Srv1Soap12" binding="tns:Srv1Soap12">
<soap12:address location="http://localhost:8090/Srv1.asmx"; />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
On Sun, May 31, 2009 at 12:21 AM, Martin Gainty <[email protected]> wrote:
> hi greg-
>
> can you post or attach the wsdl (and xsd)
>
> thanks
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci
> est interdite. Ce message sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>
> ------------------------------
> Date: Sat, 30 May 2009 18:31:29 +0100
> Subject: Re: Passing parameters from a calling client to registered request
> handler- can I use headers for this purpose?
>
> From: [email protected]
> To: [email protected]
>
> hi,
> thanks for your reply but I still see some problems
>
> 1) if I understand correctly WSDDHandler API let me set parameters
> declaratively in server-config.wsdd or client-config.wsdd files.
> Unfortunately I don't know what my parameters' values should be during
> deployment, there is some business logic involved in calculating my
> parameters hence the values for my parameters are available only as a
> runtime values. Perhaps I could create my own implementation of this class
> but I suspect that I'd have to do a lot of changes to AXIS engine itself in
> order to use it. What's more I would have to further customize my generated
> stubs in order to pass my parameters' values to a new handler. All I want to
> do is pass some parameter along with it's value from a stub to some
> registered axis handler. And what's your opinion about putting additional
> header's to my soap envelope (e.g ... myParam=log2 )? Is it safe and more
> importantly could it break server implementation of the WebService ? (e.g.
> incorrect SOAP envelope e.t.c)
>
>
> 2) I like the idea with optional parameter as an array but again I'm only a
> client of some WS. As such, WSDL file I got is pretty closed (I can't do any
> changes to it as it would probably cause problems on the server side).
>
>
> I've already read Axis Architecture Guide but couldn't find any solution to
> my problem
>
>
>
>
> On Sat, May 30, 2009 at 4:57 PM, Martin Gainty <[email protected]>wrote:
>
> http://ws.apache.org/axis/java/architecture-guide.html
> allows you to conceptualise the use of Handlers for communicating from your
> client to service and bacl
>
> if you want to store the information DB is always your safest and most
> reliable option
>
> concerning optional params take a look at this example which defined
> stringElement as optional with minOccurs="0"
> <xsd:complexType name="ArrayOfString">
> <xsd:complexContent>
> <xsd:restriction base="soap-enc:Array">
> <xsd:sequence>
> <xsd:element name="stringElement" type="xsd:string" minOccurs="0"
> maxOccurs="unbounded"/>
> </xsd:sequence>
>
>
> http://ws.apache.org/axis/java/apiDocs/org/apache/axis/deployment/wsdd/WSDDHandler.html
> where parameters can be read collectively via getParametersTable (into
> HashTable)
> or individually via getParameter
>
> java.lang.String
> *getParameter<http://ws.apache.org/axis/java/apiDocs/org/apache/axis/deployment/wsdd/WSDDDeployableItem.html#getParameter%28java.lang.String%29>
> *(java.lang.String name)
> Get the value of one of our parameters
> LockableHashtable<http://ws.apache.org/axis/java/apiDocs/org/apache/axis/utils/LockableHashtable.html>
> *getParametersTable<http://ws.apache.org/axis/java/apiDocs/org/apache/axis/deployment/wsdd/WSDDDeployableItem.html#getParametersTable%28%29>
> *()
> Returns the config parameters as a hashtable (lockable)
> hth
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci
> est interdite. Ce message sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>
> ------------------------------
> Date: Sat, 30 May 2009 15:20:45 +0100
> Subject: Passing parameters from a calling client to registered request
> handler- can I use headers for this purpose?
> From: [email protected]
> To: [email protected]
>
>
> hi,
>
> Are there any good patterns on how to pass parameters from a client to
> request handlers? Can I use for this purpose headers ? I thought about
> putting some additional header with call specific parameters I would read in
> my registered request handler but I'm not sure what impact will it
> (additional headers) have on the actual WebService (will it recognize such
> request as a valid XML document/request).
>
> My original problem is that once I do a call to the WS I need to log SOAP
> message (as a text) in some location (this location is per call specific so
> I can't use one folder). I use request handler registered in my
> client-config.wsdd file and it works fine but recognizing location. Probably
> I could use for this purpose database with three columns: 1) OperationName,
> 2) ServiceName, 3) location or even static class with some hashmap. The
> problems I see here are that in the first case my logger will slow down WS
> calls significantly as it will have to go to database and in case of static
> class.. they're always a problem while testing.
>
> I'd appreciate any suggestion how could I improve this.
>
>
> Environment
> Axis 1.4
>
> --
> Greg Stasica
>
> ------------------------------
> Hotmail® has a new way to see what's up with your friends. Check it
> out.<http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009>
>
>
>
>
> --
> Greg Stasica
>
> ------------------------------
> Hotmail® has a new way to see what's up with your friends. Check it
> out.<http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009>
>
--
Greg Stasica
