Java Field<String> vs String

Question

What is the benefits of using Java Field<String> vs String except for the cloneable possibility?

We have a system that seems to use Field<String> here and there for no obvious reasons (into which I also put "we have done like that before").

Which Field do you mean? Specify the fully qualified path. Or is it a custom one? — Alex Abdugafarov
– Alex Abdugafarov, Commented Feb 16, 2012 at 10:52
You mean the reflection field vs a normal String? I don't get the question. — Tudor
– Tudor, Commented Feb 16, 2012 at 10:56
Are you allowd to use Field directly or do you have to Field<Field<String>> ... ouch, recursing into deep space ;) — Andreas Dolk
– Andreas Dolk, Commented Feb 16, 2012 at 10:56

Andreas Dolk · Accepted Answer · 2012-02-16 11:26:25Z

3

This Field<String> is a field (concept) that can hold a String type value, while a String is just a String.

To understand the why, you'll have to look at the code (the oldest parts of the code base, where this class has been used). Maybe, they wanted to handle database fields via a common interface or base class. I wouldn't look for technical benefits (cloneing, performance, ...), there should be a design decision (at least, I hope, there is one).

Once you found the real reason, you can start to fighting all abuses of the concept (aka - "we always did it that way")

answered Feb 16, 2012 at 11:26

Andreas Dolk

115k20 gold badges185 silver badges275 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Java Field<String> vs String

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related