On Dec 21, 2004, at 10:53 PM, mahanare wrote:
> Hi all
>
> I want to know the exact procedure of testing an ejb.
> suppose if i want to write a simple session bean and deploy it on
> jboss and then want to test the functionality.
>
> then how do i go ahead?
I think of session beans as remote access points. They provide a
porthole through which remote clients can invoke server-side business
logic. As such, I make them as thin as possible. They intercept a
remote method invocation and delegate the real work to a non-EJB Java
class. That way, I don't have to test the business logic inside of a
J2EE container. More important, my business logic isn't tied
intimately with J2EE technology.
So here's your exact procedure:
1. Refactor so you can test as much as possible without a J2EE
container because it will make your next software change more
economical.
2. To test J2EE-specific stuff, use Cactus.
--
Mike Clark
Clarkware Consulting, Inc.
http://clarkware.com
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/junit/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
