Materialized views use older dbms_job instead of scheduler? Very new to this topic - using 11g.

When I create a materialized view, a matching job (not a scheduler job) is created.  But it's my understanding that dbms_job is being replaced by dbms_scheduler.

Am I doing something wrong or am I totally misunderstanding what's going on?
dbms_scheduler, while being much more powerful/flexible than dbms_job, is not a simple/complete replacement for it. dbms_job is still widely used as you have discovered and is unlikely to go away