> -----Original Message----- > From: Andrew Morrison [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 25, 2006 1:54 AM > To: [email protected]; [EMAIL PROTECTED] > Subject: RE: WSDD reference or examples > > > Thanks Derek, it looks like this is something quite a few > people would like to see. Would anyone have an opinion on the > following? > > It is my understanding that for message style there is little > point in including a schema within the WSDL as there is no > direct way to use this schema for validation. I have read > many articles describing the great advantages of being able > to share valid XML documents using document literal/wrapped > web services. However, it is difficult to find any concrete > examples where this is actually being done. Essentially, both > the client and the service would require a separate copy of > the schema elsewhere to use with a third party XML API. > > Thanks, > Andy.
What's supposed to happen is: The person implementing the server generates WSDL, along with any associated referenced schema documents. The person implementing the server runs WSDL2Java to generate Java server code implementing the objects described in the schema, and uses thes for his/her web service. The person deploying the server makes sure that the WSDL and schemas are available to anyone who can download them from a URL associated with the service. A person who wants to build a client downloads the WSDL and the schema documents. He/she then runs WSDL2Java to generate Java client code, and then uses the generated code to build a web service. So, the schemas are not useless just because Axis2 doesn't use them for validation. They do at least document the interface that a WSDL2Java-like tool (Axis2's or some other project's) can use to generate both client and server generation/parsing code. How much validation is done by the generated code is up to the tool. Axis2 currently does very little validation (unfortunately). Other tools might do more. Still, using tools like these is a great deal easier and less error-prone than writing the parsers and generators by hand and manually trying to keep them up to date as the schema changes. Derek > > > -----Original Message----- > From: Derek [mailto:[EMAIL PROTECTED] > Sent: 24 July 2006 19:22 > To: [email protected] > Subject: RE: WSDD reference or examples > > Andrew: > > You might want to search the mailing list archives for the > thread titled "Schema Validation", which went over this > subject in a bit more depth. At the moment there's still no > easy solution. > > Derek > > > -----Original Message----- > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 24, 2006 7:38 AM > > To: [email protected] > > Subject: Re: WSDD reference or examples > > > > > > That's correct. Axis does not validate messages. If you use a > > databinding framework, then the framework will perform > > rudimentary validation -- basically because it is expecting > > the message to conform to a known structure so that it can > convert it. > > > > Anne > > > > On 7/24/06, Andrew Morrison <[EMAIL PROTECTED]> wrote: > > > Will do. Regarding my other question, am I right to assume > > that schema > > > validation of the messages is not provided by Axis and would still > > > have to be done within the web service implementation class? > > > > > > -----Original Message----- > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > Sent: 24 July 2006 14:31 > > > To: [email protected] > > > Subject: Re: WSDD reference or examples > > > > > > That sounds like a bug. File a JIRA please. > > > > > > On 7/24/06, Andrew Morrison <[EMAIL PROTECTED]> wrote: > > > > Thanks for the help Anne. > > > > > > > > Yes, I am using message style and I want both the input > > and output > > > > to > > > be > > > > the eligibility type specified by the schema. I was defining the > > > > extra elements as I thought it was necessary to > > explicitly specify > > > > the type > > > of > > > > the input and output. It looks like I was complicating the WSDD > > > > unnecessarily, your suggestion seems to be the answer. > > > > > > > > The attached WSDL is now generated by Axis. It is > > interesting though > > > > that it generates the same element twice: <element > > > > name="eligibility" type="cns:eligibilityType"/> as > expected, but > > > > also <element name="eligibility" type="xsd:anyType"/>. Do > > you know > > > > if this is something I can disable? > > > > > > > > My intention was to specify the schema type on order to > force the > > > > SOAP body XML messages to be of a particular type through > > validation > > > > - but now I think this may not be possible with Axis. Am > > I right to > > > > assume that schema validation of the messages is not provided by > > > > Axis and > > > would > > > > still have to be done within the web service > implementation class? > > > > > > > > All the best, > > > > Andrew. > > > > > > > > -----Original Message----- > > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > > Sent: 21 July 2006 18:23 > > > > To: [email protected] > > > > Subject: Re: WSDD reference or examples > > > > > > > > So, help me understand -- you want both the input and > > output message > > > > to contain the eligibility element? And you're using > > Message style? > > > > Then why are you defining additional elements called > > > > "ProcessSOAPBody" and "ProcessSOAPBodyReturn"? > > > > > > > > I think you just want: > > > > > > > > <operation > > > > name="processSOAPBody" > > > > qname="curamns:eligibility" > > > > returnQName="curamns:elegibility" > > > > returnType="curamns:eligibilityType"> > > > > </operation> > > > > > > > > On 7/21/06, Andrew Morrison <[EMAIL PROTECTED]> wrote: > > > > > Here you go, sorry. > > > > > > > > > > I am doing this is because I am working on creating a > framework > > > > > that will allow users to create a web service by simply > > writing an > > > > interface > > > > > (and implementation class). I want to generate a wsdd > > dynamically > > > > which > > > > > can then be deployed to Axis. This process already > > works well for > > > RPC > > > > > and WRAPPED, and I want to enhance it with Message style. > > > > > > > > > > Thanks for taking an interest in my query, > > > > > Andy. > > > > > > > > > > -----Original Message----- > > > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > > > Sent: 21 July 2006 17:34 > > > > > To: [email protected] > > > > > Subject: Re: WSDD reference or examples > > > > > > > > > > Please attach the WSDD. (You included the schema > twice, but not > > > > > the > > > > > WSDD.) > > > > > > > > > > If you already have the Schema, why not just create the > > WSDL first > > > > > (rather than the WSDD)? > > > > > > > > > > Anne > > > > > > > > > > On 7/21/06, Andrew Morrison > <[EMAIL PROTECTED]> wrote: > > > > > > Hi Anne, > > > > > > > > > > > > Thanks for your replies - further investigation is making me > > > wonder > > > > if > > > > > > there is an issue with the runtime WSDL generation in > > Axis 1.4. > > > > > > > > > > > > I am working on a proof-of-concept for creating a > deploy.wsdd > > > where > > > > an > > > > > > XML Schema can be used to defined what XML is sent > within the > > > > > > <soap:body>. > > > > > > > > > > > > Looking at the WSDL generated by the Axis webapp running on > > > Tomcat, > > > > I > > > > > > think I am most of the way there. However, the WSDL > > describing > > > > > > the request element is not what I expected. The schema types > > > > > > include > > > > > > <element name="processSOAPBody" > > type="xsd:anyType"/> and > > > > > > the wsdl messages for the input is <wsdl:message > > > > > > name="processSOAPBodyRequest"> > > > > > > <wsdl:part element="impl:processSOAPBody" > > name="part"/> > > > > > > </wsdl:message> > > > > > > > > > > > > I would have expected these to be in the same format as the > > > entries > > > > > for > > > > > > the return > > > > > > <element name="processSOAPBodyInput" > > > > > > type="cns:eligibilityType"/> <wsdl:message > > name="processSOAPBodyRequest"> > > > > > > <wsdl:part element="impl:processSOAPBodyInput" > > > > > > name="processSOAPBodyInput"/> > > > > > > </wsdl:message> > > > > > > > > > > > > I have attached the wsdd and the schema it > references and the > > > > > generated > > > > > > WSDL in the hope you may have time to look over this. Any > > > > suggestions > > > > > or > > > > > > comments would be extremely appreciated. > > > > > > > > > > > > Thanks, > > > > > > Andy. > > > > > > > > > > > > -----Original Message----- > > > > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > > > > Sent: 21 July 2006 16:03 > > > > > > To: [email protected] > > > > > > Subject: Re: WSDD reference or examples > > > > > > > > > > > > @qname refers to the name of the element which is the > > child of > > > > > > the <soap:Body>. @type refers to the type of that element. > > > > > > > > > > > > The type corresponds to the typemapping. > > > > > > > > > > > > Anne > > > > > > > > > > > > On 7/21/06, Ben Reif <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > Anne, > > > > > > > > > > > > > > I'm confused. The reference link you included says that > > > attribute > > > > > > > > > > > > > > qname - Qualified name of the XML element containing the > > > parameter > > > > > > value in > > > > > > > a SOAP message > > > > > > > type - Qualified name of the parameter type > > > > > > > > > > > > > > So, is the reference page incorrect? Should the > > type attribute > > > in > > > > > the > > > > > > > <parameter> be the qualified type in the SOAP > > request/response > > > and > > > > > the > > > > > > qname > > > > > > > attribute be the same qname that matches the qname > > attribute > > > > > > > of > > > > the > > > > > > > <typeMapping> defined to serialize/deserialize the object? > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Ben > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 7/21/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > > > > > > http://www.oio.de/axis-wsdd/parameter-operation.htm > > > > > > > > > > > > > > > > The @type specifies the XML type of the request. > > > > > > > > > > > > > > > > Anne > > > > > > > > > > > > > > > > On 7/21/06, Andrew Morrison > <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > I've been looking at that WSDD reference but I > > can't find > > > > > > > > > a > > > > way > > > > > to > > > > > > > > > specify the XML type of the <soap:body> request. > > > > > > > > > > > > > > > > > > I want to specify a schema in the generated > > WSDL and then > > > > state > > > > > > the XML > > > > > > > > > in the soap body request/response to be of that schema > > > > > > > > > type. > > > > Is > > > > > > this > > > > > > > > > possible? > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Andrew > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > > > > > > > Sent: 20 July 2006 22:48 > > > > > > > > > To: [email protected] > > > > > > > > > Subject: Re: WSDD reference or examples > > > > > > > > > > > > > > > > > > See http://www.oio.de/axis-wsdd/ > > > > > > > > > > > > > > > > > > > > > > > > > > > On 7/20/06, Andrew Morrison > > <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, but I am looking for something a bit more > > > detailed. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I am able to create working Message style > web services > > > from > > > > a > > > > > > WSDD, > > > > > > > > > but I > > > > > > > > > > would like to specify a schema in the > > generated WSDL to > > > > state > > > > > > the type > > > > > > > > > of > > > > > > > > > > the XML in the soap body. Has anyone done this? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I want to: > > > > > > > > > > > > > > > > > > > > 1. Include a schema in the generated WSDL - > > this can be > > > > > achieved > > > > > > > > > using: > > > > > > > > > > > > > > > > > > > > <parameter name="wsdlInputSchema" > > > > > > > > > > > > > > > > > > > value="http://localhost:8080/axis/schemas/eligibility_noxs.xsd > > > > > > > "/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Specify that the request message should > contain an > > > > > > > > > > XML > > > > > > message that > > > > > > > > > can > > > > > > > > > > also be validated against the same schema - > > does anyone > > > know > > > > > if > > > > > > this > > > > > > > > > is > > > > > > > > > > possible, or have an example of how to > > specify this in > > > > > > > > > > the > > > > > WSDD? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 3. Specify the response will be of a type defined by > > > > > > > > > > that > > > > > schema > > > > > > - I > > > > > > > > > think > > > > > > > > > > this can be achieved with: > > > > > > > > > > > > > > > > > > > > <operation > > > > > > > > > > > > > > > > > > > > > > > > > > > name="processSOAPBody" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > qname="myns:processSOAPBody" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > returnQName="myns:processSOAPBodyReturn" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > returnType="myns:eligibility"> > > > > > > > > > > > > > > > > > > > > </operation> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > My complete WSDD so far is below - if anyone > > can suggest > > > any > > > > > > > > > references or > > > > > > > > > > examples they would be appreciated. > > > > > > > > > > > > > > > > > > > > BTW: this site is useful but not complete: > > > > > > > > > > http://www.oio.de/axis-wsdd/deployment.htm > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > > > > Andrew. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <deployment name="MyWebService" > > > > > > > > > > xmlns="http://xml.apache.org/axis/wsdd/ " > > > > > > > > > > > > > > > > > xmlns:java=http://xml.apache.org/axis/wsdd/providers/java > > > > > > > > > > xmlns:xsi=" > > > > > > > http://www.w3.org/2000/10/XMLSchema-instance";> > > > > > > > > > > > > > > > > > > > > <service name="MyMessageService1" > > > > > > > > > > > > > > > > > > > > provider="java:MSG" > > > > > > > > > > > > > > > > > > > > style="message" > > > > > > > > > > > > > > > > > > > > use="literal" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > xmlns:curamns=" > > > > > > > http://localhost:8080/axis/services/MyMessageService1Name > > > > > > > > > space"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <namespace> > > > > > > > > > http://localhost:8080/axis/services/MyMessageService1Namespac > > > > > > > > > e</namespace> > > > > > > > > > > > > > > > > > > > > <parameter name="className" > > > > > > > > > > value="my.messagestyle.service.MyMessageService " /> > > > > > > > > > > > > > > > > > > > > <parameter > > name="allowedMethods" > > > > > > > > > > value="processSOAPBody" /> > > > > > > > > > > > > > > > > > > > > <parameter > > > > > > > > > > name="wsdlInputSchema" > > > > > > > > > > > > > > > > > > > > value="http://localhost:8080/axis/schemas/eligibility_noxs.xsd"/> > > > > > > > > > > > > > > > > > > > > <parameter > > > > name="wsdlTargetNamespace" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > value="http://localhost:8080/axis/services/MyMessageService1Namespace"; > > > /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <operation > > > > > > > > > > > > > > > > > > > > > > > > > > > name="processSOAPBody" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > qname="myns:processSOAPBody" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > returnQName="myns:processSOAPBodyReturn" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > returnType="myns:eligibility"> > > > > > > > > > > > > > > > > > > > > </operation> > > > > > > > > > > > > > > > > > > > > </service> > > > > > > > > > > > > > > > > > > > > </deployment> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: Ted Jones [mailto:[EMAIL PROTECTED] ] > > > > > > > > > > Sent: 20 July 2006 16:49 > > > > > > > > > > To: [email protected]; Andrew Morrison > > > > > > > > > > Subject: RE: WSDD reference or examples > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Here is an example of wsdd for what you describe: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <deployment name="test" > > > > > > > > > > xmlns=" http://xml.apache.org/axis/wsdd/"; > > > > > > > > > > > > > > > > > > > > > > > > > > > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; > > > > > > > > > > > > > > > > > > > > xmlns:xsi=" > > > > > > > http://www.w3.org/2000/10/XMLSchema-instance";> > > > > > > > > > > <!-- note that either style="message" OR > > > > > provider="java:MSG" > > > > > > both > > > > > > > > > work > > > > > > > > > > --> > > > > > > > > > > <service name="serviceName" provider="java:MSG"> > > > > > > > > > > <parameter name="className" > > > > > > value="com.test.service.MyWebService > > > > > > > " > > > > > > > > > /> > > > > > > > > > > <parameter name="allowedMethods" > > > > > > > > > > value="MyMethodName" > > > > /> > > > > > > > > > > </service> > > > > > > > > > > </deployment> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: Andrew Morrison [mailto: > > > [EMAIL PROTECTED] > > > > > > > > > > Sent: Thursday, July 20, 2006 7:11 AM > > > > > > > > > > To: [email protected] > > > > > > > > > > Subject: WSDD reference or examples > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Can anyone point me to a reference for creating a > > > > > > > > > > *.wsdd? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I am trying to create a WSDD for a Message style web > > > > service. > > > > > > > > > > > > > > > > > > > > The intention is that the Axis generated WSDL will > > > > > > > > > > specify > > > a > > > > > > > > > user-defined > > > > > > > > > > XML schema (wsdlInputSchema) and assert that > > the input > > > > > > > > > > and > > > > > > output for > > > > > > > > > the > > > > > > > > > > web service should be an XML document as > > defined by the > > > > > schema. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If anyone knows where I could see an example > > that would > > > > > > > > > > be > > > > > great > > > > > > - I > > > > > > > > > am > > > > > > > > > > finding snippets of info on the web, but am having > > > > difficulty > > > > > > finding > > > > > > > > > a > > > > > > > > > > detailed listing of the options etc. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > All the best, > > > > > > > > > > > > > > > > > > > > Andrew. > > > > > > > > > > The information in this email is confidential > > and may be > > > > > legally > > > > > > > > > privileged. > > > > > > > > > > It is intended solely for the addressee. > > Access to this > > > > email > > > > > by > > > > > > > > > anyone else > > > > > > > > > > is unauthorized. If you are not the intended > > recipient, > > > any > > > > > > > > > disclosure, > > > > > > > > > > copying, distribution or any action taken or > > omitted to > > > > > > > > > > be > > > > > taken > > > > > > in > > > > > > > > > reliance > > > > > > > > > > on it, is prohibited and may be unlawful. If > > you are not > > > the > > > > > > intended > > > > > > > > > > addressee please contact the sender and > > dispose of this > > > > > e-mail. > > > > > > Thank > > > > > > > > > you. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The information in this email is confidential > > and may be > > > > > legally > > > > > > > > > privileged. > > > > > > > > > > It is intended solely for the addressee. > > Access to this > > > > email > > > > > by > > > > > > > > > anyone else > > > > > > > > > > is unauthorized. If you are not the intended > > recipient, > > > any > > > > > > > > > disclosure, > > > > > > > > > > copying, distribution or any action taken or > > omitted to > > > > > > > > > > be > > > > > taken > > > > > > in > > > > > > > > > reliance > > > > > > > > > > on it, is prohibited and may be unlawful. If > > you are not > > > the > > > > > > intended > > > > > > > > > > addressee please contact the sender and > > dispose of this > > > > > e-mail. > > > > > > Thank > > > > > > > > > you. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: > > > > > > > [EMAIL PROTECTED] > > > > > > > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > The information in this email is confidential > and may be > > > > legally > > > > > > > privileged. > > > > > > > > > It is intended solely for the addressee. > Access to this > > > email > > > > by > > > > > > anyone > > > > > > > else > > > > > > > > > is unauthorized. If you are not the intended > recipient, > > > > > > > > > any > > > > > > disclosure, > > > > > > > > > copying, distribution or any action taken or > > omitted to be > > > > taken > > > > > > in > > > > > > > reliance > > > > > > > > > on it, is prohibited and may be unlawful. If > > you are not > > > > > > > > > the > > > > > > intended > > > > > > > > > addressee please contact the sender and > dispose of this > > > > e-mail. > > > > > > Thank > > > > > > > you. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > 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] > > > > > > > > > > > > > > > > > > The information in this email is confidential and may > > be legally > > > > > privileged. > > > > > > It is intended solely for the addressee. Access to > > this email by > > > > > anyone else > > > > > > is unauthorized. If you are not the intended recipient, any > > > > > disclosure, > > > > > > copying, distribution or any action taken or omitted > > to be taken > > > in > > > > > reliance > > > > > > on it, is prohibited and may be unlawful. If you are not the > > > > intended > > > > > > addressee please contact the sender and dispose of > > this e-mail. > > > > Thank > > > > > you. > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > - > > > > > > 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] > > > > > > > > > > > > > > > The information in this email is confidential and may > be legally > > > > privileged. > > > > > It is intended solely for the addressee. Access to > this email by > > > > anyone else > > > > > is unauthorized. If you are not the intended recipient, any > > > > disclosure, > > > > > copying, distribution or any action taken or omitted to > > be taken > > > > > in > > > > reliance > > > > > on it, is prohibited and may be unlawful. If you are not the > > > intended > > > > > addressee please contact the sender and dispose of > this e-mail. > > > Thank > > > > you. > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > > > The information in this email is confidential and may be legally > > > privileged. > > > > It is intended solely for the addressee. Access to this email by > > > anyone else > > > > is unauthorized. If you are not the intended recipient, any > > > disclosure, > > > > copying, distribution or any action taken or omitted to > > be taken in > > > reliance > > > > on it, is prohibited and may be unlawful. If you are not the > > > > intended addressee please contact the sender and > dispose of this > > > > e-mail. Thank > > > you. > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > - > > > > 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] > > > > > > > > > The information in this email is confidential and may be legally > > > privileged. It is intended solely for the addressee. > Access to this > > > email by anyone else is unauthorized. If you are not the intended > > > recipient, any disclosure, copying, distribution or any > > action taken > > > or omitted to be taken in reliance on it, is prohibited and may be > > > unlawful. If you are not the intended addressee please > contact the > > > sender and dispose of this e-mail. Thank you. > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > The information in this email is confidential and may be > legally privileged. It is intended solely for the addressee. > Access to this email by anyone else is unauthorized. If you > are not the intended recipient, any disclosure, copying, > distribution or any action taken or omitted to be taken in > reliance on it, is prohibited and may be unlawful. If you are > not the intended addressee please contact the sender and > dispose of this e-mail. Thank you. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
