Hi Dan, thanks for the advice!
We have a multiple stages for our system (Dev PC, DEV, INT, PROT), the
context root value changes - at least between developer pc and deployment
on Tomcat.
Developer PC:
No context root since running with embedded jetty - no adaptations needed
for swagger-ui/index.
Ah, I remember this issue.
It turns out that it does work, so long as you deploy the webapp as
ROOT.war.
The issue is the path to the swaggerService does not resolve correctly when
running as anything other than the root app.
I did manage to figure out the hacks though if you really do want to d
Ok, thanks for reporting, I'll take a look hopefully this evening.
Dan.
On 16 May 2016 10:02 am, "Vladimir Nišević" wrote:
Based on discussion in https://issues.apache.org/jira/browse/ISIS-1358 I
think I've found an issue, but I cannot create new JIRA issue any more -
seems the issue creation po
Based on discussion in https://issues.apache.org/jira/browse/ISIS-1358 I
think I've found an issue, but I cannot create new JIRA issue any more -
seems the issue creation policy has been changed, so I am sending the issue
on this way.
*Steps to reproduce:*
1. Create archetype as described in guid
