This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
As far as I know you can only initialize an EJB using @PostConstruct method which takes no parameters. It's invoked by the container and it's the only hook to use between class instantiatation and giving it's EJB nature.
I think you'll need to go with specific business method that you'll invoke in order to store the data as a part of the conversational state. If the particular data / parameter is required to be set for further processing, you can check this and throw i.e. some IllegalStateException or ApplicationException.
Joined: Aug 30, 2011
I thought there was a way to do this, without using annotation/dependency injection, by creating an ejbCreate() method in the local interface that had parameters and then when looking up through JNDI you pass those parameters to the create() method. Am I mistaken?