You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Robert Liguori (JIRA)" <ji...@apache.org> on 2010/10/05 16:39:33 UTC
[jira] Created: (CXF-3038) Update online CXF Architecture Document
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
Considering the CXF Architecture Guide (http://cxf.apache.org/docs/cxf-architecture.html), the leading paragraph, does not model the actual content of the web page.
Consider reworking the content and/or the leading paragraph so they are in sync.
For example:
The overall CXF architecture is primarily made up of the following parts:
1. Bus: This is the backbone of the CXF architecture.
2. Messaging & Interceptors: These provide the low level message and pipeline layer upon which most functionality is built.
3. Front ends: Frontends provide a programming model to create services (e.g. JAX-WS).
4. Services: Services host a Service model which is a WSDL-like model which describes the service.
5. Bindings: Bindings provide the functionality to interpret the protocol (i.e. SOAP, REST, Corba).
6. Transports: Destinations and Conduits make up the transport abstraction that CXF uses to achieve transport neutrality.
SHOULD READ
The overall CXF architecture is primarily made up of the following parts:
1. Bus: This is the backbone of the CXF architecture.
2. Messaging & Interceptors: These provide the low level message and pipeline layer upon which most functionality is built.
3. Transports: Destinations and Conduits make up the transport abstraction that CXF uses to achieve transport neutrality.
4. Data Bindings: [TBD]
5. Service Model: Services host a Service model which is a WSDL-like model which describes the service.
6. Bindings: Bindings provide the functionality to interpret the protocol (i.e. SOAP, REST, Corba).
7. Endpoints: [TBD]
8. Front ends: Frontends provide a programming model to create services (e.g. JAX-WS).
----------------------
Also, the initial TOC of links can be removed in favor of adding hyperlinks to the above number list (as they provide the same purpose)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-3038) Update online CXF Architecture Document
Posted by "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 closed CXF-3038.
-------------------------------
Issue resolved.
> 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
(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
(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
(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 nook 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.
was:
Considering the CXF Architecture Guide (http://cxf.apache.org/docs/cxf-architecture.html), the leading paragraph, does not model the actual content of the web page.
Consider reworking the content and/or the leading paragraph so they are in sync.
For example:
The overall CXF architecture is primarily made up of the following parts:
1. Bus: This is the backbone of the CXF architecture.
2. Messaging & Interceptors: These provide the low level message and pipeline layer upon which most functionality is built.
3. Front ends: Frontends provide a programming model to create services (e.g. JAX-WS).
4. Services: Services host a Service model which is a WSDL-like model which describes the service.
5. Bindings: Bindings provide the functionality to interpret the protocol (i.e. SOAP, REST, Corba).
6. Transports: Destinations and Conduits make up the transport abstraction that CXF uses to achieve transport neutrality.
SHOULD READ
The overall CXF architecture is primarily made up of the following parts:
1. Bus: This is the backbone of the CXF architecture.
2. Messaging & Interceptors: These provide the low level message and pipeline layer upon which most functionality is built.
3. Transports: Destinations and Conduits make up the transport abstraction that CXF uses to achieve transport neutrality.
4. Data Bindings: [TBD]
5. Service Model: Services host a Service model which is a WSDL-like model which describes the service.
6. Bindings: Bindings provide the functionality to interpret the protocol (i.e. SOAP, REST, Corba).
7. Endpoints: [TBD]
8. Front ends: Frontends provide a programming model to create services (e.g. JAX-WS).
----------------------
Also, the initial TOC of links can be removed in favor of adding hyperlinks to the above number list (as they provide the same purpose)
> 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.
> (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
> (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
>
> (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 nook 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
(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*.
(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 nook 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.
was:
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.
(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*.
(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
(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 nook 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.
> 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.
> (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*.
> (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 nook 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.
[jira] Resolved: (CXF-3038) Update online CXF Architecture Document
Posted by "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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
(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*.
(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
(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 nook 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.
was:
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.
(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
(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
(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 nook 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.
> 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.
> (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*.
> (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
>
> (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 nook 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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 nook 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.
was:
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.
(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*.
(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 nook 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.
> 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 nook 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.
[jira] Commented: (CXF-3038) Update online CXF Architecture
Document
Posted by "Robert Liguori (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919689#action_12919689 ]
Robert Liguori commented on CXF-3038:
-------------------------------------
I'm trying to learn from the existing CXF documentation. As I find issues with the material, I believe that I am acting responsibly by raising the issue flag. As I am not a CXF expert at this time, I cannot comfortably add and/or refine technical content. However, once my skills mature, I may be able to contribute on nights and weekends. I did apply for wiki access, so once I get it, I'll make quick and easy refinements as I go along the learning trail. Thanks.
> 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
(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*.
(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
(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 nook 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.
was:
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.
(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*.
(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
(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 nook 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.
> 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.
> (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*.
> (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
>
> (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 nook 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
(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*.
(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
(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 nook 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.
was:
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.
(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*.
(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
(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 nook 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.
> 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.
> (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*.
> (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
>
> (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 nook 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.
[jira] Updated: (CXF-3038) Update online CXF Architecture Document
Posted by "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 updated CXF-3038:
--------------------------------
Description:
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.
was:
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 nook 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.
> 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.
[jira] Commented: (CXF-3038) Update online CXF Architecture
Document
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919686#action_12919686 ]
Benson Margulies commented on CXF-3038:
---------------------------------------
Robert,
To repeat what Dan said: like every other Apache project, we're volunteers with varying level of 'day-job' support. We do appreciate suggestions on the doc, but we'd appreciate your actually working on it more.
--benson
> 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.