Hi!

Catherine Jung wrote:
> Hi, my company uses an object database called Objectivity as an object
> store for our product, and I'm trying to figure out how to get that
> working with jBoss.
> 
> We're not planning to use entity beans (long story, but the decision has
> been made) only stateless and stateful beans, accessing the DB through a
> JNDI interface that we're writing for Objectivity. Objectivity doesn't
> have JDBC drivers.

Ok so far..

> How would jBoss deal with not having a DB properly at it's back? 

No problemo.

> I.E. what
> would happen if it tried to passivate one of the stateless session
> beans? 

Stateless session beans are not passivated (see EJB spec for reference).
Stateful session beans are, but not to a database.

> I've read the architecture description, do you think we'd be better off
> writing a plugin to allow us to properly integrate Objectivity, rather
> than just using it through JNDI lookups?

No, that seems like an ok way to do it. I would recommend copying some
of the code we have in JBoss to do it, for example the Reference trick
used in TransactionManager.

> I don't even want to think about the transaction management, but I'm
> presuming that given the above arrangement, we'd be explicitly handling it
> all ourselves wouldn't we?

Yes. Although you could register your stuff in our TransactionManager if
you want to, and then handle whatever you need to do on the XAResource
callback methods.

> As you may have guessed, I'm fairly new to this whole thing (although
> perfectly prepared to wade into jBoss code if someone can suggest a good
> starting point). So I'm just trying to get some suggestions from people
> that actually know what's going on, rather than me who's just read the
> docs and only has a vague idea.....

1) Using JNDI seems ok
2) Access your database by using something like the Reference trick in
TransactionManager (unless you connect to your DB through some sockets,
in which case simply binding a serializable object might be easier)
3) Hook into the TM to synch with your DB's transaction management. The
TM lives at "java:/TransactionManager" and implements the JTA
interfaces.

regards,
  Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to