1:30 a.m.
Hello
We recently ran into an issue because WildFly exports an old version of
Jasypt. We created WFLY-13059 for this [1].
We would be willing to work on a patch but we need guidance on which
proposed solution you prefer.
[1] https://issues.redhat.com/browse/WFLY-13059
Cheers
Philippe
7:24 a.m.
*bump*
As I explained we would be willing to work on a patch but we need
guidance on which proposed solution you prefer.
Cheers
Philippe
On 17.02.20 08:30, Philippe Marschall wrote:
Hello
We recently ran into an issue because WildFly exports an old version of
Jasypt. We created WFLY-13059 for this [1].
We would be willing to work on a patch but we need guidance on which
proposed solution you prefer.
[1] https://issues.redhat.com/browse/WFLY-13059
Cheers
Philippe
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
8:43 a.m.
Hi Philippe,
Did you try to provide a jboss-deployment-structure.xml to exclude
org.apache.ws.security module and add all the jars you need in your
application ?
Thanks,
Jim
On Fri, Mar 13, 2020 at 8:26 PM Philippe Marschall <kustos(a)gmx.net> wrote:
*bump*
As I explained we would be willing to work on a patch but we need
guidance on which proposed solution you prefer.
Cheers
Philippe
On 17.02.20 08:30, Philippe Marschall wrote:
> Hello
>
> We recently ran into an issue because WildFly exports an old version of
> Jasypt. We created WFLY-13059 for this [1].
> We would be willing to work on a patch but we need guidance on which
> proposed solution you prefer.
>
> [1] https://issues.redhat.com/browse/WFLY-13059
>
> Cheers
> Philippe
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
12:32 p.m.
On 13.03.20 14:43, Jim Ma wrote:
Hi Philippe,
Did you try to provide a jboss-deployment-structure.xml to exclude
org.apache.ws.security module and add all the jars you need in your
application ?
Yes, we found a workaround but we would like to get rid of it and see
the underlying issue fixed. Otherwise other users could be affected as
well and have a bad experience using WildFly.
Cheers
Philippe
5:35 a.m.
Hi Philippe,
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 ?
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.
Cheers,
Jim
On Sat, Mar 14, 2020 at 1:32 AM Philippe Marschall <kustos(a)gmx.net> wrote:
On 13.03.20 14:43, Jim Ma wrote:
> Hi Philippe,
> Did you try to provide a jboss-deployment-structure.xml to exclude
> org.apache.ws.security module and add all the jars you need in your
> application ?
Yes, we found a workaround but we would like to get rid of it and see
the underlying issue fixed. Otherwise other users could be affected as
well and have a bad experience using WildFly.
Cheers
Philippe
1711
days inactive
1739
days old
4 comments
2 participants
participants (2)
-
Jim Ma -
Philippe Marschall