Re: [VOTE] Release Apache CXF 2.0.11

+1 On Thu, Apr 23, 2009 at 7:04 PM, Sergey Beryozkin wrote: > +1 > - Original Message - From: "Ulhas Bhole" > > To: > Sent: Thursday, April 23, 2009 11:48 AM > Subject: Re: [VOTE] Release Apache CXF 2.0.11 > > > > +1 >> -- Ulhas >> >> Daniel Kulp wrote: >> >>> This is a vote to release

Re: [VOTE] Release CXF 2.2.1

+1 On Thu, Apr 23, 2009 at 6:49 PM, Ulhas Bhole wrote: > +1 > -- Ulhas > > Daniel Kulp wrote: > >> his is a vote to release CXF 2.2.1 >> >> >> Once again, there have been a bunch of bug fixes and enhancements that >> have been done compared to the 2.2 release. Over 55 JIRA issues >> are resolve

Re: [VOTE] Release CXF 2.1.5

+1 On Thu, Apr 23, 2009 at 6:48 PM, Ulhas Bhole wrote: > +1 > -- Ulhas > > Daniel Kulp wrote: > >> This is a vote to release CXF 2.1.5 >> >> >> Once again, there have been a bunch of bug fixes and enhancements that >> have been done compared to the 2.1.4 release. Over 87 JIRA issues >> are reso

Re: [VOTE] Release CXF 2.1.6

+1 On Thu, Jul 30, 2009 at 2:55 AM, Sergey Beryozkin wrote: > +1 > > Cheers, Sergey > > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: 29 July 2009 18:54 > To: dev@cxf.apache.org > Subject: [VOTE] Release CXF 2.1.6 > > > > This is a vote to release CXF 2.1.6 > >

geronimo jars

Is there any specific reason we use geronimo-*-spec-x.x.x.jar ? Why we do not use sun's equivalent ? Cheers, Jim

Re: how to setup a http proxy in wsdl2java

Did you try to set the http proxy server and port in wsdl2java or wsdl2java.bat ? -Dhttp.proxyHost=proxyserver -Dhttp.proxyPort=8080 Cheers Jim 2009/11/19 郑东哲 : > hi all! > because my pc is behind a firewall.when i use wsdl2java cause a connection > time out error.how to setup a http proxy whe

SAAJ for xop element

Hi all , When set the jaxws handler in client side to check if CXF 2.2.5 can get the XOP element(xop:include element) content(encoded message) from the SAAJ model . It looks like the SAAJIn/OutInterceptor does not parse and inline the encoded request message in the "dataHandler" element : The exp

Enable @Action inspection when create service from wsdl

Hi all, When there is no wsaw:action specified in wsdl input/out : http://schemas.xmlsoap.org/soap/http"; style="document" />

Endorse jaxws 2.2 API jar

Hi all , When we update to jaxws 2.2 , we have to endorse the jaxws api jar for jdk6. I've updated the jaxws api dependency to 2.2 and endorsed the jaxws api 2.2 jar to maven surefire and compiler plugin . If there is no objection , I will check in this change . We also need to look at endorsing

Distribution build failure

Hi all , When I build distribution module I got this failure : POM Location: /x1/code/cxf/trunk/distribution/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for ant:ant Reason: Failed to validate POM for project org.apache.cxf:apache-cxf at /x1/code/cxf/trunk/dis

Re: Endorse jaxws 2.2 API jar

ne, it's looking pretty good. Anyway, I would need to update the release profiles to add the jaxws22 profile stuff and I still need to update the distribution to somehow take it into account and create the new jaxws22-endorsed lib dir as well. But I wanted you to look at this so

PolicyVerificationInterceptor

Hi all , When I ran a service with ws addressing policy enabled and an handler which always throw exception configured in server side . When I sent a soap request WITHOUT wsa header , I saw the SOAPHandlerInterceptor in server side eat the WS addressing violation exception and just throw the excep

Re: PolicyVerificationInterceptor

erationInfo set in exchange which stops me to get the normalized policy. > > Dan > > > On Jul 5, 2010, at 4:02 AM, jim ma wrote: > >> Hi all , >> >> When I ran a service with ws addressing policy enabled and an handler >> which always throw exception configure

