This is what the javadocs say for a java.lang.AbstractMethodError: <javadoc> public class AbstractMethodError extends IncompatibleClassChangeError
Thrown when an application tries to call an abstract method. Normally, this error is caught by the compiler; this error can only occur at run time if the definition of some class has incompatibly changed since the currently executing method was last compiled. </javadoc> Sounds to me like you have an old version of Jetspeed or Turbine somewhere in your classpath. Looking at your previous message "Re: Who changed this?": "I just did a search through all the files I received as a part of the distribution including the configuration files for the alpha version. I cannot find a newuser.confirm.enable=false ( or true )." The newuser.confirm.enable feature has been a part of the cvs head for a very long time, but I believe it wasn't in 1.3a1. And then: "3) I get an error when logging our or updating an account about a class cast exception for BigNum." Which I specifically remember as being a bug in 1.3a1.. Could it be possible that version 1.3a1 is somewhere in your classpath? When you drop the jetspeed.war into your webapps directory, are you deleting the old jetspeed directory from webapps? > -----Original Message----- > From: John Wooten [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 10, 2001 6:57 AM > To: Jetspeed Users List > Subject: RE: Jetspeed release 1.3a2 candidate > > > Why does this keep getting released with a set of > instructions that say, > drop the jetspeed war file into the tomcat webapps and then > start the server > and it will work? > > Once again, I did that. > I then connected to Jetspeed via the browser, logged in as > turbine, turbine. > Got logged in. Then chose Customize and got the same page as > after logging > in. NO CUSTOMIZATION. > > LOG STILL READS: > jetspeed.portalfactory - /WEB-INF/psml/default.psml > [Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the > PortletFactory > [Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local > cached URL > [Mon Dec 10 09:50:12 EST 2001] -- ERROR -- > Exception: java.lang.AbstractMethodError > Stack Trace follows: > java.lang.AbstractMethodError > at > org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalH > andler.java:66 > 3) > at > org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335) > at > org.apache.xerces.validators.common.XMLValidator.callStartElem > ent(XMLValidat > or.java:840) > at > org.apache.xerces.framework.XMLDocumentScanner.scanElement(XML > DocumentScanne > r.java:1852) > at > org.apache.xerces.framework.XMLDocumentScanner$ContentDispatch > er.dispatch(XM > LDocumentScanner.java:1233) > at > org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDo > cumentScanner. > java:380) > at > org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908) > at > org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335) > at > org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267) > at > org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388) > at > org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(P > ortlets.java:4 > 52) > at > org.apache.jetspeed.portal.factory.PortletSetFactory.init(Port > letSetFactory. > java:230) > > --------PLEASE NOTE. This was reported as a problem over a > week ago. NO > ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. > NEW RELEASE STILL > DOES EXACTLY THE SAME THING AS BEFORE> > > OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY > TO GET THIS TO > WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES > SOMETHING ELSE NEED TO > BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE > WEBAPPS AND IT WILL > WORK? > > Inquiring minds really would like to join the in-crowd and > get their setup > so it will work like everyone else who apparently can run > these releases. > > > > -----Original Message----- > From: David Sean Taylor [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 10, 2001 1:41 AM > To: 'Jetspeed Users List' > Subject: Jetspeed release 1.3a2 candidate > > > There is a 1.3a2 release candidate at > > http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/ > > If you get a chance, please give it a try and let us know how > it works for > you. > > The documentation is updated at http://jakarta.apache.org/jetspeed > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
