Install a JVM along with XE on the client.....Write some java code to communicate with the web service....use the keytool to handle SSL..Sure, we could do that. But then it would be triggered outside the database. What if you need to get the result from whitin the database? There are nasty workarounds available but we have almost everything in place using utl_http, just need the ssl thing going.
Does it matter if its called outside the DB. You'llI am positive that your approach will work.It is just that over the years I have come to the conclusion that less complexity and less dependencies are a good thing in the long term ;). This is based on many unhappy experiences in the past.
lose a few seconds and have to code an
infrastructure...but it will work.
Maybe I have misread this entire thread. Is the question about call outs from the database, or call ins (i.e client to database network encryption). Only the latter requires ASO, SSL call outs don'tjudging by the answer given by Mark Townsend (the former Oracle product manager for Oracle XE), I would clearly see ssl callouts using utl_http and wallets as a legal use for Oracle XE.