Re: 2.2.x Build failure

I am using java6 and there is no problem for me on Fedora . java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Server VM (build 14.3-b01, mixed mode) I did not find failures in cxf hudson : http://hudson.zones.apache.org/hudson/view/CXF. Which jdk ver

Re: Need for normalization? (Re: svn commit: r980880 - in /cxf/trunk/tools/common/src)

When we input the following arguments to wsdl2java : wsdl2java -b /home/jimma/code/jaxws/ee/w2j/document/literal/headertest/customfile.xml" file:/home/jimma/code/tmp/all/../../tests/jaxws/ee/w2j/document/literal/headertest/HeaderTestService.wsdl" and customfile.xml contains : http://java.sun

Re: Need for normalization? (Re: svn commit: r980880 - in /cxf/trunk/tools/common/src)

On Sat, Jul 31, 2010 at 7:52 PM, Benson Margulies wrote: > To chime in: it's a really, really, bad idea for non-file URLs, as it > can violate stringprep. Why do you say that ? Can you explain it more with a example ? ;-) > > For file URLs, it is an attempt to deal, with non-NFC (or NFKC) > stri

Re: [VOTE] Release CXF 2.2.10

+1 Jim On Sat, Aug 14, 2010 at 7:01 AM, Willem Jiang wrote: > +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:

Re: svn commit: r986571 - in /cxf/trunk: distribution/src/main/release/samples/jms-spec-demo/wsdl/ rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/ rt/bindings/soap/src/main/java/org/apache

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 message property) checks in SoapJMSInInterceptor

Re: svn commit: r986571 - in /cxf/trunk: distribution/src/main/release/samples/jms-spec-demo/wsdl/ rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/ rt/bindings/soap/src/main/java/org/apache

gt; http://cxf.apache.org/transports/jms";> http://org.jboss.ws/samples/jmstransport}JmsPort.jms-destination";> http://org.jboss.ws/samples/jmstransport}JmsPort.jms-conduit";> On Tue, Sep 14, 2010 at 1:27 PM, Jim Ma wrote: > Hi

Re: svn commit: r986571 - in /cxf/trunk: distribution/src/main/release/samples/jms-spec-demo/wsdl/ rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/ rt/bindings/soap/src/main/java/org/apache

completely move to soap jms stuff ? On Tue, Sep 14, 2010 at 3:46 PM, Jim Ma wrote: > The cxf.xml  I just pasted is I modified to test . > Here is the original one which works before the soap jms change : > > >  xmlns='http://www.springframework.org/schema/bean

Re: Łukasz Moreń for CXF Committer

+1 Cheers, Jim On Wed, Nov 17, 2010 at 11:10 AM, Willem Jiang wrote: > 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

Re: [VOTE] Release CXF 2.3.1

+1 Jim On Sun, Dec 5, 2010 at 12:08 AM, Alessio Soldano wrote: > +1 > > As mentioned to Dan, I actually noticed that when building the 2.3.1 tag > using 'mvn -Pjaxws22,fastinstall' (java 1.6.0_21), a 2.3.1-SNAPSHOT artifact > is referenced, unless I locally apply a change like the following one:

Re: [VOTE] Release CXF 2.2.12

+1 On Sun, Dec 5, 2010 at 12:08 AM, Alessio Soldano wrote: > +1 > > On 12/02/2010 03:51 PM, 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. >> >> Lis

Re: [VOTE] Colm O hEigeartaigh for CXF committer

+1 On Sun, Dec 5, 2010 at 11:45 AM, Glen Mazza wrote: > > +1 > > Glen > > > John Fuhr wrote: >> >> On Thu, Dec 2, 2010 at 3:32 PM, David Bosschaert >> >> +1 >>> >>> David >>> >>> On 2 December 2010 12:01, Daniel Kulp wrote: >>> > >>> > In the last 2 years, Colm has logged 11 issues with CXF.  Ev

Re: svn commit: r1049357 - in /cxf/branches/2.3.x-fixes: rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/ rt/bindings/soap/src/test/java/org/apache/cxf/binding/soap/ systests/ja

