> > > don't need EJB's anymore, just plain jane
> > > MBeans and JDO will do the trick :-)
> >
> > What deals with transactions?
>
> Either do JDO transactions manually, or make a simple generic proxy that
> deals with it by calling JDO transactions or JTA.
Hrm... not sure how to to that really. Wouldn't the client still be
required to manage references to tx mgr, to add objects that will be
managed?
Perhaps if there was a thin proxy layer which automated this.
> Nope. EntityBeans -> JDO, stateless session beans -> POJO's (Plain Old
> Java Objects). Stateful session bean stuff is done in web session.
>
> I've gained a lot though, since MBeans are inherently more manageable
> (how do you manage/configure beans at runtime? you don't!), and there's
> no distribution which means I can drop all the value object nonsense.
What about the configuration of a given deployment? EJB lets you write
components which are not directly assocated and link them together via
deployment descriptors.
I guess with the new deployable services system, a similar linking scheme
could be employed. But still let that configuration and linkage be changed
(or specified) at runtime.
I have not done much JDO. Do you provide the jdbc/sql or is there a
subsystem that simply takes your object and persists it?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
