Re: [VOTE] Apache CXF 3.0.10 and 3.1.7

+1 regards, aki 2016-07-26 20:25 GMT+02:00 Daniel Kulp : > > It’s been a long time coming, but we’re finally ready to release > 3.0.10/3.1.7. We’ve resolved over 75 issues for 3.1.7 which is a LOT for a > “.7” release. > > Staging areas: > 3.1.7: > https://repository.apache.org/content/reposi

Re: [VOTE] CXF 3.1.6/3.0.9

+1 regards, aki 2016-03-23 21:48 GMT+01:00 Daniel Kulp : > > It’s been awhile since the last set of releases and we’ve fixed over 45 > JIRA’s (some of which may be needed for the Fediz release) so I’d like to > get this out. > > Staging areas: > 3.0.9: > https://repository.apache.org/content/re

Re: [VOTE] CXF 3.1.5/3.0.8

+1 regards, aki 2016-02-02 22:28 GMT+01:00 Daniel Kulp : > It’s been 3 months since the last patch releases so we really need to get > these out. > > Staging areas: > 3.1.5 > https://repository.apache.org/content/repositories/orgapachecxf-1059/ > 3.0.8 > https://repository.apache.org/content/rep

Re: CXF Client ReceiveTimeout not working on weblogic server

is your 'local' system the same system where your weblogic server runs and has the same jdk and the network setup? could it be that something else is interrupting the connection from your web logic server? 2015-11-19 17:30 GMT+01:00 Tomi Prifti : > Hi, > > I'm setting the receive timeout in cxf W

Re: Drop support for Jetty 8?

+1 sounds good. thanks, regards, aki 2015-11-12 16:40 GMT+01:00 Daniel Kulp : > You may have seen a bunch of updates for 3.2 around getting the Jetty support > updated to allow for Jetty 9.3 (which requires Java 8, BTW). I have all > the tests passing with both Jetty 9.2 and Jetty 9.3 now whi

Re: [3/3] cxf git commit: Update version to 3.2.0-SNAPSHOT

Hi Dan, something seems to have gone wrong during the version number update for the distribution/src/main/release/samples folder? it looks like distribution/src/main/release/samples/pom.xml was not updated and all the child projects seem to have this old parent version value. regards, aki

Re: [VOTE] CXF 2.7.18/3.0.7/3.1.4

+1 aki 2015-10-31 20:52 GMT+01:00 Daniel Kulp : > > This is a vote to release a bunch of patches for CXF. > > Staging areas: > https://repository.apache.org/content/repositories/orgapachecxf-1056/ > https://repository.apache.org/content/repositories/orgapachecxf-1057/ > https://repository.apache.

Re: Releases tomorrow?

w weeks to try to fix this issue. -- Forwarded message ------ From: Aki Yoshida Date: 2015-06-19 18:56 GMT+02:00 Subject: RMStore no longer working in 3.x in some cases To: Dennis Sosnoski Hi Dennis, I think the change that took place along the restructuring of the WS-RM in C

Re: Question about start-level used in cxf's karaf feature entries

rks”. For the most part, “specs” and impls > of specs are very early, (<=20) most other 3rd party things are 25-35, CXF > itself at 40. > > > Dan > > > >> On Oct 21, 2015, at 8:07 AM, Aki Yoshida wrote: >> >> Hi, >> while adding a new featu

Question about start-level used in cxf's karaf feature entries

Hi, while adding a new feature and making sure to use somewhat consistent start-level for the bundles with the existing features, I noticed there are several inconsistent start-level entries: mvn:commons-codec/commons-codec 25 35 mvn:commons-lang/commons-lang none 35 40 mvn:org.apache.servicemix

Re: [VOTE]Apache CXF 3.1.3

+1 Aki 2015-09-17 15:53 GMT+02:00 Daniel Kulp : > It’s been about 6 weeks since the 3.1.2 release and we’ve fixed a bunch of > things that some users have been asking for: > > Tag: > https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=commit;h=f3185100ec7caea0ac4b52108210ed7e68e85271 > > Staging

Re: Describe those bean based features in the features list document page more consistently

nt in italic. And it is explained at the bottom of the table what this means - the entries are sorted by the name for the named entries first, followed by those no-name entries ordered by the simple name of their implementing classes. 2015-08-25 20:16 GMT+02:00 Aki Yoshida : > Or maybe add an extr

