Re: cxf-codegen-plugin next releases

You can update the dependency in your own POM or whatever dependency system you happen to have. Gary On Mon, Nov 28, 2022, 10:28 wrote: > Hi Apache CXF Dev Team, > > > > Kindly can you provide an update on my request below ? > > > > The latest version of cxf-codegen-plugin >

Re: Apache CXF 3.1.15 released

notes for 3.1.14. > > 3.1.15 is: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > version=12342151&projectId=12310511 > > > Dan > > > > On Mar 13, 2018, at 10:42 AM, Gary Gregory > wrote: > > > > Hi All, > > > > Thank you f

Re: Apache CXF 3.1.15 released

Hi All, Thank you for another release. Are you sure about the 57 items resolved? I only see 23 listed on https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12341567 Gary On Tue, Mar 13, 2018 at 8:34 AM, Colm O hEigeartaigh wrote: > Apache CXF™ is an open source

Re: Possible bug in UriBuilder?

Hi Sergey, Can you formulate the issue you are seeing in the form of a failing unit test? Gary On Mon, Jun 19, 2017 at 9:02 AM, Sergey Beryozkin wrote: > Hi > > Awhile back, may be 5-6 years back, I had to deal with the following TCK > test: > > assertEquals("mailto:testu...@sun.co

Re: WADL not available in OSGi

Make sure Xalan is on the endorsed class path. Gary On Oct 25, 2016 7:21 AM, "Christian Schneider" wrote: > I got a problem from a customer. They define a REST service. The service > works but the wadl can not be retrieved. > > Instead the exception below is logged. Did anyone see this before?

WADL and Swagger

Hi All: I see that CXF includes supports for both WADL [1] and Swagger [2]. Is to possible to programatically use CXF to convert a WADL file to a Swagger file? Perhaps by first parsing WADL to some CXF internal format and then back out to Swagger? Thank you, Gary [1] https://cxf.apache.org/docs/

href and id

Hi All, Are SOAP XML href and id supported by CXF? hrefs are not being resolved in our CXF implementation. Our implementation includes many custom interceptors so I want to ask before I go in some deep rabbit hole. Thank you! Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Pe

Re: Calling org.apache.cxf.endpoint.Client with SOAP header values

On Mon, Apr 20, 2015 at 6:56 PM, Gary Gregory wrote: > I forgot to mention that I am on 2.7.15. > > Gary > > On Mon, Apr 20, 2015 at 6:50 PM, Gary Gregory > wrote: > >> Hi All: >> >> We have an app server that uses org.apache.cxf.endpoint.Client to call &g

Re: Calling org.apache.cxf.endpoint.Client with SOAP header values

I forgot to mention that I am on 2.7.15. Gary On Mon, Apr 20, 2015 at 6:50 PM, Gary Gregory wrote: > Hi All: > > We have an app server that uses org.apache.cxf.endpoint.Client to call > various third party services. > > We are now dealing with a new WSDL which requires an

Calling org.apache.cxf.endpoint.Client with SOAP header values

Hi All: We have an app server that uses org.apache.cxf.endpoint.Client to call various third party services. We are now dealing with a new WSDL which requires an element and child element in the SOAP header for each invocation (a session header element and a sesssion ID child element). The SOAP

Roadmap update?

Hi All: Now that 3.0 is out and 3.1 is on the horizon, an update to the roadmap ( https://cxf.apache.org/roadmap.html) would be nice. Thank you, Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in

Re: CXF accepts 'tru*' for boolean fields

what about doIt("truthiness")? :-) Gary On Mon, Oct 6, 2014 at 10:49 AM, Daniel Kulp wrote: > > This is also not really a bug in CXF but a bug in the JDK.The JAXB > runtime would use javax.xml.bind.DatatypeConverter to parse the booleans > and if I write a quick test like: > > @Test >

Re: How to change SAML signatur algorithm

Do we have a guess date for 2.7.11? Gary Original message From: Colm O hEigeartaigh Date:03/26/2014 07:03 (GMT-05:00) To: users@cxf.apache.org Subject: Re: How to change SAML signatur algorithm It'll be fixed for the next release: https://issues.apache.org/jira/browse/C

XML validation problem with SAAJ Node vs. Xerces Node.

Hi All: We do custom validation on output of the SOAP body org.w3c.dom.Node against a Schema object in a custom interceptor. The problem is that org.w3c.dom.Node is implemented by SAAJ (com.sun.xml.internal.messaging.saaj.soap.ver1_1.BodyElement1_1Impl) which fails when we validate it with the JA

Re: [ANN] Apache CXF 2.7.6/2.6.9/2.5.11 released

The release notes link is incorrect, it points to the wrong version. Gary On Jul 23, 2013, at 4:10, Daniel Kulp wrote: > > The Apache CXF team is proud to announce the availability of the latest > patches: 2.7.6, 2.6.9, and 2.5.11. > > One very important note: this is the last planned release

Re: CXF soap client send an empty SoapAction.

Can you try the current version of CXF, 2.7.5? Gary On Jun 14, 2013, at 5:17, Thomas Manson wrote: > Hi, > > I've generated my WSDL client with CXF 2.7.0 (from 2.7.1 I get a NPE at > generation time, didn't find a workaround). > > When I use the client I get a NPE on the server side, while wi

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

