cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-3046) Refine Apache CXF technical content on main page of web site: http://cxf.apache.org/
Date Thu, 07 Oct 2010 17:05:31 GMT

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

Daniel Kulp resolved CXF-3046.
------------------------------

       Resolution: Fixed
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


I've made the changes mentioned above that really are applicable.  I didn't do the SCA changes
as nothing CXF does at this point really involves SCA.   The Jabber thing I just made  link
to the Camel/CXF docs to explain all of those. 

I also didn't put the fixed/csv change in as no-one has ever done anything with that for CXF.


That all said, I would HIGHLY encourage you to submit and ICLA ( http://apache.org/licenses/icla.txt
) which would allow us to grant you edit access to this site.  Thus, any technical details
that you find missing or inadequate, you could just fix.   Probably would take less time than
filing a JIRA anyway.  :-)

> 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
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: Invalid
>
>   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.


Mime
View raw message