New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong order of context files in archetype generated projects #345

Closed
skopf opened this Issue Nov 6, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@skopf
Collaborator

skopf commented Nov 6, 2015

The archetype creates this module-context.xml file:

<beans>
    <!-- This is filtered by Maven at build time, so that module name is single sourced. -->
    <import resource="classpath:alfresco/module/${project.artifactId}/context/service-context.xml" />
    <import resource="classpath:alfresco/module/${project.artifactId}/context/bootstrap-context.xml" />
    <import resource="classpath:alfresco/module/${project.artifactId}/context/webscript-context.xml" />

</beans>

But order is important here.

The bootstrap-context.xml file has to be loaded first.
Otherwise your custom models are not yet loaded when your service beans are instantiated and you cannot register policies on them!

@ohej ohej added this to the 2.2.0 milestone Jan 11, 2016

@gravitonian gravitonian changed the title from Wrong order of context files in archetype genertaed projects to Wrong order of context files in archetype generated projects Jan 12, 2016

@gravitonian

This comment has been minimized.

Show comment
Hide comment
Contributor

gravitonian commented Jan 12, 2016

@gravitonian gravitonian self-assigned this Jan 12, 2016

@gravitonian

This comment has been minimized.

Show comment
Hide comment
@gravitonian

gravitonian Jan 20, 2016

Contributor

fixed

Contributor

gravitonian commented Jan 20, 2016

fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment