This one time, at band camp, Timothy Reaves said:
TR > Would it be difficult to add an attributer to the class declaration in
TR >the mappings file to allow use of encryption? For example, you might have
TR >something like:
TR >
TR > <field name="password" type="string" encrypt="someEncryptor">
TR > <sql name="password" type="char" />
TR > </field>
TR >
TR >where encrypt could be similer to the way key generators are now.
TR >Encryption could be handleded in application space by some JCE provider,
TR >or at the database level if the db supports it (such as DB2).
Timothy,
This is a cool idea. As for the amount of work it would require,
there's a considerable amount, but it's certainly doable. Just look
through the source code at the implmentation of key generators or
jdo engines. If you do decide to tackle this task, remember to
create some test cases for all the functionality before submitting
it to the list.
Your idea to structure such a mechanism similar to that of the key
generators is a good one. It would allow Castor users to plug in
whatever JCE provider they prefer via the castor.properties.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
