wscompile issues

[Alan Bateman]

On 29/08/2017 06:45, Peter Major wrote:
> Hi,
>
>
> I'm not quite sure if this is the right mailing list to ask, but I'm
> wondering whether there is a bug in wscompile in the build 9+181 version.
>
> In a project of mine, I have a java ant task calling
> com.sun.xml.rpc.tools.wscompile.Main directly to generate some classes,
> however it seems like that although I can influence the --add-modules
> parameter for the java process itself, when wscompile eventually will
> try to compile the classes it generated, it will fail to specify
> java.xml.ws module, and as such the compilation fails with something like:
>
>       [java]
> /Users/aldaris/projects/foo/target/generated-sources/wscompile/com/mycompany/FooBar_Tie.java:91:
> error: cannot access Detail
>       [java]                 e.getFaultString(), e.getFaultActor(),
> e.getDetail());
>      
> [java]                                                                   ^
>       [java]   class file for javax.xml.soap.Detail not found
>       [java] Note: Some input files use unchecked or unsafe operations.
>       [java] Note: Recompile with -Xlint:unchecked for details.
>       [java] 1 error
>       [java] error: compilation failed, errors should have been reported
>
>
> Is this a bug in the JDK or am I just missing something glaringly obvious?
>
Is this JAX-RPC or the standalone version of the JAX-WS? Just checking 
as I thought the tools in the later were updated several years ago to 
use the javax.tools API. From your mail it sounds like the `wscompile` 
tool is forking `javac` and isn't picking up the environment and CLI 
options that are needed to compile the generated code.

-Alan