Re: [VOTE] Apache CXF 3.5.2 and 3.4.7

+1 Thanks!

Re: [VOTE] Apache CXF 3.5.3 and 3.4.8

+1 Thanks!

Re: Please update 4.0-SNAPSHOT

Hi Vladimir, the reason for that is that the build is failing since then: https://ci-builds.apache.org/job/CXF/job/CXF-JDK17-deploy/ Will take a look... Dennis

Re: Please update 4.0-SNAPSHOT

Hi Andriy, I think you are close, the errors are just Javadoc-related for Swagger and Jetty 9. Great work so far, really unfortunate that I didn't found the time to contribute... Best, Dennis

Re: [VOTE] Apache CXF 3.4.9 and 3.5.4

+1 Greetings from ApacheCon New Orleans :-) Dennis

Re: [VOTE] - Move Apache CXF DOSGi to the attic

+1

Re: Deprecate aegis databinding ?

Hi Jim, good call out. The first I can think of is aegis databinding. Is the aegis databinding still used by CXF users ? Is it a good time to deprecate and remove in the future release ? I liked the databinding in the past but nowadays JAXB is the standard. To get an indication who else migh

Re: [VOTE] - Andriy Redko as CXF PMC Chair

Am 02.08.2024 um 16:54 schrieb Colm O hEigeartaigh: As Dan has confirmed he is stepping down, this is a vote to ask Andriy Redko to become the next CXF PMC Chair. +1

Re: [VOTE] Apache CXF 3.1.10

+1 -- View this message in context: http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-3-1-10-tp5776820p5776828.html Sent from the cxf-dev mailing list archive at Nabble.com.

Timeline for 3.2.0 or 3.1.11 release

Hi, what is the timeline for the next release? Currently there is no CXF release that is usable with Spring Boot 1.5.x. In JIRA there are still 22 issues left for 3.2.0, so maybe it's a good idea to release 3.1.11 soon. Cheers Dennis

Re: Timeline for 3.2.0 or 3.1.11 release

Hi, is there anything that prevents a 3.1.11 release? Please let me know if a can help with something... Cheers Dennis

Re: 3.1.11/3.0.13 tomorrow

Great to hear this. Could you please accept the PR for CXF-7316 before building the release? Cheers Dennis

Re: [VOTE] Apache CXF 3.1.11 and 3.0.13

+1

Re: New security advisories for Apache CXF

Hi, OWASP dependency check still reports CVE-2012-5786 and it's not on the list. Should we add it? Regards Dennis

Re: New security advisories for Apache CXF

> It's not a bug - that advisory was just raised against a sample that CXF > ships with. I know, unfortunately the dependency check reports it as soon as any CXF dependency is present (try mvn org.owasp:dependency-check-maven:check to reproduce). If failBuildOnCVSS is set, the build will fail un

Re: String to CXF SoapMessage Conversion

Hi! > I'm working on a project which requires converting a String representation > of a SOAP message to CXF SoapMessage. Is there any way to achieve that? Use Stax to parse it. If you need helper methods check StaxUtils. Regards Dennis

Re: String to CXF SoapMessage Conversion

Btw: please use the users list for further discussion. It's not necessary to post to both lists.

Re: New security advisories for Apache CXF

