+1
Willem
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
+1
Willem
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
+1
Willem
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/se
Hi，
Did you compare the two messages ?
Here are some useful links[1][2] for your debugging.
[1] http://cwiki.apache.org/CXF/testing-debugging.html
[2] http://cwiki.apache.org/CXF20DOC/debugging.html
Please feel free to ask more specified question :)
Willem
liucong wrote:
> Hi all,
>
> I'm wo
Hi,
CXF uses the WSDL4J to parser the WSDL, I think you just need to add the
the SOAP/JMS extension yourself.
I think the override rule is implemented by the CXF ServiceModel[1],
if you configure a interceptor on the bus , you can override it from
service, or from endpoint, etc.
So , you just ne
Hi
I think MTOM message should have the attachment info, we could check
that for it. We have some trouble to send the MTOM message if we send
the message in Text model, and Liu Cong is working on the patch.
Willem
Daniel Kulp wrote:
> Doesn't it already support MTOM?
>
> Basically, it provides
configuration of the JMS message type,
and make sure the JMS message type is BytesMessage, if not, the JMS
transport will throw an Exception for it.
Any thought?
Willem
Daniel Kulp wrote:
> On Wed May 6 2009 9:15:54 am Willem Jiang wrote:
>> Hi
>>
>> I think MTOM message shoul
.
BTW, Freeman did some work to make the JMS transport support MTOM[1]
[1] http://issues.apache.org/jira/browse/CXF-1760
Willem
Willem Jiang wrote:
> Hi,
>
> If we defer the creation of JMS Message until we know the Content-Type
> for the client, we still need to flight with the miss c
will be sent as
> ByteMessage.
>
> Willem Jiang wrote:
>> After digging the code, I found we could know if the Message has
>> attachments by looking the message in the JMSConduit.sendExchange()
>> method. We can tell if the message is MTOM enabled and has the
>> atta
Hi,
ActivmeMQ provides a failover transport[1] which could support this
feature out of box. You just need to setup right connection URL with it
in you JMS endpoint configuration.
[1] http://activemq.apache.org/failover-transport-reference.html
Willem
Christian Schneider wrote:
> Hi Hubert,
>
>
+1
Willem
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 releas
Hi Sergey,
I'm working on integrating the CXF JAXRS with Camel, and just found
there are some elements which are defined in the JAXRS client are useless.
such as
Did I miss something ?
Thanks,
Willem
most likely made it into jaxrs:server as a result of copying
> from jaxws:endpoint. We may end up adding some of these
> elements/attributes back, but at the moment we just don't use them...
>
> thanks for raising the issue on the dev list
> Sergey
>
>
> -Orig
s using serviceBeans (using a List programmatically).
> But I do agree
> It can be handy using @serviceClass when only a single resource class is
> used, this simplifying a configuration a bit.
>
> Thanks, Sergey
>
> -Original Message-
> From: Willem Jiang [mailto:
result of copying
> from jaxws:endpoint. We may end up adding some of these
> elements/attributes back, but at the moment we just don't use them...
>
> thanks for raising the issue on the dev list
> Sergey
>
>
> -Original Message-
> From: W
Maybe we also need to introduce a JAXRSBindingConfiguration for it :)
Willem
Willem Jiang wrote:
> Hi Sergey,
>
> I noticed there is a JAXRSBindingFactory in the cxf-jaxrs-frontend,
> but you remove the bindingId attribute from the .
>
> After checking the code of AbstractJ
Hi Sergey,
I just added some unit tests to verify the spring parser of
JAXRSServerFactoryBean and JAXRSClientFactoryBean.
I found the ModuleRef does not work on the JAXRSClientFactoryBean side,
Could you take a look at it if you get time?
Here is the spring configuration file of it[1].
[1]
http
Hi Sergey,
If you remove the comment and wrong the test of
JAXRSClientFactoryBeanTest, you will see the error :)
It looks like the resource checking can't find any resource info from
the setting.
Thanks,
Willem
Sergey Beryozkin wrote:
> Hi Willem
>
> Thanks for this commit, just would like to c
Hi,
It may relate to your default maven repository directory "C:\Documents
and Settings\jason\". It has space in the maven repository directory,
which will cause the process starting error.
Willem
liucong wrote:
> Hi all,
>
> I have encountered a question when I run the JUnit test in eclipse.
>
Hi,
I think you mean how to throw the fault from the JMS transport.
Basically , if you throw the fault from a CXF interceptor, CXF's
interceptors chain will take care of it and build the fault message and
throw it out.
If you want to check the Content type , you could write an interceptor
and loa
Hi Dan,
LiuCong created a wiki page[1] of his project working status on apache
wiki , he doesn't have the write right of cwiki.apache.org/CXF, neither
to me (njiang) :(. Could you grand the karma for us? So we can move the
page into CXF.
I just talked to LiuCong today on IRC , he will creates so
+1,
Willem
Daniel Kulp wrote:
> This may be a "thorny" issue, but I'd like to bring it up and start a
> discussion.
>
> July 4th will mark the 2 year anniversary of the CXF 2.0 release. Since
> then, we have released 11 patches to that branch, along with 2.1 (and 5
> patches for it) and 2
liucong wrote:
> Hi,
>
> Willem Jiang Writes:
>> Hi,
>>
>> I think you mean how to throw the fault from the JMS transport.
>> Basically , if you throw the fault from a CXF interceptor, CXF's
>> interceptors chain will take care of it and build the fault messa
I just want to find a way without any configuration, and soap jms
transport can use it out of box.
Willem
liucong wrote:
> Hi,
>
> Willem Jiang 写道:
>> Hi,
>>
>> I think you mean how to throw the fault from the JMS transport.
>> Basically , if you throw the fa
+1
Willem
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 helpin
Hi,
Forward this mail to the dev mail list.
liucong wrote:
> Hi,
> I have added a simple interceptor in the SOAP binding. If the
> transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
> interceptor will be added. But I have some question for that:
> 1. I feel a little wei
Hi,
You added a wrong schema, your schema should like this
Hi LiuCong,
I applied your patch on my local workspace, the jms system tests are
failed, I fixed some of them.
But there is still an error , if you are online today, please ping me.
Willem
Daniel Kulp wrote:
> Liu,
>
> Just to let you know, I plan on looking at a lot of this early next week
>
I guess you have something wrong on the plugin's pom.
Maybe you need to show the code to let us help you :)
Willem
liucong wrote:
Hi,
I am writing a plugin for xjc.
First I just modify the cxf-xjc-ts and cxf-xjc-ts-test, and make it
work with the -Xwsdlextension, not -Xts. The pom file
svn:http://svn.apache.org/repos/asf/cxf/trunk/common/xjc/wsdlextension-test
scm:svn:https://svn.apache.org/repos/asf/cxf/trunk/common/xjc/wsdlextension-test
Willem Jiang wrote:
I guess you have something wrong on the plugin's pom.
Maybe you need to show the code to let u
Hi,
I think this is a bug of CXF, if the user define the extension in the
service and binding,
we should use the service's value.
Willem
liucong wrote:
> Hi all,
>
> In the
> SOAP/JMS(http://www.w3.org/TR/2008/WD-soapjms-20081121/#wsdl-11-properties).
> If a property is specified at multiple l
Hi,
Can you submit a test case for it ?
BTW, is there anything wrong with creating the server from this WSDL ?
Willem
liucong wrote:
> Hi all,
> When I implement the WSDL usage for SOAP/JMS, I encountered an exception.
> I create an service and invoke it using wsdl-first.
>
> If the wsdl file l
Hi
Since SOAP/JMS test suit could work with the other SOAP/JMS implementation,
I think we should not just write the test against CXF stack.
We could leverage the spring template and listener to implement the
generation of
the test JMS message, check the response JMS message.
In this way the tes
Hi,
I think its OK to use the Message Id pattern by default for the
interoperation
with the other SOAP/JMS implementation, if there is no correlation id is set
on the JMSMessageHeader.
Willem
liucong wrote:
> Hi,
>
> Should I change to use Message ID Pattern and make it compatible with
> the s
Hi,
You can choice what you want to generate the correlationID, and you
just need to make sure the CorrelationID is unique.
In you proposal, you give the user a choice to set the correlationID
from the JMSMessageHeader which he set, it's OK for me.
For the useConduitIdSelector, it's just for the
+1,
Willem
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 releas
+1
Willem
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://repositor
+1,
Willem
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/fixforv
Hi Benson,
I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
to create a durable subscriber jms destination.
Added a sleep make the test passed again :)
Willem
Benson Margulies wrote:
Can't someone do something about:
Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Ti
aniel Kulp wrote:
On Thu August 27 2009 10:06:33 pm Willem Jiang wrote:
Hi Benson,
I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
to create a durable subscriber jms destination.
Added a sleep make the test passed again :)
Willem, Thanks for tracking that down. I cou
er the jms destination started
to see if it works?
Willem
Daniel Kulp wrote:
On Fri August 28 2009 8:34:46 pm Willem Jiang wrote:
Hi Dan,
Maybe we need to switch the JMS broker to use the VM transport instead
of the TCP transport for the Unit test.
Sure. I have no idea how to do it. :-)
We hi
My +1.
Willem
Daniel Kulp wrote:
This is a vote to release CXF 2.1.7
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.6 release. Over 25 JIRA issues
are resolved for 2.1.7
List of issues:
The Maven staging area is at:
https://reposi
+1.
Willem
Daniel Kulp wrote:
This is a vote to release CXF 2.2.4
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.3 release. Over 59 JIRA issues
are resolved for 2.2.4.
List of issues:
https://issues.apache.org/jira/browse/CXF/fixfo
+1
Willem
Daniel Kulp wrote:
This is a vote to release CXF 2.1.8
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.7 release. Over 25 JIRA issues
are resolved for 2.1.8
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote
+1,
Willem
Daniel Kulp wrote:
This is a vote to release CXF 2.2.5
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.4 release. Over 90 JIRA issues
are resolved for 2.2.5
List of issues:
The Maven staging area is at:
https://repository
+1
Willem
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 answering some questions
+1.
Willem
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
Willem
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/ReleaseNote
+1
Willem
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 patches
are all very complete with excellent unit te
+1
Willem
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:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12314534&styleName=Html
Hi kevin,
It's an interesting project, I'd like to be your mentor.
But before we begin the project, I'd like you to go through the
ZooKeeper web site this week to find a general way of implementing the
location transparency and clustering.
Cheers,
Willem
kevin wrote:
> Hi all,
>
> My name
Hi Glen,
I'm sorry you are late, maybe we can wait for another student to apply
this project next time :)
Willem
Glen Mazza wrote:
Hmmm, I wonder if we could get Kevin to implement a Secure Token Service for
us (CXF-1940) instead, and if we could get Willem to mentor him for that as
well.
oc2010-cxf2738-proposal-discussion
Best Regards,
Kevin Wu.
Willem Jiang wrote:
Hi kevin,
It's an interesting project, I'd like to be your mentor.
But before we begin the project, I'd like you to go through the
ZooKeeper web site this week to find a general way of implementing the
Hi Seumas,
Please see my comments in the mail.
Seumas Soltysik wrote:
I am trying to get support for using the JMS MessageID as the JMS CorrelationID
as specified in https://issues.apache.org/jira/browse/CXF-2760 . After putting
some work/thought into this issue, I became aware that this featu
handle the asynch scenario. As opposed to having a
listener per thread, it would be better to have a pool of listeners which could
be allocated as individual threads make asych calls. A workqueue is not going
to help with this issue.
Regards,
Seumas
____
From: Wi
Hi Seumas,
I'm sorry to reply your mail so late, please check out my comments in
the mail.
Seumas Soltysik wrote:
There are a couple of elements in the JMSConduit code on the trunk
that are troublesome.
First of all there is the use of the outstandingAsync data member.
Effectively it keeps t
+1
Willem
Daniel Kulp wrote:
As mentioned earlier in the week, I'd like to get 2.2.8 released which
contains some WS-SC fixes that are needed for Dennis' next Developerworks
article. That said, 2.2.8 does contain over 44 other fixes and enchancements
as well which are valuable for everyone.
+1
Willem
Daniel Kulp wrote:
This is a vote to release CXF versions 2.0.13, 2.1.10, and 2.2.9. The main
reason for the releases is to fix a potential security vulnerability that will
be disclosed soon. That is why 2.0.13 and 2.1.10 are included despite us not
really "supporting" those bra
Hi,
Daniel Kulp wrote:
I'd like to try and get a handle on what is needed to get 2.3 out the door.
It's really long, long overdue. The things I can think of off the top of
my head:
1) JAX-WS 2.2 - we're close on this, just need to figure out a few more
things.
2) JAX-RS 1.1 - Sergey:
Daniel Kulp wrote:
On Thursday 15 July 2010 2:33:26 pm Benson Margulies wrote:
The first part of the JIRA I filed above is easy: make a new project that
depends on jetty 7 instead of 6.
I'm somewhat rusty after that. A profile in systests to use it? Where is
the default transport established (w
Hi Sergey,
CXF JMS transport is base on Spring JMS template now, so even you remove
the spring dependency of JMSConfiguration. You can't let the
cxf-jms-transport work without Spring :(.
What's your plan about it ?
Willem
Sergey Beryozkin wrote:
Hi
I'm looking at the issue to do with the
+1
Willem
Daniel Kulp wrote:
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.9 release. Over 55 JIRA issues
are resolved for 2.2.10.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315110&styleName=Htm
Hi
I just did some work to let the camel-cxf leverage the CXF continuation
framework which you did. I just found current CXF continuation which
suspend is implemented by throw the runtime exception. This
implementation has a shortcoming which cannot call the other framework's
async API after
Hi Dan,
Daniel Kulp wrote:
On Thursday 02 September 2010 9:32:46 am Willem Jiang wrote:
Hi
I just did some work to let the camel-cxf leverage the CXF continuation
framework which you did. I just found current CXF continuation which
suspend is implemented by throw the runtime exception. This
er 2010 10:02:50 am Willem Jiang wrote:
Hi Dan,
Daniel Kulp wrote:
On Thursday 02 September 2010 9:32:46 am Willem Jiang wrote:
Hi
I just did some work to let the camel-cxf leverage the CXF continuation
framework which you did. I just found current CXF continuation which
suspend is implemented by
On 9/9/10 10:57 AM, Daniel Kulp wrote:
On Wednesday 08 September 2010 9:08:36 pm Willem Jiang wrote:
...
I'm afraid I had to introduce other status into interceptor chain like
SUSPEND, it will move the interceptor iterator to the preious one and
through the SuspendedInvocationException
Hi Jim
On 9/14/10 1:27 PM, Jim Ma wrote:
Hi all ,
After this commit, the SoapJMSInInterceptor is added to check the
"SOAPJMS_conentType" and other key/value pairs in message header . It
requires the "SOAPJMS_contentType" and other properties added in the
jms message. Are such header (jms messa
On 9/14/10 4:01 PM, Jim Ma wrote:
We already replaced "http://cxf.apache.org/transports/jms"; with
"http://www.w3.org/2010/soapjms/"; in SOAPBindingFactory:
if ("http://cxf.apache.org/transports/jms".equals(config.getTransportURI()))
{
info.setTransportURI("http://www.w3.org/201
On 9/14/10 4:16 PM, Willem Jiang wrote:
On 9/14/10 4:01 PM, Jim Ma wrote:
We already replaced "http://cxf.apache.org/transports/jms"; with
"http://www.w3.org/2010/soapjms/"; in SOAPBindingFactory:
if
("http://cxf.apache.org/transports/jms"
Hi Dan
On 9/14/10 11:06 PM, Daniel Kulp wrote:
On Tuesday 14 September 2010 8:47:34 am Willem Jiang wrote:
On 9/14/10 4:16 PM, Willem Jiang wrote:
After checking the change log and the chat log, I found why we have the
upper codes. The upper codes is try to support to specify the address
with
Hi Dan,
I agree with you and will commit a patch with your suggestion shortly.
Willem
On 9/15/10 9:23 AM, Daniel Kulp wrote:
On Tuesday 14 September 2010 8:58:27 pm Willem Jiang wrote:
Hi Dan
On 9/14/10 11:06 PM, Daniel Kulp wrote:
On Tuesday 14 September 2010 8:47:34 am Willem Jiang wrote
On 9/17/10 10:43 PM, Daniel Kulp wrote:
We've now challenged the last few remaining JAX-RS 1.1 tests. We're waiting
to see if the challenge is accepted or not (and it's going to be slow due to
JavaOne), but that pretty much means we're really close to having JAX-RS 1.1
stuff ready. JAX-WS 2.2
On 9/20/10 9:23 AM, Benson Margulies wrote:
Willem,
If you've been reading the email, you'll see that I've hit a snag in
using the JAX-WS API to create a client proxy over JMS in the
java_first_jms sample. If you'd care to dive in and see if you can fix
the sample (or some bug in the underlying
On 9/20/10 8:00 AM, Benson Margulies wrote:
That doesn't change the strange 'no endpoint' error. Do you have any
hints for how to track this down, or do you JMS hackers want to pick
up from here?
The no endpoint error is caused by you set a wrong PortName :)
As the SEI doesn't have the @WebServi
On 9/29/10 4:06 AM, Daniel Kulp wrote:
On Monday 27 September 2010 9:44:25 pm Benson Margulies wrote:
It looks like our close and personal relationship with Spring
continues to really inconvenience very few and serve the majority. I
wonder if we would want to invest energy in merely designing so
day, September 29, 2010 01:19 PM
To: dev@cxf.apache.org
Subject: Re: Fun with the survey
+1 on an osgibus, that would be great.
On Sep 28, 2010, at 8:10 PM, Willem Jiang wrote:
On 9/29/10 4:06 AM, Daniel Kulp wrote:
On Monday 27 September 2010 9:44:25 pm Benson Margulies wrote:
It looks like our clo
On 10/2/10 5:25 AM, Daniel Kulp wrote:
I'd still like to get 2.3 released next week if possible. However, there are
still some things to do:
1) JIRA triage - could everyone please look through the JIRA items that would
fall into your area and see if any of them are resolved. I'd like to get
It's done. My bad of forgetting to resolve the issue.
On 10/6/10 12:07 AM, Daniel Kulp wrote:
Willem,
Is
https://issues.apache.org/jira/browse/CXF-2948
now resolved? There is a SVN commit for it so I THINK it is, but wanted to
check. If it is, can you mark it resolved.
Thanks!
--
Wille
Just ran some tests with Camel 2.5-SNAPSHOT, everything looks good.
Here is my +1.
On 10/8/10 4:44 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.10 release. Over 56 JIRA issues
are resolved for 2.2.11.
List o
+1.
It's good to see we have a CXF committer from GSOC :)
On 10/31/10 12:20 AM, Sergey Beryozkin wrote:
Hi
I'd like to initiate a vote for Tomasz Opanovicz to become a CXF committer.
As you may recall, Tomasz became known in the CXF community after starting
to work on the Log Browser project
Here is my +1.
On 11/17/10 6:35 AM, Sergey Beryozkin wrote:
Hi
I'd like to initiate a vote for Łukasz Moreń to become a CXF committer.
You may recall that Łukasz came forward and proposed to have OAuth 1.0
implemented in CXF as part of GSOC 2010.
During GSOC 2010 Łukasz tried his best to comp
Hi,
I did some clean up work[1] on the CxfRsInvoker in Camel to let it work
better with CXF 2.3.0 continuation API.
Current JAXRSInvoker is not friendly to extends, and the method
public Object invoke(Exchange exchange, Object request)
is stateful and can't be called by the continuation resume
On 11/18/10 8:49 PM, Sergey Beryozkin wrote:
Hi Willem
thanks for working on it. The patch looks fine.
Can you just explain please why the changes are needed given that
JAXRSContinuationsTest is passing at the moment.
I just went through the JAXRSContinuationsTest, it doesn't test the
getSubRe
cover the
stats of ResourceProvider and ServiceObject in the exchange to make the
JAXRSInvoker.invoke() method recallable.
[1]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/CxfRsRouterTest.java
cheers, Sergey
On Thu, Nov 1
On 11/23/10 1:56 AM, Sergey Beryozkin wrote:
Hi
I've found out, while working with CXF Continuations API recently is that
continuation.suspend()
is returning normally and no SuspendedInvocationException is thrown.
This is unexpected in that now, when continuation.suspend() is used directly
in
Here is my +1,
Willem
On 12/2/10 12:01 PM, Daniel Kulp wrote:
In the last 2 years, Colm has logged 11 issues with CXF. Every single one of
them came with a patch file to fix the issue:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&reporterSelect=specificuser&reporter=co
+1,
Willem
On 12/2/10 9:51 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.11 release. Over 43 JIRA issues
are resolved for 2.2.12.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=
+1.
Willem
On 12/2/10 9:54 AM, Daniel Kulp wrote:
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.3.0 release. Over 55 JIRA issues
are resolved for 2.3.1.
Note: this vote also includes a release of the cxf-buildutils to fix some
com
Hi Freeman,
I think as there is no Content-Encoding/Accept-Encoding "JMS Message
Properties" defined in the specs, we are safe to extends the gzip
support in soap over jms.
If the server doesn't support the gzip encoding, CXF client can adjust
itself, as this extension is not in the spec.
Hi Dan,
I will try to work with sonatype to get jaxb 2.2.2 into the central repo
today, then I will revert the change as you suggested.
Willem
On 12/9/10 10:46 PM, Daniel Kulp wrote:
I'm -1 to this.
If the deps are not in central, we should not be depending on it. If we
want to upgra
Hi Freeman,
Maybe you need to use mvn clean first like this
mvn clean test -Dtest=TestClassName
On 12/17/10 4:07 PM, Freeman Fang wrote:
Hi,
Today I experience a wired problem when I try to run a single test with
what I always do like
mvn test -Dtest=TestClassName
But I just get error like,
To get all the CXF dependencies bundles to be OSGi ready is not an easy
thing, that is why ServiceMix spends lots of time to wrap the bundles
itself.
By using these bundles with Karaf will save lots of your time, and with
the Service CXF features you can install these bundles just by typing a
Hi Dan,
I had to admit that the issue is introduced by the new added test
PolicyEngineImplInitTest.
I think you already fix it just before I commit my fix :)
Willem
On 12/27/10 8:53 PM, dk...@apache.org wrote:
I'm -1 to this as it fixes the wrong thing. We need to find the test that is
le
Yes, set the transport ID can do the trick.
Here is the CXFEndpoint configuration which can be used to set up the
camel-cxf endpoint.
address="jms:jndi:dynamicQueues/request"
transportId="http://www.w3.org/2010/soapjms/";
serviceClass="org.apache.camel.component.cxf.HelloService">
Wil
implementation to disable the checks that
cause these problems. Of cause cxf is not absolutely compliant to the
spec in this case but I think the customers will not care too much about
this.
Best regards
Christian
Am 07.01.2011 01:14, schrieb Willem Jiang:
Yes, set the transport ID can do the trick
nt. I will create an issue to track this.
Btw. Do you know why the interceptor is in the soap binding and not in
the jms transport? To me what it does sounds very jms specific.
Christian
Am 07.01.2011 11:19, schrieb Willem Jiang:
Hi Christian,
Maybe we can introduce some configuration to let th
Hi
Which version of CXF are you using?
If you are using CXF 2.3.x, you can use the JMS_URI[1] for the address,
even you don't choice SOAP over JMS[2].
[1]http://tools.ietf.org/id/draft-merrick-jms-uri-09.txt
[2]http://cxf.apache.org/docs/soap-over-jms-10-support.html
Willem
On 1/12/11 11:17 P
Can you check if the server send the response back?
There are some tips[1] that you may take a look.
[1]http://cxf.apache.org/docs/debugging-and-logging.html
On 1/19/11 11:21 AM, cxfuser71 wrote:
Hello All,
I am using JBoss 6.0.GA release which comes with CXF webservice stack
(version 2.3.1).
I
Maybe we can consider to release XJC 2.3.2 as it doesn't relate to TCK
failures. And we don't need to cut new version of XJC 2.3.2 again.
Can we start a new vote for CXF XJC 2.3.2 ?
Willem
On 1/20/11 11:02 AM, Jim Ma wrote:
I have to vote -1 for this release.
The new changes in tagged CXF 2.3.
Hi Dan,
Yeah, JDK ships the CORBA implementation.
But if the customer doesn't want to the JDK's one and use other ORB
implementation, these imports mandatory will cause some trouble and
customer had to modify the etc/jre.properties of karaf himself.
Willem
On 1/24/11 11:05 PM, Daniel Kulp w
1 - 100 of 308 matches
Mail list logo
