Win a copy of Head First Android this week in the Android forum!

Bob Walker Jr

Ranch Hand
+ Follow
since Jun 02, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Bob Walker Jr

Originally posted by Matt Cao:
I would go for brand name school that offers online programme. Remember to ask about employment assistant for alumni deal, screen the creditibilities of the professors, testing procedures, tuition and textbook materials included, etc.
The tuition has the tendency to be higher than traditional classroom method, but you do not have to beat traffic, purchase parking decal, pay for health and school services.

Thanks for your post. But I was really hoping for some information
17 years ago
I want to do MS but cannot attend regular classes. What is the cheapest way to do it online?
I get so many junk mails talking about online degree. Are they all fake/unrecognized degrees?
Are there any "valid" or recognized by the govt. masters degrees available online?
Could anybody please give any information on this?
17 years ago
Is there a user guide somewhere?
17 years ago
The finder method is called on a bean that is in the pool. It does not mean that that particular bean is "found". So when the client get a reference to the "found" bean, the found bean must be in the ready state.
The bean instance on which the finder was called could be potentially different from the one that was found.

Originally posted by Edward Tse:
My guess to why stub are so important is because even though the programmer is only dealing with an interface, however, the remote object will still serialized and transfer over the network. Without the stub, client side has no way of knowing how the remote object should look like.

The client does not have to know how the remote object looks like. All it cares about is the interface. It doesn't need the stub for that. Saying that a client program needs a stub is, imho, same as saying that a client program needs socket classes.
I don't get it. Why is the stub skeleton issue so important?? They are transparent to the application programmer. In fact, the client only needs classes/interface that it uses (references in the code). Everything else is managed by the RMI infrastructure. When I package my EJBs for clients, I DO NOT put stubs in there. All I put is the home and remote interface classes (and other value object classes). That's it. Stubs classes are marshalled to the client by the RMI framework as needed. That's the job of PortableRemoteObject.narrow().
Is it not so??
On the second thought, the option says, "provides the configuration information for mapping resource references and resource managers.".
Not "maps the resource references and resource managers.
So if the sysadmin configures the resource manager, only he/she can "provide" that information. The deployer uses it to "map" the resource references to it. Does it even make any sense?
Wow..what a wonderful explanation
Just one confusion. This is caused by the specs and not you
Section 3.1.6 says, "The System Administrator is responsible for the configuration and administration of the enterprise's computing and networking infrastructure that includes the EJB Server and Container. "
The way I was understanding it was (which is wrong), the SysAdmin will provide the infrastructure such as the server (physical box), networking etc. The deployer will use that infrastructure to set up the EJB container and configure it because the deployer is an expert at a "specific operational environment". So he/she knows how to configure the weblogic (or whatever) server etc. and, of course, deploy the application.
thanks a million for being there !!!
This is from one of the cheaper mock exams (softSCBCD or INES one).
A bean deployer...
1. provides configuration information for mapping resource references and resource managers.
2. configures resource managers in the operational environment.
Which is correct?
Any ideas?

Originally posted by Kathy Sierra:
Oh yeah, I forgot about your client jar question. Your server is *somehow* preparing a client jar for you -- or at the least, you can find out *where* it puts the classes you need.
Remember, the client jar needs the stub classes! That's the main thing that has to go into the client jar. The client MUST have access to the j2ee.jar, of course, (where javax.ejb is, etc.) AND your interfaces, and the stub classes. So if you haven't even compiled the client yet, you can put the interface and the stub classes into a jar, and that's the client jar.

As far as I know (in fact I do have a sample working application that I keep tweaking for learning purposes), stubs are not needed in the client's jar. At least when your app server is WebLogic.
I have a web application that I run in Tomcat. It uses the EJBs in WebLogic and I have only two jars in my WEB-INF\lib : wlclient.jar (which is Weblogic stuff) and a client.jar that only has EJB interfaces. No stubs.
I believe that the stubs are automatically marshalled by weblogic over to the client when i do lookup.
That's great!
Thank you for everything you've done for SCBCD seekers
Thanks a lot for your explanation, Mikalai.

Originally posted by Swaminath Akella:
My question is with reference to the following line from the spec.
"The accessor methods for the container-managed relationship fields must not be exposed in the remote interface of an entity bean." Section 10.3.1, page 129.
If the CMR fields are not exposed to the clients through the remote interface, how can the client program can manipulate or use the relationship data?

I'm not an expert but here is my guess:
By using the local interfaces. It is possible for a bean that does not have any remote interface to participate in a relationship. So exposing the cmr fields through the remote interface of the second bean does not make any sense.
Here is one question for the "special" version of Whizlabs simulator that they are giving for free.
Given the following code for the home interface of a stateful session bean, which of the following statements are true? (BTW, you can't even copy-paste from the damned thing. I have to type it to post it here.)

Correct options are:
C. MyBean is the remote component interface.
E. The code will be valid only if create and createBean methods throw RemoteException.
My problem: What's up with the createBean method? Can you even have such a method in the home interface of a session bean?