Hi John, I get compile problems when checking out the HEAD. Basically
I think you didn't add/checkin the org.apache.woden.internal.util.om.*
package.
Also, we need to add the additional jars to the build.xml - I volunteer.
I'm a bit concerned that a user of DOMWSDLReader now needs the axiom
and stax jars. Also concerned that the OMWSDLReader needs DOM jars -
but they're in the JRE anyway. I guess the user doesn't need axiom and
stax jars if only using DOMWSDLReader - should probably have a junit
for testing without those on the classpath.
Cheers,
Jeremy
On 7/4/06, John Kaputin <[EMAIL PROTECTED]> wrote:
I have committed Oshani's patch for OMWSDLFactory and OMWSDLReader. The
following jar files from the Axiom 1.0 release must be added to the
classpath for Woden to compile:
<classpathentry kind="lib" path="downloads/lib/axiom-api-1.0.jar"/>
<classpathentry kind="lib" path="downloads/lib/axiom-impl-1.0.jar"/>
<classpathentry kind="lib" path="downloads/lib/stax-api-1.0.jar"/>
John Kaputin
"Oshani
Seneviratne"
<[EMAIL PROTECTED] To
m> [email protected]
cc
03/07/2006 12:48
Subject
Re: OM / StAX implementation
Please respond to
[EMAIL PROTECTED]
he.org
Hi John,
I did not run the the patch I submitted against AllWodenTests. However
I wrote some test cases for OMWSDLFactory and the OMWSDLReader. And
those tests passed without any complaint :).
I guess the reason the tests failed for you is because the
readWSDL(String wsdlURI, ErrorHandler errorHandler) method is not
implemented in the OMWSDLReader. That method returns a null
DescriptionElement at the moment, and explains the test failures
you've got. The patch I submitted is sort of like a proof of concept
and only the readWSDL(String wsdlURL) method is implemented there.
That method seems to be working fine and returns a valid
DescriptionElement.
I will implement the remaining readWSDL signatures and send a patch
soon. But, in the mean time if you want, I could send in those test
cases I've written. But they were implemented separately from the
woden test suite. Anyway, it's just a matter of rewriting the DOM
test cases. So, would it be okay to integrate them into the woden test
suite? If so, can you suggest a naming convention to be used for the
OM based tests?
Thanks for reviewing the patch and apologies for not including the
Apache copyright boilerplate text. I will make sure to include it next
time I send a patch :)
Regards,
Oshani
---------------------------------------------------------------------
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]