Right , Dan. No need to add this interceptor in the client side. Thanks for the review and committed the optimized code in revision 1049415. On Wed, Dec 15, 2010 at 8:18 AM, Daniel Kulp wrote: > > Jim, > > > On Tuesday 14 December 2010 7:07:47 pm e...@apache.org wrote: >> MustUnderstandEndingInte

Re: Does anybody also see OOBHeaderTest failure

Hi Freeman , This failure is introduced in this commit : http://svn.apache.org/viewvc?rev=1050167&view=rev. Dan, is your change in rev. 1050167 with Freeman's modification are what you meant to optimize ? Thanks, Jim On Fri, Dec 17, 2010 at 4:25 PM, Freeman Fang wrote: > Ok, we also need add >

Re: [VOTE] Apache CXF 2.3.2

I have to vote -1 for this release. The new changes in tagged CXF 2.3.2 introduced several JEE6 TCK regression failures . I am looking for a quick fix for these failures. Jim On Wed, Jan 19, 2011 at 8:28 AM, Eric Johnson wrote: > +1 > > On Tue, Jan 18, 2011 at 6:31 PM, Christian Schneider > wr

Re: [VOTE] Apache CXF 2.3.2

t; >> Glen >> >> On 19.01.2011 22:37, Willem Jiang wrote: >> > 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 f

Re: [VOTE] Dennis Sosnoski for CXF committer

+1 On Wed, Feb 16, 2011 at 10:10 PM, Alessio Soldano wrote: > +1 > > On 02/16/2011 06:53 AM, Glen Mazza wrote: >> >> Hello Team, >> >> Here's a vote to make Dennis Sosnoski a committer on the CXF project.  Of >> course we all know Dennis from his extensive IBM developerWorks articles[1] >> on web

Re: [VOTE] Apache CXF 2.3.3

+1 On Thu, Feb 24, 2011 at 9:47 AM, UlhasBhole wrote: > +1, > > -- Ulhas Bhole > On 23 Feb 2011, at 20:30, Daniel Kulp wrote: > >> >> >> We've resolved over 50 issues since 2.3.2.   Thus, we really should get >> 2.3.3 out, especially since 2.3.2 contained an issue preventing it from >> being us

Re: [VOTE] Aki Yoshida for CXF committer

+1 On Fri, Apr 8, 2011 at 5:43 AM, Madhav Bhargava wrote: > +1 > > Madhav > > On Thu, Apr 7, 2011 at 10:03 PM, Jeff Genender wrote: > >> +1 >> >> Jeff >> >> >> On Apr 6, 2011, at 10:11 AM, Alessio Soldano wrote: >> >> > +1 >> > >> > On 04/06/2011 06:03 PM, Daniel Kulp wrote: >> >> I'd like to ca

Re: [VOTE] Release Apache CXF 2.4.0

+1 On Fri, Apr 15, 2011 at 9:41 AM, Willem Jiang wrote: > This is my +1. > > On 4/13/11 3:51 PM, Daniel Kulp wrote: >> >> It's been about 6 months since the release of 2.3 and we've done a >> fantastic >> job implenting new features  and cleaning up various parts of the code and >> integrating ne

Re: [VOTE] Release Apache CXF 2.3.4

+1 On Fri, Apr 15, 2011 at 9:42 AM, Willem Jiang wrote: > This is my +1. > On 4/13/11 3:42 PM, Daniel Kulp wrote: >> >> >> We've resolved over 59 issues since 2.3.3 and thus is time for a release. >> >> List of issues: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231051

Wrapped or Unwrapped

Hi all , Can not remember if we talked about this before, raise this question again if we did. If the schema element's type is RegistrationContext which contains an extension ,should we map it to wrapped ?

Re: Jenkins build became unstable: CXF-Trunk-JDK15 #2088

I am looking at these failures. Thanks Jim On Tue, May 24, 2011 at 5:20 PM, Apache Jenkins Server wrote: > See > > >

Re: [VOTE] Release Apache CXF 2.4.1 - take 2

+1 On Sat, Jun 11, 2011 at 3:49 AM, Dennis Sosnoski wrote: > +1 > >  - Dennis > > > On 06/10/2011 02:38 PM, 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. >> >> Li

Re: [VOTE] Release Apache CXF 2.3.5 - take 2

