WebSphere Commerce commands interact with access beans rather than directly with entity beans. Access beans provide a simpler interface to clients, caching of the home object, and reduced call traffic to the enterprise bean.Access beans behave LIKE Java beans, and hide all enterprise bean-specific programming INTERFACES from the client, like the JNDI, home and remote interfaces.

Advantage of accessbean:

 At run time the access bean caches the enterprise bean home object because LOOK ups to the home object are expensive, in terms of time and resource usage.

The access bean implements a copyHelper object that reduces the number of calls to the enterprise bean when commands get and set enterprise bean attributes. Only a single call to the enterprise bean is required when reading or writing MULTIPLE enterprise bean attributes. 

WebSphere Commerce commands interact with access beans rather than directly with entity beans. Access beans provide a simpler interface to clients, caching of the home object, and reduced call traffic to the enterprise bean.Access beans behave like Java beans, and hide all enterprise bean-specific programming interfaces from the client, like the JNDI, home and remote interfaces.

Advantage of accessbean:

 At run time the access bean caches the enterprise bean home object because look ups to the home object are expensive, in terms of time and resource usage.

The access bean implements a copyHelper object that reduces the number of calls to the enterprise bean when commands get and set enterprise bean attributes. Only a single call to the enterprise bean is required when reading or writing multiple enterprise bean attributes.