# Neo4j 3.5.x: It is not allowed to define functions in the root namespace

**URL:** <https://community.neo4j.com/t/neo4j-3-5-x-it-is-not-allowed-to-define-functions-in-the-root-namespace/8221>\
**Category:** Procedures & APOC\
**Tags:** procedure, plugin\
**Created:** [June 20, 2019, 6:11pm UTC](https://community.neo4j.com/t/neo4j-3-5-x-it-is-not-allowed-to-define-functions-in-the-root-namespace/8221 "2019-06-20T18:11:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jiropole](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/jiropole/32/223_2.png) [@Jiropole](https://community.neo4j.com/u/Jiropole)\
**Post date:** [June 20, 2019, 6:11pm UTC](https://community.neo4j.com/t/neo4j-3-5-x-it-is-not-allowed-to-define-functions-in-the-root-namespace/8221/1 "2019-06-20T18:11:51Z")

</div>

So, just upgrading from 3.4.x to 3.5.6. I had to rebuild our plugin, as it depends newer versions of other plugins. No other changes. Yet, I am getting the odd error:

```auto
It is not allowed to define functions in the root namespace please use a namespace, e.g. `@UserFunction("org.example.com.randomUUID")

```

I've tried using increasingly lengthy names, e.g.

```auto
@Procedure(value = "com.company.project.category.function", mode = WRITE)

```

But the error persists. I feel like I must be missing something obvious, as I can't find any references to this issue. Little more background: our plugin defines nine `@Procedure`s and no `@UserFunction`s, and defines a transaction handler. It's presently a mix of Kotlin and Java code (not that it would seem to matter).

Thanks!

---

<div class="post-metadata">

**Author:** ![Jiropole](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/jiropole/32/223_2.png) [@Jiropole](https://community.neo4j.com/u/Jiropole)\
**Post date:** [June 20, 2019, 11:01pm UTC](https://community.neo4j.com/t/neo4j-3-5-x-it-is-not-allowed-to-define-functions-in-the-root-namespace/8221/2 "2019-06-20T23:01:27Z")

</div>

Seems to be related to dependence on `tx-api` – [tracking here](https://github.com/graphaware/neo4j-framework/issues/92).