+1 On Sat, Jun 11, 2011 at 2:51 PM, Alessio Soldano wrote: > +1 > > On 06/10/2011 04:37 AM, Daniel Kulp wrote: >> >> We've resolved over 58 issues since 2.3.4 and thus is time for a release. >> >> This is take #2 fixing the attachment issue I found while testing with >> Camel. >> >> >> List of is

Re: [VOTE] CXF buildutils and xjc utils 2.4.0

+1 On Fri, Aug 5, 2011 at 2:55 PM, Sergey Beryozkin wrote: > +1 > Cheers, Sergey > > On Thu, Aug 4, 2011 at 6:55 PM, 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 warnin

Re: commits to JaxWsEndpointImpl (r1177248)

Thanks Glen for pointing out my typo and errors. The error message you suggested is better , I just slightly changed it to "Unknown wsd binding extension with required=true attribute found while RespectBindingFeature enabled". Thanks Jim On Fri, Sep 30, 2011 at 5:33 AM, Glen Mazza wrote: > Hi

Re: [VOTE] Release Apache CXF 2.4.4-3rd try

+1 On Tue, Nov 8, 2011 at 9:06 AM, Freeman Fang wrote: > Here is my +1 > > Freeman > On 2011-11-4, at 下午9:58, 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/R

Remove xml-resolver dependency

Hi , Since all the equivalent classes in xml-resolver.jar are all packaged in jaxb-xjc.jar. We can change the org.apache.cxf.catalog.CataLogManager to use com.sun.org.apache.xml.internal.resolver.* class to decrease 82k distribution size. If there is no objection, I am going to commit the change.

Re: Remove xml-resolver dependency

gt; > On Thu, Dec 15, 2011 at 6:36 PM, Daniel Kulp wrote: > > > On Friday, December 16, 2011 10:20:38 AM Jim Ma wrote: > > > Hi , > > > Since all the equivalent classes in xml-resolver.jar are all packaged > in > > > jaxb-

Re: [DISCUSS] Drop 2.3.x patches....

+1 On Wed, Apr 25, 2012 at 9:38 AM, Willem Jiang wrote: > 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 >> y

Re: Release 3.5.0 next week?

+! On Thu, Dec 9, 2021 at 2:25 AM Romain Manni-Bucau wrote: > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github < > https://github.com/rmannibucau> | > LinkedIn

Re: [DISCUSS] CXF 3.5.x and beyond

t; >> is JDK17 baseline for Spring Framework & Co, that could be a bummer > but > >> I > >> >> have the feeling that > >> >> it will be lowered to JDK11. Thank you. > > >> >> Best Regards, > >> >> Andriy Redko >

Re: [DISCUSS] CXF 3.5.x and beyond

I accidentally clicked the send button, please ignore my previous email and look at this reply. On Sat, Jan 29, 2022 at 7:58 PM Jim Ma wrote: > > > > On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: > >> Hey guys, >> >> A bunch of good things have happ

Re: [DISCUSS] CXF 3.5.x and beyond

