Bug 1013502

lot of examples is in the jbossws testsuite. Solution would be to productize the TS (jbossws is already productized, but TS is excluded from build) and reference it in dev docs

It would be helpful to see in the guide what you view as a good example
of a component using for demonstration and documentation code from quickstarts.
Would you provide a pointer to 1 or more examples?

Hi Rebecca, not sure if we have such component and Quickstarts example.

It would be great to have Quickstarts Petr was describing in the description.
I know that JBossWS CXF testsuite contains examples, maybe for the beginning we could mention them in the documentation. Question is if it's possible to link project resources from product documentation.

4 new WS quickstarts added.  Each provides a service and client which matches
a code fragment in the 6.x JBoss Development Application Platform Development Guide(s) WS section.

jaxws-ejb  (see 
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Development_Guide/Write_and_Deploy_a_JAX-WS_Web_Service_Endpoint.html,
  Example 14.12. Exposing an Endpoint in an EJB)

jaxws-pojo  (see 
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Development_Guide/Write_and_Deploy_a_JAX-WS_Web_Service_Endpoint.html,
  Example 14.10. Example POJO Endpoint)

jaxws-retail  (see 
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Development_Guide/Write_and_Deploy_a_JAX-WS_Web_Service_Endpoint.html,
  14.3.2. Write and Deploy a JAX-WS Web Service Endpoint)

jaxws-addressing  (see 
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Development_Guide/Write_and_Deploy_a_JAX-WS_Web_Service_Endpoint.html,
  14.5.1. Enable Web Services Addressing (WS-Addressing))


Pull request submitted:  https://github.com/jboss-developer/jboss-eap-quickstarts/pull/1151.

@David Michaels: These quickstarts were never merged into the release because we were waiting for necessary updates, therefore we can not update the EAP 6.4 documentation with these examples. We can consider adding this to EAP 7 docs if we add the quickstarts there.

@Rebecca Searls: What happened to these quickstarts? You issued this pull [1] but never made the requested updates. Do you want to resurrect these for JBoss EAP 7?

[1] https://github.com/jboss-developer/jboss-eap-quickstarts/pull/1151

Talked to Rebecca and she is updating the quickstarts and plans to submit them for EAP 7.

Submitted new pull request, https://github.com/jboss-developer/jboss-eap-quickstarts/pull/1443
was not able to push squashed changes back into initial pull request,

I issued a pull with fixes back to Rebecca: https://github.com/rsearls/jboss-eap-quickstarts/pull/1

I have accepted all your edits.  I integrated your pull request to my account.
Thanks for all those edits.

In JDK 8, wsconsume (org.jboss.ws.plugins:maven-jaxws-tools-plugin)
requires the presence of ${SOMEPATH}/jdk1.8.0_05/jre/lib/jaxp.properties,
contents javax.xml.accessExternalSchema = all
(see http://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#ACCESS_EXTERNAL_SCHEMA
 http://stackoverflow.com/questions/23011547/webservice-client-generation-error-with-jdk8) 

For quickstart jaxws-retail the user needs to be informed they require
this file.  How should I handle this?  Provide jaxp.properties in the
quickstart and document this in the README?

Yes. That works. Provide the file in the root directory of the quickstart and add  instructions to copy it to the correct location. Also add the link to http://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#ACCESS_EXTERNAL_SCHEMA,

Migrated to JIRA -> https://issues.jboss.org/browse/JBEAP-1692