Shahfazal Mohammed

Ranch Hand
+ Follow
since Jan 08, 2004
Merit badge: grant badges
For More
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 Shahfazal Mohammed


currently they come out to fazal at louisiana dot edu
19 years ago
Hey guys-

I'd updated my profile to unsubscribe from any "occasional" promotional emails about JavaRanch Giveaways.. but i still keep getting them. Can somebody look into this plz??

19 years ago

There could be an application ( possibly another server?) running on your machine that's already listening to port 9191 and when the j2ee server tries to open that port for its web service, it's getting an error because the port is already being used by some application/server.



not atleast for another 6-8 months i guess. Wotsay Kathy???

Originally posted by candy varma:
HI all
which one is the best book for preparing SCBCD exams

One more for HFEJB - Although the EJB Spec might be a li'l bit more than necessary.
Hi there-

I took my SCBCD exam on friday 05/14 and was wondering how long would it take for CertManager to show up the results in my 'Certification Progress'

I guess when you say 'call a bean', doesnt it mean 'call a bean method'???, in that case the question stands correct because a bean (bean method) needs to be called in a transaction context, otherwise a TransactionRequiredException will be thrown.

correct me if i'm wrong.


As a Bean Provider, your deliverable is an ejb-jar file with your beans/interfaces/deployment-descriptor. This ejb-jar file can possibly be mixed with other ejb-jar's from the application-assembler, to better fit a domain, based on the requirements. And I guess that's why EJB spec does not recommend putting classes in packages.



all of the following inferred/quoted from HFEJB page#610 and page#616

the <resource-ref> tag is used to get a resource manager connection factory reference, through which you get what you really want. for example

in the above you;re getting a reference to javax.sql.DataSource that you can use to get a connection.

the resource environment reference <resource-env-ref> tag is used to get a reference to something called an administered object like javax.jms.Queue or javax.jms.Topic. The main difference here is that the resource environment reference is to a thing you want, the destination.
for example

'.... the administered object is the destination, whereas a resource manager connection factory reference is just the first step in getting what you really want..'


hiya there-

I'm just back from a graduation party for one of my friends, but guess i'm sensible/sane/sober enough to discuss this . The Container is free to throw any of the related exception to the client, meaning it can either throw a NoSuchObjectException or a RemoteException.

HFEJB page#550 - 'BANG!' note

The client might NOT get the most specific exception
'...The Container might not, according to the spec, send the client a DuplicateKeyException even if that is the problem... .. It's upto the Container whether it gives you the more specific exception'

So, I guess the exception thrown .. RemoteException or NoSuchObjectException .. really depends on the implementation of the Container

- Fazal.
Answer (1): True, implementing javax.ejb.SessionBean gives you the 'beanie attributes' (SessionContext, container callbacks) and lets the Container kick in to provide its services like security, transactions etc.

Answer (2): i. EJB Container crash
ii. Bean times out while passivated state
iii. Bean throws system exception.

and I'm finding it kinda hard to understand what you try to mean in the third question. maybe some clarification would help me.

Also, can you please post where you get/got these questions from???

hope this helps-
I guess it's TRUE.

you have an entry in the DD for an MDB

the above example is for a MDB that listens to a queue, if it were for a Topic, the <destination-type> tag would have been

So, the deployer can look into the <message-driven-destination> tag for an MDB and can find out if it's intended for a Queue or a Topic.

I guess when you say a 1--* relationship, it's more better represented when the entities are different tables - House table and Room table (you know, normalization and stuff)
and, technically, when you say a collection-valued relation field - 'room', it's a getter method getRoom() (or more comfortably getRooms() when your cmr-field is 'rooms') which will return a Collection of local component interfaces of the Room entity bean (a different table), so that you can iterate thru them. your database might actually have to be modified as

in this case your EJB-QL would look something like -

hope this helps

Originally posted by Pourang Emami:
Is the following statement true?

"client's transaction context is never passed to a MDB. The container creates a new transaction context for a MDB if it requires a transaction"

A client can never call an MDB directly. MDBs do not have home/remote/local interfaces for the client to lookup/create/use the MDB. The Container manages everything about an MDB, instantiation, removal, calling the onMessage(Message m) method .... in fact, 'Required' and 'NotSupported' are the only transaction attributes that an MDB can use w/ it's onMessage() method, because the others do not make sense.

HFEJB page#500
'You can say only two things for onMessage():
YES, I want to start a transaction (Required)
NO, I don't want to start a transaction (NotSupported)

hope this helps

[ May 15, 2004: Message edited by: Shahfazal Mohammed ]
[ May 15, 2004: Message edited by: Shahfazal Mohammed ]