> [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp > > Best Regards, > Andriy Redko > > JM> I accidentally clicked the send button, please ignore my previous > email > JM> and look at this reply. > > JM> On Sat, Jan 29, 2022 at 7:58 PM Jim Ma

Re: Change default branch to main

+1 On Tue, Feb 1, 2022 at 8:59 PM Colm O hEigeartaigh wrote: > Hi, > > Most other Apache projects I work on (Camel, ActiveMQ, Karaf, etc.) > have switched to use main as the default branch, to align with what > the default branch is for new projects on GitHub etc. I'd like to > propose switching

Re: [DISCUSS] CXF 3.5.x and beyond

ines. > > Thank you. > > [1] https://issues.apache.org/jira/browse/CXF-5477 > [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp > > Best Regards, > Andriy Redko > > JM> I accidentally clicked the send button, please ignore my previous > email > JM&

[Proposal] CXF OSGI Jakarta EE 9.x support

Hi, I took more time to look at more things about Jakarta EE9.x support work from last week. Like Spring integration code, now OSGI relevant code is in different maven modules : ./core/src/main/java/org/apache/cxf/bus/osgi ./rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jett

Re: [Proposal] CXF OSGI Jakarta EE 9.x support

branch: https://github.com/apache/cxf/tree/CXF-8371. Thanks, Jim On Fri, Mar 4, 2022 at 6:42 PM Grzegorz Grzybek wrote: > Hello > > As long-term OSGi supporter, I'd like to give my +1 for CXF 4.0.0 (?) with > OSGi bits moved to slower-paced github.com/apache/cxf-osgi repo (modules

Systest failures with wss4j-3.0.0-SNAPSHOT

Hi Colm, After I upgraded wss4j version to 3.0.0-SNAPSHOT(jakarta version) in CXF, I got the following ws-security systests failures. Could you please help look at if there is still something we need to fix in wss4j ? Or we need to fix it in CXF ? Thanks, Jim [ER

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

when trying this out. Thanks, Jim On Tue, Mar 22, 2022 at 5:18 PM Colm O hEigeartaigh wrote: > Hi Jim, > > Which branch are you testing this on in CXF? > > Colm. > > On Mon, Mar 21, 2022 at 7:26 AM Jim Ma wrote: > > > > Hi Colm, > > After I upgraded wss

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

On Wed, Mar 23, 2022 at 7:15 PM Colm O hEigeartaigh wrote: > The SAML failures were caused by a hard-coded String in SAMLUtils, I > fixed it in CXF master here: > > https://github.com/apache/cxf/commit/1e90f53f720b76c2dbac910e58ef0b291f98c032 > > Colm. > > On Tue, Mar 22,

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

ook at what's failing with WSS4J 3.0.0? > > Colm. > > On Wed, Mar 23, 2022 at 12:42 PM Jim Ma wrote: > > > > Thanks for the quick fix, Colm. > > > > It seems there is another failure under services/sts/systests/advanced: > > > > [INFO] Running org.a

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

t; >> Your branch is behind CXF master with regards several commits. I think > >> it would be better if we just worked off one official branch at CXF. > >> @Andriy Redko maybe we should just incorporate > >> https://github.com/apache/cxf/tree/opensa

Re: Releases soon?

+1 On Tue, Apr 5, 2022 at 8:59 PM Colm O hEigeartaigh wrote: > Hi, > > We've received a JIRA request to get new releases out due to the > recent Spring CVE issue. I think it's reasonable due to the publicity > surrounding the issue, and also we have quite a few issues fixed since > the last rele

Re: Releases soon?

/jira/browse/CXF-8668 > COh> https://issues.apache.org/jira/browse/CXF-8683 > > COh> Colm. > > COh> On Wed, Apr 6, 2022 at 11:33 AM Jim Ma wrote: > > >> +1 > > >> On Tue, Apr 5, 2022 at 8:59 PM Colm O hEigeartaigh > wrote: > > >>> Hi

Copied classes in cxf-rt-management.jar with JDK11

When building cxf-rt-management 3.5.1 with JDK11, some api classes are copied to the jar file. It looks like these classes are copied by the maven-bundle-plugin from java9-plus profile : *java9-plus[9,) org.apache.felix maven-bundle-p

Re: Copied classes in cxf-rt-management.jar with JDK11

Thanks Andriy. Jira is filled :https://issues.apache.org/jira/browse/CXF-8695 and PRs are sent. On Sun, Apr 17, 2022 at 9:28 AM Andriy Redko wrote: > Hey Jim, > > This is interesting, I believe it is not needed, only some compiler args > need > tailoring (for JDK-11) but the classes should not

Re: Copied classes in cxf-rt-management.jar with JDK11

rg.apache.cxf.tracing* > + > > true > > This fine-grained export package can avoid including the package from > cxf-core module. > > Best Regards >

Re: Copied classes in cxf-rt-management.jar with JDK11

ider JDK8 compatible anymore), I believe we are > safe to remove java9-plus profile in management/pom.xml all together. > > Cheers > Freeman > > On Tue, Apr 19, 2022 at 10:34 PM Jim Ma wrote: > >> Hi Freeman, >> Do you know why we don't require this with

Re: Copied classes in cxf-rt-management.jar with JDK11

t; > I mean remove it from CXF 4.x which is JDK11 minimum. > > Freeman > > On Wed, Apr 20, 2022 at 8:45 PM Jim Ma wrote: > >> Hi Freeman, >> Are you saying we can remove this java9-plus profile completely from >> 3.4.x to 4.x? >> >> Cheers, >

Re: Copied classes in cxf-rt-management.jar with JDK11

o CXF 4.x > > Thanks! > Freeman > > On Thu, Apr 21, 2022 at 2:20 AM Jim Ma wrote: > >> I think we can remove this profile from 3.4.x and 3.5.x too. There is no >> reason we should still keep this, right ? >> I tried to build 3.4.x/3.5.x with jdk11, and the Export-

Re: Jakarta build hangs on test

Hi Andriy, I'll have a look today and get back to you later. Thanks, Jim On Thu, May 12, 2022 at 8:26 AM Andriy Redko wrote: > Hey Jim, > > After this commit [2] the Jakarta builds are started to hang [2] (and > eventually fail). I have > not checked the reason but I could confirm that revertin

Re: Jakarta build hangs on test

It looks this hang issue is fixed : https://ci-builds.apache.org/job/CXF/job/pipeline/job/CXF-8371/41/#showFailuresLink Regards, Jim On Thu, May 12, 2022 at 9:19 AM Jim Ma wrote: > Hi Andriy, > I'll have a look today and get back to you later. > > Thanks, > Jim > > On

Re: [VOTE] - Release Apache CXF XJC Utils 3.3.2

+1, thanks, Colm! On Fri, May 20, 2022 at 8:41 PM Andriy Redko wrote: > +1, thanks a lot, Colm! > > Best Regards, > Andriy Redko > > COh> This is a vote to release Apache CXF XJC Utils 3.3.2. > > COh> Issues fixed: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315520&v

Re: [VOTE] - Release Apache CXF Build Utils 4.0.0

+1 On Mon, May 23, 2022 at 3:52 PM Colm O hEigeartaigh wrote: > This is a vote to release Apache CXF Build Utils 4.0.0. It contains a > security fix to disable DocTypes during XML parsing and an update to > Java 11, with some other minor fixes. > > Artifacts: > https://repository.apache.org/cont

Re: [DISCUSS] CXF 3.5.x and beyond

the scope of dependencies on > >> Spring, even > >> in 3.4.x / 3.5.x release lines. > > >> Thank you. > > >> [1] https://issues.apache.org/jira/browse/CXF-5477 > >> [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp > > >> B

Re: [VOTE] - Release Apache CXF XJC 4.0.0

+1 On Fri, May 27, 2022 at 6:17 PM Alexey Markevich wrote: > +1 > > On 5/27/22, Colm O hEigeartaigh wrote: > > This is a vote to release Apache CXF XJC 4.0.0. This is a major new > > release with support for the jakarta namespace. > > > > Issues fixed: > > > https://issues.apache.org/jira/secur

Re: [DISCUSS] CXF 3.5.x and beyond

highly appreciated. > > Thank you! > > [1] https://github.com/apache/cxf/pull/912 > [2] https://issues.apache.org/jira/browse/CXF-8371 > > Best Regards, > Andriy Redko > > COh> +1 from me. > > COh> Colm. > > COh> On Thu, May 26, 2022 at 2:4

Re: [VOTE] Apache CXF 3.5.3 and 3.4.8

+1 On Sat, Jun 25, 2022 at 12:18 AM Daniel Kulp wrote: > > > This is a vote to release the latest set of patches for CXF. > > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachecxf-1180/ < > https://repository.apache.org/content/repositories/orgapachecxf-1180/>

Re: [DISCUSS] CXF 3.5.x and beyond

ld have in this 4.0.0-M1 release ? Thanks, Jim On Wed, Jun 22, 2022 at 10:02 AM Jim Ma wrote: > Thanks Andriy too for driving this and moving forward ! > > On Tue, Jun 21, 2022 at 9:49 AM Andriy Redko wrote: > >> Hey guys, >> >> The Jakarta branch [1] just we

Re: [DISCUSS] CXF 3.5.x and beyond

encies won't > JM> have the jakarta namespace artifact released in the near future. > Should we > JM> have some milestone/alpha release > JM> before all these dependencies are available ? And if we want to do a > JM> milestone release, what do you think we should have

Re: [DISCUSS] CXF 3.5.x and beyond

e right, release CXF 4.0 M1 without OSGi/Karaf bit > seems the only option we have so far, and I'm +1 for this way now(Since we > don't know how long we need to wait for the proper OSGi spec released and > upstream projects can support it). > > Just my 2 cents. > Best

