Issue 128 in zaplink: Message Base Exception classes and inheritence

0 views
Skip to first unread message

zap...@googlecode.com

unread,
Sep 2, 2011, 4:30:00 AM9/2/11
to zaplink...@googlegroups.com
Status: Accepted
Owner: tar...@bensiali.net
Labels: Type-Defect Priority-High Detected_on_Release-0.0.008
Release-0.0.009

New issue 128 by tar...@bensiali.net: Message Base Exception classes and
inheritence
http://code.google.com/p/zaplink/issues/detail?id=128

What steps will reproduce the problem?
1. Create a exception class message based
2. Create a exception class that inherit from the previous one
3. Create exception text in both classes
4. Export both classes

What is the expected output?
Both class will have exception_texts markup

What do you see instead?
Only the first one that introduce message based exception class has
exception_texts markup
This errors comes from : ZAPLINK_CLAS_DATA->FROM_DATA
` IF fm_data-class-category = seoc_category_exception.
READ TABLE _fm_data-implementings TRANSPORTING NO FIELDS WITH KEY
refclsname = intf_4_message_exception_cl.
IF sy-subrc = 0. " Message based Exception
`
Where Interface for message exception classe is searched only in the class
it-self but not in parent classes


zap...@googlecode.com

unread,
Sep 2, 2011, 4:58:13 AM9/2/11
to zaplink...@googlegroups.com
Updates:
Status: Verified

Comment #1 on issue 128 by tar...@bensiali.net: Message Base Exception

Fixed with changeset :
http://code.google.com/p/zaplink/source/detail?r=b2ce5f6649cee30fca4a64ae5ab7cf4992480c9d

Reply all
Reply to author
Forward
0 new messages