anonymous wrote : Yes, you need to also specify the authMethod and transportGuarantee. You can also take a look at the samples, in particular the jaxws-samples-context features this I'm sorry, I'm here again. I still have the same problem, WSDL pritected with password. Please look at my code once again: Web service code: @WebService @SOAPBinding(style = SOAPBinding.Style.RPC) @WebContext(authMethod = "BASIC", transportGuarantee="NONE", secureWSDLAccess = false) @SecurityDomain("e2edmwsSecurity") @Stateless public class e2edm_metadata_ws implements e2edmnwsInterface{ }
web.xml file: <servlet-name>e2edm_metadata_ws</servlet-name> <servlet-class>metadata.e2edm.e2edm_metadata_ws</servlet-class> <servlet-mapping> <servlet-name>e2edm_metadata_ws</servlet-name> <url-pattern>/e2edmws</url-pattern> </servlet-mapping> <security-constraint> <web-resource-collection> <web-resource-name>e2edm_metadata_ws_security</web-resource-name> <url-pattern>/</url-pattern> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>ws</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>e2edmwsSecurity</realm-name> </login-config> <security-role> <role-name>ws</role-name> </security-role> jbossweb.xml: <jboss-web> <security-domain>java:/jaas/e2edmwsSecurity</security-domain> </jboss-web> Why I still have WSDL with password? Thank you!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095895#4095895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095895 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user