Re: [DISCUSS] CXF 3.5.x and beyond

hanks, Jim On Wed, Sep 7, 2022 at 8:11 PM Jim Ma wrote: > Thanks for the informative input, Freeman. > IMO, If we want to decouple OSGI/Karaf, the 4.0 major release is a good > chance to do this job. When OSGI/Karaf jakarta release is ready, > We can look at bringing this back wit

Re: [DISCUSS] CXF 3.5.x and beyond

o in CXF or even in > >> Karaf about this part. > >> And Andriy, you are right, release CXF 4.0 M1 without OSGi/Karaf bit > >> seems the only option we have so far, and I'm +1 for this way > now(Since we > >> don't know how long we need to w

Re: [DISCUSS] CXF 3.5.x and beyond

b.com/openzipkin/brave/pull/1344. Do you see any other > JM> dependencies that haven't been released yet except OSGI and Karaf ? > > JM> Thanks, > JM> Jim > > > JM> On Wed, Sep 7, 2022 at 8:11 PM Jim Ma wrote: > > >> Thanks for the informative input,

Re: [DISCUSS] CXF 3.5.x and beyond

> >> Best Regards, > >> Andriy Redko > >> > >> JM> Hi Andriy, > >> JM> It looks like we still have to wait for the other dependency jakarta > >> JM> support available, like brave's new release to include this change : > &

