Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Read-only Anonymous keys?
Date: Sat, 27 Aug 2005 13:45:13 -0400
Message-ID: <41C2B90B26CA6343A75BF031D9A44E12DF6D94@ODNEXCH2.em.ohio.gov>
Thread-Topic: Read-only Anonymous keys?
Thread-Index: AcWrLoHTDOYgvIBqSU2EwJvvhLLxZgAADwlg
From: "Clute, Andrew" <Andrew.Clute@etech.ohio.gov>
To: "OJB Developers List" <ojb-dev@db.apache.org>


>=20
> Personally I'd prefer the separation over the new access=20
> value. As long as 'anonymous' still works for access (with a=20
> deprecation
> warning) it should be ok IMO.
> =20

Agreed. The new access values is 'ugly' -- it really isn't an access
value.


> > Tom, do you mind updating the xdoclet module to accommodate=20
> this change?
> > I can take a look at it if not, but the seems to be a fair=20
> amount of=20
> > ramp up time in making changes in the xdoclet code. I will let you=20
> > know when I am about to commit these changes, so we can try to time=20
> > the commits of this, and the xdoclet module at the same time.
>=20
> Yep, I can do that sometime during the next week, I think.

Great! I do appreciate it.

>=20
> > > Btw, would it make sense to add a writeonly access type=20
> (which isn't=20
> > > queried, only inserted/updated) ?
> >=20
> > I can't see an immediate usecase for this, but it seems to=20
> make sense.
> > I would hate to limit someone's mapping by leaving this off, as it=20
> > seems valid, and easy to implement.
>=20
> Image for instance an object where the date and time of the=20
> last change shall be stored in the database (eg. for=20
> tracing). If the application has no need for this info, there=20
> could be a writeonly attribute backed by a getter method that=20
> simply returns the current date and time.

Yeah, this is a perfect example. A quasi-trigger attribute. I like it.
It isn't tough at all to add -- I will do first in 1.0 while Armin
finishes up the 1.1 merge, and then will merge it there.

-Andrew


>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org