I apologize for the delay in my response and apologize in advance for the brevity in this response... However; I am literally in the delivery room waiting for my wife to give birth.
In short, Raymond is pretty much right on:1) We are aware that we are requiring the use of an outdated version of Java but are unable to upgrade our Oracle apps without requiring a major upgrade in our application server and worse a complete rewrite of all Oracle collections.2) We are implementing VADR to automate many of these collections and will move those that aren't initially incorporated into VADR to a new collection platform. While there is some pain, and we realize there is, it doesn't make sense to completely switch/rewrite when we know many of these collections are going away in the next year.3) A district has just reached out to us to share how they are successfully maintaining the use of the old Java version, while keeping it secure. We will work with them to issue further guidance that may help the rest of you as well.
We'll share more as soon as we can. Thank you all for sharing your thoughts -and pain points- with us. We are working hard to minimize the pain while still moving forward with as little rework as possible.
I will personally follow up again with another update as soon as possible.
(Please excuse typos as this message has been sent from my iPhone.)Brian Townsend | IT Director
Vermont Agency of Education120 State StreetMontpelier, VT 05620P: 802-828-6575F: 802-828-1444
On Oct 22, 2013, at 9:44 AM, "Raymond Ballou" <[log in to unmask]> wrote:
my guess is that the state is trying to manage with whatever Oracle stuff they have now (without updates) as they bridge into VADR.
The state should support modern browsers that can run on all platforms.