On Tue, Oct 30, 2012 at 11:12 AM, Daniel Kulp wrote: > > On Oct 29, 2012, at 6:29 PM, Gary Gregory wrote: > > > Am I hearing different approaches here? > > > > (1) Don't send SOAPAction. I'm still not sure how to tell > > JaxWsDynamicClientFactory ho

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

On Tue, Oct 30, 2012 at 11:12 AM, Daniel Kulp wrote: > > On Oct 29, 2012, at 6:29 PM, Gary Gregory wrote: > > > Am I hearing different approaches here? > > > > (1) Don't send SOAPAction. I'm still not sure how to tell > > JaxWsDynamicClientFactory ho

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

spring-context > 3.0.7.RELEASE (or whatever else) > > > Glen > > > > > On 10/29/2012 10:04 PM, Gary Gregory wrote: > >> Hi All, >> >> In order to sort things out between our test code and server, I am testing >> ou

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

u advise I just remove SOAP actions from the WSDL? Thank you! Gary On Mon, Oct 29, 2012 at 6:29 PM, Gary Gregory wrote: > Am I hearing different approaches here? > > (1) Don't send SOAPAction. I'm still not sure how to tell > JaxWsDynamicClientFactory how to do that. There

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

iceProviderService>from >> class com.seagullsw.appinterface. >> **server.comm.soap.**SoapServletCxf$**LdeWebServiceProvider >> >> >> Looks like the server side isn't using the WSDL and thus may not have the >> proper Actions available for it. >> >&

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

thus may not have the >> proper Actions available for it. >> >> Dan >> >> >> >> >> >> On Oct 29, 2012, at 4:01 PM, Gary Gregory wrote: >> >> Hi All: >>> >>> I am updating our app server to 2.7.0 from 2.6.0

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

On Mon, Oct 29, 2012 at 5:16 PM, Steve Revilak wrote: > This is weird. I don't know where the "**"s come from but they are not in >> my config, logs or on pastebin where I see "The given SOAPAction >> test.**oneStringArgWssUsernameToken does not match an operation." >> > > Although this is off to

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

ttp://www.jroller.com/gmazza/** > entry/soap_calls_over_**wireshark<http://www.jroller.com/gmazza/entry/soap_calls_over_wireshark>) > that you're indeed getting those two asterisks over the wire? > > Glen > > > On 10/29/2012 04:28 PM, Gary Gregory wrote: > >>

Re: 2.7.0 vs. 2.6.0: org.apache.cxf.interceptor.Fault: The given SOAPAction test.oneStringArgWssUsernameToken does not match an operation.

ation-Behavior-td5713789.**html#a5713800<http://cxf.547215.n5.nabble.com/CXF-2-6-2-SOAPAction-Validation-Behavior-td5713789.html#a5713800> > > Glen > > > On 10/29/2012 04:01 PM, Gary Gregory wrote: > >> Hi All: >> >> I am updating our app server to 2.7.0 fr

