WebService Client Generation Error with JDK8

Question

I need to consume a web service in my project  I use NetBeans so I right-clicked on my project and tried to add a new  Web Service Client   Last time I checked  this was the way to create a web service client  But it resulted in an AssertionError  saying      java lang AssertionError  org xml sax SAXParseException  systemId  jar file  path to glassfish modules jaxb-osgi jar  com sun tools xjc reader xmlschema bindinfo binding xsd  lineNumber  52  columnNumber  88  schema reference  Failed to read schema document  xjc xsd   because  file  access is not allowed due to restriction set by the accessExternalSchema property    The default Java platform for NetBeans was JDK8  Oracle s official version   so when I changed my netbeans conf file and made JDK7  from Oracle  as well  as my default  everything worked fine  So I think the problem is with JDK8  Here is my java -version output      java version  1 8 0    Java TM  SE Runtime Environment  build 1 8 0-b132    Java HotSpot TM  64-Bit Server VM  build 25 0-b70  mixed mode    For now  I m keeping JDK7 as my default Java platform  If there is a way to make JDK8 work please share

User · Answer

Create a file named jaxp properties  if it doesn   t exist  under path to your  quot JDK version jre lib quot  and then add the following line in it  javax xml accessExternalSchema   all

User · Answer

Enabling Access to External Schema  You need to enable the IDE and the GlassFish Server to access external schema to parse the WSDL file of the web service  To enable access you need to modify the configuration files of the IDE and the GlassFish Server  For more details  see the FAQ How to enable parsing of WSDL with an external schema  Configuring the IDE  To generate a web service client in the IDE from a web service or WSDL file you need to modify the IDE configuration file  netbeans conf  to add the following switch to netbeans default options   -J-Djavax xml accessExternalSchema all   For more about locating and modifying the netbeans conf configuration file  see Netbeans Conf FAQ  Configuring the GlassFish Server  If you are deploying to the GlassFish Server you need to modify the configuration file of the GlassFish Server  domain xml  to enable the server to access external schemas to parse the wsdl file and generate the test client  To enable access to external schemas  open the GlassFish configuration file  GLASSFISH INSTALL glassfish domains domain1 config domain xml  and add the following JVM option element  in bold   You will need to restart the server for the change to take effect    lt  java-config gt           lt jvm-options gt -Djavax xml accessExternalSchema all lt  jvm-options gt   lt  java-config gt

User · Answer

NetBeans update their tutorial for JDK8 and this Issue   Getting Started with JAX-WS Web Services -  Enabling Access to External Schema

User · Answer

It is now fixed in 2 5 version  released in jul 17   https   github com mojohaus jaxws-maven-plugin issues 8   For the 2 4 x versions there is a workaround  as decribed in https   github com mojohaus jaxws-maven-plugin issues 4         lt plugin gt           lt groupId gt org codehaus mojo lt  groupId gt           lt artifactId gt jaxws-maven-plugin lt  artifactId gt           lt version gt 2 4 1 lt  version gt           lt dependencies gt               lt dependency gt                   lt groupId gt com sun xml ws lt  groupId gt                   lt artifactId gt jaxws-tools lt  artifactId gt                   lt version gt 2 2 10 lt  version gt               lt  dependency gt           lt  dependencies gt       lt  plugin gt

User · Answer

I tested this for version 2 4 of artifact org codehaus mojo and that worked     lt plugins gt       lt plugin gt           lt groupId gt org codehaus mojo lt  groupId gt           lt artifactId gt jaxws-maven-plugin lt  artifactId gt           lt version gt 2 4 1 lt  version gt           lt executions gt               lt execution gt                    lt goals gt                       lt goal gt wsimport lt  goal gt                   lt  goals gt                   lt configuration gt                       lt wsdlDirectory gt path to dir wsdl lt  wsdlDirectory gt                   lt  configuration gt                   lt id gt wsimport-web-service lt  id gt                   lt phase gt generate-sources lt  phase gt               lt  execution gt           lt  executions gt           lt dependencies gt               lt dependency gt                   lt groupId gt javax xml lt  groupId gt                   lt artifactId gt webservices-api lt  artifactId gt                   lt version gt   webservices-api-version  lt  version gt               lt  dependency gt           lt  dependencies gt           lt configuration gt               lt vmArgs gt                   lt vmArg gt -Djavax xml accessExternalSchema all lt  vmArg gt               lt  vmArgs gt               lt sourceDestDir gt generated-sources jaxws-wsimport lt  sourceDestDir gt               lt xnocompile gt true lt  xnocompile gt               lt verbose gt true lt  verbose gt               lt extension gt true lt  extension gt               lt sei gt   lt  sei gt           lt  configuration gt       lt  plugin gt   lt  plugins gt

