+1 for getting an XmlSchema release going.
I'd like to see a few more test cases, ideally, before going out the
door. How about doing a beta cycle, so we have a little time to try to
freshen up the tests and also to get some feedback from anyone
interested before really going 1.0? I'd propose
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Ws Wiki for change
notification.
The following page has been changed by JeremyHughes:
http://wiki.apache.org/ws/FrontPage/Woden/TaskList
--
I will see if I can get some tests whipped up this week. But, I would
like to point out that this code has been tested. While not via unit
tests, it is used in Axis, XFire, and other projects - which says
something about its stability IMO. So I would be more in favor of doing
a 1.0 and then a
Dan,
Let me give you something solid to chew on...How about porting this
test that we wrote for JAXME schema parser[1]. Original test for
XmlSchema is here [2] It uses the Xml Schema test suite [3]. You will
need to basically enhance the test to both read the schema and write
the schema and
John Kaputin and I have found a few
problems in XmlSchema while developing Woden [1]. We've fixed some but
do have some outstanding issues such as adding a URI resolver framework
and clearly defining an XmlSchema API capable of both reading and writing
schemas. I'd be in favour of creating a 1.0
We are about to begin our efforts in merging WSRF, Muse and Pubscribe
into a single Muse project.
Our intent is to:
-Maintain one website (Muse)
-Maintain one set of mailing lists
-Maintain one Jira instance
-Provide a single download (as opposed to three) artifact
This will make the projects
