# Elasticsearch Java Client Transport Client Exception **URL:** \ **Category:** Elasticsearch\ **Created:** [February 2, 2018, 9:10pm UTC](https://discuss.elastic.co/t/elasticsearch-java-client-transport-client-exception/118283 "2018-02-02T21:10:46Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Jeffrey\_Blayney](https://avatars.discourse-cdn.com/v4/letter/j/838e76/32.png) [@Jeffrey\_Blayney](https://discuss.elastic.co/u/Jeffrey_Blayney)\ **Post date:** [February 8, 2018, 10:50pm UTC](https://discuss.elastic.co/t/elasticsearch-java-client-transport-client-exception/118283/9 "2018-02-08T22:50:21Z")
Never tried it unfortunately, had to move on. I'm hard pressed to imagine how spring could cause the inability to find a class from a completely different maven library. If the issue does have something to do with spring, personally I'd call it a defect with the ES maven library, as an external dependency shouldn't cause class resolution problems. Similar post (no maven though): [Could Not Initialize Class PreBuiltTransportClient](https://discuss.elastic.co/t/could-not-initialize-class-prebuilttransportclient/70097/4) Personally my opinion is that we should just let the TransportClient get deprecated, ignore this issue as a very uncommon situation, and for anyone reading this post, they should move on to using the RestClient or RestHighLevelClient. Thanks for your continued help and support! --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-java-client-transport-client-exception/118283)._