To deploy the application client, assemble the application client to create a standard J2EE .ear file and then deploy the application client to Sun ONE Application Server
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
If application client is for client then why do we need to create ear file and deploy it in the application server?
How it would be different to access the EJB components from stand alone client to the client runnng under the Application client container?
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
The main difference I see is that you can use some container services in your client if it's running in the Application client container. For example: With an Application client container you can use dependency injection to access an ejb while a standalone client has to do a JNDI lookup.Siva Masilamani wrote: How it would be different to access the EJB components from stand alone client to the client runnng under the Application client container?
All you need is the client jar (irrespective it's packaged with an app server IDE or, say, "by hand"). Then you can run the client with the Application client container.Siva Masilamani wrote:Lets say i have Swing application which needs to access EJB deployed in a remote server, so i will make this swing application as Application client(under the container) with DD and deploy it in the server where my ejb is deployed and generate the client jar file and distribute it to the client and make the client to invoke this client jar file using the tool provided by my container?
SCJP 5 (98%) - SCBCD 5 (98%)
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
Siva Masilamani wrote:what files need to be given to the client?
SCJP 5 (98%) - SCBCD 5 (98%)
SCJP 6,SCWCD 5,SCBCD 5
Failure is not an option.
Don't get me started about those stupid light bulbs. |