Ron V.

Greenhorn
+ Follow
since Dec 30, 2002
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 Ron V.

Hi Joe,

I believe this is the situation (I'm open for a better explanation though)
When using plain RMI, we're talking about a protocol that is native to Java. So when using it, we can be sure that we will receive a Java object. So a simple cast is enough.

When using RMI-IIOP though, we could receive any Corba compliant object, possibly written in another language. To make this work, we need to perform a narrow. The narrow method will execute some code written by the container vendor that will make the object you looked up through JNDI usable within your application.

Cheers,

Ron
When an entity bean is in the pool, it is not connected to a specific EJBObject, and as such cannot perform actions specific to the bean.
It can only perform home business methods, which do not require a specific bean, but involve all beans, such as calculating the average salary for all employees.

Only when an entitybean is brought out of the pool it is connected to an EJBObject, and can then perform actions on that specific bean. This means calling methods that are defined in the component interface, for example update the salary of a (specific) employee.

So the difference is really: in the pool -> bean in not connected to an EJBObject, out of the pool -> bean is connected to an EJBObject
I also found that Paul Sanghera's book "SCBCD Exam Study Kit" was quite useful. It's latest version is updated to reflect the current SCBCD specs.
It is published by Manning.

You might also be interested in the free download of 'Mastering EJB' at www.theserverside.com
If this is your businessmethod (so the one in the bean) than it should never throw a RemoteException. The RemoteException must be declared in the component interface (the one that extends EJBObject), but never in the actual bean (the class implementing the SessionBean/EntityBean interface).

Could be the container has some clue in it's errorlog.

Also, CreateException should be thrown from a create<method>(), not from a normal businessmethod, but I do not think this caused your problem.
Hi,

I've got the same book and it does cover all things you need to know for SCWCD 1.4 exam.
It is indeed a great book from a great series.

If you feel you need more information you might consider the SCWCD from manning. It is recently updated to the 1.4 exam standards.

Cheers,

Ron