Thursday Feb 19, 2009
Friday Sep 12, 2008
By Mark Foster on Sep 12, 2008
Whilst JavaCAPS6, and specifically the HTTP Binding Component, have many useful features, there are currently limitations with it, notably calling JAX-RPC webservices using soap encoded arrays and calling webservices using SOAP1.2.
With JAX-WS you get access to the Dispatch API which makes it easy to call both of these use-cases from Java code.
Wrapping the Dispatch code inside an EJB, exposed as a doc/literal webservice, is a simple way to create a proxy to these external webservices, this EJB-WS can then be called from BPEL, for example, via the JavaEE SE making the overall process very efficient.[Read More]
Mark Foster, Obernai, FranceI work for Sun in a team called FAST helping to enable the open source community for Open ESB.
- Intro to Oracle SOA Suite for GFESB Users
- IronMan Switzerland T-21 Weeks
- Orchestrating Data Integrator ETLs with BPEL
- IronMan Switzerland T-23 Weeks
- IronMan Switzerland T-24 Weeks
- Creating Dynamic EJB Proxies to JAX-WS External WebServices using the Dispatch API
- Creating Dynamic EJB Proxies to JAX-RPC External WebServices using the Dynamic Invocation Interface (DII)
- Creating EJB Proxies to External WebServices Using the Dispatch API
- Frankfurt Marathon 2008: T-9 weeks
- Frankfurt Marathon 2008: T-10 weeks