Why remote interfaces cannot be cached in service locator
[139 byte] By [wickeddaisya] at [2007-9-30 23:43:50] 
Using the service locator pattern, for a stateless bean can a remote interface(EJBObject) be cached?If not, why cannot it be cached?
«« simple read inputline does not work
»» java.io.NotSerializableException: java.awt.Component$AccessibleAWTComponent
»» java.io.NotSerializableException: java.awt.Component$AccessibleAWTComponent
> Using the service locator pattern, for a stateless> bean can a remote interface(EJBObject) be cached?No, because remote interface can be invalidated by invoking remove().
Maris_Orbidansa at 2007-7-7 14:57:50 >
Enterprise & Remote Computing New Topic
Enterprise & Remote Computing Hot Topic
Enterprise & Remote Computing
All Classified
- Archived Forums
- Enterprise & Remote Computing
- Java Essentials
- Desktop
- Core
- Solaris Operating System
- Security
- Database Connectivity
- Java Mobility Forums
- Web & Directory Servers
- Development Tools
- Application & Integration Servers
- Java HotSpot Virtual Machine
- Other Topics
- E-Mail, Calendar, & Collaboration
- Developer Tools
- General
- Administration Tools
- Sun Hardware
- Storage Forums
- Java Enterprise System
- StarOffice
- Open Source Technologies
- BigAdmin
- Real-Time
- Java Coding