Re: Improvement proposal for CXF Transformation Feature

On Thu, Oct 18, 2012 at 11:21 AM, Sergey Beryozkin wrote: > Hi Andrei > On 18/10/12 16:05, Andrei Shakirin wrote: > >> Hi, >> >> Actually CXF Transformation feature covers 99% of user needs: >> 1) changing input and output element names and namespaces >> 2) appending new input and output elements

Re: [Diploma thesis] Implement missing WS specification for CXF

>From this user's POV, anything security related. For example, we just about to >start using SAML and I am not sure how complete the CXF support is there. Gary On Jul 24, 2012, at 9:42, "Glen Mazza" wrote: > Hi Jan. Note WS-MetadataExchange has already been implemented, so you can > scratch

RE: Anyone use embedded jetty in production out there?

We use an embedded Jetty in our application server that we configure through a standard jetty.xml file. Gary -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Tuesday, June 12, 2012 8:44 AM To: users@cxf.apache.org Subject: Re: Anyone use embedded jetty in p

Re: clarifying questions re: CXF 2.6.0 recent changes

Could CXF simple deliver an all in one Spring jar? I'd do the same for Jetty. Seems simple and the extra bytes don't matter to my project. I imagine others would differ. Gary On Apr 27, 2012, at 13:06, "Mark Streit" wrote: > Hello, > > Recently we had a web service WAR project that used CX

Re: Aware of compatibility issue between CXF and Metro/Weblogic ?

On Apr 20, 2012, at 8:39, "Colm O hEigeartaigh" wrote: >> Regarding the "OnlySignEntireHeadersAndBody property", I don't think that >> the fact that, the BinarySecurityToken is not included in the response, is >> only linked to this property. According to me, my interpretation is that it >> is

RE: NullPointerException with WSDL loading (cxf 2.4.2 and 2.4.3)

Could code that uses Apache Commons VFS be plugged in at just the right spot to resolve "jar:file:..."? Gary -Original Message- From: Glen Mazza [mailto:gma...@talend.com] Sent: Friday, October 28, 2011 10:41 AM To: users@cxf.apache.org Subject: Re: NullPointerException with WSDL loading

Re: CXF User Poll: jetty-all or individual jars....

Now, why can't I get all my Spring framework in one jar too? :) Gary On Aug 23, 2011, at 12:41, "Gary Gregory" wrote: > See CXF-3741, it's an extra 800K on top of the 30MB that make up all jars. > > Gary > > On Aug 23, 2011, at 12:02, "Ron Wheeler&

Re: CXF User Poll: jetty-all or individual jars....

See CXF-3741, it's an extra 800K on top of the 30MB that make up all jars. Gary On Aug 23, 2011, at 12:02, "Ron Wheeler" wrote: > I would lean towards 2 but would be curious about what "a little bit" mean in > the phrase > > "increases the size a little bit". > > If this means 30-50k bytes

Re: CXF User Poll: jetty-all or individual jars....

+1 for #2. I wrote the Jira ;) Gary On Aug 19, 2011, at 14:01, "Daniel Kulp" wrote: > > I just wanted to get users opinions on: > https://issues.apache.org/jira/browse/CXF-3741 > > > Basically, right now, we ship just the 6 individual jetty jars that we need > for the various CXF features (

Re: ConcurrentModificationException on Client when processing SOAPHeaders....

On Jul 27, 2011, at 20:40, "Daniel Kulp" wrote: > On Wednesday, July 27, 2011 7:57:58 PM Gary Gregory wrote: >> Hi Dan, >> >> Any thoughts on the timing for 2.4.2? > > We need a release of WSS4J 1.6.2 first as we now rely on some of the new > functi

Re: ConcurrentModificationException on Client when processing SOAPHeaders....

Hi Dan, Any thoughts on the timing for 2.4.2? Gary On Jul 27, 2011, at 15:34, "Daniel Kulp" wrote: > > Just looked at the code > > > The JaxWsProxyFactoryBean doesn't have the synchronized flag on the create > method like the one on the superclass does. :-( > > You can likely workar

RE: Welcome Colm to the CXF PMC

