# Add plugins from classpath in embedded Elasticsearch client node

**URL:** <https://discuss.elastic.co/t/add-plugins-from-classpath-in-embedded-elasticsearch-client-node/36269>\
**Category:** Elasticsearch\
**Created:** [December 3, 2015, 10:10am UTC](https://discuss.elastic.co/t/add-plugins-from-classpath-in-embedded-elasticsearch-client-node/36269 "2015-12-03T10:10:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![joschi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joschi/32/44946_2.png) [@joschi](https://discuss.elastic.co/u/joschi)\
**Post date:** [December 3, 2015, 10:39am UTC](https://discuss.elastic.co/t/add-plugins-from-classpath-in-embedded-elasticsearch-client-node/36269/3 "2015-12-03T10:39:14Z")

</div>

Thanks for your reply!

This is basically what I'm doing right now:

> For the time being I "cheated" a little bit by creating a sub-class of `Node` which exposes the constructor which allows passing a collection of plugin classes to be loaded on startup, but this feels kind of dirty.

The question is, if this is the intended way to do it.

---

_[View the full topic](https://discuss.elastic.co/t/add-plugins-from-classpath-in-embedded-elasticsearch-client-node/36269)._