> Could you file an issue with the OWasp plugin instead to remove this CVE > from their list (if this is possible - I'm not sure how they are pulling > down advisories)? The plugin downloads the NVD CVE data hosted by NIST. So to get rid of it, the configuration pattern cpe:2.3:a:apache:cxf:-:*

Re: CXF support for JDK8

Hi Himanshu, JDK 8 is supported and working without problems for me. The docs need to be updated. Regards Dennis

CXF on builds.apache.org/analysis

Hi, the Sonar instance that is linked on http://cxf.apache.org/automated-builds.html is no longer active. I would setup a separate Jenkins job for the new installation on https://builds.apache.org/analysis. Any objections? Cheers Dennis

Re: CXF on builds.apache.org/analysis

Analysis is now done by this Jenkins job: https://builds.apache.org/view/A-D/view/CXF/job/CXF-Master-Analysis/ Results are available here (I also updated the link on the Wiki page): https://builds.apache.org/analysis/dashboard/index/org.apache.cxf:cxf Each developer should login once otherwise

Re: A fault found while use CXF.

Hi! > Just like the following pictures. There are no pictures attached. Please check the logs for error messages and include the message in your posting. Cheers Dennis

Re: Getting Full Address of Server?

> Is there a way to ascertain the full address of a server created with > JAXRSServerFactoryBean? For example, if I only set the address to "/foo", > is there any way to know that the full address is actually " > http://10.1.1.1/cxf/foo";? You can get the Address from EndpointInfo or use the publ

Re: Removing old Swagger code from the master

Definitely +1

Re: commons-lang3

Hi Alessio! > What do you think about us trying to upgrade to recently released > velocity 2.0 in master, before releasing 3.2.0, so that we can have only > commons-lang3 dependency ? +1 but it's not published to central yet, is it? Regards Dennis

Re: cxf git commit: fixed test

Hi Sergey, thanks, I already noticed that changing the order doesn't really fix it. What about the other flapping tests? SequenceTest is frequently failing, RequestResponseTest sometimes runs into timeouts, XKRSSDisableTest has ports conflicts if another build is running in parallel. Cheers De

Re: cxf git commit: Update maven-surefire-plugin and maven-failsafe-plugin

Hi Colm, how to reproduce this? There was a successful build on Jenkins after the change: https://builds.apache.org/view/A-D/view/CXF/job/CXF-Trunk-JDK18/2661/ Cheers Dennis

Re: cxf git commit: Update maven-surefire-plugin and maven-failsafe-plugin

Hi Colm, sorry for that. Looks like this is the related issue: https://issues.apache.org/jira/browse/SUREFIRE-1302 I've reverted to 2.18.1 and added the link so that we can try again after 2.20.1 is released. Regards Dennis

Re: Wrong url for release notes for 3.1.11

Just noticed that https://cwiki.apache.org/confluence/display/CXF/CXF+3.1.11+Release+Notes still mentions that JDK 7 must be installed (JDK 8 also works fine). The link points to JDK 6 download page. I'll fix this.

Re: [VOTE] Apache CXF 3.1.12 and 3.0.14

+1 Dennis

Gitbox

Hi, Infra recently optimized the GitHub integration by providing a new service: http://gitbox.apache.org Merging pull requests would be much easier. What do you think about migrating to it? Regards Dennis

Re: Gitbox

I already replied yesterday, somehow Ponymail seems not to deliver anything at the moment, so I try again... > We'd obviously all have to update the URL's for our local repos, is that it? Basically yes, I don't see any disadvantages. See this thread for experiences in Accumulo project: https://l

Re: [VOTE] - Release Apache CXF 2.6.17

+1

Re: Gitbox

Thank you for summarizing, Dan. +1 for filing the ticket. Cheers Dennis

Re: CXF 3.2?

Good plan. I'd like to see support for Swagger/ OpenAPI Spec 3.0.0 in CXF 3.2 but we should postpone it if no updated swagger-core library is available by Sept 1st. Regards Dennis

Re: [VOTE] CXF build utils 3.3.0 and xjc-utils 3.2.0

+1

Re: cxf git commit: improved Swagger description

Hi Sergey! > I guess the feature would check the properties at the configurable > 'swaggerPropertiesLocation', with "/swagger.properties" being the > default one, and then use them to set the simple Swagger properties > which has not been already set by SwaggerFeature setters ? Yes, this makes se

Re: cxf git commit: improved Swagger description

Hi Sergey! > Thanks, I've done some initial work on it, next step is to update again > the scan demo to show the auto-discovered feature can be initialized > from the properties, but I'd like to keep your demo code and migrate it > to a simple spring_boot demo, hope you are OK with it, will let yo

Re: cxf git commit: improved Swagger description

Hi Sergey! > Have a look please when you get a chance Only one minor thing: What I noticed is that it's no longer possible to leave license/ license url null, in this case it's currently always set to Apache License. If it's used for APIs in a company environment they will not have a license, so

Re: cxf git commit: improved Swagger description

Hi Sergey! > Before my update they were set to Apache values by default, thus it was > impossible to detect if there was a need to check the properties for the > default values or not. > Now with the code I did, if no license is needs, it should be enough to > set the license value only to "", no

Re: cxf git commit: improved Swagger description

Hi Sergey! > I'll just introduce an internal property to track the setLicense call > and make sure that setLicense(null) works as before in 3.1.x. That's working now. > Let me do it first. After that, do we want to keep the default license > value/url in 3.2.0 ? I would drop it to simplify the

Re: CXF 3.2?

Ok, just pushed some dependency updates and will try to fix some bugs until Tuesday. Btw. as this will be a new major version, we should involve Sally to prepare a press release. Regards Dennis

Re: CXF 3.2?

> The spring-boot-sample-rs-scan-app example is failing. Can someone look at that? Just fixed it. Cheers Dennis

Re: cxf git commit: fixed NPE

> Thanks Dennis, you were right when you were talking about simplifying > > the code and having the default licenses removed :-)> Hehe never mind, I should have reviewed the code instead of just testing the functionality... :-) Regards Dennis