All right! Congratulations Colm. Looking f/w more great CXF releases :) Gary -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Wednesday, July 13, 2011 13:40 PM To: d...@cxf.apache.org; users@cxf.apache.org Subject: Welcome Colm to the CXF PMC I'm very happy to repor

RE: CXF and Jetty versions

Thank you for the update Dan. Jetty 8 requires Java 6: http://wiki.eclipse.org/Jetty/Starting/Porting_to_Jetty_7 Gary -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Wednesday, June 01, 2011 10:40 AM To: users@cxf.apache.org Cc: Gary Gregory Subject: Re: CXF and

CXF and Jetty versions

Hi All: Is there a release schedule for CXF 2.4.1? Are there plans for moving CXF to Jetty 8 when it is released? Would that be in the 2.x branch or a 3.x release? I think Jetty 8 may require Java 6. Thank you, Gary

RE: SAML2.0 Assertions in CXF

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Wednesday, February 09, 2011 19:42 > To: users@cxf.apache.org > Cc: Morris Jr, David P > Subject: Re: SAML2.0 Assertions in CXF > > On Wednesday 09 February 2011 1:19:16 pm Morris Jr, David P wrote: > > Is CXF curre

RE: WSIF and CXF

Sound like this project page should be better annotated or the project moved to some dormant area of the site... Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 • Atlanta, GA 30326 • USA Tel: +1.404.760.1560 Email: ggreg...@seagullsoftware.com Web

RE: 2.2.13?

I would want to keep the build active as well. You just never know when you'll need to release a critical fix. Then, the last thing you want is to get tripped up by your build infrastructure. Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 • Atlant

RE: Failure building latest trunk

Hi All: The problems I've seen in general with spaces in path names is when code tries to use a URL path without converting the %20 and other %'s to proper characters. This is no good: aURL.getFile() orr in general anything URL provides as a "file" or for use with a java.io.File This is ok: aUR

RE: CXF in Action

;nothing ventured, nothing gained. > > -- Robert > > On Mon, 13 Dec 2010 19:29:43 +, Gary Gregory > wrote: > > If one or more knowledgeable CXFers are interested in writing an In > > Action book, let me know and I can help move the ball forward. > > > > Ga

RE: CXF in Action

If one or more knowledgeable CXFers are interested in writing an In Action book, let me know and I can help move the ball forward. Gary > -Original Message- > From: robert [mailto:rob...@gliesian.com] > Sent: Monday, December 13, 2010 11:38 > To: users@cxf.apache.org > Subject: RE: CXF

RE: CXF in Action

