HI:
Q1: I want to know that which one is correct .
1). the client released with EJB interface class.
2). the client released with EJB stub class.
3). the client released with EJB interface class and get stub class after lookup from JNDI.
Q2: Do I need to update the client when I update the EJB component.
Q2: What changed before lookup from JNDI and after that from the viewpoint of client.
Regards!
John Lee
-
HELP, question about EJB stub. (2 messages)
- Posted by: John Lee
- Posted on: February 25 2003 07:50 EST
Threaded Messages (2)
- HELP, question about EJB stub. by Maris Orbidans on February 26 2003 16:20 EST
- HELP, question about EJB stub. by Rajiv Narula on February 27 2003 11:20 EST
-
HELP, question about EJB stub.[ Go to top ]
- Posted by: Maris Orbidans
- Posted on: February 26 2003 16:20 EST
- in response to John Lee
A1:
I think it's server dependent, but generally 3. Only J2EE ref. implementation required to generate EJB stub classes and include them in client's classpath.
A2: No, unless you change EJB interface -
HELP, question about EJB stub.[ Go to top ]
- Posted by: Rajiv Narula
- Posted on: February 27 2003 11:20 EST
- in response to John Lee
The client should be packaged with the Remote and Home interface only
So whenever these two interfaces change in the Bean - the client needs to be updated
IMHO ,The stub should 'never' be bundled with the client.
The stubs are downloaded dynamically at run time when the client does a JNDI lookup. A diiferent version already present at the client side might cause some problems if the stub has changed