On Sun August 2 2009 10:12:36 am Krzysztof Wilkos wrote:
> 2009/7/27 Daniel Kulp :
> We didn't decided which MINA version we will use. 2.x branch has new
> features and performance improvements but still there are no stable
> realease. There are API differences between 1.x and 2.x branch so if
> we
We have 8 (7 binding) +1 votes and no other votes.
+1: dkulp, asoldano, jgenender, sberyozkin, ningjiang, eglynn, seanoc, ffang,
This vote passes. I'll get the artifacts promoted.
Dan
On Wed July 29 2009 1:36:27 pm Daniel Kulp wrote:
> This is a vote to release CXF 2.0.12
>
> Once again,
We have 9 (8 binding) +1 votes and no other votes.
+1: dkulp, asoldano, jgenender, sberyozkin, ningjiang, eglynn, seanoc, ffang,
jimma
This vote passes. I'll get the artifacts promoted.
Dan
On Wed July 29 2009 1:54:05 pm Daniel Kulp wrote:
> This is a vote to release CXF 2.1.6
>
> Once a
We have 8 (7 binding) +1 votes and no other votes.
+1: dkulp, asoldano, jgenender, sberyozkin, ningjiang, eglynn, seanoc, ffang,
This vote passes. I'll get the artifacts promoted.
Dan
On Wed July 29 2009 1:56:28 pm Daniel Kulp wrote:
> his is a vote to release CXF 2.2.3
>
> Once again, ther
Honestly, I'm not sure you can. Under most circumstances in CXF, we don't
ever create the SAAJ based SOAPMessage. Thus, it would never be available.
If you add in the SAAJInInterceptor, we would create it, but that's not really
exposed to the context that the endpoint would get. Two way
