# Stardog not able to find custom extractor

**URL:** https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891
**Category:** Support
**Created:** [March 23, 2018, 6:33pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891 "2018-03-23T18:33:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jss1clist](https://avatars.discourse-cdn.com/v4/letter/j/48db29/32.png) [@jss1clist](https://community.stardog.com/u/jss1clist)
#### Post date: [March 23, 2018, 6:33pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891/1 "2018-03-23T18:33:39Z")

</div>

Hi there,

I'm creating a custom extractor following [this example](https://github.com/stardog-union/stardog-examples/tree/develop/examples/docs).

However, I got the following error when adding a document via StardocsConnection.

> Unknown extractor name: com.some.package.name.CustomExtractor

I have the file _META-INF/service/com.complexible.stardog.docs.extraction.RDFExtractor_ pointing the custom extractor and the following dependency in the pom.xml file

> ```
> <dependency>
> <groupId>com.complexible.stardog.stardocs</groupId>
> <artifactId>stardog-stardocs-protocols-embedded</artifactId>
> <version>${stardog.version}</version>
> <type>pom</type>
> </dependency>
> 
> ```

Please let me know what I'm missing.

Thanks!!

---

<div class="post-metadata">

### Author: ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)
#### Post date: [March 23, 2018, 6:51pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891/2 "2018-03-23T18:51:56Z")

</div>

Is your `com.some.package.name.CustomExtractor` available on the classpath of the running Stardog server?

---

<div class="post-metadata">

### Author: ![jss1clist](https://avatars.discourse-cdn.com/v4/letter/j/48db29/32.png) [@jss1clist](https://community.stardog.com/u/jss1clist)
#### Post date: [March 23, 2018, 7:21pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891/3 "2018-03-23T19:21:12Z")

</div>

Ah, that is it. The example uses an embedded server. Mine does not.

I put the JAR that contains the custom extractor into the _\<STARDOG\_HOME\>/server/pack_ directory; restart Stardog server and it works now.

Thank you!

---

<div class="post-metadata">

### Author: ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)
#### Post date: [March 23, 2018, 7:24pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891/4 "2018-03-23T19:24:50Z")

</div>

FYI: Stardog will, on startup, look for a STARDOG\_EXT environment variable, and will bring in any jars it finds there. This proves useful so that in the future if/when you upgrade you don’t have to remember to put external jars inside the new install directory.

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)
#### Post date: [April 6, 2018, 7:25pm UTC](https://community.stardog.com/t/stardog-not-able-to-find-custom-extractor/891/5 "2018-04-06T19:25:09Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.