Sadly, no. There's code in J2SE that's been deprecated since JDK 1.2 but is still there in 1.6, and will be forever.
Not the way I'd do things (at my day job, @deprecated generally means it's around for minor rev's and gone in the next major rev), but that's the J2EE compatibility rules. -- Adam On 11/29/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > That's what I was afraid of. Presumably the deprecated stuff will be > dropped in the next spec? > > sean > > On 11/29/05, Adam Winer <[EMAIL PROTECTED]> wrote: > > On 11/29/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > > > I have a question regarding the new EL. Does the old EL have to be > > > supported still? It seems like a bunch of methods are *deprecated* > > > but not removed. That's certainly going to complicate things in the > > > interim. > > > > Sadly, the rules we work under require complete API compatibility. > > We can deprecate methods, but we can't remove them. I'd > > like nothing more than to kill the old APIs (and make some other > > changes, too), but it's just not in the cards. > > > > The EL side of things isn't actually that bad, since the old APIs > > can all be implemented in terms of the new ones in a rather > > straightforward fashion. The real ugliness is in supporting the old > > and new state manager APIs - now *that* is painful. > > > > -- Adam > > >
