You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sa...@us.hsbc.Com on 2003/10/28 18:28:03 UTC
Re: adding an element (a field in a bean) in a webservice without changing
the stubs
Is it possible to pass javabeans as arguments from soap client to the soap
service without having to
code for custom serializers and de-serializers?
Thanks,
"Olivier Lamy" <LA...@accor-hotels.com> on 28 Oct 2003 12:14
Please respond to axis-user@ws.apache.org
To: "Axis-User" <ax...@ws.apache.org>
Subject: adding an element (a field in a bean) in a webservice without
changing the stubs
****************************************************************************
This message originated from the Internet. Its originator may or
may not be who they claim to be and the information contained in
the message and any attachments may or may not be accurate.
****************************************************************************
Hello,
I have a webservices in a version.
In the next version, I want to add a field in bean which add an element in
the soap.
If I don't generate again the stubs with the ant task, i get an exception :
[junit] org.xml.sax.SAXException: Invalid element in
com.accor.services.ws.cli
ent.data.geo.GeoResult - hotelsFound
[junit] at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(Bean
Deserializer.java:260)
[junit] at
org.apache.axis.encoding.DeserializationContextImpl.startElemen
t(DeserializationContextImpl.java:963)
[junit] at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecor
der.java:198)
I don't understand why ?
Because, the new field which was not in the scope of the first stubs, it
should be ignored.
But it doesn't had to generate an exception ?
**********************************************************************
This e-mail, any attachments and the information contained therein ("this
message") are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send it
back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part is
strictly prohibited.
Ce message electronique et tous les fichiers joints ainsi que les
information contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci
de le renvoyer a son emetteur et de le detruire. Toute diffusion,
publication, totale ou partielle ou divulgation sous quelque forme que se
soit non expressement autorisees de ce message, sont interdites.
**********************************************************************
(See attached file: winmail.dat)
************************************************************************
This E-mail is confidential. It may also be legally privileged. If you
are not the addressee you may not copy, forward, disclose or use any
part of it. If you have received this message in error, please delete
it and all copies from your system and notify the sender immediately
by return E-mail.
Internet communications cannot be guaranteed to be timely, secure,
error or virus-free. The sender does not accept liability for any
errors or omissions.
************************************************************************
Complex Types - BeanDeserialiser problem
Posted by Bhuvan Gupta <bh...@fiorano.com>.
Hi All,
I am trying to invoke a WebService which takes GetTradingCustomerProfile_IN
as an argument and GetTradingCustomerProfile_IN has a member variable of
Type ExternalCustomerId.
Both these classes are of type Java Beans and have specified TypeMappings
for both.
<typeMapping
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle="" qname="ns1:>GetTradingCustomerProfile_IN"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
type="java:corso.types.x_type.move.GetTradingCustomerProfile_IN"
xmlns:ns1="urn:x-type:move.corso:types"/>
<typeMapping
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle="" qname="ns2:ExternalCustomerId"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
type="java:corso.types.x_type.move.ExternalCustomerId"
xmlns:ns2="urn:x-type:move.corso:types"/>
But when I try to invoke the WebService I am encountering the following
exception :
(WSDL is attached)
Any help is appreciated.
Exception Trace:
=============
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Invalid element in
corso.types.x_type.move.GetTradingCustomerProfile_IN - CustomerExternalId
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
org.xml.sax.SAXException: Invalid element in
corso.types.x_type.move.GetTradingCustomerProfile_IN - CustomerExternalId
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.
java:252)
at
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deserializa
tionContextImpl.java:893)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:200)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
684)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:207)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:265)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:1
90)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:276)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:437)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:316)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:
335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:549)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:666)
at java.lang.Thread.run(Thread.java:479)
org.xml.sax.SAXException: Invalid element in
corso.types.x_type.move.GetTradingCustomerProfile_IN - CustomerExternalId
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
51)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:16
8)
at
org.apache.axis.encoding.DeserializationContextImpl.endElement(Deserializati
onContextImpl.java:1001)
at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1528)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
at
org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at
org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationCon
textImpl.java:242)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:375)
at org.apache.axis.client.Call.invokeEngine(Call.java:2545)
at org.apache.axis.client.Call.invoke(Call.java:2515)
at org.apache.axis.client.Call.invoke(Call.java:2210)
at org.apache.axis.client.Call.invoke(Call.java:2133)
at org.apache.axis.client.Call.invoke(Call.java:1656)
at
gtcp.movcorso.GtcpBindingStub.getTradingCustomerProfile(GtcpBindingStub.java
:236)
at
gtcp.movcorso.GtcpServiceTestCase.test1gtcpServicePortGetTradingCustomerProf
ile(GtcpServiceTestCase.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
com.borland.jbuilder.unittest.JBTestRunner.run(JBTestRunner.java:210)
at
com.borland.jbuilder.unittest.JBTestRunner.initiateTest(JBTestRunner.java:25
2)
at
com.borland.jbuilder.unittest.JBTestRunner.main(JBTestRunner.java:558)
Re: adding an element (a field in a bean) in a webservice without
changing the stubs
Posted by Mike Klein <mi...@sbcglobal.net>.
Actually it's wsdl2java that generates the correct wsdd files (with
mappings), etc.
The only code you should have to handroll in web services deployment (at
least for me so far...) is the underlying intf/impl that my soap service
is calling. You shouldn't need to handcode wsdl, wsdd, xsd, or do any
filling in of generated skeletons/impls. At least I don't based upon
what I'm doing.
Based upon some ant magic in my build scripts (plus wsdl2java/java2wsdl
ant tasks), my generated Skeleton is mated perfectly for calling into my
existing implementation code. My jar'g task in ant copies some relevant
.class files from my source tree, plus the Skeleton from generated path
and deploys using generated wsdd. I can also then of course use
additional java classes generated to do client-side testing of stubs,
junit, etc.
mike
Mike Klein wrote:
> This is done for you when you use java2wsdl...notice the typeMapping
> entry (really an exploded beanMapping).
>
>
> chris wrote:
>
>> Yes… you don’t have to write any code in order for Axis to pass
>> objects conforming to the Java beans convention.
>>
>> You do have to provide the serialization framework configuration
>> information; Specifically, the Java class, corresponding XML QName,
>> and appropriate serialization factory to use…..
>>
>> /Chris
>>
>> -----Original Message-----
>> *From:* Sabyasachi.Gupta@us.hsbc.Com
>> [mailto:Sabyasachi.Gupta@us.hsbc.Com] *On Behalf Of
>> *Sabyasachi.Gupta@us.hsbc.Com
>> *Sent:* Tuesday, October 28, 2003 12:28 PM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: adding an element (a field in a bean) in a webservice
>> without changing the stubs
>>
>> Is it possible to pass javabeans as arguments from soap client to the
>> soap
>> service without having to
>> code for custom serializers and de-serializers?
>> Thanks,
>>
>>
>>
>>
>>
>> "Olivier Lamy" on 28 Oct 2003 12:14
>>
>> Please respond to axis-user@ws.apache.org
>>
>>
>>
>> To: "Axis-User"
>> Subject: adding an element (a field in a bean) in a webservice without
>> changing the stubs
>>
>>
>> ****************************************************************************
>>
>>
>> This message originated from the Internet. Its originator may or
>> may not be who they claim to be and the information contained in
>> the message and any attachments may or may not be accurate.
>> ****************************************************************************
>>
>>
>> Hello,
>>
>> I have a webservices in a version.
>>
>> In the next version, I want to add a field in bean which add an
>> element in the soap.
>>
>> If I don't generate again the stubs with the ant task, i get an
>> exception :
>>
>> [junit] org.xml.sax.SAXException: Invalid element in
>> com.accor.services.ws.cli
>> ent.data.geo.GeoResult - hotelsFound
>> [junit] at
>> org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(Bean
>> Deserializer.java:260)
>> [junit] at
>> org.apache.axis.encoding.DeserializationContextImpl.startElemen
>> t(DeserializationContextImpl.java:963)
>> [junit] at
>> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecor
>> der.java:198)
>>
>> I don't understand why ?
>>
>> Because, the new field which was not in the scope of the first stubs,
>> it should be ignored.
>>
>> But it doesn't had to generate an exception ?
>>
>> This e-mail, any attachments and the information contained therein
>> ("this message") are confidential and intended solely for the use of
>> the addressee(s). If you have received this message in error please
>> send it back to the sender and delete it. Unauthorized publication,
>> use, dissemination or disclosure of this message, either in whole or
>> in part is strictly prohibited.
>>
>> **********************************************************************
>>
>> Ce message électronique et tous les fichiers joints ainsi que les
>> informations contenues dans ce message ( ci après "le message" ),
>> sont confidentiels et destinés exclusivement à l'usage de la personne
>> à laquelle ils sont adressés. Si vous avez reçu ce message par
>> erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes
>> diffusion, publication, totale ou partielle ou divulgation sous
>> quelque forme que se soit non expressément autorisées de ce message,
>> sont interdites.
>>
>> **********************************************************************
>>
>> **********************************************************************
>> This e-mail, any attachments and the information contained therein
>> ("this
>> message") are confidential and intended solely for the use of the
>> addressee(s). If you have received this message in error please send it
>> back to the sender and delete it. Unauthorized publication, use,
>> dissemination or disclosure of this message, either in whole or in
>> part is
>> strictly prohibited.
>>
>> Ce message electronique et tous les fichiers joints ainsi que les
>> information contenues dans ce message ( ci apres "le message" ), sont
>> confidentiels et destines exclusivement a l'usage de la personne a
>> laquelle ils sont adresses. Si vous avez recu ce message par erreur,
>> merci
>> de le renvoyer a son emetteur et de le detruire. Toute diffusion,
>> publication, totale ou partielle ou divulgation sous quelque forme
>> que se
>> soit non expressement autorisees de ce message, sont interdites.
>> **********************************************************************
>>
>>
>> (See attached file: winmail.dat)
>>
>>
>>
>>
>>
>>
>>
>> ************************************************************************
>> This E-mail is confidential. It may also be legally privileged. If you
>> are not the addressee you may not copy, forward, disclose or use any
>> part of it. If you have received this message in error, please delete
>> it and all copies from your system and notify the sender immediately
>> by return E-mail.
>>
>> Internet communications cannot be guaranteed to be timely, secure,
>> error or virus-free. The sender does not accept liability for any
>> errors or omissions.
>> ************************************************************************
>>
>
>
>
Re: adding an element (a field in a bean) in a webservice without
changing the stubs
Posted by Mike Klein <mi...@sbcglobal.net>.
This is done for you when you use java2wsdl...notice the typeMapping
entry (really an exploded beanMapping).
chris wrote:
> Yes… you don’t have to write any code in order for Axis to pass
> objects conforming to the Java beans convention.
>
> You do have to provide the serialization framework configuration
> information; Specifically, the Java class, corresponding XML QName,
> and appropriate serialization factory to use…..
>
> /Chris
>
> -----Original Message-----
> *From:* Sabyasachi.Gupta@us.hsbc.Com
> [mailto:Sabyasachi.Gupta@us.hsbc.Com] *On Behalf Of
> *Sabyasachi.Gupta@us.hsbc.Com
> *Sent:* Tuesday, October 28, 2003 12:28 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: adding an element (a field in a bean) in a webservice
> without changing the stubs
>
> Is it possible to pass javabeans as arguments from soap client to the soap
> service without having to
> code for custom serializers and de-serializers?
> Thanks,
>
>
>
>
>
> "Olivier Lamy" on 28 Oct 2003 12:14
>
> Please respond to axis-user@ws.apache.org
>
>
>
> To: "Axis-User"
> Subject: adding an element (a field in a bean) in a webservice without
> changing the stubs
>
>
> ****************************************************************************
>
> This message originated from the Internet. Its originator may or
> may not be who they claim to be and the information contained in
> the message and any attachments may or may not be accurate.
> ****************************************************************************
>
> Hello,
>
> I have a webservices in a version.
>
> In the next version, I want to add a field in bean which add an
> element in the soap.
>
> If I don't generate again the stubs with the ant task, i get an
> exception :
>
> [junit] org.xml.sax.SAXException: Invalid element in
> com.accor.services.ws.cli
> ent.data.geo.GeoResult - hotelsFound
> [junit] at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(Bean
> Deserializer.java:260)
> [junit] at org.apache.axis.encoding.DeserializationContextImpl.startElemen
> t(DeserializationContextImpl.java:963)
> [junit] at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecor
> der.java:198)
>
> I don't understand why ?
>
> Because, the new field which was not in the scope of the first stubs,
> it should be ignored.
>
> But it doesn't had to generate an exception ?
>
> This e-mail, any attachments and the information contained therein
> ("this message") are confidential and intended solely for the use of
> the addressee(s). If you have received this message in error please
> send it back to the sender and delete it. Unauthorized publication,
> use, dissemination or disclosure of this message, either in whole or
> in part is strictly prohibited.
>
> **********************************************************************
>
> Ce message électronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci après "le message" ), sont
> confidentiels et destinés exclusivement à l'usage de la personne à
> laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
> merci de le renvoyer à son émetteur et de le détruire. Toutes
> diffusion, publication, totale ou partielle ou divulgation sous
> quelque forme que se soit non expressément autorisées de ce message,
> sont interdites.
>
> **********************************************************************
>
> **********************************************************************
> This e-mail, any attachments and the information contained therein ("this
> message") are confidential and intended solely for the use of the
> addressee(s). If you have received this message in error please send it
> back to the sender and delete it. Unauthorized publication, use,
> dissemination or disclosure of this message, either in whole or in part is
> strictly prohibited.
>
> Ce message electronique et tous les fichiers joints ainsi que les
> information contenues dans ce message ( ci apres "le message" ), sont
> confidentiels et destines exclusivement a l'usage de la personne a
> laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci
> de le renvoyer a son emetteur et de le detruire. Toute diffusion,
> publication, totale ou partielle ou divulgation sous quelque forme que se
> soit non expressement autorisees de ce message, sont interdites.
> **********************************************************************
>
>
> (See attached file: winmail.dat)
>
>
>
>
>
>
>
> ************************************************************************
> This E-mail is confidential. It may also be legally privileged. If you
> are not the addressee you may not copy, forward, disclose or use any
> part of it. If you have received this message in error, please delete
> it and all copies from your system and notify the sender immediately
> by return E-mail.
>
> Internet communications cannot be guaranteed to be timely, secure,
> error or virus-free. The sender does not accept liability for any
> errors or omissions.
> ************************************************************************
>
RE: adding an element (a field in a bean) in a webservice without changing the stubs
Posted by chris <ch...@cobia.net>.
Yes
you dont have to write any code in order for Axis to pass objects
conforming to the Java beans convention.
You do have to provide the serialization framework configuration
information; Specifically, the Java class, corresponding XML QName, and
appropriate serialization factory to use
..
/Chris
-----Original Message-----
From: Sabyasachi.Gupta@us.hsbc.Com [mailto:Sabyasachi.Gupta@us.hsbc.Com]
On Behalf Of Sabyasachi.Gupta@us.hsbc.Com
Sent: Tuesday, October 28, 2003 12:28 PM
To: axis-user@ws.apache.org
Subject: Re: adding an element (a field in a bean) in a webservice
without changing the stubs
Is it possible to pass javabeans as arguments from soap client to the
soap
service without having to
code for custom serializers and de-serializers?
Thanks,
"Olivier Lamy" on 28 Oct 2003 12:14
Please respond to axis-user@ws.apache.org
To: "Axis-User"
Subject: adding an element (a field in a bean) in a webservice without
changing the stubs
************************************************************************
****
This message originated from the Internet. Its originator may or
may not be who they claim to be and the information contained in
the message and any attachments may or may not be accurate.
************************************************************************
****
Hello,
I have a webservices in a version.
In the next version, I want to add a field in bean which add an element
in the soap.
If I don't generate again the stubs with the ant task, i get an
exception :
[junit] org.xml.sax.SAXException: Invalid element in
com.accor.services.ws.cli
ent.data.geo.GeoResult - hotelsFound
[junit] at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(Bean
Deserializer.java:260)
[junit] at
org.apache.axis.encoding.DeserializationContextImpl.startElemen
t(DeserializationContextImpl.java:963)
[junit] at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecor
der.java:198)
I don't understand why ?
Because, the new field which was not in the scope of the first stubs, it
should be ignored.
But it doesn't had to generate an exception ?
This e-mail, any attachments and the information contained therein
("this message") are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send it
back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
**********************************************************************
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après "le message" ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion,
publication, totale ou partielle ou divulgation sous quelque forme que
se soit non expressément autorisées de ce message, sont interdites.
**********************************************************************
**********************************************************************
This e-mail, any attachments and the information contained therein
("this
message") are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send it
back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is
strictly prohibited.
Ce message electronique et tous les fichiers joints ainsi que les
information contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci
de le renvoyer a son emetteur et de le detruire. Toute diffusion,
publication, totale ou partielle ou divulgation sous quelque forme que
se
soit non expressement autorisees de ce message, sont interdites.
**********************************************************************
(See attached file: winmail.dat)
************************************************************************
This E-mail is confidential. It may also be legally privileged. If you
are not the addressee you may not copy, forward, disclose or use any
part of it. If you have received this message in error, please delete
it and all copies from your system and notify the sender immediately
by return E-mail.
Internet communications cannot be guaranteed to be timely, secure,
error or virus-free. The sender does not accept liability for any
errors or omissions.
************************************************************************