I know that newer versions of tomcat use the Eclipse java compiler rather than Suns javac to get around memory leaks that Suns javac has when used in a runtime environment... I'm unsure why your setup is complaining about this. If theres a chance you can upgrade to more recent version of tomcat, you'll probably save yourself having to debug issues with an older tomcat (4.0) running on a newer java (1.6.0)
On May 8, 2008, at 8:20 AM, Blanco, Jose wrote: > Mark: > > I've done this and I it seems to be working, but I'm stuck with this > error everytime browse/full.jsp file is requested: > > 2008-05-08 11:16:24 StandardWrapperValve[browse]: Servlet.service() > for > servlet browse threw exception > org.apache.jasper.JasperException: Unable to compile class for > JSPNote: > sun.tools.javac.Main has been deprecated. > > > An error occurred between lines: 342 and 349 in the jsp file: > /browse/full.jsp > > Generated servlet error: > /usr/local/jakarta-tomcat-4.0/work/Standalone/ > blancoj.dev.deepblue.lib.u > mich.edu/_/browse/full$jsp.java:980: ';' expected. > for (SortOption sortBy : sortOptions) > ^ > 1 error, 1 warning > > at > org.apache.jasper.compiler.Compiler.compile(Compiler.java:285) > > > I've checked the java version and it's 1.6. > > -bash-3.00$ java -version > java version "1.6.0" > Java(TM) SE Runtime Environment (build 1.6.0-b105) > Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode) > > > Any ideas. Thank you! > Jose > > -----Original Message----- > From: Mark Diggory [mailto:[EMAIL PROTECTED] > Sent: Friday, May 02, 2008 3:31 PM > To: Blanco, Jose > Cc: [email protected] > Subject: Re: [Dspace-tech] Run time error with 1.5 > > Stay out of modifying the ant build file. You'll want to implement > this > in maven as the following: > > 1.) You'll want to initially install it locally into your repository > with something like... > > mvn install:install-file -Dfile=cosign.jar \ > -DgroupId=edu.umich.auth.cosign \ > -DartifactId=cosign \ > -Dversion=<your-version-of-the-jar-here> \ > -Dpackaging=jar \ > -DcreateChecksum=true > > We want them to eventually make it available via a repository. I can > place it in our repo under org.dspace.edu.umich.auth.cosign and it > would > ease your reuse of it because you'd need to reinstall it on each > machine > you want to run the build on. > > 2.) You'll want to add > > <dependency> > <artifactId>cosign</artifactId> > <groupId>edu.umich.auth.cosign</groupId> > <version><your-version-of-the-jar-here></version> > </dependency> > > to any pom.xml that you require cosign to be present for. The best > solution is to add it to [dspace-source]/dspace/pom.xml and [dspace- > source]/dspace/modules/pom.xml and it will just get added to every > war. > > 3.) Add your configuration files to the [dspace-source] directory as > resources for that webapplication you wish to use it in > > [dspace-source]/dspace/modules/xmlui/src/main/resources/edu/umich/ > auth/cosign/cosignConfig.properties > > Copy it for any webapp you want it present in. > > There are other alternatives that we can explore but they will be more > involved than this. > > -Mark > > On May 2, 2008, at 12:00 PM, Blanco, Jose wrote: >> Mark, I have a question about our auth customization. We are using >> cosign, in 1.4.2 we had the cosign jar file in [dspace-source]/lib >> dir > >> and we had a properties file in the [dspace-source]/etc directory, so >> when we did a build_war our build.xml file had this in it. >> >> <target name="cosign" >> description="Copy files for CoSign support"> >> <mkdir dir="build/classes/edu/umich/auth/cosign"/> >> <copy file="etc/cosignConfig.properties" >> >> tofile="build/classes/edu/umich/auth/cosign/cosignConfig.properties" >> preservelastmodified="true"/> >> </target> >> >> <!-- >> ============================================================= --> >> <!-- Build the .war >> files --> >> <!-- >> ============================================================= --> >> >> <!-- modified to depend on cosign 2005-04-07 csnavely --> >> >> <target name="build_wars" >> depends="compile,cosign" >> description="Build the .war files"> >> >> >> So, I think for the the buil.xml file for 1.5 I need something like >> it, but I'm a bit uncertain about some of the details. >> >> 1. Where do the I put the cosign.jar file in 1.5? >> >> 2. Where do the put cosgingConfig.properites now? >> >> 3. And what should my <target naem="cosign" directive ( I guess >> that's what it might be called ) should look like? >> >> Thank you again!!!!!! >> >> Jose >> >> >> -----Original Message----- >> From: Mark Diggory [mailto:[EMAIL PROTECTED] >> Sent: Friday, May 02, 2008 2:01 PM >> To: Blanco, Jose >> Cc: [email protected] >> Subject: Re: [Dspace-tech] Run time error with 1.5 >> >> >> On May 2, 2008, at 9:51 AM, Blanco, Jose wrote: >>> I think I know what may be going on. I'm testing things out in the >>> development enviroment, but that env is also being used as a staging >>> area, so I did not want to mess with some of our instances of >>> dspace, > >>> so I created a copy of dspace.cfg called dspace15.cfg and when I did >>> the update, I did: >>> >>> /l/local/bin/ant -Dconfig=/l1/dspace/repository/dev/config/ >>> dspace15.cfg >>> update >>> >>> And I assumed dspace would use dspace15.cfg, but it is still looking >>> at dspace.cfg and in there I have the AuthenticationMethod living in >>> eperson, rather than authenticate, so I think this may be it. >>> >>> Is there a way for me to do what I intended here? >> >> Sometimes I think the timestamping on the files is messing up these >> getting properly copied in place in Ant. >> go under [dspace-source]/dspace/src/main/config/build.xml and change >> >> <copy file="${config}" >> tofile="${dspace.dir}/config/dspace.cfg" >> preservelastmodified="true"/> >> >> to >> >> <copy file="${config}" >> tofile="${dspace.dir}/config/dspace.cfg" >> preservelastmodified="true" overwrite="true"/> >> >> this should force your referenced dspace.cfg into place no matter the >> timestamps on the files. (You'll need to do a mvn package again to >> get > >> this into your target/dspace..../ >> >> I'm testing this and planning to put it in the 1.5.1 release as a >> fix. >> >> -Mark >> >>> Thanks! >>> Jose >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of >>> Blanco, Jose >>> Sent: Friday, May 02, 2008 10:12 AM >>> To: Mark Diggory >>> Cc: [email protected] >>> Subject: Re: [Dspace-tech] Run time error with 1.5 >>> >>> Yes, >>> This is from my dspace.cfg file >>> >>> #### Stackable Authentication Methods ##### >>> >>> # Stack of authentication methods >>> # (See org.dspace.authenticate.AuthenticationManager) >>> plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \ >>> org.dspace.authenticate.PasswordAuthentication >>> >>> >>> Since the code I was using was code that I had merged in with >>> changes > >>> I had made to 1.4.2, I thought that maybe something in my merge was >>> causing this problem, and to test this I built a dspace instance >>> with > >>> just the 1.5 code and got the same error, so it must have something >>> to >> >>> do with my setup, or my dspace.cfg file. Another thing I noticed is >>> that the dspace.log file is not getting updated. I have also NOT >>> run >>> >>> [dspace]/bin/index-init >>> >>> Yet. Could that have something to do with it? >>> >>> Thanks! >>> Jose >>> >>> -----Original Message----- >>> From: Mark Diggory [mailto:[EMAIL PROTECTED] >>> Sent: Thursday, May 01, 2008 7:25 PM >>> To: Blanco, Jose >>> Cc: [email protected] >>> Subject: Re: [Dspace-tech] Run time error with 1.5 >>> >>> Are you customizing your authentication stack in this case? >>> >>> On May 1, 2008, at 8:28 AM, Blanco, Jose wrote: >>>> I'm having the following runtime error with 1.5, >>>> >>>> Caused by: java.lang.ClassCastException: [Ljava.lang.Object; cannot >>>> be >>> >>>> cast to [Lorg.dspace.authenticate.AuthenticationMethod; >>>> at >>>> org.dspace.authenticate.AuthenticationManager.<clinit> >>>> (AuthenticationMan >>>> ager.java:95) >>>> ... 41 more >>>> >>>> >>>> Any ideas? >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> --- >>>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>>> Don't miss this year's exciting event. There's still time to save >>>> $100. >>>> Use priority code J8TL2D2. >>>> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// >>>> java.sun.com/javaone >>>> _______________________________________________ >>>> DSpace-tech mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >>> >>> >>> -------------------------------------------------------------------- >>> - >>> - >>> -- >>> - >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's still time to save >>> $100. >>> Use priority code J8TL2D2. >>> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// >>> java.sun.com/j >>> avaone >>> _______________________________________________ >>> DSpace-tech mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> >> >> --------------------------------------------------------------------- >> - >> --- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save >> $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// >> java.sun.com/javaone >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
