Minor Description
Muliple CXF example projects start their packaging with "demo." in the package name, including (but not limited to):
aegis, callback, configuration_interceptor, groovy_spring_support, in_jvm_transport, java_first_jaxws, java_first_jaxws_factory_bean, java_first_pojo, java_first_spring_support, jax_server_aegis_client, jaxws_async, jaxws_dispatch_provider, jaxws_handlers, jms_pubsub, jms_queue, jms-spec-demo, js_browser_client_java_first, js_browser_client_simple, js_client, js_provider, logbrowser, mtom, mtosi_1.1, restful_dispatch, restful_http_binding, ruby_spring_support, soap_header, ws_addressing, ws_policy, ws_rm, wsdl_frist_dynamic_client, wsdl_first_https, wsdl_first_pure_xml, wsdl_first_rclit, wsdl_first_soap12, wsdl_first_xml_wrapped and wsdl_first_xmlbeans.
Note: I list them all here to stress the convention that is used across the majority of the sample projects.
Only a handful of the projects use the directory layout generally expected by Maven (src/main/java); http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
However, the maven standards does leave room for not following the convention, "Please try to conform to this structure as much as possible; however, if you can't these settings can be overridden via the project descriptor."
My recommendation for conformity across all of the sample projects is to modify the few projects that conform to the maven convention (main.java) and change them to what is being used by the majority of the projects (demo.).
The projects that would need to be refactored include:
java_first_jms
jms_spring_config
sts_issue_operation
wsdl_first
jax_rs/basic_https
ws_security/sign_enc
Thanks for the consideration.