Deprecated Date methods in Java?
Asked Answered
M

10

8

What is really meant when using Java Date utilities and something has been deprecated. Does this mean that it is discouraged to use, or does it imply that it is forbidden?

I am guessing it is bad practice to use deprecated methods, but am not sure and wanted to find out.

For example, I am trying to use code such as the following

String date = request.getParameter("date"); 
model.setDate(new Date(date));

Of course...this is a high level example, but in this situation, my model uses type Date and I need to pull the date off the request as a String and create a date with it.

It works fine how I have it, but it is using a deprecated method.

EDIT - I have gone back and used

SimpleDateFormat formatter = new SimpleDateFormat(); 
model.setDate(formatter.parse(request.getParameter("date");



The date is in the format MM/DD/YYY like 07/23/2010 but I am getting a ParseException

What could this be from?

Malignancy answered 29/7, 2010 at 16:46 Comment(0)
C
6

You're right that this is bad practice. In almost all cases, deprecated methods tell you what to use instead, and this is no exception (see the Javadocs).

You're trying to create a Date out of a String. But what format is the String in? How should it be parsed? Is it UK or US date format?

The "proper" way to do this is to create an instance of SimpleDateFormat, and call its parse() method passing in your text string. This is guaranteed to work in future, and will be more robust now.

Comradery answered 29/7, 2010 at 16:50 Comment(4)
... or preferably, use a better API such as Joda Time :)Juniorjuniority
Well... yes. :-) But suggesting rewriting all existing code to use new Date objects is overkill for this situation.Comradery
@Jon Skeet, the problems with always using Better API is you end up having a directory of API's and constantly having to check for new releases in repositories.Ashelyashen
@The Elite Gentleman: While I agree you can get into problems in general, Joda Time is stable and so much better than the existing API, it's definitely worth doing. It's a massive step up from java.util.Date/Calendar.Juniorjuniority
A
3

Deprecated objects or methods merely means that if you want to use it in current project, rather use what is recommended. The reason why they still have it is for legacy codes who have used the deprecated method before it was deprecated. Typical example is StringTokenizer vs String.split() method.

For your Date example use SimpleDateFormat to do conversion from String to Date. This allows you to create a date format from which your string date can be parsed to create a Date object.


For your EDIT do this

SimpleDateFormat formatter = new SimpleDateFormat("MM/dd/yyyy"); 

model.setDate(formatter.parse(request.getParameter("date")));

ParseException is caused since you didn't provide a date format structure so the SimpleDateFormat didn't know how your date was structured.

Ashelyashen answered 29/7, 2010 at 16:50 Comment(0)
S
3

A lot of people have mentioned what Deprecated means, but I don't see any explanation of why these methods are deprecated:

Sun (before they were part of Oracle) deprecated a number of methods in Date to get people to use the Calendar/GregorianCalendar classes for date manipulation instead.

Stowell answered 29/7, 2010 at 17:18 Comment(0)
T
2

What "Deprecated" Means

You may have heard the term, "self-deprecating humor," or humor that minimizes the speaker's importance. A deprecated class or method is like that. It is no longer important. It is so unimportant, in fact, that you should no longer use it, since it has been superseded and may cease to exist in the future.

Java provides a way to express deprecation because, as a class evolves, its API (application programming interface) inevitably changes: methods are renamed for consistency, new and better methods are added, and fields change. But such changes introduce a problem. You need to keep the old API around until developers make the transition to the new one, but you don't want them to continue programming to the old API.

The ability to deprecate a class, method, or member field solves the problem. Java supports two mechanisms for deprecation: and an annotation, (supported starting with J2SE 5.0) and a Javadoc tag (supported since 1.1). Existing calls to the old API continue to work, but the annotation causes the compiler to issue a warning when it finds references to deprecated program elements. The Javadoc tag and associated comments warn users against using the deprecated item and tell them what to use instead.them what to use instead.

http://download-llnw.oracle.com/javase/1.5.0/docs/guide/javadoc/deprecation/deprecation.html

Tatouay answered 29/7, 2010 at 16:49 Comment(0)
I
2

You are right, Its discouraged to use deprecated methods. This is because these methods may have issues in some situation or have been replaced with more optimistic solutions And also future versions may not support these.

Inoperative answered 29/7, 2010 at 17:4 Comment(0)
C
1

Deprecated means it is planned for removal, because it is buggy or some other bad reason. It is better to use SimpleDateFormat.parse(); to parse your strings.

Cohligan answered 29/7, 2010 at 16:51 Comment(0)
C
1

In general, when Sun (Oracle, whatever) declares a Java method deprecated, it means that they changed their minds about including it, they discourage you from using it, and they may remove it in some future version. Of course it's likely to be a long time before it gets removed as who knows how much existing code there is out there using it, and what's the point of breaking existing programs just because the inventors of Java think they now have a better idea about how to do something?

Presumably they had a good reason for deprecating something, so you should investigate WHY they say that some newer function is better.

In the case of deprecated Date methods, usually this means that they suggest you now use the Calendar or SimpleDateFormat classes. In your case, probably the latter.

Conventionality answered 29/7, 2010 at 16:51 Comment(0)
T
0

deprecated: something that exists in the current version of Java, but will be removed from future versions at some point.

For your edit, you need to properly initialize the SimpleDateFormat, so it knows what format is coming in. For 07/22/1978 format:

SimpleDateFormat sdf = new SimpleDateFormat("MM/dd/yyyy");

Trackless answered 29/7, 2010 at 17:15 Comment(0)
D
0

As other said, the java.util.Date methods were deprecated because the Java team believed they had a better solution in the java.util.Calendar.

Unfortunately that class also proved to be confusing, troublesome, and poorly designed.

So, yes, you should avoid deprecated methods in deference to their replacements. But now those replacements (.Calendar) have a replacement (java.time).

java.time

All the old date-time classes have been supplanted by the java.time framework built into Java 8. The new classes are inspired by the highly successful Joda-Time framework, intended as its successor, similar in concept but re-architected. Defined by JSR 310. Extended by the ThreeTen-Extra project. See the Tutorial.

Use the java.time.format package for parsing and generating String representations of date-time values.

String input = "07/23/2010";
DateTimeFormatter formatter = DateTimeFormatter.ofPattern( "MM/dd/yyyy" );

The new classes include LocalDate for representing a date-only value without time-of-day.

LocalDate localDate = LocalDate.parse( input , formatter );

If you call toString on a LocalDate you get a String representation of the date value in the standard ISO 8601 format, YYYY-MM-DD. To generate a String in other formats, define another formatter. Or call the 'localize' methods to let java.time do the heavy lifting in determining a particular localized format.

Dimpledimwit answered 7/12, 2015 at 6:45 Comment(0)
D
-1

Nothing will break if you use them...yet.

But they may well be removed in future versions.

Dearborn answered 29/7, 2010 at 16:47 Comment(1)
most of the Date related deprecations are due to bugs, so things might break because of the bugsCohligan

© 2022 - 2024 — McMap. All rights reserved.