Originally posted by Ajith Kallambella:
Yes,both SAX and XMLSchema are covered in the exam.
Originally posted by Ajith Kallambella:
Yes,both SAX and XMLSchema are covered in the exam.
Originally posted by Cindy Glass:
When a class is loaded but before any instances are created, the static variables are created. If those variables can be initialized using simple assignments, then you really DON'T need static initializer blocks. But what if you have to do some complex logic in order to figure out what the value of those variables should be? You can't use for( ) or while( ) logic in an assignment statement.
If you put the logic in a static method, then you run the chance that someone will try to USE it after class load time - that could be a problem. If the logic is in a static initializer, then it only gets executed ONE time.
As for interface variables, take a look as interface SwingConstants. It declares all sorts of fields to hold values that represent North, South, top, bottom, vertical, horizontal, etc. You know, widget or component sorts of things. LOTS of components implement the SwingConstants interface and all of them can use the same North field value to manipulate their particular components, without redefining all those fields. It also helps to know that the fields available and their spelling will be consistant across components.
Originally posted by Mikael Jonasson:
Overriding can't throw anything that the superclass version of the function doesn't allow. Overloading is basicly making a whole new function, so you're free to what you want (as long as the overloading function isn't an overridning function too. If so, then the normal rules for overrinding apply).
/Mike