currently Java action jars are stored in couch DB and the streamed to the JarLoader while invocation. @gorkem is working to refactor that approach to save load and invocation time.
One of the thought is define a m2 kind of lay out and Java Action pick the jar from it instead of streaming. It could be modelled around GlusterFS and PV.
currently Java action jars are stored in couch DB and the streamed to the JarLoader while invocation. @gorkem is working to refactor that approach to save load and invocation time.
One of the thought is define a m2 kind of lay out and Java Action pick the jar from it instead of streaming. It could be modelled around GlusterFS and PV.