Thanks Jonathan, that worked like a charm. Just to make sure though, I
am supposed to deploy my server modules first using the Manage Modules
interface on the
Server Manager GUI before installing the new server component using
the Manage Server interface right? I did try it without deploying the
modules but it did not work, so
I deployed the modules and then installed the server component and
that worked just fine.
On Apr 26, 5:20 pm, Jonathan Kaplan <
jonathan...@gmail.com> wrote:
> There is no documentation for creating new services, but there are a bunch
> of examples:
>
>
http://code.google.com/p/openwonderland-modules/source/browse/trunk/0...http://code.google.com/p/openwonderland-modules/source/browse/trunk/0...
>
> The red5 example is probably the easiest to follow. If you look at the red5
> modules after it is built, you will see a structure like this:
>
> module.xml
> requires.xml
> runner/
> runner/red5-dist.zip
> weblib/
> weblib/red5-server-weblib.jar
>
> The entry point for the service is the "runner" class, which is located in
> red5-server-weblib.jar. This class basically specifies how the module will
> be deployed:
>
>
http://code.google.com/p/openwonderland-modules/source/browse/trunk/0...
>
> The important method is getDeployFiles(), which returns a set of zip files.
> In the red5 module, this includes the red5-dist.zip file from our module,
> and the wonderland-client-dist.zip which is supplied by Wonderland.
>
> Once you have a module with these components installed, you can create an
> instance of your service using the name of the runner class. See the
> "Configuring" section of the Red5 module README for details:
>
>
http://code.google.com/p/openwonderland-modules/source/browse/trunk/0...