Hi All: As an author (JUnit in Action http://www.manning.com/tahchiev/ and Spring Batch in Action http://www.manning.com/templier/), I've worked with Manning and I can help shepherd (co-write, edit, introduce, propose) an In Action book. Who at or around CXF would be available as an author? Mor

2.3.1 jar names with "2.3.0"?

Hi All: Any reason why the cxf-xjc* jars have "2.3.0" in the name instead of "2.3.1"? Any reason why Jetty 7.2.0 was used instead of 7.2.1? Thank you, Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA Tel: +

RE: IVY and CXF

Why not use the current version of CXF, 2.3.x? Gary > -Original Message- > From: mjparme [mailto:mjparme...@west.com] > Sent: Tuesday, December 07, 2010 11:33 > To: users@cxf.apache.org > Subject: Re: IVY and CXF > > > Of course, I figured it out on my own after asking for help, this g

RE: 2.3.1 status?

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Sunday, November 28, 2010 13:12 > To: users@cxf.apache.org > Cc: Jason Pell > Subject: Re: 2.3.1 status? > > On Thursday 25 November 2010 9:01:34 pm Jason Pell wrote: > > Hi, > > > > Is 2.3.1 still expected to be re

SAML how to

Hi All: Is there any CXF documentation or examples for using SAML? Thank you, Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA Email: ggreg...@seagullsoftware.com Web: seagull.rocketsoftware.com 

Re: cxf 2.3 and Jetty 7

Porting configuration files from jetty 6 to 7 is a pain. Jetty provides a utility to get you started but it will never get you 100% there. Manual editing is required. Gary On Oct 27, 2010, at 11:48, "Willem Jiang" wrote: > Are you deploying the example into an OSGi platform? > If so there ma

RE: Apache CXF product branding

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Monday, October 25, 2010 06:21 > To: users@cxf.apache.org > Cc: Glen Mazza > Subject: Re: Apache CXF product branding > > On Monday 25 October 2010 8:36:15 am Glen Mazza wrote: > > While artistic and well-drawn, tho

RE: Jetty versions in 2.3.0

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, October 22, 2010 19:49 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Jetty versions in 2.3.0 > > On Friday 22 October 2010 8:44:18 pm Gary Gregory wrote: >

RE: Jetty versions in 2.3.0

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, October 22, 2010 17:27 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Jetty versions in 2.3.0 > > On Friday 22 October 2010 2:57:21 pm Gary Gregory wrote: > >

RE: Apache Commons pool versions in 2.3.0

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, October 22, 2010 17:28 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Apache Commons pool versions in 2.3.0 > > On Friday 22 October 2010 2:51:06 pm Gary Gregory wrote:

Jetty versions in 2.3.0

Hi All: Do you see any issue with replacing Jetty 7.1.6 with 7.2.0 in CXF 2.3.0? Thank you, Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA Tel: +1.404.760.1560 Email: ggreg...@seagullsoftware.com Web: seagull.rocketsoftware.com 

Apache Commons pool versions in 2.3.0

Hi All: Our server relies on Apache Commons Pool (ACP) 1.5.5 and I see that CXF 2.3.0 ships with ACP 1.5.2. We plan on shipping ACP 1.5.5 with our product and not 1.5.2. Do you see this as an issue? Could CXF 2.3.1 migrate up to ACP 1.5.5? Thank you, Gary Gregory Senior Software Engineer

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, October 22, 2010 07:50 > To: Gary Gregory > Cc: users@cxf.apache.org > Subject: Re: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and > 2.2.11 > > On Thursday 21 Oc

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Thursday, October 21, 2010 19:08 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and > 2.2.11 > > On Thursday 21 O

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Thursday, October 21, 2010 15:55 > To: Gary Gregory > Cc: users@cxf.apache.org > Subject: Re: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and > 2.2.11 > > On Thursday 21 O

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

ntextPath) throws IOException { String address = getAddress().getAddress().getValue(); if (address.startsWith("http")) { return URI.create(address).getPath(); } return contextPath + address; } Thank you, Gary > -Original Message- > From: Gary Gregory [mailto:gg

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

" [\n]" 2010-10-21 15:05:55,269 [main] DEBUG: << " [\n]" 2010-10-21 15:05:55,269 [main] DEBUG: << " [\n]" 2010-10-21 15:05:55,269 [main] DEBUG

RE: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Thursday, October 21, 2010 13:41 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: NullPointerException migrating from 2.1.10 to CXF 2.3.0 and > 2.2.11 > > > I really don&

NullPointerException migrating from 2.1.10 to CXF 2.3.0 and 2.2.11

tartsWith("http")) { return URI.create(address).getPath(); } return contextPath + address; } ? Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA Tel: +1.404.760.1560 Email: ggreg...

RE: Version 2.2.10 scehdule?

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Monday, August 16, 2010 11:10 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Version 2.2.10 scehdule? > > On Monday 16 August 2010 1:57:33 pm Gary Gregory wrote: >

RE: Version 2.2.10 scehdule?

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Wednesday, August 11, 2010 12:23 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Version 2.2.10 scehdule? > > On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote: >

RE: Version 2.2.10 scehdule?

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Wednesday, August 11, 2010 12:23 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Version 2.2.10 scehdule? > > On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote: >

Version 2.2.10 scehdule?

Hi All, We are currently using a 2.2.10 snapshot build to address two bugs. Is there a schedule for a 2.2.10 release? Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com

Hudson CXF builds

://hudson.zones.apache.org/hudson/view/CXF/job/CXF-2.2.x-JDK15/ Which was run 5 hours ago. What is the difference between these two builds? And which one should I keep track of? Thank you, Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org

