Yes, warning shots prior to sending are fair. I just don't want people
intimidated from going public if they feel they need to. This is an
ASF-wide issue, not just a CXF one.
Glen
On 2/27/2011 2:52 AM, Christian Schneider wrote:
Hi Glen,
as a last resort this may be a way to go. My advice
I am opposed to dropping 1.5. There are a surprising 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:
> Wel
I think, if only because of the nontrivial amount of upgrade work Dan
was mentioning earlier, we'll be keeping 1.5 at least for CXF 2.4.
I do have a philosophical concern about staying *too* much in the past
though. In my view, for the open source model to work, it needs to be
for the benefit
Glen,
While I'm sympathetic to your general argument, I don't think it's
especially applicable here.
Adopting 1.6 means allowing approximately 5 new functions in the
Arrays class. (OK, a slight exaggeration.) Really, the practical
impact of 1.6 is tiny. No one working on CXF is deprived of any
in
All true.
On 2/27/2011 7:57 AM, Benson Margulies wrote:
Glen,
While I'm sympathetic to your general argument, I don't think it's
especially applicable here.
Adopting 1.6 means allowing approximately 5 new functions in the
Arrays class. (OK, a slight exaggeration.) Really, the practical
impact
I'm still waiting to see one of the "abusive" emails you speak of Glen. So far
you just kind of come off as a goof.
And enough with the "inactive" jabs, Jeff's paid his dues. You don't question a
Sensei's belt just because you weren't around when he was competing.
Craig
On 2011-02-27, at 2:10
I plead with all and sundry to back off from this unedifying spectacle.
If someone posts something on a public list you don't like, start by
politely calling it out on the dev list. If you don't get an answer
that satisfies you, head for private@. If you think something truly
awful is going on, or
Hi All
I honestly don't understand why this thread hasn't died out yet.
IMHO (after rereading for the 3 time) what was meant to be a subtle
though a bit too over-elaborate remark involving the reference to the
Russian Tsar and the not so healthy core and which I read as an
attempt to protect the r
Hi Tomasz
I've spent some time and it is some sort of the asynchronous exception
which when captured shows the Date of the log entry. It is thrown when
the ViewerViewImpl.setEntries(List entries) is called. We'll
track it down soon :-)
Sergey
On Sat, Feb 26, 2011 at 1:23 PM, Tomasz Oponowicz
wr
String text = columnDefinition.getContent(entry);
in SelectableTable.setData
is causing it,
and it's only happening when the Date column is filled in, the Level
and Message are fine.
Looks like the code co0nverting the Atom/http-format date is brittle a bit
cheers, Sergey
On Sun, Feb 27, 2011
May be this can help -
http://www.ibm.com/developerworks/library/specification/ws-wadlwsdl/index.html
WSDL (pre-2.0) describes SOAP engpoints. WSDL 2.0 includes appropriate
annotations
for REST services. WADL is geared towards description of resources which
is what
REST/HTTP is based on.
I a
Apologies for my late posting. I missed the later postings on this by a
few of you.
If it helps that's awesome otherwise you can just ignore it.
Regards
On 2/27/2011 10:48 PM, Demetris wrote:
May be this can help -
http://www.ibm.com/developerworks/library/specification/ws-wadlwsdl/index.ht
12 matches
Mail list logo
