This forum is for mechanize4j, a stateful web services client. Mechanize was originally an HTML client but this version also supports JSON and XML.
Right now the code generally works but we have little documentation or tutorials. The unit tests document most of the features... but that's of course not very accessible. We're working to improve this situation, and we could always use help.
Recently, caching was merged into the code.
What's next?
- Link support for JSON documents (based on URITemplates interpreted over JSON)
- Link support for XML... but not sure what standard to use
- Clean up the various search API (both a DSL and CSS selectors are available...)
Expect some changes to break the API, we'll keep those to a minimum but want to clean up the system while it's still young.
Also, we might split it up into modules by resource type... so mechanize-html and mechanize-json would be separate dependencies. Any opinions?
Cheers,
John Heintz