From: Joel Rosi-S. <Joel.Rosi-Schwartz@Etish.org> - 2002-09-05 11:02:29
|
Hi, I am considering using Exist within a J2EE application running on JBoss. First question is, has anyone done a JBoss 3.0 integration such that Exist starts up with JBoss using a JMX MBean? If not, I am wondering what would be the most sensible approach to embedding. I understand that Exist can run in both standalone and embedded modes. I have found very little information about the architecture of the embedded mode. Is it appropriate to start up Exist inside the JBoss VM in embedded mode and then connect to the database via multiple EJB beans? I read that embedded mode is thread safe, but does this imply that it can live safely as the backend store for beans while in embedded mode. I gather that there is not yet transaction management within Exist, so I am being rather cautious in the initial approach. btw, it would be my intention to *strickly* limit access to the database to be *only* from the EBJ beans, i.e. no exteral clients will be able to reach the database. I suspect that this will possiblely make the integration easier to achieve safely. Your thoughts would be very appreciated. Regards, Joel |
From: Joel Rosi-S. <Joel.Rosi-Schwartz@Etish.org> - 2002-09-21 17:16:29
|
Hi Wolfgang, I posted this message a week or so ago. but I understand that you were on holiday so perhaps you missed it. Just thought I would give it another try :-) I am considering using Exist within a J2EE application running on JBoss. First question is, has anyone done a JBoss 3.0 integration such that Exist starts up with JBoss using a JMX MBean? If not, I am wondering what would be the most sensible approach to embedding. I understand that Exist can run in both standalone and embedded modes. I have found very little information about the architecture of the embedded mode. Is it appropriate to start up Exist inside the JBoss VM in embedded mode and then connect to the database via multiple EJB beans? I read that embedded mode is thread safe, but does this imply that it can live safely as the backend store for beans while in embedded mode. I gather that there is not yet transaction management within Exist, so I am being rather cautious in the initial approach. btw, it would be my intention to *strickly* limit access to the database to be *only* from the EBJ beans, i.e. no exteral clients will be able to reach the database. I suspect that this will possiblely make the integration easier to achieve safely. Your thoughts would be very appreciated. Regards, Joel |
From: Wolfgang M. <me...@if...> - 2002-09-21 20:16:44
|
Hi, I'm forwarding your message to Chris, who has already done some work to integrate eXist with JBoss. He knows more about JBoss than I do, so he is probably the right person to answer your questions. BTW: Embedded mode just means that the database engine is running in the same virtual machine as the main application. It uses the same architecture as the standalone servers: Internally, every request to the database backend is handled by an instance of type DBBroker, which cares about all synchronization issues. All available instances of DBBroker are managed by class BrokerPool, which must be configured during startup. A DBBroker instance should be retrieved for every single call to the backend and released after that. As long as these rules are respected, the db engine should be thread safe. The XML:DB API cares about that. Basically, an embedded db instance is not accessible from outside. Cheers, Wolfgang > Hi Wolfgang, > > I posted this message a week or so ago. but I understand that you were > on holiday so perhaps you missed it. Just thought I would give it > another try :-) > > I am considering using Exist within a J2EE application running on JBoss. > First question is, has anyone done a JBoss 3.0 integration such that > Exist starts up with JBoss using a JMX MBean? > > If not, I am wondering what would be the most sensible approach to > embedding. I understand that Exist can run in both standalone and > embedded modes. I have found very little information about the > architecture of the embedded mode. Is it appropriate to start up Exist > inside the JBoss VM in embedded mode and then connect to the database > via multiple EJB beans? I read that embedded mode is thread safe, but > does this imply that it can live safely as the backend store for beans > while in embedded mode. I gather that there is not yet transaction > management within Exist, so I am being rather cautious in the initial > approach. btw, it would be my intention to *strickly* limit access to > the database to be *only* from the EBJ beans, i.e. no exteral clients > will be able to reach the database. I suspect that this will possiblely > make the integration easier to achieve safely. > > Your thoughts would be very appreciated. > > Regards, > Joel > -- |
From: Joel Rosi-S. <Joel.Rosi-Schwartz@Etish.org> - 2002-09-24 12:04:12
|
Wolfgang , Thank you for your relply. Wolfgang Meier wrote: >Hi, > >I'm forwarding your message to Chris, who has already done some work to >integrate eXist with JBoss. He knows more about JBoss than I do, so he is >probably the right person to answer your questions. > Yes, he has emailed me, thank you. >BTW: Embedded mode just means that the database engine is running in the same >virtual machine as the main application. It uses the same architecture as the >standalone servers: Internally, every request to the database backend is >handled by an instance of type DBBroker, which cares about all synchronization >issues. All available instances of DBBroker are managed by class BrokerPool, >which must be configured during startup. A DBBroker instance should be >retrieved for every single call to the backend and released after that. As long >as these rules are respected, the db engine should be thread safe. The XML:DB >API cares about that > >Basically, an embedded db instance is not accessible from outside. > Thank you for the explanation., it is helpful. >Cheers, > >Wolfgang > > Mit Freundlichen Gruss, Joel |