Was just taking a look at this, but I'm afraid I cannot reproduce.

I'm running the app in deployment (server) mode using
org.apache.isis.WebServer -t SERVER ... this flag overrides the
<configuration> parameter in web.xml.

Seems to render ok for 1.10.0 and 1.11.0-SNAPSHOT in Chrome, Firefox and
Edge.

Admittedly I haven't deployed as regular webapp, eg using tomcat, but
running with -t SERVER flag is/should be equivalent.

Perhaps you could outline in more detail how to reproduce the problem?

Thx
Dan


On 17 November 2015 at 20:34, Stephen Cameron <[email protected]>
wrote:

> 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 <[email protected]
> >
> wrote:
>
> > Interesting.  OK, then, will look at that first.
> >
> > On 17 November 2015 at 20:30, Stephen Cameron <
> [email protected]>
> > 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 appearance
> > of
> > > the whole page.
> > >
> > >
> > >
> > > On Tue, Nov 17, 2015 at 10:43 PM, Stephen Cameron <
> > > [email protected]> 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 render.
> > > >
> > > > This was what the setting was in my 1.9.0 version where the maps did
> > > > appear, so that seems to be a regression sorry to say.
> > > >
> > > > I cannot confirm its affected the calendar component too, as I have
> > > > another exception appearing there, which might be due to another
> error
> > on
> > > > my part maybe, but before there was nothing rendering at all, so
> > similar
> > > to
> > > > the maps.
> > > >
> > > >
> > > > Regards
> > > > Steve
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Reply via email to