[ https://issues.jboss.org/browse/WFLY-3463?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-3463: --------------------------------------- It's not CXF WSDLManagerImpl who needs read access to JRE wsdl.properties, but WSDL4J javax.wsdl.factory.WSDLFactory#findFactoryImplName(). That method goes through multiple options for figuring out the actual wsdl factory impl to use and eventually defaults to "com.ibm.wsdl.factory.WSDLFactoryImpl" if no preference is set (which is the most common scenario). While the lookup of the "javax.wsdl.factory.WSDLFactory" system property is performed properly by catching a possibly SecurityException, the last mechanism (which is accessing the JRE wsdl.properties) does not consider a possible SecurityException. That makes the findFactoryImplName() method fail and not return the default factory name. That's why I mentioned the workaround, which is basically asking in advance to use the default factory. Now, to me this is a bug in WSDL4J. We could "workaround" it in CXF by catching the SecurityException and using the "com.ibm.wsdl.factory.WSDLFactoryImpl" factory name in that case, but it would really be ugly (not something I'm going to to). -- This message was sent by Atlassian JIRA (v6.2.3#6260)