session bean container

[sawan parihar]

Hi all,
I have some doubts and just want to discuss with all you guys. I was just wondering that why the spec doesn't allow a container to introspect the bean class and generate the component and home interface. Then the developer only need to code the bean class and also for the bean class the API can provide a class that contains the default implementation of all the container callback methods. Atleast it can be done for session bean . For entity beans there are these home business methods etc but for session beans I am not able to think of any restriction. Appreciate if you guys can give me some inputs on this .

Well the problem I can think in this case is that how the container will know about what all are the business methods that needs to be exposed but for that we can have a variable that the business method will set.

Thanks.
[ April 18, 2005: Message edited by: sawan parihar ]

[Mudi Appu]

I guess they are not doing it only for session beans because of they need to keep consistency.

[Arun]

Take the case of stateful session beans whose home interface has multiple create() methods. This too cannot be generated by introspection.

So as the previous post says, since it is only for stateless session beans that you can possibly introspect everything from the bean class, I guess they left it out there for consistency.

[sawan parihar]

HI linoops ,
I guess for stateful we can introspect . In case of stateful session bean whose home interface has multiple create method will have corresponding ejbCreate in the bean class. That means with introspection we can generate the interface.

Thanks.

[Arun]

Oh yeah.. i forgot that. Thanks for correcting me.

Regards.