StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20239188
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-27T09:59:10.297
FavoriteCount
0
LastActivityDate
2013-11-27T09:59:10.297
LastEditDate
LastEditorUserId
0
OwnerUserId
2745755
ParentId
20238536
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<code>ClassLoader.loadClass</code> or <code>Class.forName</code> seem to be synonyms for the same basic operation: request a dynamic class load. Yet calling <code>Class.forName</code> does additional "checking" which is not very useful (certainly in OSGi). When doing a dynamic class load, the returned type has no implied type by the code. The code must use reflection to access static members or to create an instance. A created instance can either be reflected upon or cast to a type which must already implicitly know by the code. This cast will result in a runtime type check which will ensure type safety. This is very different than an implicit class load done by the VM to resolve a class constant pool entry. Since it is the goal of these implicit class loads to avoid runtime type checks, the loader constraints are used to ensure type safety. It does not seem necessary or reasonable to impose loader constraint checks on some dynamic class load requests. That is, code calling <code>Class.forName</code> (or <code>ClassLoader.loadClass</code>) and the VM resolving a class constant pool entry have different type safety needs. The former does not require loader constraint checks since that will be done at runtime by a type cast if needed. The latter does require loader constraint checks to avoid the need for runtime type checks. So it does seem reasonable to have <code>Class.forName</code> behavior altered to avoid loader constraint checks. Only internal <code>VM</code> class load requests need to check loader constraints. For more understanding <a href="http://java-career.blogspot.in/2012/10/classforname-vs-classloaderloadclass.html" rel="nofollow">Click here</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the difference between class.forName() and classLoader.loadClass() in osgi framework
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAJ.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.