I did set the isis version to 1.10.0 in that demos parent project, not
1.11.0-SNAPSHOT as it is in the repository, in case that matters.
On Wed, Nov 18, 2015 at 7:31 AM, Dan Haywood
wrote:
> Interesting. OK, then, will look at that first.
>
> On 17 November 2015 at 20:30, Stephen Cameron
> wro
Interesting. OK, then, will look at that first.
On 17 November 2015 at 20:30, Stephen Cameron
wrote:
> Same thing happens in the gmaps addon demo. I tried setting the switch
> isis.viewer.wicket.stripWicketTags=false in the file
> viewer_wicket.properties to compensate but that affected the a
Same thing happens in the gmaps addon demo. I tried setting the switch
isis.viewer.wicket.stripWicketTags=false in the file
viewer_wicket.properties to compensate but that affected the appearance of
the whole page.
On Tue, Nov 17, 2015 at 10:43 PM, Stephen Cameron <
steve.cameron...@gmail.com>
Thanks for this, Steve, will take a look.
On 17 November 2015 at 11:43, Stephen Cameron
wrote:
> Hi,
>
> I found an explanation for the missing Google maps after migrating to
> 1.10.0, which was that if the 'configuration' context-param in web.xml is
> 'deployment' then then the maps don't rend
Hi,
I found an explanation for the missing Google maps after migrating to
1.10.0, which was that if the 'configuration' context-param in web.xml is
'deployment' then then the maps don't render.
This was what the setting was in my 1.9.0 version where the maps did
appear, so that seems to be a regr
Hi Dan,
thx a lot, the resource bundle approach worked just fine for me.
I created a folder structure inside the webapp resource folder following that
pattern org.apache.isis.viewer.wicket.ui.components.actions. Inside there I
could override the properties via an equivalent
ActionParametersFo
