It's
possible that each different declared session bean would have its own object
pool.
Wouldn't declarative security allow you to achieve the same
results?
Juan Pablo Lorandi
Chief Software
Architect
Code Foundry Ltd.
Barberstown, Straffan, Co. Kildare, Ireland.
Tel: +353-1-6012050 Fax: +353-1-6012051
Mobile: +353-86-2157900
www.codefoundry.com
Disclaimer:
Opinions expressed are entirely
personal and bear no relevance to opinions held by my employer.
Code Foundry Ltd.'s opinion is that I
should get back to work.
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED] On Behalf Of Sven van't Veer
Sent: Thursday, February 27, 2003 5:17 PM
To: [EMAIL PROTECTED]
Subject: Multiple Home & Remote interfaces for SessionBeanI have a session bean which is acessed by several applications and I do not want to expose all the beans methods to all applications. In some cases the Remote Interfaces will extend some others. IMHO there is no problem in doing so, simply creating a separate different set of <session></session> tags for each and using a diferent remote in the <remote> tag would do the trick.Any reasons not to do so ??sven
