[JAX_WS-1116] wsgen: relative ext metadata file is not found if s and/or d options are used Created: 14/May/13  Updated: 14/May/13

Status: Open
Project: jax-ws
Component/s: wsgen
Affects Version/s: 2.2.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Lukas Jungmann Assignee: miroslav.kos
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


culprit is in following method

private List<File> getExternalFiles(List<String> exts) {
    if (!file.exists()) {
        // then relative path ...
        file = new File(options.sourceDir.getAbsolutePath() + File.separator + ext);

so for following cmd line: wsgen -x a.xml -s dir -keep some.Service metadata file will be resolved to dir/a.xml which is wrong; it should be resolved to $WORK_DIR/a.xml instead

Comment by Lukas Jungmann [ 14/May/13 ]

it may be also good to consider adding support for handling URLs; I can see 2 use-cases for it now:
-metadata file is published on the web
-jaxws-maven-plugin could search for ie '/META-INF/mtd.xml' file on CP and pass it to the wsgen tool (the will result in jar URL)

Generated at Sun Aug 28 11:24:45 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.