Re: cxf git commit: [CXF-6557] add a CORS filter for swagger2 samples

Hi Sergey, yes. Thanks. I saw that. But that is in another dependency and I only wanted to have "allow *" for these demos to be easily accessible, so I opted for just adding a simple filter. regards, aki 2015-08-26 11:20 GMT+02:00 Sergey Beryozkin : > Hi Aki > > Benson added CrossOriginResourceSha

Re: Describe those bean based features in the features list document page more consistently

Or maybe add an extra column to describe the common feature name for each entry. 2015-08-25 20:12 GMT+02:00 Aki Yoshida : > I noticed that the features described in the below features list page > are not very consistently described for those bean based features. > > http://cxf.apa

Describe those bean based features in the features list document page more consistently

I noticed that the features described in the below features list page are not very consistently described for those bean based features. http://cxf.apache.org/docs/featureslist.html variant 1 (GZIPFeature, etc) Name Namespace ... bean ... variant 2 (StaxData

Re: [VOTE] CXF 3.0.6 and 3.1.2

+1 aki 2015-07-28 20:13 GMT+02:00 Daniel Kulp : > This is a vote to release 3.0.6 and 3.1.2. We’ve fixed over 40 issues for > 3.1.2. > > Staging areas: > https://repository.apache.org/content/repositories/orgapachecxf-1049/ > https://repository.apache.org/content/repositories/orgapachecxf-1051

Re: [VOTE] CXF 2.7.17

+1 aki 2015-07-27 21:26 GMT+02:00 Alessio Soldano : > This is a vote to release 2.7.17. It’s been over 2 months since the last > release and we’ve fixed more than 18 issues. > > Staging area: > 2.7.17: > https://repository.apache.org/content/repositories/orgapachecxf-1048/ > > Tag: > 2.7.17: > h

Re: What dataType in Dispatch API should I use to gain best performance?

Hi, Maybe SOAPMessage is slow because you are internally building the object using DOM? I suppose one of the stream based Source variants should perform better. regards, aki 2015-07-16 4:09 GMT+02:00 iris ding : > HI guys, > Looking at the introduction for: > http://cxf.apache.org/docs/jax-ws-disp

Re: [VOTE]xjc-utils 3.0.4

+1 aki 2015-07-09 23:40 GMT+02:00 Daniel Kulp : > This is a vote for the XJC-Utils 3.0.4. This is mostly to release the extra > fixes we need for the bug986 plugin required to get the jetty/netty settings > properly parsed in blueprint. However, it also includes two fixes from > users. > >

Shutting down CXF IBM-JDK jenkins job?

This build hasn't passed for quite a long long time. When I just looked at the error page, it is complaining about some gwt incompatibility that seems to relate to this message. https://groups.google.com/forum/#!topic/google-web-toolkit/MAti0jQqgws But a while ago, when I looked at the error, it

Re: tabs in pom.xml

ially for xml. > > Christian > > > > On 07.07.2015 14:53, Aki Yoshida wrote: >> >> Hi, >> while updating one of the pom.xml files, I noticed there were some TAB >> characters and other pom.xml files also contain TAB characters >> randomly. >> &g

Re: [1/9] cxf git commit: CXF-6046: Enhance SwaggerFeature to support JAX-RS annotations. Replaced embedded Swagger UI with webjar.

Hi Dan, yes. The js scripts temporarily got pushed to the repo while I was cherry picking the original commits one by one. Those js scripts were later removed at one of the commits in the series. I should have squashed those commits into a few before pushing them. regards, aki 2015-07-09 15:06 GM

tabs in pom.xml

Hi, while updating one of the pom.xml files, I noticed there were some TAB characters and other pom.xml files also contain TAB characters randomly. Should we correct them (replacing each TAB with 4 SPs) or keep them in that way? If we agree to fix them, I can do this for all the files. the follow

Re: [VOTE] CXF 3.1.1

Hi Andriy, Thank you for the information regarding cxf-jaxrs-cdi. Then, we keep it that way. regards, aki 2015-06-09 1:17 GMT+02:00 Andriy Redko : > Hi Aki, > > Thanks a lot for trying out cxf-jaxrs-cdi. It is true, it needs CDI dependency > to be present in the OSGi container. There are few rea

Re: [VOTE] CXF 2.7.16 and 3.0.5

