[nuanda]

> Well you can't have a BMP entity bean..etc..etc...


Doh! I was reading BMT and CMT...you can of course have a BMP entity bean ;-) Are you sure you meant to ask re: managed persistence or managed transactions ?

[davidjencks]

I'm not sure of all the things you (erik) are asking.

Dave is correct after correcting himself, BMP, CMP, session beans can all participate in the same transaction: BMT and CMT don't mix.

Jboss does support distributed transactions (one transaction encompasses resources (ejbs) located on several jboss instances IF you use the Tyrex transaction manager. The default jboss tm works only with one jboss instance, although you can have xa transactions using several databases, or a db and several message queues.

I recommend, if your processes need to visit several jboss instances, considering how much you can do with asynchronous messaging: do work on one machine, and commit it along with one or more messages about the next step(s). If you don't need an immediate response from a further along step, this can significantly reduce latency and through queueing provide better load distribution.

I would like to know more about what kind of configuration stuff you are thinking about. MBeans are probably the answer;-) but it would help to know the question better. Jboss 3 is getting an easier-to-remotely-administer and update configuration framework.

[erik777]

David,

I created a new thread called "ASP model" describing the scenario I have in mind. I will post it on the EJB forum, since we are kinda moving to a higher architectural level with this discussion.