Hi

it depends how you build your client (injected, manually created from the
wsdl etc...). Also depends which kind of webservice it is and the
configuration you use.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-11-15 16:22 GMT+01:00 Piercarlo Alberto Beghetto - Diennea <
[email protected]>:

> Hi!
>
> I got a strange issue. It doesn't happen on Tomcat (java 7 or 8)
> applications.
> I tested on TomEE 1.7.4 and 7.0.2 with java 8.
> In previous version (< 1.6) of TomEE seems ok.
>
> When a WSDL of a webservice, i connect to, changes in a ComplexType (for
> example a field is added to a class mapped in the WSDL), the client can't
> start properly throwing an
>      org.apache.cxf.interceptor.Fault: Unmarshalling Error: ...
>
> Have you found any fix to manage the WSDL changes or to ignore the WSDL
> check at client start?
>
> Thanks
> ;-)
>
> Piercarlo Alberto Beghetto
> Analyst Developer @ Diennea - MagNews
> Tel.: (+39) 0546 066100 - Int. 967
> Viale G.Marconi 30/14 - 48018 Faenza (RA)
>
> [Magnews.it]<http://www.magnews.it/it>
> [Linkedin]<http://www.linkedin.com/company/diennea---magnews>
>  [Twitter] <http://twitter.com/DienneaMagNews>      [Facebook] <
> http://www.facebook.com/pages/MagNews/197617841797>      [Newsletter] <
> http://www.magnews.it/it/iscriviti-alla-newsletter>
>
>
>
>
> ________________________________
>
> Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed
> email marketing! http://www.magnews.it/newsletter/
>
> The information in this email is confidential and may be legally
> privileged. If you are not the intended recipient please notify the sender
> immediately and destroy this email. Any unauthorized, direct or indirect,
> disclosure, copying, storage, distribution or other use is strictly
> forbidden.
>

Reply via email to