> In one of our application, we developed/complied a java code which
> uses couple of 3rd party JAR files. Since last couple of years we have
[quoted text clipped - 3 lines]
> compile it with the latest JAR files. The compilation is throwing lot of
> errors due to the deprecated methods we are calling.
Deprecatad methods of what? The core API, or the
3rd party Jars?
> I am wondering how did it work earlier i.e the same class file with new
> 3rd PARTY JAR files.
I do not understand your question. Do you know
what 'deprecated' means (in this context)?
Basically it means 'we will remove these classes
someday, stop using them'. Note that 'someday'
will usually not be 'soon'.
BTW - I note you cross-posted to
comp.lang.java.programmer,comp.lang.java.developer
I'm not sure of the correct term, but c.l.j.d. is not
one of the 'core' Java usenet groups, for a list of the
major Java groups, check here..
<http://www.physci.org/codes/javafaq.jsp#groups>
Follow-Ups to this post set to c.l.j.programmer only.
HTH

Signature
Andrew Thompson
physci.org 1point1c.org javasaver.com lensescapes.com athompson.info
"If I could find the reason, I'd know the answer why"
Status Quo 'Gerdundula'
>I am wondering how did it work earlier i.e the same class file with new
>3rd PARTY JAR files.
The linkage is by name. That way if a class you call acquires new
methods your old code calling it still works.
The deprecated warnings come only at compile time not run time. If you
ignore them at compile time, the run time is happy to use deprecated
methods. That is why you never noticed the problem until now.
Look at Sun's code in AWT. They use deprecated methods all the time.
Deprecation is just a warning.