Hi Jan, Some of the integration tests have too much dependency to the external causes because of the asynchronous nature of those tests. So, we have some tests sporadically failing and there seem to be a couple of tests that fall into this category more frequently. As a result, the error status of

Re: [VOTE] CXF 3.1.1

+1 but I noticed two minor issues that need to be fixed in the next 3.1.x version. Feature cxf-transports-websocket-server can't get installed out of the box because it was my fault in not noticing earlier that atmosphere 2.3.0 was requiring javax.enterprise.context. (CXF-3.1.0 was using atmosphe

Re: [VOTE] CXF 3.1.0

+1 regards, aki 2015-05-01 19:30 GMT+02:00 Daniel Kulp : > It’s been a year since the 3.0.0 release and we’ve made a bunch of > significant improvements. We really need to get this out. :-) > > This also include the latest cxf-build-utils which allows CXF to import into > the latest Eclips

Re: [VOTE] CXF 2.7.16 and 3.0.5

+1 regards, aki 2015-05-01 19:26 GMT+02:00 Daniel Kulp : > This is a vote to release 3.0.5 and 2.7.16. It’s been over 2 months since > the last release and we’ve fixed more than 70 issues. > > Staging areas: > 2.7.16: > https://repository.apache.org/content/repositories/orgapachecxf-1039/ > 3.0

CXF specific status for Re: [PROPOSAL] Move IRC channel to freenode ?

Hi, I see #apache-cxf available at freenode but there are much less people in there than at #cxf at codehaus. There are more people in #apache-camel and the camel guys already changed the info message shown at the old #camel room at codehaus to display: IMPORTANT - This room is moved to freenode.

Re: HTTP/2 transport for CXF

Hi, I'll add my comments to the jira ticket. regards, aki 2015-04-16 22:22 GMT+02:00 Sergey Beryozkin : > Hi > > Interesting, we chatted with Aki where he did mention HTTP/2, and I opened > > https://issues.apache.org/jira/browse/CXF-6349 > > I guess we are about to witness a higher demand for a n

Re: what is the current status of checkstyle issue in cxf master?

> Might need to ping them. > > Dan > > > >> On Mar 20, 2015, at 8:15 AM, Aki Yoshida wrote: >> >> Hi, >> Yesterday, I upgraded the checkstyle plugin to 6.2 by accident in my >> eclipse setup while intending to upgrade other plugins. After that I &

what is the current status of checkstyle issue in cxf master?

Hi, Yesterday, I upgraded the checkstyle plugin to 6.2 by accident in my eclipse setup while intending to upgrade other plugins. After that I started to get a warning pop up every time I tried to save the working file and it was awful. Then, I remembered this Dan's mail from a while ago. http://cxf

Re: Planning for Java8 trunk

I just checked the release dates of the last 2.4.x, 2.5.x and 2.6.x versions. Closed 2.4.10 05-Oct-2012 Closed 2.5.11 16-Jul-2013 Closed 2.6.16 07-Oct-2014 So I think it is reasonable to expect 2.7.x to be closed sometime later this year, that means to have only a few more releases on 2.7.x. Mayb

Re: cxf jetty blueprint issue (was: [VOTE] CXF 3.0.4/2.7.15)

ion did you use to test this? >> Which Karaf feature have you installed? Have you installed the bundle >> separately too? The bundle is not installed per default in Karaf now. >> >> Thanks for the hint :-) >> >> Regards >> Krzysztof >> >> >>

Re: [VOTE] CXF 3.0.4/2.7.15

+1 Aki 2015-02-12 2:53 GMT+01:00 Daniel Kulp : > This is a vote to release 3.0.4 and 2.7.15. It’s been about 2 months since > the last release and we’ve fixed more than 70 issues. > > Staging areas: > 2.7.15: > https://repository.apache.org/content/repositories/orgapachecxf-1036/ > 3.0.4: > htt

Re: [VOTE] CXF 3.0.4/2.7.15

But this org.apache.aries.blueprint.reflect is available from org.apache.aries.blueprint.core.compatibility, so it isn't a problem of CXF, no? karaf@root()> exports | grep org.apache.aries.blueprint.reflect org.apache.aries.blueprint.reflect | 1.0.0| 14

Re: build failure in systests/jaxrs

