Chapter 7. Installation and Setup

webseer is currently distributed for a very short-term basis, as a single JAR file that contains everything AND the kitchen sink, which is why it's named webseer-XX-sink.jar. To use this in your code, just include it on the classpath like any other library and you should be able to call all the code referenced in this manual.

However easy this may seem, it's not the right way to distribute code and I imagine it's probably also illegal. In the future and hopefully by the time you get to this guide, the binary distribution will be in a ZIP file which mainly contains JAR files. You will need to put all of these on your classpath to run webseer. If you're using Eclipse or some other IDE, I'd advise copying them into a lib directory in your project and then just adding them all at once to your classpath. If you're running Java on command line, Java 6 now allows wildcard classpaths, so you can do something like java MyClass -classpath lib/*.jar to include all the webseer JARs at once. There are a lot of them, so I'd advise not trying to list them all out.

The only thing that these steps won't get you is the ability to generate the rendered-html model in webseer. This model requires an installation of XULRunner on your machine which serves as the Mozilla implementation for rendering the HTML. You can download and install that from Mozilla's site. After it's installed and registered, that model should work properly. If you don't need rendered HTML models, you should be good off the bat.