Re: [VOTE] Apache CXF 3.2.0

+1 (non-binding)

Re: [DISCUSS] Status of 3.0.x...

Hi! > Just wanted to start a quick discussion about 3.0.x. We’ve historically > done work on the master and then supported two fixes branches. With 3.2.0 > being voted on now, I’m not sure if we would branch the 3.2.x-fixes branch > immediately or wait a bit (we have historically waited a bi

Re: [VOTE] Apache CXF 3.0.15 and 3.1.13 patch releases...

+1 (non-binding)

Re: All CXF repos moved to gitbox....

> FYI, all our repos have now been moved over to gitbox. In order to commit to > the repos, you will need to do the gitbox setup to associate your Apache ID > with your GitHub account. Follow the steps at: > > https://gitbox.apache.org/setup/ > > There are a bunch of steps starting from enabl

Re: [VOTE] Apache CXF 3.2.0

> I just checked with Guillaume to get some other opinion. He also > approves going ahead with the release. > So I am back to +1 again but we should not wait too long with a 3.2.1. Good to hear this. After 3.2.0 is public there may be other bug reports anyway so we can release 3.2.1 soon to fix t

Re: All CXF repos moved to gitbox....

Or just use git remote set-url origin newurl Am 11. September 2017 15:41:01 MESZ schrieb Daniel Kulp : > >Cool…. Looks like things are working as I see more Team members today >and commits from the new repo. > >However, I also see a couple commits in the old git-wip repo.Can >everyone make s

Re: All CXF repos moved to gitbox....

nfluence/display/CXF/Source+Repository >>> It shouldn’t matter. It’s a “dual hosted” repo that is automatically >>> synced between the two. So take your pick. :) >>> >>> Dan >>> >>> >>> >>> >>>> Colm. >>>&

Re: 3.2 on web site...

> I’ve added the 3.2 javadocs, cleaned up the migration guide, etc…. I > think it’s all set now. Can folks double check? Thanks for your efforts, Dan, Are you going to add a news entry on the main page? I suggest to remove the 3.0.16-SNAPSHOT link from the download page. Currently 404 is r

Re: 3.2 on web site...

Hi, I just continued fixing broken links. >> http://cxf.apache.org/docs/atom-logging.html -> >> http://cxf.apache.org/javadoc/latest/org/apache/cxf/management/web/logging/atom/package-summary.html Does this Atom stuff still exist? Regards Dennis

Re: 3.2 on web site...

Ok I put a note on top of the page. > Hi > > It's gone from 3.2.0, still in 3.1.x > > Thanks, Sergey > On 15/09/17 09:52, Dennis Kieselhorst wrote: >> Hi, >> >> I just continued fixing broken links. >> >>>> http://cxf.apache.org/docs/ato

Re: 3.2 on web site...

> Thanks, we had the master opened for a while, I should've updated the > relevant pages the moment the changes possibly affecting the migration > were committed. > Can you also please update the 3.2.0 migration (though I don't think > anyone ever used this feature). Just noticed it's already par