Hi Jason, yes. We had this issue that was caused by some inconsistency with jetty8 and jetty9 wiring and it was fixed yesterday. regards, aki 2015-02-06 23:05 GMT+01:00 Jason Pell : > Sorry should have mentioned, I received this building master > > Results : > > Failed tests: > > JAXRSClientCondui

Re: maven setting for cxf build in using com.googlecode.maven-download-plugin behind firewall?

0 Aki Yoshida : > 2015-01-22 12:05 GMT+01:00 Sergey Beryozkin : >> Hi Aki >> On 22/01/15 11:02, Aki Yoshida wrote: >>> >>> Hi Sergey, >>> >>> 2015-01-22 11:27 GMT+01:00 Sergey Beryozkin : >>>> >>>> Hi Aki >>>> >>

Re: [1/5] cxf git commit: Update plugins to use annotations instead of the javadoc things

confirmed. I used 3.2.5 and it's building fine. regards, aki 2015-02-03 11:11 GMT+01:00 Aki Yoshida : > Hi Alessio, > thanks. I'll try with that maven version. > But that means someone has to update the central jenkins build job to > use that maven version as well. > i

Re: [1/5] cxf git commit: Update plugins to use annotations instead of the javadoc things

02-03 11:03 GMT+01:00 Alessio Soldano : > AFAICS, it's a matter of the Maven version being used. Just tried with 3.2.3 > and it works fine. > Could be caused by http://jira.codehaus.org/browse/MNG-5346 . > > Cheers > Alessio > > On 03/02/15 10:34, Aki Yoshida wrote: &

Re: [1/5] cxf git commit: Update plugins to use annotations instead of the javadoc things

