Let user decides what form choose to use right? Good, I think is a very good
idea!!! If he wants a programmatic or declarative form he only need to
decide!!
Hi,
I've been reading this thread and I think Woody's suggestion to let the
user decide is a really good one. It would not even be hard
Hi felows, I´m new here and if this message is on wong place, please, sorry
...
I dono if I need to introduce myself, besides I will go direct to the
subject ok?
Daniel, what dou you think about put constraints rules on some type of
propertie file? These constraints must have some type of
On Sun, 23 Jan 2005 15:19:51 -0800, Anaximandro (Woody)
[EMAIL PROTECTED] wrote:
Daniel, what dou you think about put constraints rules on some type of
propertie file? These constraints must have some type of identification (in
one ore more contexts). This is flexible and make the code more
Developers List
Betreff: [contract] Suggestions
Hi felows, I´m new here and if this message is on wong place, please,
sorry
...
I dono if I need to introduce myself, besides I will go direct to the
subject ok?
Daniel, what dou you think about put constraints rules on some type of
propertie
Thanx Daniel, I´ve already see the sources of contract, i18n and xmlio but I
never see before the other project you told (Slide/Projector). This other is
a jakarta project?
In contract sources I see all constraints classes (these classes is similar
to the classes suggested in book Hardcore Java,
Daniel, what dou you think about put constraints rules on some type of
propertie file? These constraints must have some type of identification
(in
one ore more contexts). This is flexible and make the code more clean
(and,
like ejb, can be changed without the need to recompile the code).
On Sun, 23 Jan 2005 17:49:39 -0800, Anaximandro (Woody)
[EMAIL PROTECTED] wrote:
Daniel, what dou you think about put constraints rules on some type of
propertie file? These constraints must have some type of identification
(in
one ore more contexts). This is flexible and make the code
