Having a distributed OTS would be great, but don't you have to have
distributed EntityBean locking as well to have a complete solution?
Let's say you have two instances of Jboss running and they're both
trying to use EntityBean A in separate transactions. Shouldn't the bean
be locked across the two instances of JBoss? Or maybe the db layer
should handle this?
Bill
Anatoly Akkerman wrote:
> Thank you, Ole for your reply and post on tyrex-dev, it clarified things
> for me.
>
> So, what is our plan? There is really a lot to discuss among the
> JBoss developers. Since with the latest EJB spec Sun is moving towards
> CORBA, we might as well start pushing in that direction as well. This
> means we need an ORB component in JBoss.
>
> In the short term, though.
> To get Tyrex to work in distributed transactions, we would need to start
> an ORB. Ideally it should be started as a separate MBean (this should be
> doable). Then, Tyrex gets started and uses this ORB (found through JNDI)
> for whatever it needs it for. The initialization code can be taken from
> tyrex.corba.OTSServer and split into starting an OpenORB MBean and Tyrex
> MBean.
>
> I am starting to work on this, let's see how far I can get.
>
> Another issue is, how are we handling the associateThread() stuff. Should
> I start rewriting JBoss code to use javax.transaction.TransactionManager
> instead of jboss-specific tm? Do you want to do this while I am trying to
> get OpenORB and Tyrex into JBoss as MBeans or you have other things to do?
>
> - Anatoly
>
>
>
>
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