Re: [DISCUSS] CXF 3.5.x and beyond

> This is great, thanks Jim, I will also take a look shortly. Thanks! > > Best Regards, > Andriy Redko > > On Wed, Sep 21, 2022, 1:02 AM Jim Ma wrote: > >> Hi All, >> I tried to remove the osgi and karaf from CXF with this draft PR : >> https://gith

Re: [DISCUSS] CXF 3.5.x and beyond

bjections from my side, thank you. > > > > Best Regards, > > Andriy Redko > > > > On Tue, Sep 27, 2022, 9:31 PM Jim Ma wrote: > >> > >> Hi all, > >> If there is no objection, I will create a branch > "osgi-pre-removal-v4.0" to r

Re: [VOTE] Apache CXF 3.4.9 and 3.5.4

+1 On Wed, Oct 5, 2022 at 5:31 PM Alexey Markevich wrote: > +1 > > On 10/5/22, Jean-Baptiste Onofré wrote: > > +1 (non binding) > > > > Regards > > JB > > > > On Mon, Oct 3, 2022 at 8:05 PM Daniel Kulp wrote: > >> > >> > >> > >> This is a vote to release the latest set of patched for CXF. > >>

Re: [DISCUSS] - Retire CXF DOSGI?

+1. It makes sense to retire it. On Wed, Oct 19, 2022 at 4:49 AM Colm O hEigeartaigh wrote: > Hi all, > > What do you think about moving CXF DOSGI to the attic? There is very > little activity for many years now (last commit 2.5 years ago - > https://github.com/apache/cxf-dosgi/commits/main). It

CXF 4.0.0 jakarta release

Hi all, After 9 months of work, we finally fixed/worked around all issues for Jakarta support. Now all the cxf tests are passed: https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/ and we can say that CXF successfully migrated to Jakarta namespace(and support Jakarta EE9.1). To get cxf jakarta

Re: CXF 4.0.0 jakarta release

> >>> on JDK-17 or above? If yes, I think we have to make all Spring > > related > > > >>> dependencies optional and document > > > >>> clearly that JDK-17 is needed in case Spring / Spring Boot are > used, > > we > > > >>> sure

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

+1 On Tue, Nov 8, 2022 at 10:54 PM Colm O hEigeartaigh wrote: > This is a vote to move Apache CXF DOSGi to the attic. There is very > little activity for many years now (last commit 2.5 years ago - > https://github.com/apache/cxf-dosgi/commits/main). > > Previous discussion thread: > https://lis

Re: CXF 4.0.0 jakarta release

year, hopefully. > > On Mon, Nov 7, 2022 at 12:19 PM Jim Ma wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > https://ci-builds.apache.org/job/CXF/job/CXF-JDK

Re: CXF 4.0.0 jakarta release

;https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance &

Re: CXF 4.0.0 jakarta release

tory). Btw, I believe JakartaEE 9.1 was meant to be used with JDK 8 or > 11; support for JDK 17 is something coming with JakartaEE 10 afair. > > Thanks > > On Tue, Nov 8, 2022 at 1:34 PM Jim Ma wrote: > > > Yes. Spring is optional for CXF runtime for a long time. Now all CX

Re: CXF 4.0.0 jakarta release

+1 to release 4.0.0 even partial release. > > Regards > JB > > On Mon, Nov 7, 2022 at 9:19 AM Jim Ma wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > h

Re: CXF 4.0.0 jakarta release

? That would give a week to get any final updates in. > > > > Dan > > > > > > > > > > Thank you guys! > > > > > > > > > Best Regards, > > >Andriy Redko > > > > > > On Sun, Nov 27, 2022, 10:27 PM Jim Ma

Re: [VOTE] CXF 3.5.5 and 3.4.10

+1 On Thu, Dec 8, 2022 at 5:21 AM Daniel Kulp wrote: > > I was only able to get the 3.4 and 3.5 patch releases built today, but I’d > like to go ahead and get the vote started for them. > > > This is a vote to release the latest set of patched for CXF. > > > Staging repositories: > 3.5.5 > https

Re: CXF 4.0.0 jakarta release

anything else planned? > >> > >> > Colm. > >> > >> > On Wed, Nov 30, 2022 at 10:48 AM Colm O hEigeartaigh > >> > wrote: > >> >> It works for me as well. I'm coordinating with @Andriy Redko on two > >> >> fixe

Re: CXF 4.0.0 jakarta release

che/cxf/pull/1033 > >> >> > >> >> Best Regards, > >> >> Andriy Redko > >> >> > >> >> > I'm done now in terms of any remaining fixes for the next > >> >> > releases...not sure if @Andriy Redko ha

Re: CXF 4.0.0 jakarta release

Thanks for the update, Dan. Are these basic tests failed because Spring6 is built with java17 and it isn't compatible with java11 anymore ? On Mon, Dec 12, 2022 at 11:01 AM Daniel Kulp wrote: > > On Dec 11, 2022, at 9:36 PM, Jim Ma wrote: > > > > Hi Andriy, > >

Re: CXF 4.0.0 jakarta release

with java17), but many > don’t actually work. None of the JMS samples seem to work at all. > Some are still setup to use activemq (might be OK, but the class path > doesn’t have activemq) and others that are setup for Artemis don’t have > proper spring bean configuration for it