It looks like this commit has broken cxf-codegen-plugin in trunk. [INFO] Apache CXF Command Line Tools WSDL to JavaScript Front End SUCCESS [2.062s] [INFO] Apache CXF Command Line Tools WSDLTo JAXB Databinding SUCCESS [1.981s] [INFO] Apache CXF Maven Plugins .. SUCCESS [0.

Re: maven setting for cxf build in using com.googlecode.maven-download-plugin behind firewall?

2015-01-22 12:05 GMT+01:00 Sergey Beryozkin : > Hi Aki > On 22/01/15 11:02, Aki Yoshida wrote: >> >> Hi Sergey, >> >> 2015-01-22 11:27 GMT+01:00 Sergey Beryozkin : >>> >>> Hi Aki >>> >>> Not sure about configuring this plugin, may

Re: maven setting for cxf build in using com.googlecode.maven-download-plugin behind firewall?

and then upon not finding it, use this download plugin to go to the internet, that would be a good option. regards, aki > > Cheers, Sergey > > On 22/01/15 10:14, Aki Yoshida wrote: >> >> the current CXF snapshots uses com.googlecode.maven-download-plugin to >> down

maven setting for cxf build in using com.googlecode.maven-download-plugin behind firewall?

the current CXF snapshots uses com.googlecode.maven-download-plugin to download a remote file during build. The background for this is described in https://issues.apache.org/jira/browse/CXF-6143. I am trying to make this plugin use a local http proxy. I have tried setting those java proxy properti

Re: [VOTE] CXF 2.7.14/3.0.3

+1 Regards, aki 2014-12-03 17:20 GMT+01:00 Daniel Kulp : > This is a vote to release CXF 2.7.14 and 3.0.3. These versions fix a bunch > of bugs users have encountered. They also provide some additional > functionality to make it easier to configure various SSL/TLS things to > mitigate vario

Re: build error in 3.0 systests/jaxrs

I haven't updated my ubuntu box for some time (and I still have 13.10 with JDK 1.7.0_45). On that system, I just ran the test and am seeing the same problem Jason is getting. I am not seeing this problem on my OSX with JDK 1.7.0_67. Does that mean something is incompatible with some Ubuntu or JDK

Re: cxf git commit: Including Ekstazi (www.ekstazi.org) profile to optimize execution of the tests

@Milos, this file usually gets deleted after the test completes, right? And even when the test gets aborted and leaves this file, this will be be deleted in the next test. In that case, this file is currently doing not much harm to the build. We can keep the current pom setting for now and wait fo

Adding profile ekstazi to cxf

Hi, I am adding profile ekstazi to cxf build shortly and wanted to inform you about this. Ekstazi (http://www.ekstazi.org) is a regresssion test tool that can keep track of the test results and the changed code to minimize the number of tests that need to be executed. Maybe some of you have read

Re: Two different tests for isRequestor??

I didn't know there are so many isRequest methods hiding in the code ;-) I knew only MessageUtils's one, which was probably added later after some time. The inconsistency that you observed between AbstractInDatabindingIntereceptor and AbstractOutDatabindingIntereceptor was the result of this patc

Re: xkms test failures

I think you have another karaf instance running on your box. Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" java.lang.RuntimeException: Port already in use: 4; 2014-11-27 3:28 GMT+01:00 Jim Ma : > Hi, > Does anyone hit these fai

Re: [DISCUSS] Remove spring and spring-dm from featues.xml.....

+ 1 sounds good. thanks., aki 2014-11-05 15:40 GMT+01:00 Daniel Kulp : > > For 3.1, I’m thinking about removing the dependencies on spring and spring-dm > from the features.xml file. Right now, if you do a "feature:install cxf”, > you would get spring 3.2 and spring-dm forcibly installed even

Re: [VOTE] CXF XJC Utils 3.0.2

+1 Aki 2014-09-19 15:42 GMT+02:00 Daniel Kulp : > > This is a vote to release the 3.0.2 version of the XJC Utils.There are > two major changes: > > 1) Update the plugin to use all the repositories in the pom to find the > extensions so it can locate extensions that aren’t found in central >

Re: [VOTE] CXF 2.6.15/2.7.12/3.0.1

+1 Aki 2014-07-15 21:57 GMT+02:00 Daniel Kulp : > > This is a vote to release the latest patch releases on all three branches. > > There are over 80 fixes for 3.0.1 with most back ported to 2.7.12 and some to > 2.6.15. > > Note: this is expected to be the last release of the 2.6.x branch. > > T

Re: Performance issue with Content-ID computation of multipart MTOM/XOP messages

I'm not sure whether it is really necessary to make the cid part depend on the namespace string. If we only need to guarantee uniquness within a document, a single thread calling the createContentID method will get a series of unique IDs. However, as the static variable counter is not synchronousl

Re: git commit: [CXF-5866] Adding XMLStreamReaderWrapper to WSDLManagerImpl and providing a XMLStreamReader wrapper that resolves system properties

just to note that there are a few PMD errors with this commit. currently core is failing with PMD errors. 2014-07-10 16:51 GMT+02:00 Jason Pell : > That definitely sounds good. I am so sick of system properties for > configuration. > On 10/07/2014 10:30 PM, "Daniel Kulp" wrote: > >> >> Alessio,

Re: [VOTE] CXF XJC Utils 3.0.1 and buildutils 3.0.0

+1 regards, aki 2014-07-02 17:34 GMT+02:00 Daniel Kulp : > > This is a vote to release our xjc-utils 3.0.1 subproject and our build utils > as 3.0.0. > > Changes for xjc: > [CXFXJC-7] Make sure list types aren't instantiated. > Attempt to workaround JAXB-1026 via some byte bode manipulation. >

Re: git commit: [CXF-5827] Use only local name matching for inbound rpc/literal processing

Hi Dan, yes. I changed it to use the local name comparison so that both unqualified and qualified elements are accepted, where this latter "qualified" case seems to happen frequently in some old implementations in production. The comment lines above that part, which you added in 2007, talks exactly

Re: SOAP over WebSocket

I think there is a gap between mux and what you will need for doing async request-response calls. With mux, you can have multiple websockets layered on a single socket connection. With that, you can queue requests and response multiplexed over a single socket. But this still won't give you a reques

Re: [VOTE] - Release Apache CXF Fediz 1.0.4

+1 Aki 2014-06-11 12:43 GMT+02:00 Colm O hEigeartaigh : > This is a vote to release Apache CXF Fediz 1.0.4. It fixes a couple of > minor issues and contains an upgrade to the latest version of CXF 2.6.x. > > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecxf-1022/ > >

Re: [VOTE] - Release Apache CXF Fediz 1.1.1

+1 Aki 2014-06-11 12:45 GMT+02:00 Colm O hEigeartaigh : > This is a vote to release Apache CXF Fediz 1.1.1. It upgrades to the latest > CXF 2.7.x and fixes a licensing issue with a dependency. > > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecxf-1021/ > > Git tag: >

Re: Build Failure in git

http://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/sec-Disabling_firewalld.html if you have further problems in setting up your fedora system, you should probably ask at the Fedora forum. regards, aki 2014-06-11 6:55 GMT+02:00 Malintha Adikari : > Hi, > > Yes the problem is not en

Re: How to get a public jaxrs.xsd at org.apache.cxf support multiple CXF versions

2014-06-06 17:44 GMT+02:00 Sergey Beryozkin : > Hi Aki, > thanks for the comments, > > On 06/06/14 16:32, Aki Yoshida wrote: >> >> Hi Sergey, >> Maybe, I am not getting the down side of option 1 right. Option 1 >> means, the schema contains some definitions that

Re: How to get a public jaxrs.xsd at org.apache.cxf support multiple CXF versions

Hi Sergey, Maybe, I am not getting the down side of option 1 right. Option 1 means, the schema contains some definitions that are no longer used. I don't know if this is really bad. A component can decide which part to implement and which part to ignore, no? The down side of option 3 is that you w

Re: [VOTE] CXF XJC Utils 3.0.0

+1 2014-05-30 21:10 GMT+02:00 Daniel Kulp : > > This is a vote to release a 3.0.0 version of our XJC utils. > > This fixes a bunch of issues that I’ve found and users have found. It also > updates to the latest JAXB which will help on Java8.All tests pass with > Java8. > > This drops suppor

Re: [DISCUSS] Java 8 and JAXB and 3.0.1

+1 3.0.0 is still very young and having this change in 3.0.1 sounds more reasonable than postponing it to 3.1.0. 2014-05-28 16:41 GMT+02:00 Daniel Kulp : > > There is a new version of JAXB available in central (2.2.10-b140310.1920) > that allows it to work better with Java 8. All the CXF tool

Re: [VOTE] CXF 3.0.0

+1 I forgot to add the karaf feature part for the websocket transport. But this is a minor thing and we can add it in 3.0.1. regards, aki 2014-05-14 22:13 GMT+02:00 Daniel Kulp : > > This is a vote to release CXF 3.0.0.It’s been a long time coming, but I > think it’s ready to be released.

Re: git commit: Reorder some of hte calls to get the createSequence stuff occuring immediately to fix the tests

directly on any issues and emails for now - I'm not receiving > emails from the CXF lists at present. > > - Dennis > > > On 05/07/2014 10:47 PM, Aki Yoshida wrote: >> >> Hi, >> Alessio identified the cause of this problem to be CXF-5726 and I just >>

Re: git commit: Reorder some of hte calls to get the createSequence stuff occuring immediately to fix the tests

Hi, Alessio identified the cause of this problem to be CXF-5726 and I just commented on that ticket about this issue. regards, aki 2014-05-06 20:01 GMT+02:00 Aki Yoshida : > Hi Dennis, > I was wondering about the code change that caused the test error that > lead to this test code chan

Re: RM CloseSequence message with the wrong Sequence header

take from when I was doing the split. I'll take out the added > clause on the if. > > Thanks for catching this, Aki! > > - Dennis > > > On 05/14/2014 08:24 AM, Aki Yoshida wrote: >> >> Hi Dennis, >> I noticed CloseSequence is sent out when the RM

Re: RM CloseSequence message with the wrong Sequence header

committed the correction. 2014-05-14 12:01 GMT+02:00 Aki Yoshida : > Hi Dennis, > after playing around the modified code that omits this handling, I > discovered that that special handling is needed for RM 1.0. because RM > 1.0. has a pseudo CloseSequence behavior using its lastMe

Re: CXF 3.0 builds tomorrow....

ed So this is apparently not a decoupled endpoint issue but just a logging issue. So we can fix it in 3.0.1. regards, aki -- 2014-05-13 23:44 GMT+02:00 Aki Yoshida : > Hi Dennis, Dan, > I think the oneway decoupled WS-RM scenario seems to be working fin

Re: CXF 3.0 builds tomorrow....

Hi Dennis, Dan, I think the oneway decoupled WS-RM scenario seems to be working fine when I look at the client side log transcription. http://pastebin.com/wRReBcqz One error, I believe, that I saw while I was trying out a few other things was the CloseSequence generation. I wrote to the dev list a

RM CloseSequence message with the wrong Sequence header

Hi Dennis, I noticed CloseSequence is sent out when the RM 1.1 endpoint is shutdown for 3.0.0-SNAPSHOT. But it seems that this CloseSequence message is incorrectly generated, including the Sequence header. The message looks like when the endpoint is shutdown after sending two messages (see the Se

Re: git commit: Reorder some of hte calls to get the createSequence stuff occuring immediately to fix the tests

Hi Dennis, I was wondering about the code change that caused the test error that lead to this test code change. I am seeing the following exception in one of my local old scenarios that invokes oneway and request-responser operations in that order. This has been working for 2.7.x and also working

Re: SOAP over WebSocket

y has much less work to do compared to > BE, so usually you need an order of magnitude less instances of it) > > Thanks for your inputs > > > On Tue, Apr 29, 2014 at 3:16 PM, Aki Yoshida-3 [via CXF] < > ml-node+s547215n5743415...@n5.nabble.com> wrote: > >> Hi Pr

Re: SOAP over WebSocket

Hi Przemyslaw, Andrei's blog (the one linked in his earlier reply http://ashakirin-cxf-async.blogspot.de/) has some examples about asynchronous soap calls over HTTP. But the limitation of this approach is that you will need two separate HTTP connections: one from the client to the service and the o

Re: Copy all these properties to RMClient's message ?

Hi Dennis, a combined scenario of ws-rm + ws-sec works fine in general. (and there is a test case in systests/ws-rm that Jim mentioned). But I think Jim is trying to control some of its behavior by passing some properties in the client context and that won't work if those properties are not copied

Re: Copy all these properties to RMClient's message ?

Hi Jim, I think the new client should be using the same context as the original one, as the newly created one is logically still part of the original one. But I'm not sure if all the context needs to be copied into the new one. I noticed this behavior some months ago (something was not set in thos

Re: [VOTE] CXF 2.6.14/2.7.11 - take 2

+1 Aki 2014-04-09 5:44 GMT+02:00 Daniel Kulp : > > > It's been 2 months since the last releases... This is a vote to release > 2.7.11 and 2.6.14. > > There are over 60 issues fixed for 2.7.11 and more than 20 ported back to > 2.6.14. > > > This second attempt fixes the blueprint parsing issues

Re: [VOTE] CXF 2.6.14/2.7.11 - take 2

t; 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 8:15:28 PM, Aki Yoshida (elak...@gmail.com) wrote: >&

Re: [VOTE] CXF 2.6.14/2.7.11 - take 2

I see camel-cxf's CxfRsProducerTest tests (using camel 2.13.0 and trunk) are failing with cxf-2.7.11 and this behavior seems to be caused by https://issues.apache.org/jira/browse/CXF-5610 @Willem, I was wondering if the issue regarding the REST services (mentioned in this ticket) has been resolved

Re: [VOTE] CXF 2.6.14/2.7.11

picked and complained for 2.7.11, I see AuthorizationPolicyHolder in 2.7.10 which is processed fine and this AuthorizationPolicyHolder was removed in the above commit. I am still confused with this symptom, But maybe you have an idea? thanks. regards, aki 2014-04-08 12:14 GMT+02:00 Aki Yoshida : >

Re: SOAP over WebSocket

Hi Przemyslaw, I am not sure if your multiplex case needs websockets or the normal asynchronous soap invocation over http is suitable. Regarding the current websocket support in cxf, it is supported out of the box in the current 3.0.0-SNAPSHOT for some scenarios and this part is documented in the

Re: [VOTE] CXF 2.6.14/2.7.11

I am observing the following error with 2.7.11 for a blueprint jaxws client using basic authentication. Caused by: org.osgi.service.blueprint.container.ComponentDefinitionException: Error setting property: PropertyDescriptor : > > It's been 2 months since the last releases... This is a vote to rel

Re: Couple more CXF 3.0 thoughts.....

no objection. 2014-03-24 19:35 GMT+01:00 Daniel Kulp : > > With 3.0 getting really close, I do realize this is kind of last minute, but > wanted to throw these out real quick. > > Would anyone object to removing all the SOAP over TCP stuff that is currently > in the SOAP binding? It was a pr

Re: WS-RM and WSDLGetInInterceptor

Hi Alessio, People thank you for spotting this error :-) I just integrated the fix to 2.7.x. regards aki 2014-03-10 15:14 GMT+01:00 Alessio Soldano : > Thanks Aki, just seen your commit :-) > > > On 10/03/14 11:20, Aki Yoshida wrote: >> >> Hi Alessio, >> Just lo

