[
https://issues.apache.org/jira/browse/CXF-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918899#action_12918899
]
Robert Liguori edited comment on CXF-3046 at 10/7/10 8:51 AM:
--------------------------------------------------------------
Okay. I will not open up any new documentation issues for Apache CXF, as
requested. I will just append my comments for broken links, incomplete text
and outdated information to existing JIRA issues.
As a general comment though:
Could someone on the Apache CXF team do the following:
(1) Resolve broken links on the Apache CXF website. This can be easily done in
an hour or two by first using a tool like Link Checker to find the links that
don't resolve: http://linkchecker.sourceforge.net/.
(2) Scrub the online web pages for 'works in progress', and resolve where
possible. Such an abundance of hanging files (for such a duration), gives the
impression that the pages aren't being maintained effectively.
(3) Technically scrub the pages for alignment purposes of changes in the last
few years. It appears as if CXF has picked up and refined several new
features.... the documentation should reflect this.
Thank you.
was (Author: gliesian):
Okay. I will not open up any new documentation issues for Apache CXF,
ServiceMix, Camel and/or ActiveMQ. I will just append my comments for broken
links, incomplete text and outdated information to existing JIRA issues.
> Refine Apache CXF technical content on main page of web site:
> http://cxf.apache.org/
> ------------------------------------------------------------------------------------
>
> Key: CXF-3046
> URL: https://issues.apache.org/jira/browse/CXF-3046
> Project: CXF
> Issue Type: Improvement
> Components: Documentation
> Reporter: Robert Liguori
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Suggestion: Make the following refinements to CXF's home page:
> http://cxf.apache.org/. I believe they are all accurate, but they need to be
> verified. Note: Comments are based on 'mainly, but not completely' by
> comparing Apache's CXF main page with this document: "Enterprise Application
> Integration Software Based on Apache CXF - DATA SHEET"
> In "Support for Standards":
> "SOAP 1.1, 1.2, WS-I Basic Profile, WS-Security, WS-Addressing, WS-RM,
> WS-Policy"
> should read
> "SOAP 1.1, 1.2, WS-I Basic Profile, WS-Security, WS-SecureConverstation,
> WS-Trust (partial), WS-Addressing, WS-RM, WS-Policy"
> In "Multiple Transports, Bindings, Data Bindings, and Formats":
> "Transports: HTTP, Servlet, JMS"
> should read
> "Transports: HTTP, Servlet, JMS, Jabber (experimental)"
> In "Multiple Transports, Bindings, Data Bindings, and Formats":
> "Extensibility API allows additional bindings for CXF, enabling additional
> message format support such as CORBA/IIOP"
> should read
> "Extensibility API allows additional bindings for CXF, enabling additional
> message format support such as CORBA/IIOP, CSV and fixed record length"
> In "Flexible Deployment":
> "J2EE integration: deploy services in J2EE application servers such as
> Geronimo, JOnAS,
> JBoss, WebLoic, and WebSphere"
> should read
> "Java EE integration: deploy services in Java EE application servers such as
> Geronimo, JBoss, JOnAS, OC4J, WebLoic and WebSphere"
> In "Flexible Deployment":
> Add:
> "SCA integration: deploy in an SCA container such as Apache Tuscany"
> In "Support for Muliple Programming Languages":
> Add:
> "JAX-RS for RESTful clients"
> In "Support for Muliple Programming Languages":
> Add:
> "Support for SCA with Tuscany"
> In "Code Generation"
> Note: Only 6 of 13 base generation capabilities are listed... consider
> listing the remaining 7.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
