I just ran all the junits and see 2 failures. In addition to the
| testSchemaId1G |
failure that John mentioned, I also see the following:
| testImport3BFromOM | Failure | Unable to read
WSDL document because of java.lang.NullPointerException
junit.framework.AssertionFailedError: Unable to read WSDL document because of java.lang.NullPointerException at org.apache.woden.tests.OMW3CTestSuiteTest.testImport3BFromOM(Unknown Source) at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423) at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137) | 20 |
I checked out the latest code and am running this from within Eclipse. Any ideas?
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| John Kaputin <[EMAIL PROTECTED]>
09/25/2006 05:06 PM
|
|
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]
