Bhakti Mehta wrote:
> 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?
If you can generate all or big enough portion of wsit-client.xml, it's
better to do that with Jelly (this is what I hope will happen --- more
generation = better.)
But if you are thinking about having a copy of wsit-client.xml for each
test case, and simply replace this one attribute value, dom4j is the way
to go.
> 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>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>
>
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com