When I use jboss-deployment-structure to import protostream dependency to the application, the protostream library can't see classes from the application deployment. It only sees classes/resources in other modules (in its dependencies defined in module.xml). As a result, when I want to use serCtx.registerProtoFiles(FileDescriptorSource .fromResources("/sample_bank_account/bank.proto")); to register protofiles on client side, I have to create a separate module with that proto file and place a dependency on it in the protostream module. This is a usability issue, similar to https://bugzilla.redhat.com/show_bug.cgi?id=1170697 or https://bugzilla.redhat.com/show_bug.cgi?id=1206702
This needs to be fixed in protostream. I'll add a variant of the FileDescriptorSource.fromResources that accepts a ClassLoader. But until then, this can be very easily worked around by users: use FileDescriptorSource.addProtoFile(String name, InputStream contents) instead.