2010 Apr 15 12:55 PM
G'Day,
With traditional exceptions, one can look at a message, go to SE91 and do a where-used for that particular message. This is not possible with ZCX classes, a where-used can be done for the entire class but there doesn't seem to be a way to find where individual exception texts are raised.
Now whilst exception classes do offer the possiblity of a far better structuerd approach that reduces the need for a where-used in first place, this is still a shortcoming of exception classes... or is it? (or am I missing some other way to search for it?)
Cheers,
Mike
2010 Apr 15 2:14 PM
All the Texts are created as the Constant Attributes in the class and we can do the where used on these constants (by where-used list button on the attributes tab).
Regards,
Naimesh Patel
G'Day,
With traditional exceptions, one can look at a message, go to SE91 and do a where-used for that particular message. This is not possible with ZCX classes, a where-used can be done for the entire class but there doesn't seem to be a way to find where individual exception texts are raised.
Now whilst exception classes do offer the possiblity of a far better structuerd approach that reduces the need for a where-used in first place, this is still a shortcoming of exception classes... or is it? (or am I missing some other way to search for it?)
Cheers,
Mike
2010 Apr 15 2:14 PM
All the Texts are created as the Constant Attributes in the class and we can do the where used on these constants (by where-used list button on the attributes tab).
Regards,
Naimesh Patel
2010 Apr 15 5:58 PM
D'Oh! That one was so obvious that I was blinded by it
(Believe it or not I've been using ex. classes for some time!)
However it still leaves another issue (which was actually the one that sparked this debate here in the office): In the old message concept it was far easier to navigate from an error to find the offending code. One could click on a message, see the message class/ID, drop into SE91 and (provided the where used is small enough) go straight to the offending code via a where-used.
Unless class-based exceptions are caught and re-raised as an old MESSAGE statement with a message number, this is not so simple anymore. Or is it?
Thanks,
Mike