The reason it doesn't scale to more complex scenarios is fairly obvious, the data contract is too loose and it becomes hard to ensure there are no mismatches in key, value pairs between the two tiers.
它不适合更复杂场景,理由很明显,数据契约太松散,它无法确保两层之间的键值对不出现错误的匹配。
Now you are left with a no-win decision: do you make the attribute understand your application's architectural tiers and call through to the service layer to do the validation?
现在您只剩下一个无法取胜的决策:您可以让属性理解您应用程序的架构层并通过服务层调用来执行验证吗?
There is no more artificially required JNDI lookup, verbose JSF backing bean declaration, excessive facade business methods, and painstakingly passing objects between tiers etc.
在层与层之间,没有了必需的手动JNDI查找,没有了冗长的JSF支持bean的声明,没有了过多facade方法,没有了艰辛的对象传递,快哉!
应用推荐