> > When we add that functionality we'll want to make an option on the > container to control how long a calling thread should wait till timeout > occurs and a ConcurrentAccessTimeoutException is thrown. Any thoughts on > what the default timeout should be? Couple seconds, couple minutes, > infinite? > Couple of seconds.
> We could add an option on the container so people can control which they'd > like to do by default. Any thoughts on what the default default should be? > I.e. first access (lazy) or at startup? > Startup > > Again the spec group hasn't determined the ejb-jar.xml xml for specifying > if the singleton bean should be loaded on startup. Any ideas? <loadOnStartup>true</loadOnStartup> Alternatively, we could also specify numbers to tell the container the order in which these should be started (I find this option more attractive than a true/false option) <loadOnStartup>5</loadOnStartup> > There are no real configurable options for this functionality that I see. > Again the spec group hasn't determined the ejb-jar.xml xml for specifying > if the "@DependsOn" data in the deployment descriptor. Any ideas? Can one use @DependsOn to specify multiple beans? In that case we could use an ANT like approach with the dependsOn attribute having a comma separated list of ejbs. > > > > > -David > > > > > -- Karan Singh Malhi