User · Answer

If you are using ant you can add a jvmarg to your java calls    lt jvmarg value  -Djavax xml accessExternalSchema all    gt

User · Answer

I have just tried that if you use SoapUI  5 4 x  and use Apache CXF tool to generate java code  put javax xml accessExternalSchema   all in YOUR JDK jre lib jaxp properties file also works

User · Answer

I run ant builds within Eclipse IDE  4 4  Luna  on Windows 7 x64    Rather than modifying the installed JRE lib or any ant scripts  I have multiple projects that include XJC in their builds   I prefer to change Eclipse Settings  External Tools Configurations  and add the following to the VM arguments for the Ant build configuration   -Djavax xml accessExternalSchema all

User · Answer

Another solution to address  wiki netbeans org  The Web Service Client wizard in the IDE parses the WSDL file when generating a web service client from a web service or WSDL file  You need to modify the IDE configuration file  netbeans conf  to add the following switch to the netbeans default options  You will need to restart the IDE for the change to take effect   -J-Djavax xml accessExternalSchema all   When deploying to GlassFish you need to enable access to external schema to generate a test client for a web service  To enable access you need to modify the configuration file of the GlassFish Server  GLASSFISH INSTALL glassfish domains domain1 config domain xml  and add the following JVM option element  You will need to restart the server for the change to take effect    lt  java-config gt           lt jvm-options gt -Djavax xml accessExternalSchema all lt  jvm-options gt   lt  java-config gt

User · Answer

I used it with a regular maven project  and got it solved with this plugin dependency configuration for running the xjc plugin          lt plugin gt           lt  -- Needed to run the plugin xjc en Java 8 or superior -- gt           lt groupId gt org codehaus mojo lt  groupId gt           lt artifactId gt properties-maven-plugin lt  artifactId gt           lt version gt 1 0-alpha-2 lt  version gt           lt executions gt               lt execution gt                   lt id gt set-additional-system-properties lt  id gt                   lt goals gt                       lt goal gt set-system-properties lt  goal gt                   lt  goals gt               lt  execution gt           lt  executions gt           lt configuration gt               lt properties gt                   lt property gt                       lt name gt javax xml accessExternalSchema lt  name gt                       lt value gt all lt  value gt                   lt  property gt                   lt property gt                       lt name gt javax xml accessExternalDTD lt  name gt                       lt value gt all lt  value gt                   lt  property gt               lt  properties gt           lt  configuration gt       lt  plugin gt

User · Answer

If you are getting this problem when converting wsdl to jave with the cxf-codegen-plugin  then you can solve it by configuring the plugin to fork and provide the additional  -Djavax xml accessExternalSchema all  JVM option            lt plugin gt               lt groupId gt org apache cxf lt  groupId gt               lt artifactId gt cxf-codegen-plugin lt  artifactId gt               lt version gt   cxf version  lt  version gt               lt executions gt                   lt execution gt                       lt id gt generate-sources lt  id gt                       lt phase gt generate-sources lt  phase gt                       lt configuration gt                           lt fork gt always lt  fork gt                           lt additionalJvmArgs gt                              -Djavax xml accessExternalSchema all                          lt  additionalJvmArgs gt

User · Answer

