In theory, sure. But in practice, no one's going to honor the @Deprecated warnings,
and in the meantime we'll still have JNDI logic to debug if I keep the
"determine" methods in place.
I wanted big glaring compile errors for all cases where the Object Model was being asked
to perform logic it shouldn't be doing, and it made resolving these problems much
easier. I've attached the AS patch to the JIRA as well.
For whom do we want to maintain backwards-compatibility? Ourselves? We should be moving
everything to the more elegant way of doing things.
That in mind, what's the argument for CR1 compatibility (with regards to metadata and
JNDI names only, not a general discussion)?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162254#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...