+1
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.0.11
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.10 release. Over 36 JIRA issues
are resolved for 2.0.11.
List of issues:
https://issues.apache.org/jira/secure/Rele
+1
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.1.5
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.4 release. Over 87 JIRA issues
are resolved for 2.1.5.
List of issues:
https://issues.apache.org/jira/secure/Release
+1
-- Ulhas
Daniel Kulp wrote:
his is a vote to release CXF 2.2.1
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2 release. Over 55 JIRA issues
are resolved for 2.2.1.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNot
Hi Bharat,
Looks like you are trying to use client side to act as server so what
you need is creating a Destination (similar to what you have done at
server side for the response)
-- Ulhas
Bharath Gargesh wrote:
Hi Dan,
I wanted to write my own transport, but then I saw your reply to this th
+1,
--Ulhas
Eoghan Glynn wrote:
Folks,
I'm calling a second vote to release CXF Distributed OSGi 1.0.
The main differences between this and the first take are:
- addition of a sources distro
- LICENSE file now contains references to licenses for 3rd party dependencies
- removal of extran
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.2.2
With only 23 JIRA's resolved for 2.2.2, this doesn't have as many "fixes" as
many of the previous patch releases. HOWEVER, there is a one major new
feature: the JAX-RS 1.0 TCK now passes. Thus, it's worth a release. :
I think I also casted my +1 but don't see in the list.
-- Ulhas
Daniel Kulp wrote:
We have +1 votes from:
dkulp, bganesh, sberyozkin, willemjiang, davidb, seanoc, eglynn, ffang,
schneider.
and no other votes.Thus, this vote passes. I'll start getting the stuff
synced to central and th
+1,
-- Ulhas
Daniel Kulp wrote:
Alessio has been one of the primary driving forces behind getting CXF to be a
certified JAX-WS provider for JBoss. As part of that work, he has identified
several bugs/issues in CXF and has provided patches for many of them. He has
also been helping in the co
+1,
-- Ulhas Bhole
Eoghan Glynn wrote:
Folks,
I'm calling a vote to release CXF Distributed OSGi 1.1.
The dOSGi subproject of CXF provides the Reference Implementation of the
Remote Services Specification version 1.0, Chapter 13 in the OSGi Compendium
Specification [1].
The release
+1,
-- Ulhas Bhole
Daniel Kulp wrote:
Cyrille has submitted several patches to various management and logging
related things for CXF starting way back in February. I think he's up to 7
or 8 submitted patches.He's also been hanging around the user list for
almost a year answ
+1,
--ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.1.9
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.8 release. Over 43 JIRA issues
are resolved for 2.1.9
*Note:* as announced earlier this will be the last 2.1.x release
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.2.6
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.5 release. Over 78 JIRA issues
are resolved for 2.2.6.
List of issues:
https://issues.apache.org/jira/secure/ReleaseN
+1,
-- Ulhas Bhole
On 10 Mar 2010, at 14:29, Daniel Kulp wrote:
David's been doing a good job lately of answering questions on the
mailing lists and getting involved there. He's also submitted
several high
quality patches for the ws-security and security-policy stuff. The
p
jaxws http://cxf.apache.org/schemas/jaxws.xsd";>
Regards,
Ulhas Bhole
+1,
-- Ulhas Bhole
On Fri, Mar 19, 2010 at 1:21 AM, Daniel Kulp wrote:
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.2.6 release. Over 55 JIRA issues
> are resolved for 2.2.7.
>
> List of issues:
>
> h
JConsole.
I will try your route.
Regards,
Ulhas Bhole
On Thu, Mar 18, 2010 at 10:05 PM, Eoghan Glynn wrote:
> Ulhas,
>
> How are you picking up the config file?
>
> For example, if you're running the server via ant, you'd need to change the
> server target
Hi Eoghan,
I did a few tests and it looks like if I try to connect to the process from
JConsole it doesn't show CXF JMX stats. If I create a new connection using
JMX URL and username/password (cxf/cxf) I do see the CXF MBean appearing.
Thanks for the help.
Regards,
Ulhas Bhole
I just
Thanks Eoghan,
I will try it out.
Regards,
Ulhas Bhole.
On Fri, Mar 19, 2010 at 11:34 AM, Eoghan Glynn wrote:
> A-ha, my bad, I assumed you were using the remote process option ... so you
> just can't see the CXF MBeans when you connect via the jconsole local
> process option?
&
+1,
-- Ulhas Bhole
On Thu, Dec 15, 2011 at 8:37 PM, Daniel Kulp wrote:
>
>
> We've resolved over 75 issues since 2.5.0 and thus is time for a release.
> We've also ported back over 40 of the fixes to 2.4.5 and 30 of those to
> 2.3.8.
>
> List of issues:
> 2.
+1,
Ulhas Bhole
On Wed, Nov 20, 2013 at 4:20 PM, Daniel Kulp wrote:
>
> We've resolved over 75 issues since 2.7.7 and almost 35 ported back to
> 2.6.11.
>
>
> List of issues:
> 2.6.11
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1
+1,
-- Ulhas Bhole
On Wed, Nov 20, 2013 at 9:28 PM, Daniel Kulp wrote:
>
> We’ve done quite a lot of work toward 3.0.0. While we still have work to
> do, I think it’s a good idea to get a stable milestone release out that
> users can depend on to start testing some of the n
+1,
--Ulhas Bhole
On Thu, Nov 28, 2013 at 12:59 AM, Freeman Fang wrote:
> +1
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
> On 2013-11-27, at 上午1:26, Daniel Kulp wrote:
>
> >
> > This is a vote fo
+1,
-- Ulhas Bhole
On Wed, Feb 5, 2014 at 1:53 PM, Aki Yoshida wrote:
> +1
>
> Aki
>
> 2014-02-05 Daniel Kulp :
> >
> > This is a vote to release 2.7.10. This is mostly to fix the JAX-WS 2.2
> problems in the 2.7.9 release that would not allow it to work as
+1,
--Ulhas Bhole
On 6 Jun 2015 02:19, "Daniel Kulp" wrote:
> 3.1.1 fixes a bunch of issues in 3.1.0 that would prevent it from working
> properly in several normal use cases, particularly in OSGi.
>
> Staging area:
> https://repository.apache.org/content/repositories/o
+1
--Ulhas Bhole
Daniel Kulp wrote:
This is a vote to release CXF 2.1.
Obviously, this is a pretty big release with a bunch of new things like
JAX-WS 2.1 support, the JAX-RS stuff, the javascripts stuff, the CORBA
binding from yoko, etc
Of course, the other MAJOR new feature: it'
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.0.6
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.5 release. Over 20 JIRA issues are
marked as resolved for 2.0.6.
Of course, the other MAJOR new feature: it's no lo
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.1.
Obviously, this is a pretty big release with a bunch of new things like
JAX-WS 2.1 support, the JAX-RS stuff, the javascripts stuff, the CORBA
binding from yoko, etc
Of course, the other MAJOR new feature: it's no longer
+1
--Ulhas
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 for 2.0.7 which is a large n
+1
--Ulhas
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.1.1
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1 release. Over 74 JIRA issues are
resolved for 2.1.1 which is a large numbe
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
Regards,
Ulhas Bhole
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
+1
-- Ulhas
Daniel Kulp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.8
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.8 release. Over 28 JIRA issues
are resolved for 2.0.8. Most importa
Hi Dan,
I also had the same problem. I don't see the edit button anywhere even
if I am logged on.
Regards,
Ulhas Bhole
Daniel Kulp wrote:
On Sunday 10 August 2008 2:57:45 pm Benson Margulies wrote:
For some reason,
http://cwiki.apache.org/confluence/display/CXF/Buildingdoesn'
+1,
--Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.1.2
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release. Over 67 JIRA issues
are resolved for 2.1.2.
List of issues:
https://issues.apache.org/jira/secure/Release
Regards,
Ulhas Bhole
Christian Schneider wrote:
In the issue CXF-1668 Eduard reported that CXF uses the system
encoding for JMS Messages. This is wrong as most times messages are to
be transmitted using UTF-8.
I want to build a patch for this issue but need some conceptional help.
When we receive
t original
message was encoded in.
Regards,
Ulhas Bhole
Ulhas Bhole wrote:
Hi Christian,
The place Eduard mentioned in Jira is correct. I was looking at this
JIRA sometime back but had the same problem of how to determine
encoding type. JMS TextMessage doesn't contain any encoding
info
I think this is happening on some unclean/old snaspshot. I also got this
yesterday but after my low level clean alternative (find . -name
"target" | xargs rm -rf) followed by svn update cured the problem and
didn't see it again.
-- Ulhas Bhole
Willem Jiang wrote:
It i
separate pool of listeners for scalability.(I don't
know how the JMS callback works so will need to look into it more)
Regards,
Ulhas Bhole
Freeman Fang wrote:
Any thoughts?
Cheers
Freeman
Freeman Fang wrote:
Hi,
Currently we are using sync way for jms transport which means the
threa
ok at how we can integrate both (SPEC/JMS and
spring jmsTemplate together) in CXF JMS transport. I would surely be in
favor of the new transport which would be more flexible than the current
one.
Regards,
Ulhas Bhole
Freeman Fang wrote:
Hi Ulhas,
Thanks.
How about we introduce Spring JmsTempla
Hi Christian,
comments inline...
-- Ulhas
Christian Schneider wrote:
Guillaume Nodet schrieb:
Commons-pool is not a JMS connection pool.
I was mostly thinking about the ActiveMQ one, but i think each JMS
provider should have its own connection pool. In a Java EE
environment, the connection p
+1
-- Ulhas
Daniel Kulp wrote:
Christian has been doing quite a bit of very good work doing an almost "ground
up" re-write of the JMS transport which is a very challenging and complicated
task.
He's done quite a bit of work documenting various JMS things on the Wiki and
even wrote an article
+1
-- Ulhas
Willem Jiang wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a vote to release CXF 2.0.9
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.0.9 release. Over 37 JIRA issues
are resolved for 2.0.9 which is a large
+1,
-- Ulhas
Willem Jiang wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.2 release. Over 51 JIRA issues
are resolved for 2.1.3.
List of issues:
https://issues.apache.org/jira/brow
+1,
-- Ulhas
Willem Jiang wrote:
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.2 release. Over 52 JIRA issues
are resolved for 2.1.3.
List of issues:
https://issues.apache.org/jira/browse/CXF/fixforversion/12313354
The staging area
+1,
I have worked with David in past and he will surely be an asset to CXF
given the knowledge he would bring in on general WS-* stuff and mainly OSGI.
-- Ulhas
Eoghan Glynn wrote:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches
I indeed is worng. Please raise a jira and someone will surely take a
look. (probably me but need to find some time.)
-- Ulhas
Peter Liljenberg wrote:
We tried to use soapheaders by adding a HeaderProcessor. When looking at the
CXF code (2.1.2) we find this:
HeaderProcessor p = bus.getExtens
+1,
-- Ulhas
Daniel Kulp wrote:
Since it's been about 4 months since the 2.0.9 release, I decided to go ahead
and do a 2.0.10 release along with 2.1.4.
This is a vote to release CXF 2.0.10
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.1.4
With a longer than normal cycle, a LOT of stuff is in this. Over 88 JIRA
issues are resolved for 2.1.3 which is quite a bit of work.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313463
+1
-- Ulhas
Daniel Kulp wrote:
(The issue with the J2EE has been corrected. This is a new vote on the new
artifacts)
Since it's been about 4 months since the 2.0.9 release, I decided to go ahead
and do a 2.0.10 release along with 2.1.4.
This is a vote to release CXF 2.0.10
Once again, t
+1
--Ulhas
Daniel Kulp wrote:
(The issue with the J2EE has been corrected. This is a new vote on the new
artifacts)
This is a vote to release CXF 2.1.4
With a longer than normal cycle, a LOT of stuff is in this. Over 88 JIRA
issues are resolved for 2.1.3 which is quite a bit of work.
+1,
-- Ulhas Bhole
Sergey Beryozkin wrote:
As you all know we've been looking for people to help us with our JAXRS
project for a while. We've had some great feedback
and a number of patches submitted from our JAXRS users which helped us
tremendously. Andrzej Michalec (Andy) has b
I am +1 on the idea because of the more regular latest snapshots.
-- Ulhas
Daniel Kulp wrote:
They've recently setup the hudson instances to allow them to deploy snapshots
to the Nexus instance using a special "snapshot" account. Thus, we could now
have automated builds that do deploys of sna
+1,
-- Ulhas
Daniel Kulp wrote:
This is a vote to release CXF 2.2
This release is a major step forward for CXF with several new features
including:
* WS-SecurityPolicy support
* WS-SecureConversation
* Some WS-Trust support (client side)
* JAX-RS 1.0
along with MANY other improvements a
+1,
-- Ulhas Bhole
On 30 May 2012, at 19:15, Daniel Kulp wrote:
>
>
> We've resolved over 90 issues since 2.6.0 was released. We've back ported
> over 70 of them to 2.5.4 and 40 to 2.4.8 and 25 to 2.3.11.
>
>
> List of issues:
> 2.3.11:
>
+1 for both branching out and dropping Java 5 Support.
Regards,
Ulhas Bhole
On 5 Jun 2012, at 10:11, Colm O hEigeartaigh wrote:
> +1.
>
> I intend on introducing streaming WS-Security support in 2.7, which will
> depend on Santuario 2.0 and WSS4J 2.0, both of which are slate
+1,
-- Ulhas Bhole
On 20 Jun 2012, at 00:22, Oliver Wulff wrote:
> It's been over 6 months since work started on Fediz and it's time for the
> first
> release. The features in this release are:
>
> * WS-Federation 1.0/1.1/1.2
> * SAML 1.1/2.0 Tokens
+1,
-- Ulhas
On 15 Aug 2012, at 02:20, Daniel Kulp wrote:
>
> We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
> release.
>
> List of issues:
> 2.4.9
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
> 2.5.5
> https://issu
+1,
-- Ulhas Bhole
On 22 Aug 2012, at 15:27, Daniel Kulp wrote:
>
> The Karaf features.xml file that was released with 2.5.5 is corrupt which is
> preventing it from actually being usable to install CXF 2.5.5 into Karaf.
> This vote is just to release a new features file (ver
+1,
-- Ulhas Bhole
On 24 Aug 2012, at 18:02, Glen Mazza wrote:
> Hi all, this new release provides significant documentation updates within
> the samples as well as new sample keys to help clarify necessary trust
> requirements. Oli has also gotten some programmatic fixes/enhanc
58 matches
Mail list logo
