Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Joe OBrien

Greenhorn
+ Follow
since Oct 06, 2004
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 Joe OBrien

Originally posted by Marc Peabody:


If it did, we could not override it and add our own application exceptions to the throws clause. Also, we would be forced to cast and narrow because it would return Object (although doing so would be consistent with everything else.

There are probably other reasons for it as well.



------------------------------------------------------

I agree with Marc on the return type of this, but I think the answer might be even simpler. We use the same interface (EJBHome)for stateful and statless session beans. If it defined no-arg create, we would have to implement it for the stateful session.

Although this by no means I agree with this implementation ...
I agree with Marc on the first one for page 132.

The rule states that it CAN have more and does not HAVE to have a no-arg.

Just wanted to make it look like I was trying as well :-)
Gayle,

As I'm looking at this, I would have to disagree with it also. I thought this is up to the vendor implementation. We can't concurrently call the same method, but whether or not we have to wait, or have another bean created ... I thought ... was up to the vendor.

Or did I get that wrong?
I know I'm late for questions.

However, could someone help explain tonight the idea of sending another remote object in the method call like they talk about on page 74-75.

-Joe
Leave it to me to forget something that we talked about last week ...

For those of you like me who did forget about this, there is a bug that interacts with the RI Server in the Chapter One example.

If you rename your getAdvice() method in the AdviceBean to something else (like getTheMessage()) it will work (don't forget to change the Advice interface as well.).

See the errata
This should be in the Sark Study Group forum.

Could someone delete this?
Leave it to me to forget something that we talked about last week ...

For those of you like me who did forget about this, there is a bug that interacts with the RI Server in the Chapter One example.

If you rename your getAdvice() method in the AdviceBean to something else (like getTheMessage()) it will work (don't forget to change the Advice interface as well.).

See the <a href="http://www.oreilly.com/catalog/hfjejb/errata/hfjejb.confirmed">errata mentioned earlier </a>
disregard my statement about the product db ... i just saw my flaw in that logic.
Mark,

I agree ... somewhat.
I came up with entity for the product database (when they talked about each one representing a row in the db).

I also thought the online expert diagnosis would be stateful not stateless. With diagnosis you have a series of questions that seem to drill down to the eventual diagnosis. (i.e., do you have a fever - if so is there a cough with it, if so is it productive, etc...).

-Joe