Re: [Discuss] Release CXF-DOSGi 2.3.0 during the next days

Hi Christian, sounds good. Just one short remark: The release_notes.txt file is outdated (1.6.0 is the latest version), I think a link to the JIRA releases page would be also ok. I noticed an exception on startup but it doesn't seem to block anything. Regards Dennis java.lang.reflect.Invocation

Re: Beans created with no package are throwing nullpointer exception

Please create an issue for it: https://issues.apache.org/jira/secure/CreateIssue!default.jspa I can fix it for the next release. Regards Dennis Am 20.09.2017 um 20:19 schrieb sumeet_it: > I have beans and service classes with no package names in my webservices. > These worked perfectly fine in c

Re: Swagger2Feature bug caused by removal of isScan() check

Hi Taylor! > This causes the subsequent code (line 196): > > BeanConfig beanConfig = appInfo == null > ? new BeanConfig() > : new ApplicationBeanConfig(appInfo.getProvider()); > > …to always instantiate an ApplicationBeanConfig object. Our production code > relied on the BeanConfig’s imple

Re: All CXF repos moved to gitbox....

Hi Andriy! > I've just ported a few fixes to 3.1.x branch and noticed that this branch is > not being built on Jenkins since Sep, 8th > (https://builds.apache.org/job/CXF-3.1.x/). I am wondering if we reconfigured > this job to use Gitbox? Or there is another one for 3.1.x? Thanks. Looks like I

Documentation: snippets no longer shown

Hi, a user reported that the snippets are broken. Is it possible to get this working? Or do we need to replace the snippets? Regards Dennis >

Re: [VOTE] Apache CXF 3.2.1 and 3.1.14 patch releases...

Hi Dan, thanks for building the release. On 2017-11-03 02:10, Daniel Kulp wrote: > Staging repos: > 3.2.1: > https://repository.apache.org/content/repositories/orgapachecxf-1107 Should be 1108, shouldn't it? Regards Dennis

Re: [VOTE] Apache CXF 3.2.1 and 3.1.14 patch releases...

