I'm sorry that I didn't respond to this. You might already know answers
to some of those questions, but anyway, here we go...
Ken Hofsass wrote:
>>> shortName - derive from partial path name, e.g.
>>> "tests.policy.parsing.test1" resources - user specified
>>
>> I think the resource directory name can be fixed --- like "resources"
>> in the test data directory.
>
> By "test data directory", am I correct to understand that you mean the
> per-test directory holding the scripts, config files, etc... not some
> global directory for resources from all tests, right?
Yes.
>>> <url-pattern> derived from "/" + shortName + specific
>>> test name (e.g. "/tests.policy.parsing.test1.testFoo")
>>
>> This is per endpoint, not per test. So the url-pattern should be
>> driven by TestEndpoint.name.
>
> Ok, so both the set of endpoints (sun-jaxws.xml <endpoint>
> <url-pattern>) and the set of servlet-mappings (web.xml
> <servlet-mapping> <url-pattern>) would be generated from the set of
> endpoints defined by the service. Namely, for each "endpointInterface"
Yeah. IOW, it could be just "/testFoo", instead of
"/tests.policy.parsing.test1.testFoo"
>>> service= derived: wsdl target namespace + wsdl service name
>>> port= derived: wsdl target namespace + wsdl port name
>>
>> Would inferring those values be easier if we can get wscompile output
>> them?
>
> Yeah, seems like it would for "from wsdl" cases. However, for the tests
> starting from java, would that help? Hmm. Maybe apt and/or wsgen would
> also need to be tweaked? Hmm.
If it's as easy as listing names of classes that have @WebService, I can
write a little annotation processor that spits out that file.
Or I suspect even a simple grep-like application may work just fine. All
we need to know is the package name (which can be easily extracted from
"package xxxx;") and class name (which is just a file name.)
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com