Jason Dillon wrote:
> 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?
All of that is done by MBeans, i.e. the client does not have to know
anything about JDO or tx's or anything.
> Perhaps if there was a thin proxy layer which automated this.
Correct.
> 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.
In reality you have to write a factory object to access them anyway, so
that factory can take care of any such configuration management.
> 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.
Exactly.
> 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?
This depends on what you use as JDO store. JDO may work with JDBC/SQL,
but that's just one option. In my case I will persist it as RDF in XML
files, and in LDAP. The JDO RI has pluggable state managers (but the
license is still bad though, so it's a wee bit in the future right now).
/Rickard
--
Rickard �berg
Software Development Specialist
xlurc - Xpedio Link�ping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