RE: CXF, Eclipse and Maven

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Thursday, July 22, 2010 18:38 > To: Gary Gregory > Cc: users@cxf.apache.org > Subject: Re: CXF, Eclipse and Maven > > > Try one of: > > mvn process-test-sources eclipse:eclipse

RE: DynamicClientFactory broken with JAXB 2.2.1

Tracking issue with patch here: https://issues.apache.org/jira/browse/CXF-2907 Allow DynamicClientFactory to use any JAXB version 2.1 or greater. Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com

RE: DynamicClientFactory broken with JAXB 2.2.1

s returned and the test AegisClientServerTest#testDynamicClient() fails in Maven but passes in Eclipse. Confusing. It also looks like the method wants a more plain version format like "2.1.2" Any help is appreciated here. Gary Gregory Senior Software Engineer Seagull S

CXF, Eclipse and Maven

f-systests-databinding was fixed by adding: And problems remain in: - cxf-systests-codegen - cxf-systests-ws-specs Thoughts? Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com

RE: DynamicClientFactory broken with JAXB 2.2.1

Thanks Dan. I am currently running a local build to see if my version of isJaxb21() breaks anything. I can then see if it fixes my issue... I'll post a patch to JIRA if all goes well. Thank you again for your prompt patch application for [CXF-2900] and guidance. Gary Gregory Senior Sof

RE: DynamicClientFactory broken with JAXB 2.2.1

I should add that in isJaxb21, the expression sc.getOptions().getBuildID() returns "hudson-jaxb-ri-2.2-7" Gary > -Original Message- > From: Gary Gregory [mailto:ggreg...@seagullsoftware.com] > Sent: Thursday, July 22, 2010 11:27 > To: users@cx

DynamicClientFactory broken with JAXB 2.2.1

using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug [CXF-2900]. Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com

RE: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

I can now report that this build fixes our big bug [CXF-2900] and that our build is 'green'. Is there any schedule for 2.2.10 so we do not have to keep a snapshot build in our deliverable? Thank you, Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullso

RE: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

Ah, great, thank you. I can also see the console output here: http://hudson.zones.apache.org/hudson/job/CXF-2.2-deploy/224/org.apache.cxf$apache-cxf/console Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org

RE: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Monday, July 19, 2010 07:14 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams > open which causes input files to be lo

RE: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

Odd, now it is Sunday and still no refresh since Friday on: http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/2.2.10-SNAPSHOT/ I thought the snapshot build was a daily build? Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg

