on 06-14-2007 1:12 PM
Dear Developers,
I wonder if there will be in the next releases of WD4A a way to send to an upperlevel component exceptions from a component. I mean it would be interesting to have the same behavior as events sent from a component to an upperlevel component.
Do you plan to release it ?
Sincerely,
Olivier MATT
PS: I am currently not really dealing with exceptions in my WD components and have to "translate" them manually to events that I have to define.
Hi Oliver,
If I am not mistaken, you can already pass on exceptions along the call stack of method calls. Since WDA was implemented using ABAP, we have no control over how exceptions are handled and the normal ABAP way happens, which is quite powerful in its own way.
Best regards,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
Is it possible in a components method to define which exception classes can be raised like in a normal method of an ABAP OO Class?
In the methods of a component, I only have to possibility to define the method name and signature but I have not found any way to define the exceptions which can be raised.
Can you help me ?
Sincerely,
Olivier MATT
Message was edited by:
Olivier Matt
Hi oliver,
In components you cannot mention the exceptions as an attribute, but you could do it in your code that you write.And acording to the exceptions you can invoke events of your choice.
As you said , it would be a beautiful functionality if they could implement exceptions at the UI level methods.
Cheers
Anzy
Hi Olivier.
I have posted a similar question some months ago:
You are not able to define it in the signature and therefore you can not raise an
exception in view/component controller methods. But if you rauise them in a
normal abap class you as (as model) you can catch it in all clalling stages.
Cheers,
Sascha
Hi Thomas.
Good point. If you set CX_NO_CHECK as parent class of the exception it should
be working.
HELP:
Exceptions that are defined using subclasses of CX_NO_CHECK must not be declared explicitly in the interface of the procedure. The class CX_NO_CHECK and its subclasses are implicitly always declared and are always propagated.
Cheers,
Sascha
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.