Oh yeah, duh. I knew they were there too since that where we discussed
them going, and that's a good enough place for them.
If the code has to use the service engine it can't go in anything
below it, and if the service engine uses it then it can't go anywhere
above it! So, it gets to be part of the service engine and I guess
that makes enough since. It's really not too strange I guess, it's a
feature of the service engine that higher level framework and
application components can use as well.
-David
On Sep 25, 2008, at 4:25 PM, Adrian Crum wrote:
Oops, you're right. It's in service.
Ugh. I can't wait for this day to be over. ;-)
-Adrian
Adam Heath wrote:
Adrian Crum wrote:
The temporal expression Java code in the security component is
already
in the trunk. I didn't mean to say that UI artifacts are in the
security
component. Instead, I was listing all of the temporal expression
related
files and how they are scattered all over the place. Sorry for the
confusion.
Are you certain it's in security? I just went thru all the commit
emails since you started adding this stuff, and I see stuff in
service,
but not security.
