One more possible error in the same section:
anonymous wrote : Java addresses this problem by generating loader constraints to validate
type consistency when the types being used are coming from different defining class
loaders. For the example, the VM generates a constraint SpoofedL1 = SpoofedL2....
Wait, isn't this a constraint about types coming from different initiating class
loaders?
This section is extremely detailed and interesting. A little more internal consistency
would make it easier to understand.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121384#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...