Fwd: XmlSchema 2.0 - WAS: Mailing list changes.....

[ant elder <an...@gmail.com>]

FYI from the general@ws.apache.org list, there is a new version of
XmlSchema happening which might be of interest to Tuscany as we use
the 1.x version currently.

   ...ant

---------- Forwarded message ----------
From: Daniel Kulp <dk...@apache.org>
Date: Thu, Oct 14, 2010 at 2:42 PM
Subject: XmlSchema 2.0  - WAS: Mailing list changes.....
To: general@ws.apache.org
Cc: Sagara Gunathunga <sa...@gmail.com>


On Thursday 14 October 2010 9:26:17 am Sagara Gunathunga wrote:
> Sorry , this should be Axis2.
>
> IMO It's better to use same or compatible XmlSchems version among all
> Axis2 dependencies.

To be clear, XmlSchema 2.0 will NOT be a drop in replacement for 1.4.x.   It
shifts to java5 so API's have changed, but it also has cleaned up a lot of
things with the way Schemas are maintained and such.   Thus, it WILL require a
porting effort for projects to port from 1.4.x to 2.x.   That process is well
underway for CXF (Benson and I had all the tests passing yesterday, but then
we made some more changes and broke everything  :-)   ).

What Benson is looking for would be someone to try porting Woden and/or Axis2
to use the new API's to see if there is anything that would be an issue and if
there are additional changes or similar that would be good to get in.   If no-
one tries it, then Axis2/Woden really have a few options:

1) Stay on 1.4.x forever.

2) Accept whatever we decide on and live with it.   If you don't participate,
you don't really have a say.    :-)

3) At some point in the future, try porting and possibly propose additions or
something for 2.1 or similar.

Obviously, I'd love it if folks would try things sooner rather than later.
The more eyes looking at it, the better.

Dan


>
> Thanks ,
>
> On Thu, Oct 14, 2010 at 8:02 AM, Andreas Veithen
>
> <an...@gmail.com> wrote:
> > AFAIK, Axiom has no dependency on XmlSchema.
> >
> > Andreas
> >
> > On Thu, Oct 14, 2010 at 04:43, Sagara Gunathunga
> >
> > <sa...@gmail.com> wrote:
> >> Benson,
> >> I just tried to build Woden trunk with XmlSchema  2.0-SNAPSHOT but
> >> found few incompatibles , basically Woden use  XmlSchemaObjectTable
> >> ,XmlSchemaObjectCollection  classes that no longer available with
> >> XmlSchema  2 .0.  But I think we can port Woden to go with XmlSchema
> >> 2.0 . Unfortunately these days I'm quite busy with other stuff and I
> >> can't make any promise about exact time frame for these modifications.
> >> I will look in to this in my earliest possible time.
> >>
> >> BTW  I like to see how Axiom trunk compatible with XmlSchema  2.0 ,
> >> because  Woden have to wait until Axiom make this move.
> >>
> >> Thanks !
> >>
> >> On Wed, Oct 13, 2010 at 10:25 AM, Benson Margulies
> >>
> >> <bi...@gmail.com> wrote:
> >>> +1 here.
> >>>
> >>> Sagara, have you been following my progress on XmlSchema 2.0 :-)
> >>>
> >>> On Wed, Oct 13, 2010 at 9:50 AM, Sagara Gunathunga
> >>>
> >>> <sa...@gmail.com> wrote:
> >>>> Woden depends on XmlSchema and Axiom, so changes of above two projects
> >>>> are important to us. I think the same matter is common for many WS sub
> >>>> projects. If we all in a single dev list it's much more easy to have
> >>>> common discussions. Only drawback is this will  increase the traffic
> >>>> on common lists but this seems not a big issue to me.
> >>>>
> >>>> +1 for merging dev and user lists.
> >>>>
> >>>> Thanks !
> >>>>
> >>>> On Tue, Oct 12, 2010 at 5:10 PM, Daniel Kulp <dk...@apache.org> wrote:
> >>>>> I'd like to make a proposal that I think would the WS community and
> >>>>> would like peoples thoughts on the matter:
> >>>>>
> >>>>> I think it would be good for the community to combine all the
> >>>>> *-dev@ws mailing lists (and likely general@ as well) in to a single
> >>>>> dev@ws.apache.org. Likewise, combine all the *-user@ws lists into a
> >>>>> single users@.   Probably a single commits list as well.
> >>>>>
> >>>>> I really think having separate lists has caused the community to
> >>>>> fracture into small little eco systems with very little knowledge of
> >>>>> what is happening in the rest of the community propogating from
> >>>>> project to project.  Doing releases is hard as the other PMC members
> >>>>> may not be following the other projects at all.   By combining them
> >>>>> back into a few, broader lists, that should make it easier to follow
> >>>>> what the entire community is doing.    Once everyone really gets a
> >>>>> feel for things and are communicating with each other, I think it
> >>>>> will be easier to figure out what can/should be spun off, retired to
> >>>>> attic, etc...
> >>>>>
> >>>>> Also, I'd like the new lists changed to be moderated lists.
> >>>>> Moderated lists are much easer for new people to get involved in,
> >>>>> especially through places like nabble.
> >>>>>
> >>>>> Thoughts?
> >>>>>
> >>>>> --
> >>>>> Daniel Kulp
> >>>>> dkulp@apache.org
> >>>>> http://dankulp.com/blog
> >>>>
> >>>> --
> >>>> Sagara Gunathunga
> >>>>
> >>>> Blog - http://ssagara.blogspot.com
> >>>> Web - http://people.apache.org/~sagara/
> >>
> >> --
> >> Sagara Gunathunga
> >>
> >> Blog - http://ssagara.blogspot.com
> >> Web - http://people.apache.org/~sagara/

--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog