dev@ws-test-harness.java.net

Modifying the harness to support sts

From: Bhakti Mehta <Bhakti.Mehta_at_Sun.COM>
Date: Tue, 19 Sep 2006 10:44:48 -0700

Hi Kohsuke,
Ken and I looked at the wstrust test in the wsit e2e test workspace and
tried it with the latest harness jars. There is a problem because the
wsit-client.xml is needing the endpoint location for the
preconfiguredSTS element . This is how the snippet of the
wsit-client.xml looks.
We were thinking of copying over the wsit-client.xml with this string
replaced with the endpoint information.
What would you recommend to do this? Is dom4j better or can jelly be
used in this case?
Please suggest.

Thanks,
Bhakti
.... snip
     <tc:PreconfiguredSTS
xmlns:tc="http://schemas.sun.com/ws/2006/05/trust/client"
                    endpoint="http://localhost:8080/jaxws-s5-sts/sts"
                    wsdlLocation="WEB-INF/wsdl/sts.wsdl"
                    serviceName="SecurityTokenService"
                    portName="CustomBinding_ISecurityTokenService"
                    namespace="http://tempuri.org/">
                </tc:PreconfiguredSTS>