...
|
||Project Name||Project Locations||Project Description|| |Generated _javascript_ using JAX-WS APIs and JSR-181 |js_browser_client_java_first|Sample shows the generation of _javascript_ client code from a JAX-WS server.|
|
|_javascript_ Client |js_browser_client_simple|sSample using Document/Literal Style sample illustrates the use of the _javascript_ client generator. This sample deploys the service based on the wsdl_first demo, and then provides a browser-compatible client that communicates with it. |
|
|Hello World Client sample using _javascript_ client |js_client|sSample demonstrates the use of (non-browser) _javascript_ to call a CXF server.|
|
|Hello World sample using _javascript_ and E4X Implementations|js_provider| sample Implementations|js_provider|Sample demonstrates the use of the _javascript_ and E4X dynamic languages to implement JAX-WS Providers.|
|
h2. WS-* Samples ||Project Name||Project Locations||Project Description||
|
|WS-Addressing|ws_addressing| sample |WS-Addressing|ws_addressing|Sample shows how WS-Addressing support in Apache CXF may be enabled. |
|
|WS-Policy |ws_policy|sSample shows how the CXF WS-Policy framework in Apache CXF uses WSDL 1.1 Policy attachments to enable the use of WS-Addressing.|
|
|WS-RM|ws_rm| sample |WS-RM|ws_rm|Sample shows how WS-ReliableMessaging support in Apache CXF may be enabled. |
|
| |ws_security\interopfest|This sample | |ws_security\interopfest|Sample is being used to help implement WS-SecurityPolicy, WS-SecureConversation, and WS-Trust within CXF.|
|
|WS-Security (Signature and Encryption) |ws_security_sign_enc|sSample shows how WS-Security support in Apache CXF may be enabled. WS-Security can be configured to the Client and Server endpoints by adding WSS4JInterceptors. Both Server and Client can be configured for outgoing and incoming interceptors. Various Actions like, Timestamp, UsernameToken, Signature, Encryption, etc., can be applied to the interceptors by passing appropriate configuration properties.|
|
|WS-Security (UsernameToken and Timestamp)|ws_security_ut| sample Timestamp)|ws_security_ut|Sample shows how WS-Security support in Apache CXF may be enabled. WS-Security can be configured to the Client and Server endpoints by adding WSS4JInterceptors. Both Server and Client can be configured for outgoing and incoming interceptors. Various Actions like, Timestamp, UsernameToken, Signature, Encryption, etc., can be applied to the interceptors by passing appropriate configuration properties.|
|
|WS-Security (UsernameToken and Timestamp)|ws_security\ut_policy| sample Timestamp)|ws_security\ut_policy|Sample shows how WS-Security support in Apache CXF may be enabled. WS-Security can be configured to the Client and Server endpoints by adding WS-SecurityPolicies into the WSDL.|
|
|WS-Security (Signature and UsernameToken)|ws_security\ut_sign| sample UsernameToken)|ws_security\ut_sign|Sample shows how WS-Security support in Apache CXF may be enabled. WS-Security can be configured to the Client and Server endpoints by adding WSS4JInterceptors. Both Server and Client can be configured for outgoing and incoming interceptors. Various Actions like, Timestamp, UsernameToken, Signature, Encryption, etc., can be applied to the interceptors by passing appropriate configuration properties.|
|
h2. Data Bindings Samples ||Project Name||Project Locations||Project Description||
|
|Aegis |aegis|sSample illustrates how to develop a service that is "code first", POJO-based. This sample uses the Aegis data binding.|
|
|Aegis Standalone|aegis_standalone| sample Standalone|aegis_standalone|Sample shows you how you can use Aegis with no web service at all as a mapping between XML and Java.|
|
Hello World using Document/Literal Style and XMLBeans|xmlbeans| sample XMLBeans|xmlbeans|Sample illustrates the use of the JAX-WS APIs and with the XMLBeans data binding to run a simple client against a standalone server using SOAP 1.1 over HTTP.|
|
h2. JBI Samples ||Project Name||Project Locations||Project Description||
|
|JBI EPEC|integration\JBI\external_provider_external_consumer| sample EPEC|integration\JBI\external_provider_external_consumer|Sample illustrates how external CXF client using SOAP/HTTP can communicate with external CXF server using SOAP/JMS through JBI SOAP and JMS binding component (as a transformer).|
|
|JBI EPIC|integration\JBI\external_provider_internal_consumer| sample EPIC|integration\JBI\external_provider_internal_consumer|Sample illustrates how internal CXF client that is deployed into CXF service engine can communicate with external CXF server through a generic JBI JMS binding component (as a router).|
|
|JBI and Handlers|integration\JBI\handlers| sample Handlers|integration\JBI\handlers|Sample shows how JAX-WS handlers can be used in CXF service engine. The sample consists of a CXF Service Engine and a test service assembly. The service assembly contains two service units: a service provider (server) and a service consumer (client).|
|
|JBI IPEC|integration\JBI\internal_provider_external_consumer| sample IPEC|integration\JBI\internal_provider_external_consumer|Sample illustrates how external CXF client can communicate with internal CXF server which is deployed into CXF service engine through a generic JBI binding component (as a router).|
|
|JBI IPIC |integration\JBI\internal_provider_internal_consumer|sSample shows how CXF can be used to implement service implementations for a Java Business Integration (JBI) container. The sample consists of a CXF Service Engine and a test service assembly. The service assembly contains two service units: a service provider (server) and a service consumer (client).|
|
h2. JCA Samples ||Project Name||Project Locations||Project Description||
|
|Inbound Connection CXF J2EE|integration\jca\inbound| sample J2EE|integration\jca\inbound|Sample shows how to expose an Enterprise Java Bean over SOAP/HTTP using CXF. |
|
|CXF Inbound Resource Adapter Message Driven Bean|integration\jca\inbound-mdb*| samples; three Bean|integration\jca\inbound-mdb*|Three samples... new inbound resource adapter samples (inbound-mdb, inbound-mdb-dispatch, and inbound-mdb-dispatch-wsdl). This series of inbound adapter samples leverages the JCA Specification Version 1.5 and Message Driven Bean in EJB 2.1 to activate CXF service endpoint facade inside the application server. For more information about the JCA message inflow model, please refer to chapter 12 (Message Inflow) of the JCA Specification 1.5.|
|
|Outbound Connection CXF J2EE|integration\jca\outbound| sample shows how to connect with an Apache CXF Web service using a Servlet deployed in an application server; Hello World (SOAP over HTTP) | |CXF Outbound Resource Adapter IBM WebSphere 6.1|integration\jca\outbound.wsa61| sample demonstrates the new CXF outbound resource adapter. |
|
...
|
h2. Miscellaneous Samples ||Project Name||Project Locations||Project Description||
|
|Callback|callback| sample |Callback|callback|Sample shows a client creating a callback object by passing an EndpointReferenceType to the server. The EndpointReferenceType is then used by the server to call back on the callback object.|
|
|Stream GZIP Interceptor|configuration_interceptor| Example shows how to develop an interceptor and add the interceptor into the interceptor chain through configuration.|
|
|Groovy with Spring Support|groovy_spring_support| sample Support|groovy_spring_support|Sample shows how to create groovy web service implemented with Spring. You'll learn how to write a simple groovy script web service. |
|
|Co-located using Document/Literal Style|in_jvm_transport| sample. Note: Project’s README.txt does not provide a sample description.|
|
|JMS Transport|jms_pubsub| sample Transport|jms_pubsub|Sample using Document-Literal Style sample demonstrates use of the Document-Literal style binding over JMS transport using the pub/sub mechanism.|
|
|JMS Transport|jms_queue| sample Transport|jms_queue|Sample using Document-Literal Style sample demonstrates use of the Document-Literal style binding over JMS Transport using the queue mechanism.|
|
|MTOM for SWA & XOP|mtom| sample XOP|mtom|Sample illustrates the use of a SOAP message with an attachment and XML-binary Optimized Packaging.|
|
|MTOSI Alarm Retrieval (SOAP OVER HTTP)|mtosi_1.1\alarm_retrieval| sample HTTP)|mtosi_1.1\alarm_retrieval|Sample demonstrates a simple CXF based client/server Web service implementing the MTOSI alarm retrieval service. |
|
|Ruby Script|ruby_spring_support| sample Script|ruby_spring_support|Sample shows how to create ruby web service implemented with Spring. You'll learn how to write a simple ruby script web service.|
|
|SOAP Headers|soap_header| sample Headers|soap_header|Sample illustrates Apache CXF's support for SOAP headers. |
|
h2. CORBA Samples ||Project Name||Project Locations||Project Description||
|
|CORBA Bank|corba\bank| sample Bank|corba\bank|Sample illustrates the use of JAX-WS API's for creating a service that uses the CORBA/IIOP protocol for communication. It also shows throwing exceptions across that connection.|
|
|CORBA Bank with WS-Addressing|corba\bank_ws_addressing| sample WS-Addressing|corba\bank_ws_addressing|Sample illustrates the use of the JAX-WS APIs to run a simple "Bank" application using CORBA/IIOP instead of SOAP/XML. It also contains standard CORBA client/server applications using pure CORBA code so you can see the JAX-WS client hit a pure CORBA server and a pure CORBA client hit the JAX-WS server. |
|
|CORBA Hello World|corba\hello_world| sample World|corba\hello_world|Sample illustrates the use of the JAX-WS APIs to run a simple "hello world" application using CORBA/IIOP instead of SOAP/XML. It also contains standard CORBA client/server applications using pure CORBA code so you can see the JAX-WS client hit a pure CORBA server and a pure CORBA client hit the JAX-WS server.|
|