Re: WS-RM and WSDLGetInInterceptor

Hi Alessio, Just look at the code and I think the problem s the RMDeliveryInteceptor sometimes gets inserted behind OutputGoingInterceptor, as it only specifies the phase condition and not the before condition. I think using the correct rule should fix this issue. I can look at it to see if that's

Re: WS-RM client callback property

ges have been acknowledged yet. > > - Dennis > > > On 02/17/2014 10:14 PM, Aki Yoshida wrote: >> >> Hi Dennis, >> >> right. It would be useful to make some information conveniently >> available to the calling client. >> >> But we might want to

Re: [VOTE] Apache CXF 3.0.0-milestone2

+1 regards, aki 2014-02-15 3:01 GMT+01:00 Daniel Kulp : > > This is a vote to release 3.0.0-milestone2 > > This has a bunch of more updates targeting 3.0 including a fully revamped JMS > transport, fully revamped WS-RM system, updates to WS-Security, JAX-RS > updates, some more deprecated API'

Re: WS-RM client callback property

Hi Dennis, right. It would be useful to make some information conveniently available to the calling client. But we might want to provide a callback not just for getting the ack status but for getting various other WS-RM information such as the sequence ID, message number and even some control ove

Re: [VOTE] CXF 2.6.13/2.7.10 (attempt 2)

