＋设为首页 ＋添加到收藏夹
let me describe the following real-life situation from my own experience, and see if you havent experienced the same thing. 【程序编程相关:The Java Extension M】
enterprise javabeans provide many advantages. but each server-side/back-end developer knows that development of ejbs is sometimes painful, time-consuming, and requires a lot of patience while creating assembly descriptors, application-server-specific configuration files, etc. and beyond that is the question: how will we test our ejb? 【推荐阅读:Java Tech: Language 】
time passes and my session bean is ready. at least i think so. but lets be more realistic! ive implemented just a tiny part of the whole business logic, and i need to check how it works. but how will i test it? do i test business logic by calling ejb methods, like a normal java class? no, never! do i need to create an additional ejb client and use that? probably. but what if i will need to share my test reports with other developers? that could definitely waste my time, and instead of developing just the ejb itself, i will have to develop a useless client, which will be only be needed during development. 【扩展信息:Java Tech: Acquire I】
i need to implement my projects business logic in a session bean, one that will work with few other ejbs. i will also create documentation in uml (and/or javadoc format) to describe the business methods exposed by my ejb. few other back-end and/or front-end developers will use these business methods from their code.
... 下一页