(The to-do list has moved onto the site itself.)

IMPORTANT: Things To Do During Deployment

How to Run the Command-line App

See the runit script to run a development copy.

What it does inside is something like:

#!/bin/sh
APPCPATH=out_D/PG2KV0Client.jar; export APPCPATH
exec ./doit runclient -client out_D/PG2KV0.7.2.ear -name PG2Kcl "$@"
where out_D/PG2KV0.7.2.ear is the application archive file, out_D/PG2KV0Client.jar is the deploytool-generated application client runtime JAE, and PG2Kcl is the display name of the client to run; in this case the main client.

2001/12/31

2001/04/25

To deploy the EAR in WebLogic (6.0) I do the following:

2001/04/29

I have PG2K deployed and running in Sun's J2EE 1.3 Beta SDK and JBoss 2.2.1. Hurrah!

2001/04/25

To deploy the EAR in JBoss (2.2.1) I do the following: Problems encountered:

2001/04/24

To deploy the EAR in Orion (1.4.5) I do the following:

2001/03/26

Successfully deployed a stateless session bean (ExhibitFacade) to provide a transaction-safe view across multiple EJB tables.

2001/03/22

Doing first `date release' version; will also try to freeze this in SNiFF with a suitable tag.

2001/02/21

Made this sync exhibits, albeit slowly and in small numbers, with filesystem copies using the generic mechanism; config has been able to do this for a little while.

2001/02/20

See architecture diagram in docs/PG2Karch20010219.rtf

See new client-side command-line app development-time runit script.

2001/02/16

By default, no client authentication seems to be done for the WAR web components even when resources are listed as protected with a security constraint.

In j2sdkee1.3/config/security.properties I note a line:

enable.clientauth=false
not to mention many other things that look as if the server is left wide open.