Domain Model should normal live in memory not in database. so cache in memory is very important for domain model life cycle. the class be cached or setModified is important, this method can be used to refresh the cache. the controller is in com.jdon.model.cache.ModelCacheManager the difference wi
| 42 | * @see com.jdon.domain.model.cache.ModelCacheManager |
| 43 | */ |
| 44 | public interface ModelIF extends Cacheable, Cloneable, Serializable { |
| 45 | |
| 46 | /** |
| 47 | * in the past version, this method name is isCacheble, |
| 48 | * now change it after 1.3 ! |
| 49 | */ |
| 50 | public boolean isCacheable(); |
| 51 | |
| 52 | /** |
| 53 | * in the past version, this method name is setCacheble, |
| 54 | * now change it after 1.3 ! |
| 55 | */ |
| 56 | public void setCacheable(boolean cacheable); |
| 57 | |
| 58 | public boolean isModified(); |
| 59 | |
| 60 | /** |
| 61 | * set the property has been modified such as : setName(String name){ |
| 62 | * this.name = name; setModified(true); } |
| 63 | * |
| 64 | */ |
| 65 | public void setModified(boolean modified) ; |
| 66 | |
| 67 | |
| 68 | |
| 69 | } |
no outgoing calls
no test coverage detected