On 6/11/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I think that there is an important distinction here. There's a difference between providing JMX access and what features deployment capabilities have. For example, while I may have access to an individual instance of an entity bean, I'm not sure because, thank god, I do not know JSR-77, I am certain that one cannot *create* an instance of an entity bean using GBean. One can only create its container.
I'm not sure what the distinction is. If you deploy a EJB JAR full of classes and XML, the end result is that the EJB container runs EJBs. I'm suggesting that if you deploy a "jobs" JAR full of classes and XML, the end result will be that the scheduler runs jobs. Thanks, Aaron
