A common requirement in databound applications is to allow the user to view
changes before they commit them to the database, showing the user both the
original-old value along with the new. This gives users a chance to review
their changes visually by comparing the old and new.
For an updated record that has yet been committed to the database, ADF BC
stores both the old and new value. Among other reasons ADF BC does this, is
it allows the user to cancel any changes, and rather than having to fetch the
original value back from the database, ADF BC just retrieves the old value it
has cached without a roundtrip to the database.
This cache gives us the ability to solve our original requirements as the ADF
BC framework exposes methods to fetch both new and old non committed valu... (more)
Java Developer Magazine on Ulitzer
In the previous post we looked at how to configure the SQLAuthenticator
password encryption options. Among other encryption algorithms we discovered
that on creating a user from the WLS console, WLS would create the associated
user in a database table with password "password" encrypted to:
{SHA-1}W6ph5Mm5Pz8GgiULbPgzG37mj9g=
...when the SHA-1 option was se... (more)
If you're heading to OOW and would love to hear my Aussie accent, my sessions
are:
SOA Lite: A taste of SOA with a smidgen of Web Services
S312176 - Sunday 13:00 - 14:00 - Moscone West L3 Room 3000
Abstract: Attempting to gorge yourself on a five-course SOA meal may result
in a stomachache and a bill you can least afford at the moment. Instead, a
quick and easy recipe with some simple Web se... (more)
In computing most technologies have lots of terms and acronyms to learn, it's
par for the course, you get used to it. However in computer security the
frustration is multiplied as there are often many different terms that mean
the same thing. It makes implementing security hard, because understanding it
is hard, and I'm not surprised why security is considered badly implemented
because t... (more)
A while back Gerard Davison blogged some simple examples of using WS-Security
Policies. Gerard's specific example dealt with the WLS policy
Wssp1.2-2007-Wss1.1-UsernameToken-Plain-X509-Basic256.xml. As Gerard notes
the said policy (further documented in the WLS 10.3.1 doco here) implements
user name tokens, encryption of the tokens and signing of the whole SOAP
payload.
The following pos... (more)
Chris Muir, an Oracle ACE Director, senior developer and trainer, and frequent blogger at http://one-size-doesnt-fit-all.blogspot.com, has been hacking away as an Oracle consultant with Australia's SAGE Computing Services for too many years. Taking a pragmatic approach to all things Oracle, Chris has more recently earned battle scars with JDeveloper, Apex, OID and web services, and has some very old war-wounds from a dark and dim past with Forms, Reports and even Designer 100% generation. He is a frequent presenter and contributor to the local Australian Oracle User Group scene, as well as a contributor to international user group magazines such as the IOUG and UKOUG.
Jacques Durand
Alf Pilgrim
Per Sjofors
Kirsten Lytsen
Data Recovery Services
Colin Armitage
