Skip to content
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.

Sign up for GitHub

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

Jump to bottom

URL not working #595

Merged
merged 2 commits into from
Jun 23, 2020
Merged

URL not working #595

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5341acf
URL not working
tiruis Jun 12, 2020
3a105dc
SQUASH ME: fix link
koevskinikola Jun 23, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/user-guide/runtime-container-integration/jboss.md
View file
Open in desktop
Expand Up @@ -210,7 +210,7 @@ A declarative mechanism like `@Resource` could be
@Resource(mappedName = "java:global/camunda-bpm-platform/process-engine/$PROCESS_ENGINE_NAME"

{{< note title="Look Up a Process Engine From JNDI Using Spring" class="warning" >}}
On JBoss AS 7 / Wildfly, Spring users should always [create a resource-ref for the process engine in web.xml]({{< relref "#manage-service-dependencies" >}})</a> and then lookup the local name in the `java:comp/env/` namespace. [For an example, see this Quickstart](https://github.com/camunda/camunda-bpm-examples/tree/master/deployment/spring-jboss-non-pa)</a>
On JBoss AS 7 / Wildfly, Spring users should always [create a resource-ref for the process engine in web.xml]({{< relref "#manage-service-dependencies" >}})</a> and then lookup the local name in the `java:comp/env/` namespace. [For an example, see this Quickstart](https://github.com/camunda/camunda-bpm-examples/tree/master/deployment/spring-wildfly-non-pa)</a>
{{< /note >}}


Expand Down