[jira] Resolved: (CXF-3038) Update online CXF Architecture Document

["Robert Liguori (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Liguori resolved CXF-3038.
---------------------------------

    Resolution: Fixed

I agree with Apache CXF's community comments that having an issue for every web page in progress in not a good idea.... kinda conflicts with the purpose of the wiki.  

In regards to this page in general, I added a link to a more complete CXF architecture document for the time being: http://naveenbalani.com/index.php/2010/05/apache-cxf-architecture-overview/.

As such, this issue can be closed.

> Update online CXF Architecture Document
> ---------------------------------------
>
>                 Key: CXF-3038
>                 URL: https://issues.apache.org/jira/browse/CXF-3038
>             Project: CXF
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Robert Liguori
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The CXF Architecture Guide (http://cxf.apache.org/docs/cxf-architecture.html) needs to be updated.
> Some strong suggestions:
> (1) The "Frontends" section has only one sub-section, and it's empty.  The "Frontends" section should discuss JAX-WS, JAX-RS, Simple Frontend and Javascript.  Link to and/or update this page: http://cxf.apache.org/docs/frontends.html.
> (2) It would be nice if the "Data Bindings" section referenced supported data bindings (e.g., JAXB, XMLBeans, Aegis (2.1), Aegis (2.0.x), MTOM Attachments with JAXB, Service Data Objects (SDO) and SXC*.  Note; Link to and/or update this page: http://cxf.apache.org/docs/databindings.html.
> (3) The "Bindings" section should be renamed to "Protocol Bindings".  There are currently two sections, one on SOAP bindings and an empty on on XML bindings.  Consider sub-sections on SOAP 1.1/1.2 bindings, HTTP 1.1 bindings, Pure XML bindings and CORBA bindings.
> (4) Consider adding notes on supported transports to the "Transports" section; SOAP over HTTP, SOAP over JMS, XML over HTTP, XML over JMS, CORBA, Servlet, In-VM, SMTP/POP3 via Camel Transport for CXF, TCP via Camel Transport for CXF and Jabber (Experimental) via Camel Transport for CXF.  Note: Also, link to and/or update this page: http://cxf.apache.org/docs/transports.html.
>  
> (5) The book "Apache CXF Web Service Development" by Naveen Balani and Rajeev Hathi (Packt Publishing) has a nice "CXF Architecture" section; pages 39-49.  This book should be references and/or compared to the document for alignment purposes (since the  section headers are nearly identical).
> Note: Since this is an 'architecture' document, perhaps specific implementation details and related products is outside of scope (e.g., listing specific data binding APIs), but it would still be nice to see.  At a minimum though... the empty, place holder sections of this document should be completed by someone.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.