+1 Aki 2014-02-06 19:29 GMT+01:00 Daniel Kulp : > > > This is a vote to release 2.6.13 and 2.7.10. > > For 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 a 2.2 runtime. Also has a couple > other minor fixes. > > Both builds also

Re: [VOTE] Apache CXF 2.7.10

+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 a 2.2 > runtime. Also has a couple other minor fixes. > > > Staging area: > https://repository.apache.org/content/repo

Re: [VOTE] Apache CXF 2.7.9/2.6.12

+1 Regards, Aki 2014-01-29 Daniel Kulp : > > > We've resolved over 60 issues since 2.7.8 and almost 40 ported back to 2.6.12. > > > List of issues: > 2.6.12 > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12325599 > 2.7.9 > https://issues.apache.org/jira/secur

Re: Discuss: Switching cxf to git

+1 I am using git-svn and it is a little bit of pain to sync the svn props when down porting changes. (and this is resulting in superfluous commits in the commits list of 2.7.x and even more in 2.6.x). So I also would prefer to switching to plain git. regards, aki 2014/1/22 Christian Schneider

Re: issue with schema loading in spring

aki 2013/12/16 Daniel Kulp : > > On Dec 16, 2013, at 8:13 AM, Aki Yoshida wrote: > >> Hi Dan, >> just saw CXF-5181 which switched to use the relative paths for imports. >> [CXF-5181] Use relative paths in imports so blueprint validation can >> work without long st

