alternate attribute names

[Cantor, Scott]

> So it's interesting a little concerning to read Marvin's recommendation for
> what seems a more convoluted method using activation conditions. Marvin
> or others, could you elaborate on why this is a superior approach?

Just style, it depends what you'd rather do. I think logically keeping the internal names of the attributes consistent and just encoding them selectively is clearer. Having a filter rule say to release employeeNumber is cleaner to me than having a rule to release employeeNumberWorkaroundForSP.

YMMV, and I imagine the requirement for Spring syntax to define those activationConditions is enough to put plenty of people off it. I just think that's putting off the inevitable, if you want to run this software, you're going to learn Spring basics or eventually get rid of it as too much of a pain to get anything done.

-- Scott