This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Software Teaming: A Mob Programming, Whole-Team Approach and have Woody Zuill and Kevin Meadows on-line! See this thread for details.
Ok. I agree primitive return type is not valid. SO the method is invalid.
But as I understand, create parameteres are NOT MUST a s per spec. ALthough logically it does not make much sense having create method without any parameters in ENtity bean.
SO I dont agree with Ravindra's poitn for saying this method is invalid.
[ejbSpecs] SessionBean The method arguments must be legal types for RMI/IIOP if there is a create<METHOD> corresponding to the ejbCreate<METHOD> method on the session bean�s remote home interface.
A stateless session bean must define a single ejbCreate method, with no arguments.EntityBean public PrimaryKeyClass ejbCreate<METHOD>(...);
If the ejbCreate<METHOD> method corresponds to a create<METHOD> on the entity bean�s remote home interface, the method arguments and return value types must be legal types for RMI-IIOP.
Specs specifically mentions stateless session bean must/can have ejbCreate with no arguments but it doesn't say anything about stateful session bean or entity bean and if specs leave it open for the developer to draw conclusion then it doesn't mean that it is valid to have a ejbCreate with no arguments in it in a stateful or entity bean.
Thanks
-- Ravi [ March 31, 2005: Message edited by: Ravindra Janapareddy ]
Hi, Keerthi is right. It doesn't make any sense to have a create method without any parameters but the specs don't say anything about this . That means we can have a create method with no arguments . But it will be like telling the container to create somehting and the something is nothing.
Sawan
Sawan<br />SCJP,SCWCD,SCBCD<br /> <br />Every exit is an entry somewhere.