Re: issue with schema loading in spring

g. So I suppose those schemas can get loaded locally even when the locations are kept as absolute as long as if you are not using an older Aries BP core like 0.3.2. I'll check on this. regards, aki 2013/12/16 Aki Yoshida : > Hi Dan, > thanks for your input. > > In that cas

Re: issue with schema loading in spring

could revert them back. > > Dan > > > On Dec 11, 2013, at 6:06 AM, Aki Yoshida wrote: > >> I noticed a problem of loading a certain xsd schema in spring and I >> identified the cause. But as I remember that we have had a few rounds >> of changes in the pas

issue with schema loading in spring

I noticed a problem of loading a certain xsd schema in spring and I identified the cause. But as I remember that we have had a few rounds of changes in the past and I would like to ask you if the suggested fix makes sense. The problem occurs when I try to look up the schema for namespace "http://w

Re: [VOTE] 3.0.0-milestone1 distributions...

+1 aki 2013/11/26 Daniel Kulp : > > This is a vote for the actually distributions to go along with the > 3.0.0-milestone1 release that is already in central. > > Staging area: > https://repository.apache.org/content/repositories/orgapachecxf-008/ > > Now already part of the 3.0.0-milestone1 tag:

Re: [VOTE] Apache CXF 2.7.8/2.6.11

+1 tested OK with cxf-2.7.8 with current camel and olingo. and with some manual tests on equinox. the only minor thing I noticed was the build/test order that causes the fresh clean install to fail at xkms.itests, as xkms.itests gets executed before osgi/karaf is built and consequently the cxf fea

  1   2   3   >