posted 20 years ago
Stateless and stateful session beans have different lifecycles. As you noticed, since stateless session beans are instantiated by the container, without any invocation from a client, you can't do much in ejbCreate.
I haven't heard of any real need to create session beans that are state-agnostic, so I assume that you just have to pick one that meets your requirements and implement it, documenting the fact that it is indeed a stateful or stateless session bean and hoping the application assembler sticks to it.
Nathaniel Stodard<br />SCJP, SCJD, SCWCD, SCBCD, SCDJWS, ICAD, ICSD, ICED