Nanda Kishore

Greenhorn
+ Follow
since Aug 17, 2003
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Nanda Kishore

As with instance methods and variables, an inner class is associated with an instance of its enclosing class and has direct access to that object's instance variables and methods. Also, because an inner class is associated with an instance, it cannot define any static members itself.

For details refer:
http://java.sun.com/docs/books/tutorial/java/javaOO/nested.html
As a member of its enclosing class, a nonstatic nested class has a special privilege: It has unlimited access to its enclosing class's members, even if they are declared private. However, this special privilege isn't really special at all. It is fully consistent with the meaning of private and the other access specifiers. The access specifiers restrict access to members for classes outside of the enclosing class. The nested class is inside of its enclosing class so that it has access to its enclosing class's members. For details please refer:
http://java.sun.com/docs/books/tutorial/java/javaOO/nested.html
Question - 3 will compile after removing the extra }. But it will not run. It will throw NoSuchMethodError.
When we execute a lookup to get the home interface of a bean, we normally use the lookup() method of the javax.naming.Context interface. This method will return an Object that needs to be casted to the home interface that we asked for. Unfortunately, this cannot be done using the normal casting [MyHome myHome = (MyHome)returnedObject]. The reason is related to CORBA.

For EJB, the communication between the server and the client is based on RMI (both remote and local interfaces, in fact, do implements the java.rmi.Remote interface). The underlying protocol that is used for the communication is IIOP, that is part of CORBA standards. So basically the communication protocol in EJB is Java RMI over IIOP.

IIOP has not been designed only for Java. It is for generic languages, and this means that there are some limitations. Some languages, in fact, do not have the concept of casting. Java RMI-IIOP provides a mechanism to narrow the Object received from our lookup, to the appropriate type. This is done through the javax.rmi.PortableRemoteObject class and, more specifically, using the narrow() method.

But when using EJB 2.0 Local Client API, we can do a direct/explicit cast from the looked up Object, to the interface type that we need.
19 years ago
If you mean, the maximum number of arguments that can be passed to a method, then I think it is 256.
19 years ago
Nitin, I tried on my system and it is running continuously!!
19 years ago
I think, you can use Apache's POI for this.
19 years ago
JSP
hai subha,
sorry for late reply.
Regarding I/O u concentrate on constructors of readers/writers or stream classes -i.e.,which constructor accepts what parameters etc.and methods exclusive for byt stream classes.
regarding AWT u have to be clear about layouts-including GridBag
RHE is not very clear about this.
Read GridBagConstraints-cover all variables of this class
To get good percentile u have to answer more mocks.i didnot covered RHE tester that may be the reason for less score.
i used to get 45 - 50 correct answers in mocks
hai everybody,
i am a silent visitor of this site for last few weeks.
just i continued visiting and that encouraged me to appear for scpj.
i did it and passed with 76% score.
i suggest 3 minimum things to new aspirants
-read RHE
-try atleast 5 mocks.
-and visit javaranch
Thank u all
and i will join other forums
bye
kishore