I think the jar files mentioned here i.e. wliclient.jar & wlicommon.jar are available in the integration folder, and which is under the ver of wls 8.0 and not on the earlier versions.
-----Original Message----- From: Manoj Kansal [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 12:54 PM To: vikramjit singh Subject: Re: Deploying weblogic.jar on client side Just prepare another jar and call it as ejb-client.jar. Include remote and home interfaces, stubs and helper files in that. Only these files are required by client side standalone applications as you have mentioned. Hope this will help vikramjit singh wrote: > Hi, > > We have to deploy, our application on the client side. We have middle tier > as Weblogic, and Java Swings on the client side to access the server > components. Each client has a jar of the ValueObjects and the Stateless > session bean home and remote interface on its terminal. > And we are planning to distribute weblogic.jar to the client. > Since weblogic.jar is quite heavy 32MB, and we just need it so that it can > recognize the session beans methods and runs properly. > What i want to know, is there some other way, meaning not distributing > weblogic.jar on each client terminal, since its gonna make the distribution > really heavy. The code will be max 1MB, but the total distribution is gonna > be heavy. > > Any suggestions? > Thanks in advance, > Vikram. > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
