+1
On Tue, Jun 17, 2008 at 4:44 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> This is a vote to release CXF 2.0.7
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.0.7 release. Over
+1
--
Pawel Lipka
IT Architect
AMG.net businesstechnology consulting
http://www.amg.net.pl
Łąkowa 11, 90-554 Lodz, tel/fax (42) 296 11 32
Tresc niniejszej wiadomosci moze byc poufna. Jezeli nie jestescie Panstwo
jej adresatem, to rozprowadzanie lub wy
Now that 2.1.1 is being voted on, I'd like to step back a bit and talk
a little about ideas for the next versions.
First, most likely, we'll need to do a 2.1.2 release in about 6-8
weeks (and maybe 2.0.8 as well). We've done a very good job of
getting fixes out to our users in a timely
+1
2.0.7 fix the bug CXF-1642 :)
--G
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.7
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.7 release. Over 48 JIRA issues are
resolved
I like the idea of custom annotations for making the Java-first stuff
work better.
On Wed, 2008-06-18 at 11:17 -0400, Daniel Kulp wrote:
> Now that 2.1.1 is being voted on, I'd like to step back a bit and talk
> a little about ideas for the next versions.
>
> First, most likely, we'll need to
Daniel Kulp wrote:
5) OSGi stuff - I know there are some OSGi enhancements in the works
that could be pulled in:
a) osgi http transport - this currently lives in ServiceMix, but
could be pulled into CXF to work with other OSGi runtimes
b) Distributed OSGi (RFC 119) - there is work being
I would really like to see good osgi integration as we plan to rely
quite heavily on osgi in the future. But as I myself are only starting
on this I don´t know much about the details. Basically I would like to
be able to connect the osgi internal services with cxf to communicate
with the outsi
I think our WSS4J interceptors really need to support "nonces"--IIRC
according to WS-Security w/UsernameToken profile web service calls
aren't really secure if those aren't included with the username,
password, and timestamp. I am still not sure if WSS4J supports the SAML
Token Profile, but that wo
Christian Schneider wrote:
I would really like to see good osgi integration as we plan to rely
quite heavily on osgi in the future. But as I myself are only starting
on this I don´t know much about the details. Basically I would like to
be able to connect the osgi internal services with cxf t
