cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Status of 2.5.0 release.....
Date Mon, 24 Oct 2011 21:44:32 GMT
On Tuesday, October 25, 2011 10:32:55 AM Dennis Sosnoski wrote:
> Hi Dan,
> I'm working on getting the WS-MakeConnection support in place, and
> expect to have that working by the end of the week.

Keep me up to date.  If I can help, feel free to ask.   :-)

> Aside from that, I saw you'd fixed some issues in the interface to JiBX,
> and mentioned having to work around some issues in the JiBX code itself.
> What were the JiBX issues you ran into? I'm planning to do a new JiBX
> release, and although it may not be in time for the CXF 2.5.0 release
> it'd be good to have the fixes in for 2.5.1.

Well, I'm not really sure they were bugs in JiBX.  It's very likely to be 
issues in how we're calling the JiBX tooling.   It would be very good if you 
were to look into that a bit.     If you try with the WSDL attached to:

When we called the BindingUtils.getDefinitions method to get the 
classname/qname maps, we're not getting anything as it looks like it wasn't 
traversing into the imports or something.  I was able to work around that a 
little by traversing into those myself.   I'm not sure if that's the intent or 
not.   However, it also looks like the QNames set into the MappingElement 
never includes the Namespace for elementFormDefault="unqualified" schemas.  
However, for top level elements, they are always qualified.   I try to detect 
that and generate better QNames, but I'm not sure what the intention was 

I did have to fix a bunch of issues with how we were calling the JiBX tooling.   
We were DEFINITELY doing it wrong.   How we're doing it now seems to be better 
(not generating a bunch of warnings and such from JiBX) but I'm still not sure 
it's "correct". 


>    - Dennis
> On 10/25/2011 09:50 AM, Daniel Kulp wrote:
> > Early this month, we talked about getting 2.5.0 out this month.   Since
> > then, we've made fairly good progress.  The WS-Notification stuff is in
> > (and I just created a simple sample showing it).   The STS is in.  
> > WS-MEX is in.   A ton of OSGi testing and enhancements have gone in.  
> > I really think things are "very close".
> > 
> > I currently have one issue that I'd like to fix, but it's really a "nice
> > to have" and I wouldn't block on it.   Basically, the saaj-impl Karaf
> > feature doesn't work on Java 5.   That requires a new release of the
> > bundle from SMX. I was hoping to chat with JB about that today, but
> > haven't been able to get a hold of him.   In any case, not something
> > I'd mark critical for 2.5 since the 2.4.x Karaf descriptors haven't
> > been installable on Java 5 for quite some time and no-one really
> > noticed.    :-)
> > 
> > Thus, I'm thinking about doing the 2.5.0 release later this week.   If
> > anyone has any other things they are working on and can get done by
> > then, please speak up.    Also, any testing, doc updates, etc... are
> > more than appreciated.
> > 
> > Also, I'll likely do a 2.4.4 release at the same time.   There is a bug
> > in 2.4.3 that prevents the osgi http transport and the JMX management
> > from working with Felix.   Since SMX uses Felix by default, it's
> > definitely an issue for them.
> > 
> > Is everyone in agreement with that plan?   Any other thoughts or
> > questions or concerns?   Keep in mind, there is always 2.5.1.   :-)
> > 
> > Thanks!
Daniel Kulp
Talend -

View raw message