Recent changes to feature-requests

Prevention from illegal connection use

Anonymous — Fri, 07 Jan 2005 11:17:28 -0000

After allocation of a connection in CUBA, the developer
may keep a reference to this connection beyond a
transaction border and use it later *outside* this
transaction, even for data manipulations. These changes
are commited or rolled back at random, depending on
subsequent associations of the connection to other
transactions.
Keeping connections beyond transaction boundaries is of
course forbidden according to the EJB specification.
However, it would be helpful if CUBA would check, if a
connection is currently properly allocated when
performing any operations on it.

Client-managed transactions in wired mode

Anonymous — Tue, 23 Nov 2004 12:19:46 -0000

Client-side transactions in wired mode would be nice to
have. Otherwise, many client operations require a
container-side component only to work around the fact,
that clients can't set transaction boundaries. Of course,
this would mean to introduce a feature which is not
even supported by every application server. But it would
by nice anyway :-)

Automatic component linkage in wired-application.xml

Anonymous — Sat, 20 Nov 2004 17:12:03 -0000

Most applications contain only one particular
implementation for a component interface. It would be a
nice feature if the wired container would just resolve
all inter-componente links automatically by retrieving
suitable provider components for every declared
component reference. This auto-resolvement could be
initiated by an appropriate tag in
wired-application.xml, allowing to do both, manual or
automatic linkage or even a compination of both.