On Sunday, August 21, 2011 2:47:17 PM Benson Margulies wrote: > That's two positives. @dkulp, you listening? Got an opinion?
Personally, I really feel very strongly either way. 2.0 is out and works fine and I *personally* haven't really run into issues with conflicts yet that aren't easily resolvable. If you are talking about CXF users, they are likely to also hit the same thing with WSS4J and similar (that have big updates in the same package names). That said, the entire update to XmlSchema 2 didn't seem to impact any CXF users significantly at all. Thus, I don't think changing the package names would impact them much either. Thus, I'm a -0 to changing them. Dan > > On Sun, Aug 21, 2011 at 2:09 PM, Andreas Veithen > > <[email protected]> wrote: > > On Wed, Aug 17, 2011 at 03:36, Benson Margulies <[email protected]> wrote: > >> Oh, a few hours. > > > > Considering the poorer development standards, for Axis2 this would > > take considerably more time and I don't have the motivation right now. > > I think you should go ahead an change the package names for 2.1. > > > >> I could perhaps look into making the changes to woden, but would you > >> want that without the package renames? > >> > >> On Tue, Aug 16, 2011 at 1:45 PM, Andreas Veithen > >> > >> <[email protected]> wrote: > >>> Indeed, Woden depends on XmlSchema as well. > >>> > >>> How much time did it take you to port CXF to XmlSchema 2.0? > >>> > >>> Andreas > >>> > >>> On Tue, Aug 16, 2011 at 19:27, Benson Margulies <[email protected]> wrote: > >>>> Wasn't there one of the 'w' projects related to wsdl? Or am I just > >>>> imagining the non-Axis2 case? Axis2 would probably be enough of a > >>>> reason. > >>>> > >>>> On Tue, Aug 16, 2011 at 1:20 PM, Andreas Veithen > >>>> > >>>> <[email protected]> wrote: > >>>>> On Tue, Aug 16, 2011 at 17:44, Benson Margulies <[email protected]> wrote: > >>>>>> Based on email since we released 2.0, I've become convinced > >>>>>> that it > >>>>>> was a mistake to leave the package names alone and change all > >>>>>> the > >>>>>> APIs. There are a few outstanding JIRA. I propose to make a > >>>>>> branch for 'urgent' fixes atop 2.0, and then aim the trunk at > >>>>>> 2.1, and rename the packages. This would make it possible for > >>>>>> one program to use both 'current' and the 1.4 versions that > >>>>>> are still stuck in various slow-moving projects. > >>>>> > >>>>> What were the slow-moving projects (other than Axis2) that you > >>>>> identified?>>>>> > >>>>>> -------------------------------------------------------------- > >>>>>> ------- To unsubscribe, e-mail: [email protected] > >>>>>> For additional commands, e-mail: [email protected] > >>>>> > >>>>> ---------------------------------------------------------------- > >>>>> ----- > >>>>> To unsubscribe, e-mail: [email protected] > >>>>> For additional commands, e-mail: [email protected] > >>>> > >>>> ------------------------------------------------------------------ > >>>> --- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>> > >>> -------------------------------------------------------------------- > >>> - > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
