Re: [VOTE] Release CXF 2.0.12

2009-08-02 Thread Freeman Fang

+1

Freeman
On 2009-7-30, at 上午1:36, Daniel Kulp wrote:



This is a vote to release CXF 2.0.12

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.11 release.   Over 32 JIRA issues
are resolved for 2.0.12

*Note:* as announced earlier this will be the last 2.0.x release of  
Apache

CXF.   Users are encouraged to start migrating to 2.2.x.


List of issues:
https://issues.apache.org/jira/browse/CXF/fixforversion/12313903

The Maven staging area is at:
https://repository.apache.org/content/repositories/cxf-staging-001/

The distributions are in:
https://repository.apache.org/content/repositories/cxf-staging-001/org/apache/cxf/apache-cxf/2.0.12/

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.12


Here is my +1.   The vote will be open here for at least 72 hours.

--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog



--
Freeman Fang

Open Source SOA: http://fusesource.com



Re: [VOTE] Release CXF 2.1.6

2009-08-02 Thread Freeman Fang

+1
Freeman
On 2009-7-30, at 上午1:54, Daniel Kulp wrote:




This is a vote to release CXF 2.1.6

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.5 release.   Over 74 JIRA issues
are resolved for 2.1.6


List of issues:

The Maven staging area is at:
https://repository.apache.org/content/repositories/cxf-staging-002/

The distributions are in:
https://repository.apache.org/content/repositories/cxf-staging-002/org/apache/cxf/apache-cxf/2.1.6/

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.6


Here is my +1.   The vote will be open here for at least 72 hours.

--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog



--
Freeman Fang

Open Source SOA: http://fusesource.com



Re: [VOTE] Release CXF 2.2.3

2009-08-02 Thread Freeman Fang

+1

Freeman
On 2009-7-30, at 上午1:56, Daniel Kulp wrote:



his is a vote to release CXF 2.2.3

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.2 release.   Over 86 JIRA issues
are resolved for 2.2.3.


List of issues:
https://issues.apache.org/jira/browse/CXF/fixforversion/12313983

The Maven staging area is at:
https://repository.apache.org/content/repositories/cxf-staging-003/

The distributions are in:
https://repository.apache.org/content/repositories/cxf-staging-003/org/apache/cxf/apache-cxf/2.2.3

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.2.3


Here is my +1.   The vote will be open here for at least 72 hours.


--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog



--
Freeman Fang

Open Source SOA: http://fusesource.com



Re: SOAP/TCP server-side

2009-08-02 Thread Krzysztof Wilkos
2009/7/27 Daniel Kulp dk...@apache.org:

 Krzysztof,

 On Fri July 24 2009 6:35:12 pm Krzysztof Wilkos wrote:
 We've got working client for SOAP over TCP protocol. It was tested
 with .Net service. It still needs some improvments and more
 documentation but my second task for GSoC is writting server side so I
 have to hurry up.
 I need a piece of advice about SOAP/TCP server side design. I'm
 thinking about using MINA together with CXF inside Spring.

 MINA is definitely the way to go.   Good idea.

 In
 architecture guide there's just few words about destinations.  I know
 that I have to write DestinationFactory and Destination classes.

 You may NOT have to write the DestinationFactory thing.   Since this is very
 soap specific, it's proabably would be preferred to add this into the soap
 binding like the soap/jms stuff.    The soap binding already has a
 DestinationFactory registered.   The createDestination calls in there would
 just need updating to detect when soap/tcp is needed (url scheme?) and create
 yours.

 Are
 there any other nessesary classes? How I have to register my
 DestinationFactory so that it would be avaiable from
 DestinationFactoryManager?

 Normally in spring via the META-INF/cxf/cxf-extension-XX.xml files.   Take
 a look at those.  However, if put into soap binding, it's already done.

 --
 Daniel Kulp
 dk...@apache.org
 http://www.dankulp.com/blog


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 choose 1.x we will have more work in the future. I hope that they
provide stable MINA 2.0.0 before we release CXF with SOAP/TCP so I
started with 2.0.0-M6 but I can still switch to 1.x if you want.

-- 
Krzysztof Wilkos