&quot;tom.baeyens(a)jboss.com&quot; wrote : I think the invoking an ejb should be called just 'java' I agree. As Ronald also stated before, this makes a lot of sense in for example a Seam environment. &quot;tom.baeyens(a)jboss.com&quot; wrote : | 1) there is a <jndi jndi-name="..." /> element in the wiring section of jpdl. What is then the most consistent way of naming the jndi element ? In that case the full element specifies only jndi so i don't really know what is the most consistent here. Where is that jndi element used today? I think an attribute makes sense. &quot;tom.baeyens(a)jboss.com&quot; wrote : | 2) do we need to distinct between session and entity beans ? or can we use reflection to find out ? or maybe that doesn't matter any more in ejb 3 ? i don't know. EJB 3 'entity beans', or JPA, don't have a JNDI name. So this use case doesn't make much sense. &quot;tom.baeyens(a)jboss.com&quot; wrote : | I think ejb 3 to get started with in incubation. Then if we get enough requests for ejb 2 we can consider it. I agree. EJB3 is the way to go. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269952#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...