+1
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Aug 9, 2018 at 7:14 AM, Daniel Kulp wrote:
> This is a vote to release CXF 3.2.6.
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecxf-1120/ <
> https://repository.apache.org
My +1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 12, 2015 at 9:53:41 AM, Daniel Kulp (dk...@apache.org) wrote:
This is a vote to release 3.0.4
,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On October 20, 2014 at 11:45:39 PM, cohei...@apache.org (cohei...@apache.org)
wrote:
+ if (!SSLv3.equals(proto
+1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On October 8, 2014 at 3:59:42 AM, Daniel Kulp (dk...@apache.org) wrote:
This is a vote to release CXF 2.6.16
+1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On September 19, 2014 at 9:43:05 PM, Daniel Kulp (dk...@apache.org) wrote:
This is a vote to release
FYI, I just created a JIRA[1], and committed the patch into master and
3.0.x-fixes branches.
[1]https://issues.apache.org/jira/browse/CXF-5999
Regards,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese
-plans-branching-td5744177.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
+1 to change the tools maven packaging to bundle first.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On August 28, 2014 at 2:41:45 AM, Daniel Kulp (dk
It sounds good :)
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On July 23, 2014 at 2:37:55 AM, Daniel Kulp (dk...@apache.org) wrote:
Just a quick query
I ran some tests with apache camel, everything looks good.
Here is my +1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On July 16, 2014 at 3:59:21 AM, Daniel
+1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 31, 2014 at 3:10:51 AM, Daniel Kulp (dk...@apache.org) wrote:
This is a vote to release a 3.0.0
Ran some tests with camel-cxf, every thing looks good.
Here is my +1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On April 9, 2014 at 11:45:09 AM, Daniel Kulp
before CxfRsProducerTest. It can be fixed by changing the test case, I will
update the apache camel master branch to fix the test error.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
After digging the code I found the tests failures was fixed in master and
2.7.x-fixes branches.
The tests can fixed by merge the patch[1] into 2.6.x-fixes branch.
1]https://fisheye6.atlassian.com/changelog/cxf?cs=dd1dc8ae2b163e9a000e51dabbec41024a866069
--
Willem Jiang
Red Hat, Inc.
Web
It’s not pleasure work to merge the patches between the branches in SVN behind
the GFW.
I’m +1 for swathing cxf to git.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http
+1
I just did a quick test by running the Apache CXF 2.7.7 with Camel
2.13-SNAPSHOT.
All the test passed.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
Hi Team,
I just fixed CAMEL-6609[1] by calling the
getConduitSelector().complete(cxfExchange) inside of my custom CallBack method.
But I think I should fix it from CXF.
I tried to add this call into the org.apache.cxf.message.Message.ClientCallback
class, but I found I have to get the
Hi Dan,
It's really helpful.
Thanks,
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
+1 for using Direct Dispatch by default.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
+1
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Please fill a JIRA[1] and share the patch with us.
[1]https://issues.apache.org/jira/browse/CXF
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com
I tried to build the latest version of wss4j with -U option, I still get the
errors.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
Apache CI hit the same issue as I had.
https://builds.apache.org/job/CXF-Trunk-JDK16/1849/console
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com
org.apache.wss4j.stax.securityToken.WSSecurityTokenConstants
……
So I guess you didn't commit you local change of wss4j before you updated the
CXF code.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
On Thursday, May 30, 2013 at 4:15 AM, Daniel Kulp wrote:
On May 27, 2013, at 10:14 PM, Willem jiang willem.ji...@gmail.com
(mailto:willem.ji...@gmail.com) wrote:
I just did a prototype of support Netty transport for CXF, it include
the server side implementation and client side
Hi Dan,
Please check out my comments in line.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
together :)
Any thought?
[1]http://netty.io/
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
It sounds good, here is my +1.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com
+1,
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
+1
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
support.
BTW, CXF supports the Servlet3 async invocation API out of box.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http
in CXF-4953 (https://issues.apache.org/jira/browse/CXF-4953)
to work around it.
We need implement the same interface in jaxrs front end.
[1]https://issues.apache.org/jira/browse/CXF-4953
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
+1
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
don't think there is anything wrong
with it.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
Here is my +1.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
Here is my +1.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
+1,
I did some tests on the camel trunk with cxf-2.7.2, every thing looks good.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
+1 for get more meaningful exception message.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
+1
Willem
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
DefaultSecurityTokenServiceProvider need to use the cxf-rt-ws-security module.
If we remove the import package, it will cause some trouble for us to load the
DefaultSecurityTokenServiceProvider.
On Friday, October 19, 2012 at 8:24 PM, Colm O hEigeartaigh wrote:
I'm also wondering why its
when you
publish the service.
I think we should tell user about it in the README, so they will not be
confused any more.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
Using the system property will effect CXF instance across the JVM.
It could be good if we can do it on the bus level.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
Please check out my comments in the mail.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http
address which you want to use.
With the fabric-cxf[2] component you can do the same thing by leverage the
zookeeper which just implement the feature you need.
[1]http://cxf.apache.org/docs/featureslist.html
[2]http://fuse.fusesource.org/fabric/docs/user-guide.html#CXF_Fabric
--
Willem Jiang
Red Hat
I just ran some tests with Camel trunk, it looks good.
Here is my +1.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http
+1.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
+1
Willem
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
+1. We need to fix the feature issue ASAP.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:312)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http
That's it.
OK, here is my +1.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
I just committed a quick fix for it.
Sergey, if you have time, please double check it.
On Wed Jul 4 08:44:12 2012, Freeman Fang wrote:
Hi Sergey,
This commit break some jaxrs tests in 2.5.x branch, they're
+1,it makes our life easier to share the security parameter beans
across the http conduit.
On Thu Jul 5 19:09:57 2012, Sergey Beryozkin wrote:
Hi Aki,
On 05/07/12 11:58, Aki Yoshida wrote:
2012/7/5 Sergey Beryozkinsberyoz...@gmail.com:
Hi Aki
On 04/07/12 11:59, Aki Yoshida wrote:
Hi,
I
Hi,
As you know CXF management provides a lots MBeans out of box. It works
perfect if it run as stand alone.
If we deploy the CXF endpoints into container like Apache Karaf, we may
hit the issue that Object is already registered. That is because we
don't build up unique Object name for JMX to
?
Thanks.
regards, aki
2012/6/29 Willem Jiang willem.ji...@gmail.com:
Hi,
As you know CXF management provides a lots MBeans out of box. It works
perfect if it run as stand alone.
If we deploy the CXF endpoints into container like Apache Karaf, we may hit
the issue that Object is already registered
REQUEST_URI without affect the ENDPOINT_ADDRESS by using
WebClient API ?
If not, I'm going to update the WebClient API for it.
On Tue May 29 22:40:34 2012, Willem Jiang wrote:
On Tue May 29 22:33:59 2012, Sergey Beryozkin wrote:
Hi Willem
On 29/05/12 14:53, Willem Jiang wrote:
Hi,
I just have
+1
Willem
On 5/31/12 2:15 AM, 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:
Hi Sergey,
JAXRSClientFactory provides the static method to create the proxy or the
client. I didn't find a better way to apply the features to all these
method by just changing a single method.
If you have a better idea, please share it with me.
BTW, I just found my commit introduced a
Hi,
I just have a chance to go through the missing feature of JMS transport
to support cxfrs frontend.
Current JMS transport doesn't send out Message.REQUEST_URI and
Message.HTTP_REQUEST_METHOD properties as the HTTP transport does.
So it hard for use the use the cxfrs frontend with JMS
On Tue May 29 22:33:59 2012, Sergey Beryozkin wrote:
Hi Willem
On 29/05/12 14:53, Willem Jiang wrote:
Hi,
I just have a chance to go through the missing feature of JMS transport
to support cxfrs frontend.
Current JMS transport doesn't send out Message.REQUEST_URI
Hi ,
I just found I forgot to commit merge of r1343561 yesterday. And it was
marked as integrated in CXF-2.4.x branch.
I will commit the patch after running some tests, It could be better if
we redo the CXF 2.4.8 release again.
Sorry for the mass that I made.
Willem
On Wed May 30 06:02:54
I tried to run full test on my box. JDK 1.6 with Maven 3.0.3.
I got the a check style error
cxf/branches/2.5.x-fixes/rt/ws/addr/src/main/java/org/apache/cxf/ws/addressing/ContextUtils.java:492:33:
Nested if-else depth is 4 (max allowed is 3).
Audit done.
I checked the CI it doesn't have this
Hi Dan,
Thanks for the hint, I just commit the new patch to get ride of
blueprint schema.
On Mon May 21 22:41:12 2012, Daniel Kulp wrote:
Willem,
Can we do this without having separate Blueprint and Spring schemas? Since
this is effectively a new schema for both, I'd hate to have 2
It could be more easy to leverage the servlet transport (which could be
used across the web container)
instead of starting the engine inside the CXF.
On Tue Apr 24 08:44:13 2012, Benson Margulies wrote:
On Mon, Apr 23, 2012 at 8:09 PM, Glen Mazzaglen.ma...@gmail.com wrote:
Really? AFAICT
It makes sense.
+1 for it.
On 4/25/12 2:30 AM, Daniel Kulp wrote:
Just wanted to open up a discussion about dropping support for 2.3.x.
2.3.0 was release over 18 months ago. Since then, 2.4.x was released over a
year ago and 2.5.x 6 months ago. (and 2.6 last week). Thus, there has
been
My +1.
Willem
On 3/31/12 12:11 AM, Daniel Kulp wrote:
In preparation for the CXF 2.6.0 release, we need to release a new version
of cxf-xjc that contains the updated plugins and runtime module. Since we
need that, might as well release cxf-buildutils as well.
Only one minor change in
I think we could add more integration tests of OSGi to catch the new
bundle bugs.
I'm willing to help that in the next few weeks :)
On Tue Mar 27 02:17:06 2012, Daniel Kulp wrote:
We're fast approaching 6 months since CXF 2.5.0 was released. The
migration guide keeps getting longer and
Hi Dan,
I did some test by using the http:conduit name=*.http-conduit.
It doesn't work and the created HttpConduit 's getBeanName return null.
I didn't see the http:conduit name=http.* can do the trick.
On Fri Mar 23 19:38:09 2012, Daniel Kulp wrote:
Willem,
Not objecting to this, but
Hi,
It looks some thing wrong on the server side which your client want to
access.
Caused by: java.io.IOException: The https URL hostname does not match
the
Common Name (CN) on the server certificate. To disable this check (NOT
recommended for production) set the CXF client TLS
Sorry, I didn't realized the change has so many side effects.
I will revert the back port patches and find a better solutioni on the
trunk.
On Fri Mar 16 22:48:26 2012, Daniel Kulp wrote:
I'm -1 for this change for 2 reasons:
1) This breaks existing logging configuration and thus cannot be
Hi,
As you know CXF 2.5.3-SNAPSHOT is moving to use WSS4j 1.6.5-SNAPSHOT
I'm trying to install the WSS4J feature of CXF-2.5.3-SNAPSHOT, and I get
the complain about packages of xmlsec cannot be resolved.
I compared the META-INF of the WSS4J 1.6.5-SNAPSHOT and WSS4j 1.6.4 and
found the
Hi Dan,
It's a great news, with the help of git I don't have to wait merge
command for minutes.
Cheers,
Willem
On 2/17/12 1:23 AM, Daniel Kulp wrote:
A couple of you have noticed a flurry of updates to my little DoMerges script
thingy. I'm still tweaking it a bit, but it seems to be in a
I tests these three version of CXF with camel-cxf 2.7.x, 2.8.x and
2.9.x. Everything looks good.
Here is my +1.
Willem
On 12/16/11 4:37 AM, 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
On Tue Dec 13 00:56:21 2011, Daniel Kulp wrote:
On Monday, December 12, 2011 11:41:34 AM Benson Margulies wrote:
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
Hi Aki,
If you take a look at the camel-blueprint [1], you will find the schema
is generated from JAXB annotated class and replace the target namespace
with the blueprint one.
In this way we could reuse the module class as much as possible.
+1
Willem
On 11/4/11 9:58 PM, Freeman Fang wrote:
Hi All,
We've resolved over 35 issues since 2.4.3 and thus is time for a release.
List of issues:
2.4.4:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511version=12318347
The Maven staging areas are at:
2.4.4:
+1,
Willem
On 10/29/11 7:32 AM, Daniel Kulp wrote:
It's been over 6 month since 2.4.0 was released. Since then, we've added
quite a bit of new functionality, new features, enhancements, etc... Thus,
time for a release!
The maven staging area:
I'm afraid you have to use the use the TransportFactory to do such kind
of job.
We always welcome the contributions, please fill a JIRA[1] and attache a
patch for it.
BTW, you can share you code in the github once you replace XMPP library
to be Smack or others.
[1]
Hi Dan,
I think the first option is OK, and it can let the user know what's
wrong immediately.
The other two option will be confused to the user if he just see the
error and the call is succeed.
On Thu Oct 6 09:31:30 2011, Daniel Kulp wrote:
I have a question for folks to see what folks
Spring supports the alias name, if you specify the bean id attribute and
name attribute at the same time, the name value can be the bean's alias
name.
I just did some simple test[1] on the CXF core, it show that CXF support
it out of box.
Please make sure you configure bean as id attribute
On Fri Sep 30 05:39:54 2011, Glen Mazza wrote:
Hi Willem:
On 09/29/2011 01:05 AM, ningji...@apache.org wrote:
Author: ningjiang
Date: Thu Sep 29 05:05:18 2011
New Revision: 1177165
Propchange: cxf/branches/2.4.x-fixes/
+1 for the change.
There are some OSGi tests which are based on pax-exam in
camel/trunk/tests/camel-itest-osgi can be took as an example.
On 9/28/11 3:45 AM, Daniel Kulp wrote:
I'd like to move some modules around in the src tree. Basically, we've been
hanging some stuff off of modules in
Hi monish,
It looks like you doesn't include the cxf.xml, which is important for
the local transport to share the same bus with who generates the
service list.
import resource=classpath:META-INF/cxf/cxf.xml /
On Mon Sep 26 01:09:50 2011, cogitate wrote:
hi willem :
it seems when i try
What's your JDK version and Maven version ?
Using the mvn -v can tell us lots of useful information :)
On Fri Sep 23 09:00:02 2011, Amish Gandhi wrote:
Hi All,
I have commented the failed tests locally (once I get my first build going I
can uncomment it).
But I am still getting failures on
Can you check if you installed any other spring jar in your web
container share lib ?
On Sat Sep 17 03:56:27 2011, marcin.kasinski wrote:
All spring jars are installed within application.
dir ../EnvAdminBackendWS-1.0.car\WEB-INF\lib
...
2011-09-16 21:48 321 190
On Fri Sep 16 09:35:33 2011, Freeman Fang wrote:
On 2011-9-16, at 上午12:56, Daniel Kulp wrote:
Colm and I were discussing this a bit yesterday as well. I'm not
really sure
what to do. :-(
One thought I had was that if we could somehow get the wsdl's (any Mac
TimeMachine users that may have
+1 for we introduce a services module to house these kind of Service
which is based on CXF and can be use out of box :)
It could be helpful for the user to use this kind of Enterprise service
more easily.
On 9/16/11 1:07 AM, Daniel Kulp wrote:
On Thursday, September 15, 2011 3:27:06 PM
Hi,
You just need to change the transport Id.
There is an example about soap over JMS here[1].
[1]http://dl.dropbox.com/u/1623952/soap-jms-example.zip
On Sat Sep 3 16:47:57 2011, marcin.kasin...@gmail.com wrote:
Hello.
I have small question.
I'm using cxf lib with eclipse.
Generating
These modules are released from CXF xjc project, and it is not released
every time before we cut a new version of CXF :)
On 8/30/11 10:00 PM, Robert Liguori wrote:
Just FYI...
In the 2.4.2 release, the following JAR's did not have their names updated:
cxf-xjc-boolean-2.4.0.jar
Which version of CXF are you using ?
You need to make sure the endpoint and client are using the same Bus.
Do you put the endpoint and the client into the same Spring application
configure file ?
On 8/23/11 8:23 PM, mymacin wrote:
Hi,
When I try to use Local Transport instead of Http I
Can I have a look at the whole spring configuration ?
On 8/23/11 8:51 PM, mymacin wrote:
I am using cxf-2.4.0 version.
Sorry Willem.Jiang
Just I removed this topic in cxf-dev forum and I have created new thread in
cxf-user forum.
--
Willem
--
FuseSource
Ran some tests in camel trunk with CXF 2.4.2 they are looking good :).
Here are my +1,
Willem
On 8/12/11 1:07 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.4.1 and thus is time for a release and
over 40 issues ported back for 2.3.5.
This build fixes the issue found with
+1
Willem
On 8/5/11 1:55 AM, Daniel Kulp wrote:
With the upcoming 2.4.2, we need to get new releases of these projects to add
the @threadSafe option on the maven plugins to remove some various warnings in
Maven 3.I'd like to get the votes for these out of the way now to make the
2.4.2
On 7/8/11 6:34 PM, xuhb wrote:
Recently I always encounter a Unexpected end of file from server Exception at
CXF client side. it seems this exception is caused by the CXF Serverside has unexcepted
release the http connection ;
I tried some effort to to use a simple test case to regenerate
On 7/6/11 8:39 PM, Aki Yoshida wrote:
Hi,
There seems to be a problem in working with a spring based CXF
server-side endpoint in OSGi that can lead to a serious stability
issue. I would like to bring up this problem here for discussion so
that we can find a solution to it.
We can expect that an
Hi,
You may the first one who want to use the CXF as WS client in Android.
You can find the more information the CXF third party dependency here[1].
Look luck :)
[1]https://svn.apache.org/repos/asf/cxf/trunk/distribution/src/main/release/lib/WHICH_JARS
On 6/23/11 1:30 PM, Tanveer ul Islam
+1 for it.
BTW,
Camel-CXF doesn't have the direct dependency of JBI transport.
On 6/13/11 7:15 PM, Freeman Fang wrote:
+1
I'll remove the JBI stuff from CXF and add these in Servicemix component.
Freeman
On 2011-6-10, at 下午8:57, Daniel Kulp wrote:
I want to start a discussion about
+1
Willem
On 6/10/11 10:38 AM, Daniel Kulp wrote:
We've resolved over 100 issues since 2.4.1 and thus is time for a release.
This is take #2 fixing the attachment issue I found while testing with Camel.
List of issues:
That is why I suggest to use the github.
He doesn't need anyone to approve :)
BTW, it is more easy to try and test implementation codes with help of git.
On 5/31/11 9:14 PM, Sergey Beryozkin wrote:
Hi
Shenglin submitted ICLA for him be able to start working in the
sandbox, he probably didn't
It's handy feature and I really like it :)
On 5/31/11 8:47 PM, Jean-Baptiste Onofré wrote:
Hi all,
FYI, I fixed KARAF-651.
Now, the features-maven-plugin (and karaf-maven-plugin on Karaf
3.0.0-SNAPSHOT) now embeds by default the Karaf standard and enterprise
features descriptors.
It means
Hi,
What kind of error did you get?
BTW, according the route configure that I got, you should not use the
jaxws:endpoint.
Here is an example[1] in camel that you make take a look.
[1]https://cwiki.apache.org/CAMEL/cxf-example.html
Willem
On 5/18/11 11:58 PM, Harshal wrote:
Hi All,
I am
1 - 100 of 222 matches
Mail list logo