This might be caused by this ISIS-288
<https://issues.apache.org/jira/browse/ISIS-288>, where properties
specified are not always applied and so won't override defaults. It
could be that this setting you expect is just being ignored. In the case
I had, I had to override the boot strapped class to make it work.
I have fixed the problem, but due to being poorly over the weekend I
haven't push up that work in time for the release.
Regards
Rob
On 12/15/12 17:07, Adam Howard wrote:
I started a project from the 0.2.0-incubating quickstart archetype and then
upgraded the Isis version to 0.3.1-incubating-SNAPSHOT. Everything still
worked fine.
Then I took a few months off and now I've come back to it. I updated the
dependencies and started the webapp.
Navigating to http://localhost:8080 gives me the RO home page. I can click
on the services link and I see my repositories. I then click on one of my
repositories and I get it's description but it has no members, meaning no
actions.
I did some poking around and found that the 0.2.0 archetype did not set a
deploymentType context-param in web.xml. I added
<context-param>
<param-name>deploymentType</param-name>
<param-value>SERVER_EXPLORATION</param-value>
</context-param>
and the actions returned to the repository representation. This also
happens in 0.3.1-SNAPSHOT.
There should probably be some sort of warning if the user fails to set this
parameter if it's required.
Adam