RE: [CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

Will there be a snapshot build today? http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/2.2.10-SNAPSHOT/ ? Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com > -Original Mess

[CXF-2900] WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.

- [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 minutes 31 seconds [INFO] Finished at: Thu Jul 15 18:10:02 PDT 2010 [INFO] Final Memory: 143M/322M [INFO] --

RE: [ANN] Apache CXF version 2.2.7 released!

Nice work, thank you! This fixes an outstanding issue for us. Keep up the good work :) Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com > -Original Message- > From: Daniel Kulp [mai

RE: what stax implementation is being used by cxf?

Is there a reason why CXF ships with Woodstox 3.x instead of 4.x? Thank you, Gary > -Original Message- > From: Benson Margulies [mailto:bimargul...@gmail.com] > Sent: Wednesday, March 24, 2010 12:25 > To: users@cxf.apache.org > Subject: Re: what stax implementation is being used by cxf?

RE: [ANN] Apache CXF versions 2.2.6 and 2.1.9 released

Nicely done team CXF! I've been testing 2.2.6 since yesterday and so far no problems migrating from 2.2.4. Gary > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Monday, January 25, 2010 11:25 > To: d...@cxf.apache.org; users@cxf.apache.org > Subject: [ANN] Apach

RE: [CXF-2594] No SOAP fault XML elements when a Fault is thrown in the output chain after SAAJOutInterceptor

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Thursday, January 07, 2010 12:16 > To: users@cxf.apache.org > Cc: Gary Gregory; ggreg...@apache.org > Subject: Re: [CXF-2594] No SOAP fault XML elements when a Fault is > thrown in t

RE: [CXF-2594] No SOAP fault XML elements when a Fault is thrown in the output chain after SAAJOutInterceptor

7:48 > To: users@cxf.apache.org > Cc: Gary Gregory; ggreg...@apache.org > Subject: Re: [CXF-2594] No SOAP fault XML elements when a Fault is > thrown in the output chain after SAAJOutInterceptor > > > I just committed some fixes to the unwind/handleFault logic in a couple > int

[CXF-2594] No SOAP fault XML elements when a Fault is thrown in the output chain after SAAJOutInterceptor

Hi All, Has anyone gotten the chance to look at: [CXF-2594] No SOAP fault XML elements when a Fault is thrown in the output chain after SAAJOutInterceptor https://issues.apache.org/jira/browse/CXF-2594 Thank you, Gary --- Gary Gregory Seagull Software ggreg...@seagullsoftware.com

RE: Inflexible fault interceptor chain?

> -Original Message- > From: Gary Gregory > Sent: Sunday, December 27, 2009 16:16 > To: 'Daniel Kulp'; users@cxf.apache.org > Subject: RE: Inflexible fault interceptor chain? > > > -Original Message- > > From: Daniel Kulp [mailto:dk...@ap

Test failure for JAXWSDefinitionBuilderTest.testBuildDefinitionWithXMLBinding

Hi All: I am running unit tests from Eclipse (3.6M4 / JUnit 4) and I see this failure with the latest from SVN 2.2.x. Does anyone else see this failure? Thank you, Gary Rerun org.apache.cxf.tools.wsdlto.jaxws.wsdl11.JAXWSDefinitionBuilderTest org.apache.cxf.tools.wsdlto.jaxws.wsdl11.JAXWSDefin

RE: Inflexible fault interceptor chain?

> -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Tuesday, December 22, 2009 10:06 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Inflexible fault interceptor chain? > > > Can you create a small test case and attach to a j

RE: Inflexible fault interceptor chain?

xbNpa(org.apache.cxf.tools.wsdlto.jaxb.JAXBCodeGenOptionTest) Tests run: 124, Failures: 4, Errors: 82, Skipped: 1 > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Tuesday, December 22, 2009 10:06 > To: users@cxf.apache.org > Cc: Gary Gregory > Subject: Re: Inflexible fault interceptor chain?

RE: Inflexible fault interceptor chain?

I'll see if I can create a standalone test... in the meantime I am trying to see if my fix breaks 2.2.6-SNAPSHOT tests. Gary > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Tuesday, December 22, 2009 10:06 > To: users@cxf.apache.org &

RE: Inflexible fault interceptor chain?

faceServer";>{c0a80102-00ce16ad010e75da25398002} http://schemas.xmlsoap.org/soap/envelope/"; /> Is this a bug? Why would there be a dummy writer put in place? Is there another CXF way to do this? Thank you, Gary > -Original Message- > From

RE: Inflexible fault interceptor chain?

Ok, that worked! Thank you Dan, Gary > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, December 18, 2009 07:33 > To: users@cxf.apache.org > Cc: Gary Gregory; Lee Breisacher; Nikolay Glazyrin > Subject: Re: Inflexible fault

RE: Inflexible fault interceptor chain?

I'll give that a try. Thank you. Gary > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Friday, December 18, 2009 07:33 > To: users@cxf.apache.org > Cc: Gary Gregory; Lee Breisacher; Nikolay Glazyrin > Subject: Re: Inflexible

RE: Inflexible fault interceptor chain?

n a byte > array in its place. A pre-stream-ending interceptor can take those > bytes, apply XSL to them and then write them to the original > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/ > XMLStreamWriter.html>, before putting the original > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/ > XMLStreamWriter.html> back in it original slot in the message > content map. > > That seems like big old hack. > > Any ideas on a cleaner solution? > > Thank you, > Gary Gregory > Seagull Software > ggreg...@seagullsoftware.com > www.seagullsoftware.com >

Inflexible fault interceptor chain?

am/XMLStreamWriter.html>, before putting the original XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/XMLStreamWriter.html> back in it original slot in the message content map. That seems like big old hack. Any ideas on a cleaner solution? Thank you, Gary Gregory Seagull Software ggreg...@seagullsoftware.com www.seagullsoftware.com