You didn't bother me at all and I am CC'ing the dev@oodt list so they benefit from your good work.
Thanks Lindsey! Cheers, Chris -----Original Message----- From: Lindsey Davis <lda...@nrao.edu> Date: Wednesday, November 13, 2013 9:14 AM To: jpluser <chris.a.mattm...@jpl.nasa.gov> Cc: Jeff Kern <jk...@nrao.edu> Subject: Re: new issue in wmgr-client (0.6 vs 0.3) >Hi Chris, > >Forget my previous mail. It is working fine. I did not >notice at first that I need to install the command lines >options and actions policy files. I also found out that >I needed to prefix the paths to these files with file://. > >Sorry to have bothered you. > > Lindsey > >> Hi Chris, >> >> I have come across what looks like an annoying change in >> XmlRpcWorkflowManagerClient that you may be able to help >> me with. >> >> I am porting the ALMA pipeline code from 0.3 to 0.6. I >> downloaded the tarball of jar files and replaced my current >> 0.3 jars with 0.6 jars. >> >> The pipeline code built fine and the workflow manager >> started up without any problems. However when I ran my test >> workflow I got a error about a missing class cli.CmdLineUtility. >> >> I looked in the workflow distribution code and determined that >> there is a new jar cas-cli-0.6.jar. I added that to my build system. >> The missing class definition disappears but now I get what looks >> like a very annoying parsing error >> >> The command issued on the terminal is >> >> skye<151>$ wmgr-client --url http://localhost:9001 --operation >>--sendEvent >> --eventName modelPreCasaEvent >> >> Assuming that modelPreCalsEvent exists is there anything wrong with >>this ? >> >> This gets translated into a line like the following >> >> acsStartJava -endorsed \ >> >>-Djava.util.logging.FileHandler.pattern=${SCIPIPE_WFMANAGER_LOGDIR}/cas_w >>orkflow%g.log >> \ >> >>-Djava.util.logging.config.file=${SCIPIPE_CAS_PROPERTIES}/logging.propert >>ies >> \ >> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient $* >> >> where acsStartjava with an argument -endorsed is used to start java >> >> Unfortunately is looks like the code in cli mangles these commands (see >> below). Is there >> anyway I can bypass all this and get back the original behavior which >>would >> be much >> easier to work with. >> >> Lindsey >> >> >> >> >> skye<151>$ wmgr-client --url http://localhost:9001 --operation >>--sendEvent >> --eventName modelPreCasaEvent >> --endorsed -D >> >>java.util.logging.FileHandler.pattern=/home/skye/wflogdir/cas_workflow%g. >>log >> -D java.util.logging.config.file >> >>=/export/home/skye/working/acs121/HEAD121X/introot121/Sources/Science/src >>/logging.properties >> -- org.apache.oodt.cas.workflow >> .system.XmlRpcWorkflowManagerClient --url http://localhost:9001 >>--operation >> --sendEvent --eventName modelPreCasaEvent >> 2013-11-12T22:02:20.024 INFO [acsStartJava] Starting Java application: >> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowMan >> agerClient --url http://localhost:9001 --operation --sendEvent >>--eventName >> modelPreCasaEvent >> 2013-11-12T22:02:20.066 INFO [acsStartJava] Using endorsed jar files >>in: >> -Djava.endorsed.dirs=/export/home/skye/working/acs1 >> 21/HEAD121X/introot121/lib/endorsed:/alma/ACS-12.1/ACSSW/lib/endorsed: >> Exception in thread "main" java.lang.IllegalArgumentException: The >>validated >> object is null >> at org.apache.commons.lang.Validate.notNull(Validate.java:192) >> at org.apache.commons.lang.Validate.notNull(Validate.java:178) >> at >> >>org.apache.oodt.cas.cli.option.store.spring.SpringCmdLineOptionStoreFacto >>ry.createStore(SpringCmdLineOptionStoreF >> actory.java:40) >> at >> >>org.apache.oodt.cas.cli.CmdLineUtility.<init>(CmdLineUtility.java:94) >> at >> >>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(XmlR >>pcWorkflowManagerClient.java:677) >>
