Question about intended access to EJB Beans by interface contract.

[Zachary1234]

As I understand,

One uses an InitialContext.lookup,
with an Application Server'sEJB - JNDI registered
name for an enterprise java bean, [b]with an appropriate interface name[/b] in order to reference/use the bean.

I am familiar with the design pattern/anti-pattern "extreme coupling",
where an interface type is returned by a method
which has implemented interface methods from an inner class.

The notion with
EJB application access would stipulate
you only ever deal with a bean's
JNDI name and interface names,
never the core implementation class.

-Does JBoss and other servers
conceal the name of the core bean
class itself,
such that a correctly initialised
(set with properties)
InitialContext.list()
will NEVER return the class file name?

-is the Bean implementation
class intentionally kept invisible,
accessable only by bean interfaces?

-If not, what may one do within the bean
to acheive this?

I ask here, since the JBoss response
is somewhat confusing.

[Zachary1234]

Don't worry, the SUN EJB 2.1/3.0 EJB Specification has answered my qestion!