cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Holtzman <jholtz...@berkeley.edu>
Subject Re: Final steps toward 2.3
Date Mon, 04 Oct 2010 05:50:29 GMT
Sergey,
I've made several improvements (checking for validity of the padding, proper
handling of content length, etc) to jsonp handling, so if possible, I would
wait on that patch.  I can attach a new version later this week, but I
wouldn't want that to impact anybody's schedules.

Thanks,
Josh

On Sun, Oct 3, 2010 at 10:49 PM, Sergey Beryozkin <sberyozkin@gmail.com>wrote:

> I've tried to figure out how to break a dependency between CXF JAXRS bundle
> and wsdl4j and I had to create
> https://issues.apache.org/jira/browse/CXF-3021, as I'm not sure we can fix
> it in time for 2.3; unless some obvious refactoring can be done then we'd
> have to postpone fixing it...
>
> JAXRS 1.1 TCK should be green; I'll to check a Josh's JSONP patch and see
> if
> I can do a minor WADL enhancement to do with simple types as discussed on
> the users list if I have the time left.
>
> cheers, Sergey
>
>
> On Fri, Oct 1, 2010 at 10:25 PM, Daniel Kulp <dkulp@apache.orgI've> wrote:
>
> >
> > I'd still like to get 2.3 released next week if possible.   However,
> there
> > are
> > still some things to do:
> >
> > 1) JIRA triage - could everyone please look through the JIRA items that
> > would
> > fall into your area and see if any of them are resolved.  I'd like to get
> a
> > good handle on what is there.
> >
> > 2) Issues with attachments - the scripts we had for that hasn't run since
> > the
> > last JIRA upgrade.(MONTHS)  I finally spent several hours today chasing
> > that
> > down and got it working.  I just sent a report for the last 40weeks.   It
> > would be good if people could take a look over them and see if any of the
> > attachments are useful patches that could be applied.
> >
> > 3) JIRA's blocked on external  - we've upgraded to JAXB 2.1.13 (and
> 2.2.1)
> > so
> > some of these are probably resolvable.   Once WSS4J 1.5.9 is in central,
> > some
> > more are probably resolvable.   Just need to check and test.
> >
> > 4) Documentation - again, we need to make sure all the new things are
> > properly
> > documented and listed on the release notes/migration guide[1].   Things I
> > know
> > still need work:
> >
> >   a) Continuation changes - Willem, can you handle that?
> >   b) Aegis schema validation jar requirements - the schema validation
> stuff
> > added to [2] requires some extra jars (msv things).  Need to track down
> the
> > list and add them to the docs.
> >
> > 5) Testing samples - I'd like to test the samples FROM THE KIT downloaded
> > from
> > [3].    Those kits are built with Java 5 (which is what I'll do for the
> > release) so it's a bit different than what I think many of us are using
> as
> > the
> > deps are a bit different for java6.   I'd like to make sure everyhthing
> is
> > OK.
> >
> > 6) JAX-WS and JAX-RS TCK's.   Sergey and I are on these.
> >
> > Anything else?
> >
> >
> > [1] http://cxf.apache.org/docs/23-migration-guide.html
> > [2] http://cxf.apache.org/docs/aegis-21.html
> > [3]
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/cxf/apache-
> > cxf/2.3.0-SNAPSHOT/<
> https://repository.apache.org/content/repositories/snapshots/org/apache/cxf/apache-%0Acxf/2.3.0-SNAPSHOT/
> >
> >
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message