Wednesday, January 30, 2008

Getting WSO2 registry to generate valid ATOM feed

WSO2 registry has APP support , so any operation that we can do with UI can do with APP as well. In addition to that there is something called RemoteRegistry , where we can point to a registry and do operations using any kind of Java application , there the communicate taking place using APP. To support APP WSO2 registry uses Apache Abdera an APP implementation (I would say that is cool and easy to work with).

I thought that by default Abdera generate valid feed , but when I do a validation though W3C atom validator I found that we had a number of issues with the generated feed. Then I realized that it is our job to populate Abdara correctly , so I fixed all the issue and was able to generate valid atom feed from WSO2 Registry.

3 comments:

James Snell said...

I'm glad that you're happy with Abdera. Regarding the validation issues, very early on in the project I decided that, for a variety of reasons, I did not want to burden Abdera with a lot of input validation code. Developers need to ensure that the entry and feed documents they are producing conform to the standards; Abdera will make it easier but it won't do all the work for you.

Deepal Jayasinghe said...

Yes I think it is good idea that Abdera itself not going to validate the feed . however it would be great if it can provide some kind of tool to do the validation then we can use that to validate the feed (Then we might be able to integrate that to test case)

James Snell said...

I've considered implementing a validator for testing purposes but it just didn't seem to make sense given the availability of the feedvalidator (http://feedvalidator.org). You could download a local copy of that and incorporate it into your testcases.