This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
After enabling "Secure All Service Operations" and filling in the Keystore/Trustore information, the wsit xml file correctly reflects the settings, but if you uncheck security, the wsit xml file still contais the elements for the keystore and truststore as follows <wsp:All> <wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/> <sc:TrustStore wspp:visibility="private" location="C:\Sun\certs\server-truststore.jks" type="JKS" storepass="changeit" peeralias="xws-security-client"/> <sc:KeyStore wspp:visibility="private" location="C:\Sun\certs\server-keystore.jks" type="JKS" storepass="changeit" alias="s1as" keypass="changeit"/> <wsoma:OptimizedMimeSerialization/> </wsp:All> This may be intended as a convenience (so you don't have to re-enter the settings if you subseqently re-enable security) but when you undo an option, baggage should not be left around. I set the priority lower on the assumption these elements are innocuous.
I think the stores should be removed. Fixed in 2.3
This is fixed on the service side, but the client wsdl still shows the cert store elements in its wsdl file, even after editting the client's web service attributes and erasing the setting for the Certificates. The keystore and truststore sc elements are kept but their attributes are wiped out, which may not cause problems, but it might be cleaner to remove those elems from the client wsdl altogether. Here's what the client wsdl looks like after attempting to remove the keystore/truststore config. <?xml version="1.0" ?><definitions xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://nws.me.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://nws.me.org/" name="NewWebServiceService" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsaws="http://www.w3.org/2005/08/addressing" xmlns:sc="http://schemas.sun.com/2006/03/wss/client" xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy"><wsp:UsingPolicy></wsp:UsingPolicy><types><xsd:schema><xsd:import namespace="http://nws.me.org/" schemaLocation="http://localhost:8080/WebApplication6/NewWebService?xsd=1"></xsd:import></xsd:schema></types><message name="add"><part name="parameters" element="tns:add"></part></message><message name="addResponse"><part name="parameters" element="tns:addResponse"></part></message><portType name="NewWebService"><operation name="add"><input message="tns:add"></input><output message="tns:addResponse"></output></operation></portType><binding name="NewWebServicePortBinding" type="tns:NewWebService"><wsp:PolicyReference URI="#NewWebServicePortBindingPolicy"/> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding><operation name="add"><soap:operation soapAction="add"></soap:operation><input><soap:body use="literal"></soap:body></input><output><soap:body use="literal"></soap:body></output></operation></binding><service name="NewWebServiceService"><port name="NewWebServicePort" binding="tns:NewWebServicePortBinding"><soap:address location="http://localhost:8080/WebApplication6/NewWebService"></soap:address></port></service> <wsp:Policy wsu:Id="NewWebServicePortBindingPolicy"> <wsp:ExactlyOne> <wsp:All> <wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/> <sc:KeyStore wspp:visibility="private"/> <sc:TrustStore wspp:visibility="private"/> </wsp:All> </wsp:ExactlyOne> </wsp:Policy> </definitions>
I should have reopened this as a low priority issue before when I noticed that the store elements were not removed completely from the client configuration. With the wsit nbm's updated on Nov 21 that is still the case.
Tom, would you please add some exact steps to reproduce the client behaviour? I'm not able to reproduce.
I'm not able to reproduce this issue with v2.11.