Exception :: ActiveObjects before <ao> configuration module is enabled or plugin is missing an <ao> configuration module. Note that scanning of entities from the ao.model package is no longer supported.

[Mr Parashar]

Help me to solve this exception 

"ActiveObjects before <ao> configuration module is enabled or plugin is missing an <ao> configuration module. Note that scanning of entities from the ao.model package is no longer supported."

I am using ao.version 1.1.1.

and also mention the ao module in project descriptor.

Whats going on I dont know.

[Fabio Racobaldo _Herzum_]

Hi,

Problem could be related to Class name lenght. 

Within an Atlassian application the names for AO managed tables are generated using a simple algorithm - prepend "AO_", insert a hash based on your plugin key - e.g. 55658F - and append the entity class name, where camel-case is turned to underscores, so MyAwesomeEntity is turned into AO_55658F_MY_AWESOME_ENTITY, which is almost as long as it can get. Because the generated name is rejected, if it is longer than 30 characters. So either use an appropriately short entity class name or use the @Table annotation to define a name that might be shorter than the class name. 

Hope this helps,

Fabio

[keith]

I shortened my entity name and lo-and-behold it works.  Thanks for the tip!

[Fabio Racobaldo _Herzum_]

you're welcome!

[Tobias Binna]

Of course, we have to Google search to find this information in a community post instead of the docs... 🙄

Thanks @Fabio Racobaldo _Herzum_