Re: [VOTE] Apache CXF 4.0.0

+1. Thanks everyone! On Sun, Dec 18, 2022 at 11:26 PM Daniel Kulp wrote: > This is a vote to release CXF 4.0.0.This is a major release that > completely changes the API from using the older javax.* packages to using > the jakarta.* versions. It also updates everything to more modern > de

Re: [VOTE] - Release Apache CXF Fediz 1.6.1

+1 On Tue, Dec 20, 2022 at 12:53 AM Colm O hEigeartaigh wrote: > This is a vote to release Apache CXF Fediz 1.6.1. The main features > are dependency updates (e.g. CXF 3.5.5) to pick up CVE fixes: > > Artifacts: > https://repository.apache.org/content/repositories/orgapachecxf-1186/ > Git tag: h

Re: [RESULT] [VOTE] Apache CXF 4.0.0

Happy new year, everyone ! I see the CXF 4.0.0 release note isn't finalized : https://issues.apache.org/jira/projects/CXF/versions/12351115 , and we didn't announce this release in https://cxf.apache.org/ . Is

Re: [VOTE] CXF 3.5.6, 3.6.0, 4.0.1

+1 On Wed, May 3, 2023 at 5:02 AM Daniel Kulp wrote: > > It’s been quite a while since the last round of releases and a bunch of > work has been done, lots of bug fixes, a couple of new features, etc… > > > Tags: > https://github.com/apache/cxf/releases/tag/cxf-4.0.1 ( > https://github.com/apach

  1   2   3   >