Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / April 2007

Tip: Looking for answers? Try searching our database.

Update to itext 2.0.1 from 1.3 throws Error

Thread view: 
Newie - 11 Apr 2007 07:26 GMT
Hi,

I have made a PDF with itext 1.3 and everythings works fine, now I
wanted to update itext to the newest release itext 2.0.1. After I had
done this, I received the following exception:

[11.04.07 08:22:19:404 CEST] 62893347 WebGroup      E SRVE0026E:
[Servlet-Fehler]-[java.lang.StringBuffer: method append(Ljava/lang/
StringBuffer&#59;)Ljava/lang/StringBuffer&#59; not found]:
java.lang.NoSuchMethodError: java.lang.StringBuffer: method
append(Ljava/lang/StringBuffer;)Ljava/lang/StringBuffer; not found
    at com.lowagie.text.pdf.PdfWriter$PdfBody
$PdfCrossReference.toPdf(PdfWriter.java:192)
    at com.lowagie.text.pdf.PdfWriter
$PdfBody.writeCrossReferenceTable(PdfWriter.java:505)
    at com.lowagie.text.pdf.PdfWriter.close(PdfWriter.java:1161)
    at com.lowagie.text.pdf.PdfDocument.close(PdfDocument.java:805)
    at com.lowagie.text.Document.close(Document.java:491)
    at servlet.HelloWorld.doPost(HelloWorld.java:50)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:
110)
    at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:
174)
    at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:
313)
    at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:
116)
    at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:
283)
    at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:
42)
    at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:
40)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:
1030)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:
566)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:
198)
    at
com.ibm.ws.webcontainer.servlet.InvokerServlet.service(InvokerServlet.java:
255)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:
110)
    at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:
174)
    at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:
313)
    at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:
116)
    at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:
283)
    at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:
42)
    at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:
40)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:
1030)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:
566)
    at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:
198)
    at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:
80)
    at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:
214)
    at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:
71)
    at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:
116)
    at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:
186)
    at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:
334)
    at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:
56)
    at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:
615)
    at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:449)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)

My classpath is ok and I have also compiled it on my own computer, but
ít is still the same error.
If I used instead of the itext 2.0.1 the 1.3 it works.

So can anybody help me????
I don't know what to do.......
Gordon Beaton - 11 Apr 2007 07:46 GMT
> I have made a PDF with itext 1.3 and everythings works fine, now I
> wanted to update itext to the newest release itext 2.0.1. After I
[quoted text clipped - 5 lines]
> java.lang.NoSuchMethodError: java.lang.StringBuffer: method
> append(Ljava/lang/StringBuffer;)Ljava/lang/StringBuffer; not found

[...]

> My classpath is ok and I have also compiled it on my own computer,
> but ít is still the same error. If I used instead of the itext 2.0.1
> the 1.3 it works.

Upgrade to a modern JDK. It appears you are using Java 1.3 (or earlier).

/gordon

--
Newie - 11 Apr 2007 08:10 GMT
> > I have made a PDF with itext 1.3 and everythings works fine, now I
> > wanted to update itext to the newest release itext 2.0.1. After I
[quoted text clipped - 17 lines]
>
> --

Hi Gordon,

thank you for your answer.
We are using IBM WebSphere Portal 5, and we have Java 1.3
Now we have to look, if we could update to 1.4 or 1.5
So thank you....
Lew - 11 Apr 2007 13:51 GMT
> thank you for your answer.
> We are using IBM WebSphere Portal 5, and we have Java 1.3
> Now we have to look, if we could update to 1.4 or 1.5
> So thank you....

Well, if the developer knew that they shouldn't have used methods that didn't
exist in 1.3.  However, in their defense, Java 1.3 has been obsolete for
months and obsolescent for years.  Java 1.3 is an unsupported product.  Why
would any business risk its health on an unsupported, obsolete product?

In the meantime, have a chat with your team about target platforms and not
exceeding them.

Signature

Lew



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.