Issue 135 in zaplink: Mass extractor makes source code changes
zap...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 135 by dominik....@gmail.com: Mass extractor makes source code
changes
http://code.google.com/p/zaplink/issues/detail?id=135
#WARNING : All issues must have the framework information file build using
transaction ZL_INFOS or if not working program ZAPLINK_INFOS_STANDALONE
(that could be downloaded). Each issue without these file might be close
without any investigation. Before opening an Issue please try with the last
framework version.
#What version of the product are you using? ==> add a release label
"Dectected-on ...".
0.9 Mass Extractor
What steps will reproduce the problem?
1. Create class
2. Export class using mass extractor.
What is the expected output?
I expect the classes to be dumped to XML files to my local disk. I also
expect that the classes will be accesses in READ-ONLY mode on SAP without
any changes made.
What do you see instead?
Sometimes Mass Extractor is regenerating PUBLIC/PRIVATE/PROTECTED headers
of classes (don't know exactly what the condition is). This results in a
pop-up asking for transport requests. For users that only want to use Mass
Export to keep their source code in a source code repository, this is
unacceptable, as they do not want any changes in their SAP ABAP code.
#Please provide any additional information below.
Methods _CHECK_CLASS_SECTIONS and _cleanup_class are called. They are
further calling function module SEO_CLASS_GENERATE_SECTIONS, which causes
this nasty behavior.
Maybe a flag in the interface of the program should be added that
reads 'READ_ONLY' (selected by default) meaning that no changes will be
made to SAP ABAP source code.
zap...@googlecode.com
Status: Request
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Detected_on_Release-0.0.009
Comment #1 on issue 135 by tar...@bensiali.net: Mass extractor makes source
code changes
http://code.google.com/p/zaplink/issues/detail?id=135
Hi,
We understand your issue, but mass extractor is just an autogenerated
program to work as a stand alone program.
So we can't do anything on this program, we have to change the components.
Section's class are regenarate in order to have the same code signature
which allow you to ensure "versioning"...
This is a standard behavior and is connected to issue 71.
Action made is "just" regenerate section in order to always have same
source code.
We'll think of this request, but right know I do not have any idea to add
this feature without impacting the whole framework.
I sugest to comment the two method in your version of the extractor stand
alone.