Open source SOA infrastructure project CXF elevated to full A...
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
Groups (1)
-
In-the-Clouds-with-SOA-XML-and-the-Open-Web
4 members,80 bookmarks
Discussion of SOA, Cloud Computing, SaaS, Open Web Standards, and the importance of portable XML documents.
Bookmark History
Public Sticky notes
CXF is really designed for high performance, kind of like a request-response style of interaction for one way, asynchronous messaging, and things like that. But it’s really designed for taking data in from a variety of transports and message formats, such as SOAP or just raw XML. If you bring in the Apache Yoko project, we have CORBA objects coming in off the wire. It basically processes them through the system as quickly as possible with very little memory and processing overhead. We can get it to the final destination of where that data is supposed to be, whether it’s off to another service or a user-developed code, whether it’s in JavaScript or JAX-WS/JAXB code.
That’s the goal of what the CXF runtime is — just get that data into the form that the service needs, no matter where it came from and what format it came from in, and do that as quickly as possible.
Highlighted by garyedwards
Highlighted by garyedwards
on 2008-04-21 by garyedwards
Funny but i never thought of SOA as somehow separate from the Web. A Web-Stack is how one connects the disparate backend data streams. New applications capable of acting on that data are written to the Web, not some aging client/server platform model. I guess others had a different view of SOA and are just now discovering the interop and exchange value of the Web. Very strange.
Highlighted by garyedwards


Public Comment