Perhaps a few items can be removed from Developers (placed under subtopics),
as a solid majority of CXF users will not be developing CXF so not as many
top-level links are necessary. Having too many links there may also confuse
people as they mistake "Developers" as Java coders using CXF instead
I like all the changes EXCEPT the removal of the Mailing Lists.I really
don't consider the mailing lists as a "support" thing as, at Apache, the
mailing lists are a very important part of the entire community and is the
primary way for people to be involved with the community. I would
+1 (no binding) for CXF 2.2.9 (tested in OW2 JOnAS)
Regards,
Florent
Alessio Soldano wrote:
+1
After a couple of local changes, I see no regressions in the
jbossws-cxf testsuite using CXF 2.2.9.
Cheers
Alessio
Daniel Kulp wrote:
This is a vote to release CXF versions 2.0.13, 2.1.10, and 2
We have 13 +1 votes and no other votes. Thus, this vote passes. I'll get
the artifacts released.
Thanks!
Dan
On Wednesday 02 June 2010 1:46:39 pm Daniel Kulp wrote:
> This is a vote to release CXF versions 2.0.13, 2.1.10, and 2.2.9. The
> main reason for the releases is to fix a potentia
Hi
On Mon, Jun 7, 2010 at 12:47 AM, Łukasz Moreń wrote:
> I was thinking about how to configure oauth authentication in cxf,
> below are my thoughts and doubts:
>
> 1. Oauth service provider needs to expose endpoint URLs for clients:
> Request Token URL, User Authorization URL and Access Token UR
