Permalink
Browse files

WFLY-11229, JBEAP-15192: Add JBDS import WSDL WSDLAnalyzer warning to…

… READMEs for quickstarts that include a WSDL file
  • Loading branch information...
sgilda committed Oct 23, 2018
1 parent 392f78e commit 230251e0c3a01431aa20894645a8f588b0087fb5
Showing with 31 additions and 0 deletions.
  1. +10 −0 jaxws-addressing/README.adoc
  2. +10 −0 jaxws-retail/README.adoc
  3. +11 −0 wsat-simple/README.adoc
@@ -70,6 +70,16 @@ include::../shared-doc/run-the-quickstart-in-jboss-developer-studio.adoc[levelof
// Additional Red Hat Developer Studio instructions
For this quickstart, follow the special instructions to link:{useEclipseDeployJavaClientDocUrl}[Deploy and Undeploy a Quickstart Containing Server and Java Client Projects]
[NOTE]
====
When you import this quickstart into {JBDSProductName}, you will see the following warning:
[source]
----
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
----
This is a known Eclipse issue. For more information, see Eclipse Bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=535813[Bug 535813].
====
. To build all of the artifacts, right-click on the *{artifactId}* parent project, and choose *Run As* –> *Maven install*.
. To deploy the service:
** Right-click on the *{artifactId}-service* subproject, and choose *Run As* –> *Run on Server*.
View
@@ -91,8 +91,18 @@ include::../shared-doc/run-the-quickstart-in-jboss-developer-studio.adoc[levelof
// Additional Red Hat Developer Studio instructions
This quickstart is dependent on a WSDL file that is included in the `{artifactId}-service` project, so it deploys and runs differently in {JBDSProductName} than the other quickstarts.
[NOTE]
====
When you import this project into {JBDSProductName}, you see 17 errors. These `Java Problems` are because these classes are not included in this project. Instead, they are defined in and generated from the `{artifactId}-service/src/main/webapp/WEB-INF/wsdl/ProfileMgmtService.wsdl` WSDL file. You can ignore these errors.
You will also see the following warning:
[source]
----
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
----
This is a known Eclipse issue. For more information, see Eclipse Bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=535813[Bug 535813].
====
This quickstart requires that you build the parent project, deploy the service, and then run the client.
. To build the parent project, right-click on the *{artifactId}* project and choose *Run As* –> *Maven install*.
View
@@ -154,6 +154,17 @@ include::../shared-doc/run-the-quickstart-in-jboss-developer-studio.adoc[levelof
This quickstart is more complex than the others. It requires that you configure the {productName} server to use the _standalone-xts.xml_ configuration file, which is located in an external configuration directory.
. Import the quickstart into {JBDSProductName}.
+
[NOTE]
====
When you import this quickstart into {JBDSProductName}, you will see the following warning.
[source]
----
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
----
This is a known Eclipse issue. For more information, see Eclipse Bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=535813[Bug 535813].
====
. If you have not already done so, you must configure a new {productName} server to use the XTS configuration.
** In the *Servers* tab, right-click and choose *New* -> *Server*.
** Under *Select the server type:*, expand *Red Hat JBoss Middleware* and choose *{jbdsEapServerName}*.

0 comments on commit 230251e

Please sign in to comment.