Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AOBJ Archiving Object #804

Open
larshp opened this issue Jul 4, 2017 · 8 comments
Open

AOBJ Archiving Object #804

larshp opened this issue Jul 4, 2017 · 8 comments
Assignees
Labels
new feature New feature or request serialization Translate between object types and files

Comments

@larshp
Copy link
Member

larshp commented Jul 4, 2017

Database table: ARCH_OBJ + other?

define via transaction AOBJ

function modules:
ARCHIVE_OBJECT_GET
ARCHIVE_OBJECT_CREATE
ARCHIVE_OBJECT_DELETE
ARCHIVE_OBJECT_STRUCTURE_SET
function group ARGN

@larshp larshp added the serialization Translate between object types and files label Jul 4, 2017
@larshp
Copy link
Member Author

larshp commented Jul 4, 2017

if anyone wants to make a PR, this looks like a quite easy task

just add a comment here if somebody starts working on it

@bigld bigld self-assigned this Jul 5, 2017
@bigld
Copy link
Collaborator

bigld commented Jul 5, 2017

I'll do this at the weekend

@mbtools
Copy link
Member

mbtools commented Apr 4, 2022

@bigld do you have a custom archive object that you could add to https://github.com/abapGit-tests/AOBJ.git for testing?

Thanks!

mbtools added a commit that referenced this issue Sep 7, 2022
@xtough
Copy link

xtough commented Sep 8, 2022

Hi @mbtools and @larshp ,
Sorry for throwing a spanner in the works. But SAP is currently also working on an AOBJ handler for abapGit, however with a JSON-based format based on AFF (see https://github.com/SAP/abap-file-formats ). We should avoid creating 2 incompatible formats that would need to be aligned afterwards. At least we should discuss the options. What do you think?
Thanks, Christoph

@mbtools
Copy link
Member

mbtools commented Sep 8, 2022

@xtough I'm not clear about the release compatibility of AFF. Will the JSON version also work with all lower releases supported by abapGit? >=702

@xtough
Copy link

xtough commented Sep 8, 2022

@mbtools I see your point. There is no easy answer to that. Please bear with me for a few more days until I had a chance to talk to some colleagues that are currently on vacation.

@mbtools mbtools added the new feature New feature or request label Sep 21, 2022
@xtough
Copy link

xtough commented Sep 26, 2022

Hi @mbtools ,
sorry for the late response. The short answer is "yes", it is possible to use JSON based metadata also lower releases like 702, as shown recently with the experimental handler for INTF in #5658 . A handler just has to support the format as described in AFF, but does not necessarily have to depend on the AFF framework, which is obviously only available in newer releases. This even makes it possible to reuse the type interfaces like https://github.com/SAP/abap-file-formats/blob/main/file-formats/aobj/type/zif_aff_aobj_v1.intf.abap for AOBJ. Of course, the JSON-based format proposal for AOBJ currently focused on cloud features but missing older features can be added incrementally in a compatible way.
Cheers, Christoph

@mbtools
Copy link
Member

mbtools commented Sep 26, 2022

Alright. We will wait for the AOBJ JSON handler and not implement an XML version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature or request serialization Translate between object types and files
Development

Successfully merging a pull request may close this issue.

4 participants