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

Support Zeebe 8.0 DeployResourceCommand #176

Closed
nikku opened this issue Jul 9, 2022 · 5 comments
Closed

Support Zeebe 8.0 DeployResourceCommand #176

nikku opened this issue Jul 9, 2022 · 5 comments
Assignees

Comments

@nikku
Copy link

nikku commented Jul 9, 2022

What is the issue

I tried out eze with zeebe@8. Two observations:

  • ZeebeClient#newDeplyoResourceCommand not supported:

    client.newDeployResourceCommand()
        .addProcessModel(process, "process.bpmn")
        .send()
        .join();

    Throws the following error:

    io.camunda.zeebe.client.api.command.ClientStatusException: Method gateway_protocol.Gateway/DeployResource is unimplemented
    
        at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:93)
    at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:50)
    
  • New deploy command not supported in exporter

    If I switch back to newDeployCommand (deprecated) serializing a record as JSON in a trivial exporter blows up:

    public class TestExporter implements Exporter {
       @Override
       public void export(Record<?> record) {
         System.out.println(record.toString());
       }
     }

    ...with the following error:

    Exception in thread "-zb-actors-5" java.lang.AbstractMethodError
    at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
    at java.base/java.lang.reflect.Method.invoke(Method.java:577)
    at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:689)
    at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:770)
    at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:178)
    at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:728)
    at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:770)
    at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:178)
    at com.fasterxml.jackson.databind.ser.DefaultSerializerProvider._serialize(DefaultSerializerProvider.java:480)
    at com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:319)
    at com.fasterxml.jackson.databind.ObjectMapper._writeValueAndClose(ObjectMapper.java:4487)
    at com.fasterxml.jackson.databind.ObjectMapper.writeValueAsString(ObjectMapper.java:3742)
    at io.camunda.zeebe.protocol.impl.encoding.MsgPackConverter.convertJsonSerializableObjectToJson(MsgPackConverter.java:176)
    at io.camunda.zeebe.protocol.impl.record.CopiedRecord.toJson(CopiedRecord.java:151)
    at io.camunda.zeebe.protocol.impl.record.CopiedRecord.toString(CopiedRecord.java:161)
    at io.camunda.connectors.inbound.InboundExporter.export(InboundExporter.java:14)
    at org.camunda.community.eze.ExporterRunner.onRecordsAvailable(ExporterRunner.kt:55)
    

Not sure if the later is a miss-use on my end. If so, I have no clue how to fix it.

@Zelldon
Copy link
Collaborator

Zelldon commented Jul 10, 2022

Hey @nikku thanks for trying EZE 👍 I will check this after my vaccation :)

@saig0 didn't you mentioned this is already implemented? 🤔😁

@Zelldon Zelldon self-assigned this Jul 10, 2022
@Zelldon
Copy link
Collaborator

Zelldon commented Aug 2, 2022

@saig0 found out that our artifacts are not published to maven central 🤦

@Zelldon
Copy link
Collaborator

Zelldon commented Aug 8, 2022

@saig0 I guess it should work now?

@saig0
Copy link
Collaborator

saig0 commented Aug 8, 2022

Yes. The latest version 1.0.2 is published to Maven Central. The deploy command is implemented since 1.0.0.

@Zelldon
Copy link
Collaborator

Zelldon commented Aug 8, 2022

@nikku please try with the latest release. I will close it, feel free to reopen it :)

@Zelldon Zelldon closed this as completed Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants