+1
dkulp wrote:
>
> This is a vote to release CXF 2.0.11
>
--
View this message in context:
http://www.nabble.com/-VOTE--Release-Apache-CXF-2.0.11-tp23164569p23197466.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1
dkulp wrote:
>
> This is a vote to release CXF 2.1.5
>
--
View this message in context:
http://www.nabble.com/-VOTE--Release-CXF-2.1.5-tp23164609p23197467.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1.
dkulp wrote:
>
> [T]his is a vote to release CXF 2.2.1
>
--
View this message in context:
http://www.nabble.com/-VOTE--Release-CXF-2.2.1-tp23164637p23197468.html
Sent from the cxf-dev mailing list archive at Nabble.com.
http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop ?
Kid_79 wrote:
>
> Hi all,
> I'm new with attachments in CXF.
> Can you tell me where I get an example?
> Should I use an interceptor?
>
> Thanks
>
--
View this message in context:
http://www.nabble.com/CXF-with-Attachments-tp2
Also, Kid, please ask on the CXF-Users list. Same developers as well as many
others are on that one.
Kid_79 wrote:
>
> Hi all,
> I'm new with attachments in CXF.
> Can you tell me where I get an example?
> Should I use an interceptor?
>
> Thanks
>
--
View this message in context:
http:/
I don't think so. They're a private business and are welcome to make
whatever business decisions they feel will maximize their profits. If
they've come to the conclusion that removing XFire and not including CXF
maximizes income vs. outgo for them, so be it.
Glen
bimargulies wrote:
>
> The m
Hello, the search functionality on this page is no longer working (possibly
related to the new layout?):
http://cxf.apache.org/docs/index.html
Could someone in the know fix this?
Thanks,
Glen
--
View this message in context:
http://www.nabble.com/Search-field-in-user%27s-guide-doesn%27t-work-t
My WSDL-first example provides both a Maven- and an Ant-way to create the
project (See Step #3). The Ant script closely follows the Maven standard
directory layout and can be used interchangably with the Maven pom files.
It's also in beautifully fluent, error-free German for you:
http://www.
Normally, you're creating the SOAP client for somebody else's web service,
so, yes, you'll have the code generation within the client's pom. My
SOAP-client only example does that:
http://www.jroller.com/gmazza/entry/creating_a_soap_client_with
Creating a special jar for the wsdl-first example wa
I dunno...I believe proper Wikipedia etiquette, followed approximately 5% of
the time, is that people directly related to a Wikipedia article should not
play a role in editing it.
Glen
bimargulies wrote:
>
> http://en.wikipedia.org/wiki/Apache_CXF is somewhat lame, and the Progress
> folks cou
Hello, a sentence in the CXF docs I believe I had placed in a while back I
would like to confirm--for the two code examples here:
http://cwiki.apache.org/CXF20DOC/ws-securitypolicy.html#WS-SecurityPolicy-ConfiguringviaSpring
The sentence in question is: "The properties are easily configured as
Hello, on this page:
http://cwiki.apache.org/confluence/display/CXF20DOC/WS-SecurityPolicy, it
says:
"In CXF 2.2, if the cxf-rt-ws-policy and cxf-rt-ws-security modules are
available on the classpath, the WS-SecurityPolicy stuff is automatically
enabled. Since the entire security runtime is poli
Here you go: http://www.jroller.com/gmazza/entry/cxf_usernametoken_profile
Oliver Wulff-2 wrote:
>
> Hi there
>
> I've raised a jira (CXF-2553) to add a WS-SecurityPolicy based sample for
> UsernameToken.
>
> Can anybody have a look into this?
>
> Thanks
> Oli
>
--
View this message i
+1 also (if it hasn't been decided yet.)
Glen
bimargulies wrote:
>
> I'm +1 for turning off 2.1 support.
>
> On Mon, Nov 16, 2009 at 10:05 AM, Daniel Kulp wrote:
>
>>
>> Question for everyone.
>>
>> What are peoples thoughts about making 2.1.9 (in January) the last of the
>> 2.1.x line?
I think there have been calls for option #2 for other reasons besides
disabling the X509 checks. So #2 provides additional benefits--it's
probably something we should be supporting anyway. I also like option #2
politically (we're not explicitly allowing disabling of the X509 checks,
it's just we
middleware level (I happily do it on Tomcat for both
> http proxies and ssl certificates)
> => I would be very happy to make propositions on this.
>
> Cyrille
>
>
> On Thu, Mar 4, 2010 at 11:41 AM, Glen Mazza wrote:
>>
>> I think there have been call
Hmmm, I wonder if we could get Kevin to implement a Secure Token Service for
us (CXF-1940) instead, and if we could get Willem to mentor him for that as
well. But ZooKeeper is also good.
Glen
willem.jiang wrote:
>
> Hi kevin,
>
> It's an interesting project, I'd like to be your mentor.
> But
Sergey, be careful with your first reason--that of using the CallbackHandlers
to *return* passwords, that's an old erroneous design apparently since fixed
in WSS4J (https://issues.apache.org/jira/browse/WSS-183) that should not
necessarily be used as a reason for doing what you're doing--that proc
Glen,
On Wed, Apr 7, 2010 at 5:12 PM, Glen Mazza wrote:
>
> Sergey, be careful with your first reason--that of using the
> CallbackHandlers
> to *return* passwords, that's an old erroneous design apparently since
> fixed
> in WSS4J (https://issues.apache.org/jira/brow
Hmmm...I don't think that's allowed. If I recall the JAXB spec correctly,
you're supposed to get() the list and add elements to it. CXF uses Sun's
JAXB library, so that's the way it works.
Glen
HeJam wrote:
>
> Hi All,
>
> Does any one know ways to generate the set mothed of List attribute
+1
Glen
dkulp wrote:
>
>
> As mentioned earlier in the week, I'd like to get 2.2.8 released which
> contains some WS-SC fixes that are needed for Dennis' next Developerworks
> article. That said, 2.2.8 does contain over 44 other fixes and
> enchancements
> as well which are valuable for e
Hello, doing an svn update to get the latest CXF code, then mvn clean
-Pfastinstall is all fine. But subsequently running "mvn eclipse:clean
eclipse:eclipse -e -Pfastinstall" or "mvn -Psetup.eclipse -e" to set up
Eclipse (as explained here: http://cxf.apache.org/setting-up-eclipse.html)
creates t
Hello, JIRA 101 question: I noticed that we have 92 JIRA tickets that are
not "closed" but just "resolved"[1]--when do we use the latter instead of
the former, what prevents them from being moved to "closed"?
Thanks,
Glen
[1] https://issues.apache.org/jira/browse/CXF
--
View this message in
dkulp wrote:
>
> On Wednesday 26 May 2010 4:18:25 am Seumas Soltysik wrote:
>> If I call Enpoint.publish(address, implementation) and define a
>> like this:
>>
>> > name="{http://ws.iona.com/peer_manager}PeerManagerPort";
>> address="http://localhost:/services/PeerManagerService";
>>
dkulp wrote:
>
> On Wednesday 26 May 2010 12:15:56 pm Glen Mazza wrote:
>> dkulp wrote:
>> > On Wednesday 26 May 2010 4:18:25 am Seumas Soltysik wrote:
>> >> If I call Enpoint.publish(address, implementation) and define a
>> >>
>>
dkulp wrote:
>
>> 2. There are existing Java OAuth libraries. I am wondering if we could
>> use
>> one of them. From one hand maybe it is not good idea to make
>> cxf dependent on such library, but on the other
>> it's already tested and used by developers (mainly I mean Scribe lib). I
>> can wr
+1
Glen
dkulp wrote:
>
> This is a vote to release CXF versions 2.0.13, 2.1.10, and 2.2.9. The
> main
> reason for the releases is to fix a potential security vulnerability that
> will
> be disclosed soon. That is why 2.0.13 and 2.1.10 are included despite us
> not
> really "supporting
Perhaps a few items can be removed from Developers (placed under subtopics),
as a solid majority of CXF users will not be developing CXF so not as many
top-level links are necessary. Having too many links there may also confuse
people as they mistake "Developers" as Java coders using CXF instead
Well done!
Christian Schneider wrote:
>
> I have now changed the Navigation in the Wiki. Like Dan and you proposed
> I have restored the Mailing List and Jira Links.
>
--
View this message in context:
http://old.nabble.com/Discussion%3A-Cleanup-of-Wiki-Navigation-tp28791623p28824815.html
S
BTW, what does "endorse" mean here--I don't understand the concept.
Thanks,
Glen
jim ma wrote:
>
> 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
JAXB 2.2.1[1]?
[1] http://old.nabble.com/-ANN--JAXB-2.2.1-is-released-td28583411.html
dkulp wrote:
>
> Anything else anyone can think of?
>
--
View this message in context:
http://old.nabble.com/Stuff-left-for-2.3--tp28917374p28918191.html
Sent from the cxf-dev mailing list archive at Nabb
Problem fixed. I upgraded to Maven 2.2.1 and also nuked my local Maven
repository in case a file used in the build process was corrupted. But the
NPE while building CXF-API still occurred (I'm not sure why I said "mvn
-Pfastinstall" worked below--I noticed today I was getting the NPE just
runni
Łukasz Moreń wrote:
>
> I would like start coding OAuth support finally and I have some questions
> regarding that:
>
> 1. We agreed to use OAuth 1.0 spec, I assume to use:
> http://tools.ietf.org/html/draft-hammer-oauth-10
> as is suggested in: http://oauth.net/core/1.0a/. WDYT?
>
Hi Łukasz,
Just to confirm, why should the default *not* be JAX-WS 2.2--is it because
2.1 is presently the default version in the JDK? Is setting the default to
2.1 meant to help developers of CXF or users of CXF (i.e., does this default
have any bearing on CXF usage or is just when programming CXF internal
Team, I recently noticed a problem perhaps related to Tom's[1] regarding the
schemaLocation value in a JAXB binding file[2]. CXF enumerates schemas
using Schema Component Descriptors (SCD's) within a WSDL differently from
Metro, resulting in JAXB binding files being incompatible between the two:
But are the JAXB binding files that are passed into a wsdl2java tool part of
the TCK?
jgenender wrote:
>
> The one that doesn't pass the TCK? ;-)
>
> Jeff
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/Metro-vs-CXF-difference-in-enumerating-schemas-within-a-WSDL-tp10929
forums, but
>> any
>> idea which team is "wrong"?
>
> Technically, neither.Nothing in the jax-ws spec that dictates how this
> is
> supposed to be handled.
>
> Not sure what else to say. :-(
>
>
> Maybe something more like:
>
> nod
Umm, I think there's a solution here:
mybindingfile.xjb:
May I say that in all likelihood, the problem is that the XJC version used
by CXF's codegen plugin and the XJC version used by Metro's Maven plugin is
just different, and they interpret the schemaLocations in the JAXB bind
Team,
On the STS client page[1], the property keys configured for the direct and
indirect configuration options for an STS client seem unnecessarily
different:
direct configuration uses:
indirect configuration uses:
The example would probably be clearer if the configuration we
OK, since there are (at least) two types of client<->STS validation options,
I kept the upper one at UsernameToken and the lower at X.509 so readers will
have two examples, and also fattened up the documentation a bit. You can
add in the ActAs documentation elements once 2.3 is ready (or when you
http://www.jroller.com/gmazza/entry/cxf_x509_profile
http://cxf.apache.org/docs/ws-security.html
devkatiyar wrote:
>
> Hi,
> I want to implement the CXF web service security "Pass authentication
> tokens between services" can any one provide me working example or any
> resource from which i
Oops--forgot to mention, please use the CXF user's list for these types of
questions. The same developers are on both lists, it just keeps the
archives clean that way.
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-WS-security-tp1843114p1843396.html
Sent from the cxf-dev
Hi, when I type mvn archetype:generate from the command prompt I get a huge
number of skeleton projects to choose from (249 from my machine). Two of
them are for CXF projects:
40: remote -> cxf-http-basic (null)
41: remote -> cxf-jaxws-javafirst (null)
Question: How did I get a list of 249? Do
Team, Jitendra Kotamaraju of the Metro team recently created[1] a
JAXWS-Grizzly-HTTP SPI[2] (Service Provider Interface, I guess) that allows
for a programmatic change of the underlying servlet container used for the
Endpoint class (Grizzly instead of Jetty in our case.)
I haven't tested it on
May I ask why this normalization is helpful (instead of just using the
intended file path to being with)?
Does this affect just internal CXF use or external usage by users of
CXF? If the latter, the potential problem I see is that not all URI's
are file paths and, even if they were, I'm not sur
Daniel Kulp wrote:
>
> I don't think it will as I know I haven't implemented anything using the
> http/spi things yet and I don't remember Jim doing so either.The
> JAX-WS
> 2.2 TCK doesn't hit it at all. Thus, it's not really something that
> needs
> to be there to claim compliance.
atform-dependendent. Linux does none at all,
> for example. So it's not safe in general.
>
>
> On Fri, Jul 30, 2010 at 9:50 PM, Glen Mazza wrote:
>> May I ask why this normalization is helpful (instead of just using the
>> intended file path to being with)?
>> D
Team, our org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine uses
Eclipse's wrapper of the Jetty server (org.eclipse.jetty.server.Server)
instead of the actual object (org.mortbay.jetty.Server). Out of curiosity,
is there a reason for that--is the Eclipse wrappered version more useful or
mo
Sergey Beryozkin-5 wrote:
>
> This causes problems when doing non-Spring CXF deployments.
> Generally, we should really try to keep the Spring related code in .spring
> subpackages as it will make it simpler for CXF be integrated with other
> similar frameworks or deployed in containers providin
Sergey Beryozkin-5 wrote:
>
> Don't really get it... Or is it the case of someone missing the point that
> some users of CXF just do not want to use Spring ?
>
I don't know, I just think it would be nice if there was a separate Apache
Banana project that consists of Spring but with its JARs re
Sergey Beryozkin-5 wrote:
>
> Let me put it the other way. I haven't started this thread to complain
> about
> Spring, or start any debate about the use of Spring. What I'd like to
> convey
> is that IMHO it is in the interests of CXF to ensure that those
> integrators
> who prefer to provide no
I'd ask on the CXF user's list.
raflik-nb wrote:
How to fix that?
It might be me. For SAML references, I switched to KeyIdentifier instead of
wsse:reference because that's what a Metro web service was expecting, also
that was in harmony with the relevant specifications, as discussed here[1].
To be two-thirds complete, another patch in WSS4J will need to be
ap
How does one run the interopfest tests? If I make a change to the stsclient
I would want to make sure it doesn't break anything.
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/How-to-run-interopfest-tp2644543p2644543.html
Sent from the cxf-dev mailing list archive at Nab
Sorry, my bad, I did not realize they were actually different tests, I will
revert them.
Glen
Sergey Beryozkin-5 wrote:
>
> Hi Glen
>
> thanks for trying to clean up the tests, but I'd actually like them
> retained, but I agree some code optimization needs to be done though,
> please
> note,
+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. Every single
>> one of
>> > them came with a patch file to fix the issue:
>>
+1
On 12/05/2010 09:34 PM, Jim Ma wrote:
+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 is
Not to be hated, but is getPassword() one of those functions that should
be returning a char array instead of a string?
Glen
On 12/06/2010 04:40 PM, dk...@apache.org wrote:
Author: dkulp
Date: Mon Dec 6 21:40:18 2010
New Revision: 1042803
URL: http://svn.apache.org/viewvc?rev=1042803&view=re
Just be thankful you have hair to get gray. :)
On 12/08/2010 03:26 PM, Craig Tataryn wrote:
We were using WAS 6.1 and we needed to support HL7 payloads. Axis wasn't up to
snuff. Then trying to get modern versions of JAXB and XML APIs to work with WAS
wasted soo much time and money. It w
AS WAS 6.1 is built on Axis2, perhaps this thread would be better moved
to the Axis2 Dev list.
Glen
On 12/08/2010 06:29 PM, Andreas Veithen wrote:
On Wed, Dec 8, 2010 at 22:58, Craig Tataryn wrote:
On 2010-12-08, at 3:33 PM, Andreas Veithen wrote:
Looks like you made the same mis
Best to ask these questions on the User list, all the Devs are on it as
well. You can also search the CXF-Users list on Nabble and get dozens
of hits to your question.
Glen
On 12/10/2010 09:03 AM, phper...@gmail.com wrote:
Hello,
How a basic authentifiaction should be set up ?
I suppose i
posal?
Can I help to finalize its integration in a future version?
Regards
lmg
--
Glen Mazza
gmazza at apache dot org
http://www.jroller.com/gmazza
On 10.01.2011 12:06, cohei...@apache.org wrote:
Author: coheigea
Date: Mon Jan 10 17:06:06 2011
New Revision: 1057283
URL: http://svn.apache.org/viewvc?rev=1057283&view=rev
Log:
[CXF-3236] - Add support for an Issued Token extracted from a SAML assertion
- Upgrading to use WSS4J 1.5.11-SNAPSHO
Does it make sense to have a CONTENT_TYPE key but no value for it -- any
legitimate use case? Otherwise it may be better (if possible) to throw
some runtime exception to alert the developer of the client or web
service provider that he or she is erroneously adding the CONTENT_TYPE
key but not
+1
Glen
On 17.01.2011 23:26, Daniel Kulp wrote:
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes a
bunch of OSGi related issues that are needed for
Camel and ServiceMix.
Note: this vote a
I don't think a new vote is necessary, because as stated the vote covers
both portions. So everyone has voted +1 and +1 up to Jim.
To be valid, a veto must have a justifiable reason, and Jim certainly
does have one for CXF 2.3.2 but not CXF XJC 2.3.2, so the latter can
still proceed (if desir
JAXB?
Thanks,
Glen
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
Hi, we have an IONA reference in one of our namespaces:
http://cxf.apache.org/apidocs/constant-values.html#org.apache.cxf.tools.corba.common.ReferenceConstants.REFERENCE_NAMESPACE
Can/should we switch that to something CXF specific?
Thanks,
Glen
--
Glen Mazza
Software Engineer, Talend (http
JAX-WS, WS-Security, etc... to make sure any bugs
and issues can be resolved quickly and accurately.
Change Notification Preferences
View Online | Add Comment
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
tes. Apache is
not a locale for horn tooting.
Jeff
On Feb 2, 2011, at 7:23 PM, Glen Mazza wrote:
Unless it is blatant lies (i.e., non-reputable companies), I say let the companies do a
little bit of advertising on the Support page, even if they contradict each other or
embellish a bit. W
wouldn't make much sense if it were deliberate.
- Aaron
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
Fixed on 2.3.2 and upcoming 2.4. Also, I checked the official CXF
treasury ($0.00), sorry no money for the Monster drink.
Thanks,
Glen
On 09.02.2011 14:40, Glen Mazza wrote:
Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
he's become partial to other beverages).
Thanks!
On 2/11/2011 4:26 AM, Willem Jiang wrote:
Hi Glen,
Your fix has some side effect, I just committed another patch[1] to fix
the test error of SecurityPolicyTest.
[1]http://svn.apache.org/viewvc?rev=1069716&view=rev
Willem
On 2/10/11 11:47 PM, Glen Mazza wrote:
Fixed on 2.3.2
Actually, Kerek best to ask CXF questions on the us...@cxf.apache.org
list (also on Nabble), which has virtually everybody on dev (for
internal development of CXF only) plus tons of users.
I think you're running wsdl2java with the "-validate" option, the error
below might be WS-I Basic Profile
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 services, which has allowed him to provide many
substantive responses[2] to user list questions. He's also reported,
and in
On 2/17/2011 11:20 PM, dk...@apache.org wrote:
Author: dkulp
Date: Fri Feb 18 04:20:06 2011
New Revision: 1071879
URL: http://svn.apache.org/viewvc?rev=1071879&view=rev
Log:
Push more stuff to Neethi
Cleanup some policy API's
Modified:
cxf/trunk/api/src/main/java/org/apache/cxf/ws/policy/Asse
ommit privileges to Dennis (dsosnoski at apache
dot org).
Thanks,
Glen
On 2/16/2011 12: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 services,
On 2/19/2011 8:24 AM, Christian Schneider wrote:
The next thing is how to document our architecture. We have a good
starting point at
https://cwiki.apache.org/confluence/display/CXF20DOC/CXF+Architecture
but I think some important things are lacking. This page
describes the key structural eleme
Probably nice to drop Java 5 with CXF 2.4.0, especially if there's any
architectural cobwebs in CXF necessitated by supporting it; apparently
though ActiveMQ still supports Java 5
(http://activemq.apache.org/getting-started.html#GettingStarted-PreInstallationRequirements).
Glen
On 2/22/2011
Well, older versions of CXF--2.3.x and earlier--of course would
perpetually support JRE 5.0. It's just a question of moving forward, it
looks like right now 2.4 will still support 5.0 and maybe we'll switch
to 6.0 minimum in CXF 2.5. I didn't know about royalty concerns (do
you have a link f
+1
Glen
On 2/23/2011 6:23 PM, Eric Johnson wrote:
+1
On Wed, Feb 23, 2011 at 6:04 PM, Sergey Beryozkin wrote:
+1
thanks, Sergey
On Wed, Feb 23, 2011 at 8:30 PM, 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
You can at least view the WADL using ?_wadl at the end of the service
string in a browser.
Unsure, but JMS/REST would seem to be a contradiction, because REST is
based on the HTTP transport.
Glen
On 2/24/2011 9:17 AM, robert wrote:
The Web Application Description Language (WADL) is new to m
Best to ask on the CXF User's list, devs are on both, but many more
people are on Users.
You can look over the wire to see what is being sent/received[1]
differently--it could be something different, or in addition to, the NaN
issue. I believe we went from JAXB 2.1 to 2.2 between CXF 2.2 and
that I've seen.
- Dennis
On 02/02/2011 12:17 PM, Glen Mazza wrote:
Yes, it may be time for placing it in Apache Attic.
On 01.02.2011 18:00, Gary Gregory wrote:
Sound like this project page should be better annotated or the
project moved to some dormant area of the site...
Gary Gregory
Se
The User's list would be more appropriate for this question, also is it
not already answered within our user's guide?
Glen
On 2/24/2011 2:26 PM, robert wrote:
Does CXF use something in place of the WSDL JMS Extension and this
namespace: http://schemas.xmlsopa.org/wsdl/jms?
Thanks!
s and service extensions defined by this spec be
>>> better suited in a supported WSDL or WADL?
>>>
>>> I assume WADL as supported by CXF?
>>>
>>> Thanks!
>>>
>>>
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
> errors. I apologize your bug reports weren't given my immediate full
> attention, no matter how minor (or nonexistent) they were.
>
> On 2/25/11 10:01 AM, Glen Mazza wrote:
>> Bill, I'm all for plugging but if you could spend some time on fixing
>> the five (ra
try to keep things more cordial and pleasant.
Thanks!
Dan
On Friday 25 February 2011 10:01:52 AM Glen Mazza wrote:
Bill, I'm all for plugging but if you could spend some time on fixing
the five (rather simple) RESTEasy bugs I reported (RESTEAST-494, 495,
496, 497, and 502) over a month ag
eathe before pushing the send button. Feel free to hit
me up on IRC if you need to discuss.
Thanks,
Jeff
On Feb 25, 2011, at 8:01 AM, Glen Mazza wrote:
Bill, I'm all for plugging but if you could spend some time on fixing
the five (rather simple) RESTEasy bugs I reported (RESTEAST-494, 4
t] Re: SOAP over JMS and CXF.
Date: Sat, 26 Feb 2011 04:11:50 +0100
From: Jeff Genender
To: Glen Mazza
CC: Daniel Kulp
Hi Glen!
You are right, I didn't have to go off list. I sent you the private email out
of respect to you. But that clearly was all for naught - what a
Glen
--
Subject: [offlist again and no, onlist is not fine!] Re: [onlist is
fine!] Re: [offlist] Re: SOAP over JMS and CXF.
Date: Sat, 26 Feb 2011 04:11:50 +0100
From: Jeff Genender
To: Glen Mazza
CC: Daniel Kulp
Hi Glen!
You are right, I didn't have to go off list. I se
t any further
communication is private.
What do you think?
I do not want to judge what happened between Jeff and you as I do not
know all the details. So I can only ask both of you to try to bring this
back to a normal level.
Christian
Am 27.02.2011 08:31, schrieb Glen Mazza:
Folks, if Jeff Genende
sing number of people
out there who have barely bothered to stop requiring *1.4*. We could
put the animal sniffer to work to help head off any unfortunate
accidental dependencies on 1.6 APIs.
On Wed, Feb 23, 2011 at 7:53 AM, Glen Mazza wrote:
Well, older versions of CXF--2.3.x and earlier--of
, the practical
impact of 1.6 is tiny. No one working on CXF is deprived of any
interesting learning opportunities or functionality by continuing to
stick to 1.5.
--benson
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
Agreed. The CXF PMC also held that Jeff's email simply didn't reach a
level warranting public airing, given the general view--in which I've
grown more in agreement with--that *no* email warrants such airing. Any
types of questionable emails are best sent to the internal
priv...@cxf.apache.org
Thanks, appreciate it!
On 2/28/2011 4:40 PM, Jeff Genender wrote:
Forgiven. Thanks for the apology.
Jeff
On Feb 28, 2011, at 2:26 PM, Glen Mazza wrote:
Agreed. The CXF PMC also held that Jeff's email simply didn't reach a level
warranting public airing, given the general view
(1)'s my first choice, I can help with the Mavenization of the samples
(standard directory structure) if we go that route. Reasons:
1.) Providing Ant builds is for the benefit of those developers whose
capabilities are between what is needed to use Ant and what is needed to use
Maven (anyone pas
Sounds good. My WSDL-first tutorial shows how Ant can be used
(http://www.jroller.com/gmazza/entry/web_service_tutorial), I can
incorporate that into a new CXF sample (I've been meaning to rip out the Ant
from that tutorial anyway), or we can leverage the Ant scripts in the simple
wsdl-first and j
+1
On 04/13/2011 09:51 AM, 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 new versions of libraries like WSS4J, Neethi, XmlSchema,
> etc...
> that provide
+1
Glen
Daniel Kulp wrote:
>
> We've resolved over 100 issues since 2.4.1 and thus is time for a release.
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-4-1-take-2-tp4474979p4476203.html
Sent from the cxf-dev mailing list archive at Nabble.com.
1 - 100 of 246 matches
Mail list logo
