Hello to XSOM, bye to Apache XML Schema

[Week 27]

I got a recommendation from a classmate to use XML Schema Object Model (XSOM) for the XML Schema parsing. I've looked into this and I'm glad to say after a few hours of studying the schema and search mailing list archives I'm managing to extract information from files.

I've am now moving on to try and build the tree to visually represent the XML schema.
I had a meeting with MOC on Thursday discussing the general progress of the project and the fact that I'm behind schedule. He encouraged me to continue working on getting the tree built so that a user may then build XPath expressions using my GUI. Once I have this working he suggested that we arrange another meeting to plan the next steps.

This sounds promising so hopefully I can get a fairly generic parsing process in place and the tree working soon.

Apache XML Schema not so good

[Week 26]

I've been spending the last few weeks trying to get used to the Apache XML Schema API so that I can begin to extract information from XML Schema files. This is proving quite a bit more complex than I imagined and has brought me way behind schedule.

I've been emailing the developers mailing list in search of support and have received some replies however I am still having problems extracting information. I may have to look into finding a completely different API for this.

Why does this bring me so behind schedule?
There are three main parts to the project:
- Parse XML Schemas and represent them in a GUI (I plan to use JTree)
- Allow the user to select nodes and produce the XPath expression
- Convert this to SQL and send query to a relational database and display
the results to the user.

Unless I can parse files then there is no way I can create the JTree so I need to fix this part before moving on. With other assignment deadlines at the moment this is proving difficult.