+1 from. Thanks.
On 9/26/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1
On 9/25/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote:
> +1 for Woden M6
>
> Oshani
>
> On 9/26/06, John Kaputin <[EMAIL PROTECTED]> wrote:
> >
> > I have placed the M6 release candidate at:
> > http://people.apache.org/dist/ws/woden/milestones/1.0.0M6-incubating/
> >
> > Woden committers please vote to release this build as the Milestone 6
> > release, via the builds page on the Woden website:
> > http://incubator.apache.org/woden/dev/1.0/builds.html
> >
> > Please vote as soon as possible as M6 is being release primarily for
> > the Axis2 1.1 release due Sept 29th. Time is running out for this and a
> > further vote is required from the Incubator PMC.
> >
> > This release includes the following new features:
> >
> > An implementation of the Woden API based on StAX parsing and AXIOM.
> > This implementation uses the same programming model (API) as the DOM
> > implementation, however a different WSDLFactory implementation class
> > is needed to instantiate the StAX/AXIOM implementation (i.e.
> > OMWSDLFactory).
> >
> > The way that elements are created and added by the Woden API has been
> > change to better support the scoping described by the WSDL 2.0
> > specification. The createXXXElement factory methods on
> > DescriptionElement have been removed and instead the addXXXElement
> > methods present on all parent elements instantiate and add the
> > appropriate child elements. The relevant child elements have been
> > changed to store their name as an NCName rather than a QName, but the
> > QName is still available via the API (i.e. derived from the target
> > namespace).
> >
> >
> > Since upgrading to XmlSchema 1.1 one of the W3C Testcases "testSchemaId1G"
> > is failing, apparently due to fragids on the schema import. The M6 release
> > notes capture this failure and state that it will be addressed for M7.
> >
> > I have just been reviewing the info at [1] and [2] which indicates that the
> > release files must be signed. I only discovered this requirement at
> > Apachecon and I don't yet have signing keys or any presence on the web of
> > trust. Our earlier milestone releases were not signed, but as this was an
> > oversight on our part they probably should have been.
> >
> > The M6 release archives have MD5 hashes, but no signatures. I will not be
> > able to create keys and distribute my public key in time for the Axis2 1.1
> > release, so can anyone other committers help here by signing the release
> > files?
> >
> > [1] http://www.apache.org/dev/release-signing.html
> > [2] http://incubator.apache.org/guides/releasemanagement.html
> >
> > regards,
> > John Kaputin
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
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]
