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

[Anil Saldhana]

Hi Alessio,
   it depends on how active the project is. If it is active, raising bug 
reports
and following up usually gets the resolution. If is is not active, 
forking is
the way to go unfortunately. Alternatively, you can become a contributor
to wsdl4j and apply the patch yourself. :)

Regards,
Anil

On 09/05/2013 09:42 AM, Alessio Soldano 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/
>