Re: Resolving Java import statements

2016-03-19 Thread Janet Graff
Andrew, Yes! that fixed it. I knew if I had it in a script I'd need that. I didn't realize doing this from the command line would require the export command. Thank you! Janet >You probably need to export the CLASSPATH definition: >export

Re: Resolving Java import statements

2016-03-16 Thread Jack J. Woehr
Janet Graff wrote: I searched for the commons-code*.class files and didn't find them. Does WebSphere and/or Rational Developer not provide the class files for these common java routines? A quick Google search turns up this page: http://commons.apache.org/proper/commons-logging/guide.html

Re: Resolving Java import statements

2016-03-15 Thread Andrew Rowley
You probably need to export the CLASSPATH definition: export CLASSPATH=$CLASSPATH:/usr/lpp/zWebSphere/V7R0/optionalLibraries/Apache/Struts/1.1/commons-logging.jar Due to the idiosyncrasies of unix shells, without "export" it only creates the variable in the sub-process running the command

Re: Resolving Java import statements

2016-03-15 Thread Janet Graff
Andrew, Thank you all so much for your help. I searched for commons-logging*.jar and found several copies. I tried the following in the directory with the .java file CLASSPATH=/usr/lpp/zWebSphere/V7R0/optionalLibraries/Apache/Struts/1.1/commons-logging.jar javac RemoteServer.java which

Re: Resolving Java import statements

2016-03-15 Thread Andrew Rowley
On 16/03/2016 9:18, Janet Graff wrote: I searched for the commons-code*.class files and didn't find them. Does WebSphere and/or Rational Developer not provide the class files for these common java routines? Janet Apache Commons is a project creating various reusable Java components. It's

Re: Resolving Java import statements

2016-03-15 Thread Janet Graff
Janet Graff wrote: > I set my CLASSPATH to one of the directories (the last as it happens) > > CLASSPATH=/usr/lpp/zWebSphere_OM/V7R0/FPW20M/web2mobilefep_1.1/optionalLibraries/jaxrs_1.X jars themselves don't get added to classpath by their dir being added to classpath Jack, Sorry for not

Re: Resolving Java import statements

2016-03-15 Thread Janet Graff
I searched for the commons-code*.class files and didn't find them. Does WebSphere and/or Rational Developer not provide the class files for these common java routines? Janet >Hi Janet, >yes the individual jars need to be on the classpath. The directory only works >if the individual *.class

Re: Resolving Java import statements

2016-03-15 Thread Jack J. Woehr
Janet Graff wrote: Sorry Jack, not following the intent. Are you saying I need to add the individual jar files to the CLASSPATH definition? The CLASSPATH does have the directory containing the required jar file. yes, exactly. See both answers I mailed. Jars arent' added to a classpath merely

Re: Resolving Java import statements

2016-03-15 Thread Denis
b6d-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Sent: Tue, Mar 15, 2016 09:11 PM Subject: Re: Resolving Java import statements Sorry Jack, not following the intent. Are you saying I need to add the individual jar files to the CLASSPATH definition? The CLASSPA

Re: Resolving Java import statements

2016-03-15 Thread Janet Graff
Sorry Jack, not following the intent. Are you saying I need to add the individual jar files to the CLASSPATH definition? The CLASSPATH does have the directory containing the required jar file. Janet >Jack J. Woehr wrote: >> for jar in /somedir/*.jar >>do >> export

Re: Resolving Java import statements

2016-03-15 Thread Jack J. Woehr
Jack J. Woehr wrote: for jar in /somedir/*.jar do export CLASSPATH=$CLASSPATH:$jar done Oops, this should say export CLASSPATH=$CLASSPATH:/somedir/$jar -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of

Re: Resolving Java import statements

2016-03-15 Thread Jack J. Woehr
Janet Graff wrote: I set my CLASSPATH to one of the directories (the last as it happens) CLASSPATH=/usr/lpp/zWebSphere_OM/V7R0/FPW20M/web2mobilefep_1.1/optionalLibraries/jaxrs_1.X jars themselves don't get added to classpath by their dir being added to classpath Each jar must appear in the