Thanks for the info Sanjiva. I thought Axiom may have come from Axis2, I didn't realize it was so recent that it was separated out.
>I think you need to cut some slack to the team doing the work and >support their request. > >FYI these are not "policies" .. Apache does not have policies on this >stuff- we developers have to get together and come to an agreement. >Eran's note was sent in frustration because we're working hard to get >everything sync'ed up and completed and (as you know) we're doing RC >releases to get to a stable 1.0. In that context, I think the statement >that Axiom changes that break Axis2 should be avoided is reasonable Absolutely. I haven't contributed to either project at this point. I just wanted to ensure I voiced my opinion about the suggested practice (not policy - good correction : ) ). >Yes we can create a branch for releases- that's indeed the standard >approach. However, the 1.0 release of Axiom and Axis2 is critical enough >that I personally don't want to see other forward development in these >two projects until we stabilize and release them. YMMV, of course. I think this makes sense as Axiom is still tightly related to Axis2 having only recently been separated. Are there any other adopters of Axiom at this point? Lawrence Mandel Sanjiva Weerawarana <[EMAIL PROTECTED]> 04/25/2006 03:19 AM Please respond to [email protected] To [email protected] cc Subject Re: [Axis2 Build Failing] Re: svn commit: r396597 - /webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java Lawrence, in general your statement is acceptable. However, please recognize that we created Axiom as part of Axis2, it was in Axis2 until just a few weeks ago really, and we're trying to do a 1.0 release of a product that's been under development for nearly 2 years. I think you need to cut some slack to the team doing the work and support their request. FYI these are not "policies" .. Apache does not have policies on this stuff- we developers have to get together and come to an agreement. Eran's note was sent in frustration because we're working hard to get everything sync'ed up and completed and (as you know) we're doing RC releases to get to a stable 1.0. In that context, I think the statement that Axiom changes that break Axis2 should be avoided is reasonable. Finally the request was made to Glen, a core developer of both Axiom and Axis2. I'm sure Glen didn't know that his change broke Axis2- otherwise he'd either not have made the change or fixed Axis2 himself. The change is not critical for Axis2. However, it is a "good thing" kind of change in general which we should do .. but its not fundamentally critical that we get that into 1.0. If it can be made to work on time of course we can get it in yet. Yes we can create a branch for releases- that's indeed the standard approach. However, the 1.0 release of Axiom and Axis2 is critical enough that I personally don't want to see other forward development in these two projects until we stabilize and release them. YMMV, of course. Sanjiva. On Tue, 2006-04-25 at 03:00 -0400, Lawrence Mandel wrote: > > That seems like an odd policy to me. Once a project is separated out > (was Axiom part of Axis2 like XmlSchema?) from Axis2 or any other > project Axis2 then becomes a consumer of the project. To tell someone > that they can't make a change to Axiom because Axis is shutting down > seems like a dangerous precedent to set. It doesn't seem practical for > developers working on one project to have to follow the development > schedule of another project they may not be interested in. Exploding > this out, how would this work if 5 projects relied on Axiom? Would > changes ever be able to be made to the Axiom code and would the > project simply be killed by the overhead of consulting all the > consuming projects before making changes? > > As I'm told, the policy in WS is release early and release often. I > think this policy can work but does need some coordination of the > projects beforehand. For example, how about mapping out, if only a > month or two in advance, a release of Axiom that will be used for > Axis2. That way Axiom developers should know not to make breaking > changes as the release cycle approaches the end. As well, Axis2 > doesn't have to use the latest snapshot at all times as it's trying to > stabilize. Updating the snapshot on a less frequent basis may allow > you to make more progress in light of breaking changes. Alternatively, > Axiom can branch to allow development to continue while Axis2 shuts > down. > > Just my 2 cents coming from my experience working at Eclipse. (If > you're interested in taking a look at what Eclipse is doing about the > dependencies between projects take a look at [1].) Feel free to tell > me I'm way off base or shout out alternate/better solutions. > > Lawrence Mandel > > [1] http://www.eclipse.org/projects/callisto.php > > > > Eran Chinthaka > <[EMAIL PROTECTED]> > > 04/24/2006 01:59 AM > Please respond to > [email protected] > > > > > To > [email protected] > cc > > Subject > [Axis2 Build > Failing] Re: svn > commit: r396597 > - /webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java > > > > > > > > > Hi, > > I hope we made a clear statement saying, if some one is changing > something in axis2 related ws-commons project, he/she needs to check > at > least Axis2 whether its fine or not. But this particular commit breaks > Axis2 build. > > As you all might know we are in the process of releasing Axis2 1.0 and > we are really busy with the important issues related to 1.0. We can > not > continue with work related to Axis2 1.0 when the build is failing. > So the only option for me here is to revert this particular commit to > proceed with Axis2. > > Glen, please review this and commit this when you are sure that Axis2 > build is successful. And please do not commit anything without > checking > Axis2 as well, a humble request. > > > -- Chinthaka > > > > > > [EMAIL PROTECTED] wrote: > > Author: gdaniels > > Date: Mon Apr 24 09:15:24 2006 > > New Revision: 396597 > > > > URL: http://svn.apache.org/viewcvs?rev=396597&view=rev > > Log: > > Ensure default SOAPEnvelope has a valid parent (Synapse's XPath > mediator needs this) > > > > Modified: > > > webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java > > > > Modified: > webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java > > URL: > http://svn.apache.org/viewcvs/webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java?rev=396597&r1=396596&r2=396597&view=diff > > > ============================================================================== > > --- > webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java (original) > > +++ > webservices/commons/trunk/modules/axiom/src/org/apache/axiom/soap/impl/llom/soap11/SOAP11Factory.java Mon Apr 24 09:15:24 2006 > > @@ -272,6 +272,8 @@ > > SOAPEnvelopeImpl env = new SOAPEnvelopeImpl(ns, this); > > createSOAPHeader(env); > > createSOAPBody(env); > > + SOAPMessageImpl msg = new SOAPMessageImpl(); > > + msg.setSOAPEnvelope(env); > > return env; > > } > > > > > > > > > > >
