[wildfly-dev] Patching WSDL4J (or perhaps forking?)

[Stuart Douglas]

We could alwayy fork it and do our own release. That is what we have done
to get around some JSF problems.

Stuart


On Thu, Sep 5, 2013 at 4:42 PM, Alessio Soldano <asoldano at redhat.com> wrote:

> Folks,
> when running the jbossws testsuite against WFLY master with security
> manager enabled, I've noticed that the following permission is required
> to build up JAXWS clients (actually to be able to parse any WSDL):
>
>    <permission class="java.io.FilePermission"
> name="/usr/java/jdk1.7.0_17/jre/lib/wsdl.properties" actions="read"/>
>
> That's basically a non existing file in my java.home. The reason is in
> WSDL4J, which seems to be missing a SecurityException catch block in
> javax.wsdl.factory.WSDLFactory#findFactoryImplName().
> I thought about reporting the issue, but afaics the project "lives" at
> sourceforge.net (on cvs  scm...) and, more important, since Oct 2011
> there's already a patch proposal [1] for the issue which has never been
> commented / considered.
>
> How should we move forward here? Suggestions / proposals? Anybody here
> is in the JSR-110 EG and can get in touch with the WSDL4J devs?
>
> Alessio
>
> [1] http://sourceforge.net/p/wsdl4j/patches/1/
>
> --
> Alessio Soldano
> Web Service Lead, JBoss
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20130905/aec74c7f/attachment.html