nullpointer in specifying transport guarantee

[siddharthags]

hi
i have a web service that is deployed as a war on the JBoss [Zion] 4.0.5.GA build running the jbosws1.0.3 stack. i am trying to specify the transport guarantee for it to be confidential in the web.xml as

<web-ap>
.....
<security-constraint>
 <web-resource-collection>
 <web-resource-name>myservice</web-resource-name>
 </web-resource-collection>
 <user-data-constraint>
 <transport-guarantee>CONFIDENTIAL</transport-guarantee>
 </user-data-constraint>
 </security-constraint>
</web-app>

this is following the example specified of securing and enforcing of https mentioned for jmx-console

but am getting an error on jboss start up that says

16:06:31,137 ERROR [MainDeployer] Could not create deployment: file:/D:/Program Files/jboss/server/default/deploy/myservice.war/
java.lang.NullPointerException
 at org.jboss.util.xml.DOMUtils.getTextContent(DOMUtils.java:392)
 at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.initTransportGuaranteeJSE(JSR109ServerMetaDataBuilder.java:361)
 at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:203)

i can enforce the https via https:// prepend before the REPLACE... tag in the wsdl but i guess reading various posts by jason indicate that this should be supported by also just specifying the transport guarantee value in the web.xml from the 4.04 version of the AS?

TIA for ay answers

[thomas.diesler]

You are missing the <url-pattern> in <web-resource-collection>

You can look at the source, it's really easy.

[siddharthags]

Thanks..well duh.. knew it had to be something really obvious strange the dtd did not enforce it in the xml editor. did not have access to the source to verify thanks for the information.

[siddharthags]

well even after I changed it for url pattern I cannot force the transport confidential to state https in the wsdl generated. what else do I need to do? code is same from the previous post with the url pattern updated in the web.xml as <url-pattern>/myservice/*</url-pattern>, have updated to the 1.04 stack version just to make sure I have the latest of everything