• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Obsolete Concepts in OCMJEA 6

Ranch Hand
Posts: 261
Android Angular Framework Spring AngularJS Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Greetings, All:

Like all who pursue this certification (in my case it was ultimately successful), I was required to learn some obsolete concepts in order to pass.

I think this is simply necessary, because of the nature of certification. One might think of it as a set of dated 'knowledge requirements'. As time passes, the world moves on, but the test cannot be updated, simply because it would become a moving target for people pursuing the certificate.

However, it might be nice to have a place (a forum topic) to keep a running tally of what no longer makes sense, but which you must parrot in order to pass the test. So I will start the ball rolling, with a few suggestions of my own. Then if there is strong argument that the concepts are not really so obsolete as I believe, notes to that effect can be made. It's quite easy to keep two versions of something in mind, if you work with all the concepts every day. But if part of the test forces you to stretch, or revisit things you'd left behind, it might not be so easy. So, here is my list.
* JSONP: one must be aware of this, and its use as a bypass to domain-source restrictions for feeding data into JavaScript-enabled web pages. However, there is a new (and supposedly easier) alternative called CORS.
* The security requirements for Applets/JApplets. The test seems to be geared toward what happens when various types of applets (signed or otherwise) are loaded. But that response is different, since some version of Java that was released after the test was released.

As I said, I doubt there is much the test-creators can do for this. Test-takers need to be aware of what the cutoffs for these technologies in years/versions are. There is probably more danger of failing a test, than of making an inappropriate suggestion based on what the test says.

Good luck to all who are pursuing.
All of life is a contant education - Eleanor Roosevelt. Tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic