Is the keyword oneOf supported? about jasyncapi HOT 18 CLOSED

Welcome to AsyncAPI. Thanks a lot for reporting your first issue.

Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

from jasyncapi.

@thomas-weinstein-bosch hi. Will check it

from jasyncapi.

@thomas-weinstein-bosch hi. Yes, schema in asyncapi supports oneOf - https://www.asyncapi.com/docs/specifications/2.0.0#schemaObject.

Unfortunately I have released 1.0.0-eap without actualized schema. Will fix it in next release, which is planned before end of this week(31)

from jasyncapi.

Hi,
ok, thank you very much!

from jasyncapi.

@thomas-weinstein-bosch hi.

Can you build core part from https://github.com/Pakisan/java-asyncapi/tree/feat!/Schema_updation and check that everything works fine for you? If so, I will publish update

from jasyncapi.

Hi, sure, I will check it asap.

from jasyncapi.

I tried to verify it, but unfortunately the java/lombok/maven environment didn't work out well together with my kotlin/gradle environment. But looking at the properties, I think it should work fine.

from jasyncapi.

@thomas-weinstein-bosch

I tried to verify it, but unfortunately the java/lombok/maven environment didn't work out well together with my kotlin/gradle environment. But looking at the properties, I think it should work fine.

With which problems you faced up?

from jasyncapi.

Just issues when trying to use the sources in the project directly, like kotlin not using the generated lombok methods but trying to access the properties directly, or jackson not understanding lombok either. I will give it a try to set up the project separately, which is unfortunately always a pain behind our corporate proxy.

from jasyncapi.

You can try to use delombok plugin. Looks like it's my failure to not test this case properly. Right now I'm writing kotlin demo to demonstrate usage of core/plugins. So I thing that I will faced with similar problems and will think how to fix it properly

from jasyncapi.

When the lib is built and linked as a .jar it worked like a charm, which would be the usual way, so I think no error on your side =) I will give it a try to fix the setup behind our proxy this week, to provide a veririfaction.

from jasyncapi.

it's everything ok?

from jasyncapi.

Hi, so I finally managed to locally build the branch and import it in the project. There were still some unrelated issues (our corporate proxy, an issue with dokka under windows Kotlin/dokka#656 and the generation of the javadoc somehow threw malformed html errors (from the <br> nodes and the https link inside <>).
But the schema update itself definitely helped, all the unrecognized fields are now known and the jackson deserialization correctly parses all schemas. Unfortunately the oneOf list was empty, so some more configuration or a custom deserializer is needed.

from jasyncapi.

Can you provide example of not working oneOf definition. Will check yours example too

from jasyncapi.

I'm sorry, after checking again, I found the correctly serialized oneOf properties, it was my fault. So with the feature branch with the updated schema our documentation works (basically the same structure like the example I linked in the first post). 👍

from jasyncapi.

Will release new version with fix, on next week. After release I will notify you with mention in this issue and than will close issue

from jasyncapi.

@thomas-weinstein-bosch 1.0.0-eap-1 was released.

You can download it from maven central and check it out here - https://search.maven.org/artifact/com.asyncapi/asyncapi-core/1.0.0-EAP-1/jar

from jasyncapi.

I'll close the issue. You are welcome to reopen it at any time in case of issues

from jasyncapi.