> Yea…. 1108. Copy/paste. :( Ok +1 (my first binding vote). Cheers Dennis

Re: New Java 9 master

On 2017-11-16 07:27, Christian Schneider wrote: > I dont think we can already predict when users move to Java 9. > So creating a Java 9 only branch at this time means we have to maintain two > main branches over a long time. > > What is the rationale behind a Java 9 only branch compared to being

Re: [VOTE] - Release Apache CXF 3.0.16

+1

Re: OpenAPI: Swagger2 or Swagger3

> Swagger 2 is a bit confusing, given that we have am Open Api version 3 > and the existing Swagger2Feature. We should rely on the versions of the Open API spec which is 2.0 for the original Swagger and 3.0.0 for OpenAPI. swagger-core/ jaxrs 1.5.x deals with spec 2.0 and swagger-core/ jaxrs 2.0.

Re: New Java 9 master

Hey, I would simply apply Automatic-Module-Name to existing master as the Commons guys did. See also: https://github.com/jodastephen/jpms-module-names Merry xmas Dennis

Re: New Java 9 master

> Exactly, that's the idea, updating the manifest with Automatic-Module-Name. > We could also add a sample > project (this would be Java 9 based) to illustrate the basic usage of CXF > from/within green field Java 9 > modular project (although we may need to do more work here I suspect). Thanks.

Re: [cxf] branch master updated: update swagger-core to latest version

Hi Sergey, which tests are failing for you? I don't see any related test failures here: https://builds.apache.org/view/A-D/view/CXF/job/CXF-Trunk-JDK18/lastCompletedBuild/testReport/ They fixed pretty print (https://github.com/swagger-api/swagger-core/issues/2320) and read only properties (htt

Re: [cxf] branch master updated: update swagger-core to latest version

Hi Sergey, my bad I wasn't able to run all tests locally. The ServerLauncher class produces a long classpath resulting in CreateProcess error=206 on my current environment. In general it looked fine and I thought Jenkins will run the testcases as well. So let's use 1.5.17 for 3.2.2 and I'll tr

Re: [VOTE] CXF 3.2.2

+1

Re: Going offline soon

Hi Sergey, when I saw the subject, I thought you will just leave for a long holiday :-). Sad that you will get lost somehow :-(. >From my own experience I know it's hard to contribute without dedicated time >at work. I hope you'll find time to follow us and share some ideas you get in your new

Re: CXF-3.1.x - Build # 1369 - Still Failing

On 2018/02/22 14:37:32, Colm O hEigeartaigh wrote: > I recall some emails lately saying that Jenkins doesn't support Java 7 any > more? In which case we should just update the Jenkins job to use Java 8 I > guess. I think we still need to ensure that CXF 3.1.x builds and runs with Java 7. AFAIK

Re: CXF-3.1.x - Build # 1369 - Still Failing

On 2018/02/22 16:47:15, Dennis Kieselhorst wrote: > On 2018/02/22 14:37:32, Colm O hEigeartaigh wrote: > > I recall some emails lately saying that Jenkins doesn't support Java 7 any > > more? In which case we should just update the Jenkins job to use Java 8 I > > gu

Re: Fwd: [cxf] branch 3.1.x-fixes updated: try to fix build on Jenkins using maven-toolchains-plugin

Hi Colm, as written in the other thread a toolchains.xml like this one is needed: https://github.com/apache/infrastructure-puppet/blob/deployment/modules/build_slaves/files/toolchains.xml In my view it makes sense to have this locally but I can also try to move the stuff to a separate profile t

Re: Fwd: [cxf] branch 3.1.x-fixes updated: try to fix build on Jenkins using maven-toolchains-plugin

On 28/02/2018 10:18, Colm O hEigeartaigh wrote: >> Hi Dennis, >> >> Yes adding it into a profile would be great - otherwise it wouldn't be >> possible to build the branch without making local changes. Done, please let me know if it still doesn't work for you. Cheers Dennis

Re: Fwd: [cxf] branch 3.1.x-fixes updated: try to fix build on Jenkins using maven-toolchains-plugin

> Looks great thanks! Do the Jenkins jobs for 3.1.x need to be updated to use > the new profile? The profile is automatically activated on Jenkins by checking the BUILD_NUMBER environment variable that Jenkins always sets. Cheers Dennis

Re: [DISCUSS] Time for 3.1.15

+1 Good idea. Cheers Dennis

Re: [VOTE] - Release Apache CXF 3.1.15

+1

Re: [VOTE] Apache CXF 3.2.3

+1 Thanks!

Re: CXF-3.1.x - Build # 1369 - Still Failing

Hi Francesco, there was a javadoc failure in the deploy job (this is not generated during the normal build). I've fixed that by adjusting the profile settings in the Jenkins Job config. Regards Dennis

should be [VOTE] CXF 3.2.4

+1 I appreciate to push out a release with the fixes soon. Cheers Dennis

JDK 10 build job

Hi, I've added a build job for JDK 10, it's currently failing as we only have a jdk9 profile and not a jdk9+ one. https://builds.apache.org/view/A-D/view/CXF/job/CXF-Master-JDK10/1/console The GA release is not yet available, that's why an early access build is used. See discussion in this INF

Re: Typo

Hi Gav, you're right, thanks for the info. I've just corrected it. Cheers Dennis Am 09.04.2018 um 06:22 schrieb Gavin McDonald: > Hi cxf-ers > > I spy a typo on your from page. > > The warning says do not use 3.2.2 or 3.2.3 , but use 3.2.3 ! > > You mean 3.2.4 of course. > > HTH > > Gav… >

10 years of CXF - Happy Birthday!

Hi, it's time to celebrate: 10 years ago, on April 16th in the year 2008, CXF graduated from the Apache incubator as a merge of the Objectweb Celtix project and the Codehaus XFire project (see http://incubator.apache.org/projects/cxf.html for more details). Today we have lots of more features, su

Re: Fwd: [cxf] branch master updated: update download-maven-plugin to latest version

Hmmpf looks like .cache in Maven repo folder is old on Jenkins. Before the update the wget download was failing in JDK10 build that's why I tried to update. Will take care of it later when I'm back at the keyboard...

Re: [cxf] branch master updated: update download-maven-plugin to latest version

I'm trying skipCache option otherwise I'll switch back to 1.3. https://github.com/maven-download-plugin/maven-download-plugin/issues/80

Re: Builds on Jenkins

Hi Andriy, thanks for the analysis. > John, guys, any hints who might help us here? Infra team? > Could you please open an issue at: https://issues.apache.org/jira/projects/INFRA/ Cheers Dennis

Re: Release cxf-xjc-plugin so that it works with Java 10?

> > > DK> That said, I wouldn’t say it’s critical and thus doesn’t need to hold > > things up. > > > > DK> Dan > > > > > >>> On Apr 5, 2018, at 4:43 AM, Colm O hEigeartaigh > >>> wrote: > >>> > >>> Sure

Start 3.3.x development

Hi, i'd like to update CXF to Spring/ Spring Security 5 and Spring Boot 2. There were also discussions about JAXB 2.3.0 and we might have additional changes for Java 9/10. In my view that would be a good start for CXF 3.3.x or what do you think? Cheers Dennis

Re: Start 3.3.x development

> Maybe a spring5/boot2.x compatible release could be done for 3.3, then a > 3.4 for java > 8? I've already changed things so that tatest 3.2.x work with both Spring 4/ 5 and Boot 1.5.x/ 2.x but at some point we should also deliver the latest versions as transitive dependencies, that's why I'm a

Re: Release cxf-xjc-plugin so that it works with Java 10?

Hi Andriy! > Haven't started work on automatic module names yet, my bad. But we certainly > could do that for > the plugin, the only thing we need to do is to agree on naming convention to > follow. Like f.e., > just to throw some ideas: cxf.xjc, cxf.core, cxf.cdi, cxf.opentracing, > cxf.cluste

Re: Builds on Jenkins

Have you tried to do a thread dump to see where it's hanging? So far I couldn't reproduce this, maybe I have to try with a clean local repo. Dennis Am 08.06.2018 um 11:14 schrieb Colm O hEigeartaigh: > I've also noticed Maven "pausing" recently when downloading SNAPSHOTs on my > local machine (ub

Re: Swagger upgrade issues

Hi, we already noticed this in February: https://lists.apache.org/thread.html/e440d7e162f4462972a6116cc523c78b3f1b9128ca23a2fcf9d55167@ Failing tests are part of the discussion. I think we should postpone a breaking change until 3.3.x. Regards Dennis

Re: Releases today?

> WSS4J 2.2.2 is released and we're free to call a vote on the CXF releases - > any objections to doing this later today? Or is there anything else anyone > wants to see in the releases? +1

Re: microprofile openapi @asf?

Hi Romain, currently we have an open issue for that https://issues.apache.org/jira/browse/CXF-7601 but afaik nobody has started an implementation yet. In my view CXF should work with both Swagger Core annotations and Microprofile OpenAPI annotations in the end, I don't mind where it's hosted. Re

Re: [VOTE] CXF 3.2.5/3.1.16

+1 Thanks!

Re: Change master to 3.3?

Definitely +1 > And how about for the master we also have spring 5 + spring boot 2, basically > merge the spring-5-boot-2 branch? Yes, I started the branch for testing and it looks good. Thank you for fixing some tests. Regards Dennis

Re: swagger-jaxrs2 2.0.1 / JAXB 2.3.0

Now that we have 3.3.x in master we should be able to upgrade it. Has anyone already started with this? Cheers Dennis On 2018/04/19 09:28:29, Colm O hEigeartaigh wrote: > Let's wait for Dan's opinion on this - maybe the upgrade is more suitable > for a new major release instead of 3.2.x? > >

Re: swagger-jaxrs2 2.0.1 / JAXB 2.3.0

On 2018/07/27 11:28:33, Andriy Redko wrote: > 2.2.11 > > Let us try to upgrade to 2.3.0? :-) Looks like there is not yet an OSGi Servicemix Bundle for that version (this is referenced in cxf.jaxb.bundle.version). Regards Dennis

Re: [VOTE] Apache CXF 3.2.6

+1 Thanks!

  1   2   >