• Sunday July 6th 2008
• Do you want fries with that project?

Skip to Content

multexi

resources:	Home Mailing List Documentation Download Source Code Project Plan SOC Specific

Source Code

The multexi source code is devided into two different components.

• MSC: Multexi Server Component
• MCC: Multexi Client Component

This document describes how to setup these two parts and how to let them work together.

Quick

This is just a quick HOWTO. If you initially setup MultExi you might want to go on with the next section.

	$> mkdir -p multexi/multexi_j2ee # MSC
	$> mkdir multexi/multexi_xpi # MCC
	$> cd multexi/
	$> export CVSROOT=:pserver:guest@mozdev.org:/cvs
	$> cvs login # (password is guest)
	$> cvs checkout -d multexi_j2ee multexi/src/multexi_j2ee
	   # wait .. zzZz
	$> cvs checkout -d multexi_xpi multexi/src/multexi_xpi
	$> vi multexi/multexi_j2ee/build.properties
	$> cd multexi/multexi_j2ee/
	$> ant deploy_dir
	$> vi multexi/multexi_xpi/build.properties
	$> cd multexi/multexi_xpi/
	$> ant deploy

	# open with firefox
	http://<server>:<port>/multexi/action/multexi/update.do
	http://<server>:<port>/multexi/action/multexi/getXpi.do
	
	# finished

Setup environment

Currently you will need the following components in your development/runtime environment:

Component	Version(s)	URL
Sun JDK	1.4.*/1.5.*	http://java.sun.com
Apache Tomcat	4.*/5.*	http://jakarta.apache.org/tomcat/
Jakarta Ant	1.6.5	http://ant.apache.org/
Deer Park	1.0+	http://www.mozilla.org/products/firefox/

Of course, any other J2EE- Container than Tomcat is usable, too.

Check out sources

You can check out the complete source as guest using the following cvs commands (password is guest):

	cvs -d :pserver:guest@mozdev.org:/cvs login
	cvs -z3 -d :pserver:guest@mozdev.org:/cvs co multexi

or view the source using the CVS web interface

To setup a functional build and runtime environment read the following instructions please:

• Create the MSC/MCC directories:

		$> mkdir -p multexi/multexi_j2ee # MSC
		$> mkdir multexi/multexi_xpi # MCC
	

• Check out the MSC/MCC via:

		$> cd multexi/
		$> export CVSROOT=:pserver:guest@mozdev.org:/cvs
		$> cvs login # (password is guest)
		$> cvs checkout -d multexi_j2ee multexi/src/multexi_j2ee
		   # wait .. zzZz
		$> cvs checkout -d multexi_xpi multexi/src/multexi_xpi
	

Now that you got the nessesary sources, please go on with the configuration of the server component, so that you can build and execute the deployment.

Setup MCC

Setting up the MCC is done quite fast.
First you have to adjust the file

	$> vi multexi/multexi_j2ee/build.properties

Every single parameter is described by a comment, so the adjustment won't be explained yet.
Now take a look into the build.xml file, please. There are four targets:

• init
• compile
• deploy_dir
• deploy_war

The init target will set up temporary directories for compilation and it will copy all files from

	multexi/multexi_j2ee/WebRoot/*

to

	multexi/multexi_j2ee/tmp/*

compile compiles all classes into

	multexi/multexi_j2ee/tmp/WEB-INF/classes

This target depends on init.

The two deploy_* targets are more or less the same with the difference that deploy_dir will deploy the deployment as a directory to webapps.dir and deploy_war will deploy all codes as war (Web Archive) file.

So, to build the server codes you have to do (e.g.):

	$> cd multexi/multexi_j2ee/
	$> ant deploy_dir

Before you call ant, you should add all JARs from

	multexi/multexi_j2ee/WebRoot/WEB-INF/lib/*

into your CLASSPATH.

Setup MSC

Finally you have to setup the MSC by editing:

	$> vi multexi/multexi_xpi/build.properties

You just have to copy the ${webapps.dir} property of the J2EE build.xml into ${opt.dir} property of you MSC component and then append multexi/resources.

	$> cd multexi/multexi_xpi/
	$> ant deploy

Later MultExI will be delivered containing a pre-deployed MultExI MSC package. For now, in development phase, the multexi.xpi has to be deployed manually into the server.
So please call the MSC buildfile only, if the deployed MCC in your ${webapps.dir} has been unzipped (if you called the deploy_war target.)
If you're going to play around with the codes, I recommend to use the deploy_dir target, so you do not have to start your J2EE container before deploying the MCC.

Final steps

For now, "only" two steps are left.
Every time you deployed the MCC into the server, you have to call

	http://<server>:<port>/multexi/action/multexi/update.do

The MSC will then unpack the multexi_orig.xpi, modify and publish it.
To install the MultExI extension into your Firefox call

	http://<server>:<port>/multexi/action/multexi/getXpi.do

It is important to install the MultExI extension that way, otherwise necessary information will be missing.

CVS clients and Help Documentation can be found at cvshome.org.

Today’s VCS Commits for the multexi project