<div dir="ltr">Hi Philippe, <div>I think this would be good that we provide a dedicated module for Jasypt and still export to ws security module. This will allow the old application with jbossws-cxf-client module dependency added can still access jasypt classes and work. If other application likes yours doesn't want this jasypt exported dependency , it can be excluded with one line exclusion config in jboss-deployment-structure.xml. Does this work for you ? </div><div>BTW, upgrade jasypt to 1.9.3 is the missing part in wildfly. I'll fix this soon. I added this discussion to WFLY-13059 too. If you like, let's add comment/discuss there.</div><div></div><div><br></div><div>Cheers,</div><div>Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 14, 2020 at 1:32 AM Philippe Marschall <<a href="mailto:kustos@gmx.net">kustos@gmx.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 13.03.20 14:43, Jim Ma wrote:<br>
> Hi Philippe,<br>
> Did you try to provide a jboss-deployment-structure.xml to exclude<br>
> org.apache.ws.security module and add all the jars you need in your<br>
> application ?<br>
<br>
Yes, we found a workaround but we would like to get rid of it and see<br>
the underlying issue fixed. Otherwise other users could be affected as<br>
well and have a bad experience using WildFly.<br>
<br>
Cheers<br>
Philippe<br>
<br>
</blockquote></div>