dev@ws-test-harness.java.net

endpoint in wsit-client.xml

From: Bhakti Mehta <Bhakti.Mehta_at_Sun.COM>
Date: Wed, 20 Sep 2006 16:13:19 -0700

I am trying to experiment in the e2e workspace with the wstrust
wsit-client.xml so that I will know what needs to be replaced by the harness
This is how the preconfiguredSTS looks like in wsit-client.xml
 <tc:PreconfiguredSTS
xmlns:tc="http://schemas.sun.com/ws/2006/05/trust/client"

                    
endpoint="file:/D:/wsit-fresh/wsit/wsit/test/e2e/testcases/wstrust/scenario5/work/services/sts/war/WEB-INF/wsdl/sts.wsdl"
                    
wsdlLocation="file:/D:/wsit-fresh/wsit/wsit/test/e2e/testcases/wstrust/scenario5/sts/sts.wsdl"
                    serviceName="SecurityTokenService"
                    portName="CustomBinding_ISecurityTokenService"
                    namespace="http://tempuri.org/">
                </tc:PreconfiguredSTS>

These are the different options I tried
1. Making endpoint="http://localhost:8080/jaxws-s5-sts/sts?wsdl"
and having the sts war deployed on tomcat ---works

2. Making
endpoint="file://D:/wsit-fresh/wsit/wsit/test/e2e/testcases/wstrust/scenario5/work/services/sts/war/WEB-INF/wsdl/sts.wsdl"
I get the following exception related to "Unsupported endpoint adress"
In TransportPipeFactory there is this code
  if (scheme != null) {
            if(scheme.equalsIgnoreCase("http") ||
scheme.equalsIgnoreCase("https"))
                return new HttpTransportPipe(context.getBinding());
        }

        throw new WebServiceException("Unsupported endpoint address:
"+context.getAddress());

3.Making
endpoint="local://D:/wsit-fresh/wsit/wsit/test/e2e/testcases/wstrust/scenario5/work/services/sts/war?CustomBinding_ISecurityTokenService"
     [java] java.lang.RuntimeException: java.net.MalformedURLException:
unknown
protocol: local

Please can you suggest what should be the endpoint address for non http
scheme using local transport? Is case 2 a bug and should
TransportFactory recognize file:// scheme?

Regards,
Bhakti