Author: alessio.soldano(a)jboss.com Date: 2007-11-02 10:24:04 -0400 (Fri, 02 Nov 2007) New Revision: 4973 Modified: stack/native/branches/asoldano/trunk/src/main/java/org/jboss/ws/metadata/builder/jaxws/JAXWSWebServiceMetaDataBuilder.java Log: Temporarily disabling ws-policy on server side (as previously did on client side, for wcf tests) Modified: stack/native/branches/asoldano/trunk/src/main/java/org/jboss/ws/metadata/builder/jaxws/JAXWSWebServiceMetaDataBuilder.java =================================================================== --- stack/native/branches/asoldano/trunk/src/main/java/org/jboss/ws/metadata/builder/jaxws/JAXWSWebServiceMetaDataBuilder.java 2007-11-01 16:39:13 UTC (rev 4972) +++ stack/native/branches/asoldano/trunk/src/main/java/org/jboss/ws/metadata/builder/jaxws/JAXWSWebServiceMetaDataBuilder.java 2007-11-02 14:24:04 UTC (rev 4973) @@ -371,7 +371,7 @@ //we can no longer use the user provided wsdl without parsing it right now, since we //need to look for policies and eventually choose the supported policy alternatives WSDLDefinitions wsdlDefinitions = factory.parse(wsdlLocation); - policyBuilder.processPolicyExtensions(epMetaData, wsdlDefinitions); +// policyBuilder.processPolicyExtensions(epMetaData, wsdlDefinitions); //now we have the UMDM containing policy data; anyway we can't write a new wsdl file with //the supported alternatives and so on, since we need to publish the file the user provided serviceMetaData.setWsdlLocation(wsdlLocation);