Here is a hint Hint for gradle users without admin rights  add this line to your jaxb-task   System setProperty  javax xml accessExternalSchema    all     it will look like this   jaxb       System setProperty  javax xml accessExternalSchema    all       xsdDir      project name  xsd      xjc           taskClassname    com sun tools xjc XJCTask          args     -npa    -no-header

User · Answer

Another alternative is to update wsimport sh shell script by adding the following   The wsimport sh is located in this directory   jaxws-ri 2 2 28 bin  exec   JAVA   WSIMPORT OPTS -Djavax xml accessExternalSchema all -jar   JAXWS HOME lib jaxws-tools jar

User · Answer

The following works for wsimport 2 2 9 included in jdk 1 8 0 66   wsimport -J-Djavax xml accessExternalSchema all

User · Answer

I was also getting similar type of error in Eclipse during  testing  a webservice program on glassfish 4 0 web server  java lang AssertionError  org xml sax SAXParseException  systemId  bundle   158 0 1 com sun tools xjc reader xmlschema bindinfo binding xsd  lineNumber  52  columnNumber  88  schema reference  Failed to read schema document  xjc xsd   because  bundle  access is not allowed due to restriction set by the accessExternalSchema property   I have added javax xml accessExternalSchema   All in jaxp properties  but doesnot work for me   However I found a solution here below which work for me  For GlassFish Server  I need to modify the domain xml of the GlassFish   path   lt path gt  glassfish domains domain1 or domain2 config domain xml  and add   lt jvm-options gt -Djavax xml accessExternalSchema all lt  jvm-options gt under the  lt java-config gt  tag          lt java-config gt        lt jvm-options gt -Djavax xml accessExternalSchema all lt  jvm-options gt   lt  java-config gt      and then restart the GlassFish server

User · Answer

Well  I found the solution   based on http   docs oracle com javase 7 docs api javax xml XMLConstants html ACCESS EXTERNAL SCHEMA   Create a file named jaxp properties  if it doesn t exist  under  path to jdk1 8 0 jre lib and then write this line in it   javax xml accessExternalSchema   all   That s all  Enjoy JDK 8

User · Answer

For those using the ANT task wsimport  a way of passing the option as suggested by  CMFly and specified in the documentation is the following    lt wsimport     lt  --     -- gt     fork  true     gt     lt jvmarg value  -Djavax xml accessExternalSchema all   gt   lt  wsimport gt

User · Answer

When using Maven with IntelliJ IDE you can add -Djavax xml accessExternalSchema all to Maven setting under JVM Options for Maven Build Tools Runner configuration

User · Answer

Not an actual answer but more as a reference   If you are using the jaxws Maven plugin and you get the same error message  add the mentioned property to the plugin configuration        lt plugin gt     lt groupId gt org jvnet jax-ws-commons lt  groupId gt     lt artifactId gt jaxws-maven-plugin lt  artifactId gt     lt version gt 2 3 lt  version gt     lt configuration gt       lt  -- Needed with JAXP 1 5 -- gt       lt vmArgs gt           lt vmArg gt -Djavax xml accessExternalSchema all lt  vmArg gt       lt  vmArgs gt     lt  configuration gt   lt  plugin gt

User · Answer

A very simple portable solution would be  to place the following line of code somewhere in a crucial part of your code  a part of which you are sure that it will be run  for example right in the main method     System setProperty  javax xml accessExternalDTD    all      This sets the needed system property programmatically  without having to do tricky maven pom xml changes  which for some reason didn t work for me

User · Answer

This works on jdk1 8 0 65  wsimport -J-Djavax xml accessExternalSchema all -keep -verbose https   your webservice url wsdl

User · Answer

Another reference  If you are using the maven-jaxb2-plugin  prior to version 0 9 0  you can use the workaround described on this issue  in which this behaviour affected the plugin

User · Answer

In my case adding   javax xml accessExternalSchema   all   to jaxp properties didn t work  I ve to add   javax xml accessExternalDTD   all   My environment is linux mint 17 and java 8 oracle  I ll put it there as an answer for people with the same problem

[webservice-client] WebService Client Generation Error with JDK8

Examples related to webservice-client

Examples related to java-8

Examples related to netbeans-8