Re: Dods standalone program

> Appears that you haven't set the DODS_HOME and ENHYDRA_HOME environment
> variables.

That's correct but:

1) ENHYDRA_HOME should not be an option (since DODS is independant from
ENHYDRA)
2) DODS_HOME should not be an option because DODS (IMO) should be a library
and not an installed program.

I send an email about that subject a few days ago, so please refer to it.

I digged into DODS and here the things that should be changed:

- DODS needs two configuration files and the required information to run the
dods-runtime is splitted into these two files.  Since one (dods.conf) is
application-specific (and delivered with your application) and the other one
(dodsConf.xml) is generator specific (located in the dods folder), you end up
delivering a file (dodsConf.xml) that you shouldn't (your customer doesn't
care where the dods templates are located, information that is completely
irrelevant).

- the absolute path of the filenames must be specified.  You end up writing:

> >      String fileName = "C:\\dods5.1\\output\\testando.conf";
> >      DODS.startup(fileName);

   The question is: when you deploy a J2EE application, what is the absolute
path to your conf file?  Instead of the absolute path, files should be loaded
from the classpath (as resource).

- the Common class should be simply removed.  This is IMO the easiest way to
find out where the problems are, since both systems (dods generator and dods
runtime) are configured using the Common class

Feedback?

-Vladimir

=====
Vladimir Ritz Bossicard
www.bossicard.com

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/