You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Stephen Cameron <st...@gmail.com> on 2015/11/17 12:43:40 UTC
Gmaps addon
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
Re: Gmaps addon
Posted by Stephen Cameron <st...@gmail.com>.
I can build a stand-alone 'jetty-console' jar and get an error there too.
In fact I get a stack trace in the client, which is different to the blank
map and calendar screen I see normally. Switching back to development mode
in the web.xml inside the jar makes this error disappear.
This is hitting a local MySQL database with a different set of data to the
test server. I need to create some fixtures and see an error with them
too. I will do that later. It would be nice to get to the bottom of it, but
as I said its not a high priority now.
- org.apache.wicket.WicketRuntimeException
- Method onRequest of interface
org.apache.wicket.behavior.IBehaviorListener targeted at
org.apache.wicket.ajax.markup.html.AjaxLink$1@4e01556f on component
[AjaxLink [Component id = viewLink]] threw an exception
- org.apache.wicket.RequestListenerInterface#internalInvoke(RequestListenerInterface.java:268)
- org.apache.wicket.RequestListenerInterface#invoke(RequestListenerInterface.java:241)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#invokeListener(ListenerInterfaceRequestHandler.java:250)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#respond(ListenerInterfaceRequestHandler.java:236)
- org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor#respond(RequestCycle.java:890)
- org.apache.wicket.request.RequestHandlerStack#execute(RequestHandlerStack.java:64)
- org.apache.wicket.request.cycle.RequestCycle#execute(RequestCycle.java:261)
- org.apache.wicket.request.cycle.RequestCycle#processRequest(RequestCycle.java:218)
- org.apache.wicket.request.cycle.RequestCycle#processRequestAndDetach(RequestCycle.java:289)
- org.apache.wicket.protocol.http.WicketFilter#processRequestCycle(WicketFilter.java:259)
- org.apache.wicket.protocol.http.WicketFilter#processRequest(WicketFilter.java:201)
- org.apache.wicket.protocol.http.WicketFilter#doFilter(WicketFilter.java:282)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.isis.core.webapp.diagnostics.IsisLogOnExceptionFilter#doFilter(IsisLogOnExceptionFilter.java:52)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.shiro.web.servlet.AbstractShiroFilter#executeChain(AbstractShiroFilter.java:449)
- org.apache.shiro.web.servlet.AbstractShiroFilter$1#call(AbstractShiroFilter.java:365)
- org.apache.shiro.subject.support.SubjectCallable#doCall(SubjectCallable.java:90)
- org.apache.shiro.subject.support.SubjectCallable#call(SubjectCallable.java:83)
- org.apache.shiro.subject.support.DelegatingSubject#execute(DelegatingSubject.java:383)
- org.apache.shiro.web.servlet.AbstractShiroFilter#doFilterInternal(AbstractShiroFilter.java:362)
- org.apache.shiro.web.servlet.OncePerRequestFilter#doFilter(OncePerRequestFilter.java:125)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.eclipse.jetty.servlet.ServletHandler#doHandle(ServletHandler.java:583)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:143)
- org.eclipse.jetty.security.SecurityHandler#handle(SecurityHandler.java:577)
- org.eclipse.jetty.server.session.SessionHandler#doHandle(SessionHandler.java:223)
- org.eclipse.jetty.server.handler.ContextHandler#doHandle(ContextHandler.java:1125)
- org.eclipse.jetty.servlet.ServletHandler#doScope(ServletHandler.java:515)
- org.eclipse.jetty.server.session.SessionHandler#doScope(SessionHandler.java:185)
- org.eclipse.jetty.server.handler.ContextHandler#doScope(ContextHandler.java:1059)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:141)
- org.eclipse.jetty.server.handler.ContextHandlerCollection#handle(ContextHandlerCollection.java:215)
- org.eclipse.jetty.server.handler.HandlerCollection#handle(HandlerCollection.java:110)
- org.eclipse.jetty.server.handler.HandlerWrapper#handle(HandlerWrapper.java:97)
- org.eclipse.jetty.server.Server#handle(Server.java:497)
- org.eclipse.jetty.server.HttpChannel#handle(HttpChannel.java:311)
- org.eclipse.jetty.server.HttpConnection#onFillable(HttpConnection.java:248)
- org.eclipse.jetty.io.AbstractConnection$2#run(AbstractConnection.java:540)
- org.eclipse.jetty.util.thread.QueuedThreadPool#runJob(QueuedThreadPool.java:610)
- org.eclipse.jetty.util.thread.QueuedThreadPool$3#run(QueuedThreadPool.java:539)
- java.lang.Thread#run(null:-1)
-
- Caused by:
-
- java.lang.reflect.InvocationTargetException
-
- sun.reflect.NativeMethodAccessorImpl#invoke0(null:-2)
- sun.reflect.NativeMethodAccessorImpl#invoke(null:-1)
- sun.reflect.DelegatingMethodAccessorImpl#invoke(null:-1)
- java.lang.reflect.Method#invoke(null:-1)
- org.apache.wicket.RequestListenerInterface#internalInvoke(RequestListenerInterface.java:258)
- org.apache.wicket.RequestListenerInterface#invoke(RequestListenerInterface.java:241)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#invokeListener(ListenerInterfaceRequestHandler.java:250)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#respond(ListenerInterfaceRequestHandler.java:236)
- org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor#respond(RequestCycle.java:890)
- org.apache.wicket.request.RequestHandlerStack#execute(RequestHandlerStack.java:64)
- org.apache.wicket.request.cycle.RequestCycle#execute(RequestCycle.java:261)
- org.apache.wicket.request.cycle.RequestCycle#processRequest(RequestCycle.java:218)
- org.apache.wicket.request.cycle.RequestCycle#processRequestAndDetach(RequestCycle.java:289)
- org.apache.wicket.protocol.http.WicketFilter#processRequestCycle(WicketFilter.java:259)
- org.apache.wicket.protocol.http.WicketFilter#processRequest(WicketFilter.java:201)
- org.apache.wicket.protocol.http.WicketFilter#doFilter(WicketFilter.java:282)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.isis.core.webapp.diagnostics.IsisLogOnExceptionFilter#doFilter(IsisLogOnExceptionFilter.java:52)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.shiro.web.servlet.AbstractShiroFilter#executeChain(AbstractShiroFilter.java:449)
- org.apache.shiro.web.servlet.AbstractShiroFilter$1#call(AbstractShiroFilter.java:365)
- org.apache.shiro.subject.support.SubjectCallable#doCall(SubjectCallable.java:90)
- org.apache.shiro.subject.support.SubjectCallable#call(SubjectCallable.java:83)
- org.apache.shiro.subject.support.DelegatingSubject#execute(DelegatingSubject.java:383)
- org.apache.shiro.web.servlet.AbstractShiroFilter#doFilterInternal(AbstractShiroFilter.java:362)
- org.apache.shiro.web.servlet.OncePerRequestFilter#doFilter(OncePerRequestFilter.java:125)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.eclipse.jetty.servlet.ServletHandler#doHandle(ServletHandler.java:583)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:143)
- org.eclipse.jetty.security.SecurityHandler#handle(SecurityHandler.java:577)
- org.eclipse.jetty.server.session.SessionHandler#doHandle(SessionHandler.java:223)
- org.eclipse.jetty.server.handler.ContextHandler#doHandle(ContextHandler.java:1125)
- org.eclipse.jetty.servlet.ServletHandler#doScope(ServletHandler.java:515)
- org.eclipse.jetty.server.session.SessionHandler#doScope(SessionHandler.java:185)
- org.eclipse.jetty.server.handler.ContextHandler#doScope(ContextHandler.java:1059)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:141)
- org.eclipse.jetty.server.handler.ContextHandlerCollection#handle(ContextHandlerCollection.java:215)
- org.eclipse.jetty.server.handler.HandlerCollection#handle(HandlerCollection.java:110)
- org.eclipse.jetty.server.handler.HandlerWrapper#handle(HandlerWrapper.java:97)
- org.eclipse.jetty.server.Server#handle(Server.java:497)
- org.eclipse.jetty.server.HttpChannel#handle(HttpChannel.java:311)
- org.eclipse.jetty.server.HttpConnection#onFillable(HttpConnection.java:248)
- org.eclipse.jetty.io.AbstractConnection$2#run(AbstractConnection.java:540)
- org.eclipse.jetty.util.thread.QueuedThreadPool#runJob(QueuedThreadPool.java:610)
- org.eclipse.jetty.util.thread.QueuedThreadPool$3#run(QueuedThreadPool.java:539)
- java.lang.Thread#run(null:-1)
-
- Caused by:
-
- java.lang.NullPointerException
-
- org.isisaddons.wicket.fullcalendar2.cpt.ui.EventProviderAbstract$1#apply(EventProviderAbstract.java:104)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.EventProviderAbstract$1#apply(EventProviderAbstract.java:83)
- com.google.common.collect.Iterators$8#transform(Iterators.java:794)
- com.google.common.collect.TransformedIterator#next(TransformedIterator.java:48)
- com.google.common.collect.Iterators$7#computeNext(Iterators.java:646)
- com.google.common.collect.AbstractIterator#tryToComputeNext(AbstractIterator.java:143)
- com.google.common.collect.AbstractIterator#hasNext(AbstractIterator.java:138)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.EventProviderAbstract#createEvents(EventProviderAbstract.java:62)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.EventProviderAbstract#<init>(EventProviderAbstract.java:55)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.CalendarEventableEventProvider#<init>(CalendarEventableEventProvider.java:35)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.CalendarEventableCollectionAsFullCalendar2#newEventProvider(CalendarEventableCollectionAsFullCalendar2.java:42)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.CalendaredCollectionAbstract#buildGui(CalendaredCollectionAbstract.java:78)
- org.isisaddons.wicket.fullcalendar2.cpt.ui.CalendaredCollectionAbstract#onModelChanged(CalendaredCollectionAbstract.java:109)
- org.apache.wicket.Component#modelChanged(Component.java:2166)
- org.apache.wicket.Component#setDefaultModel(Component.java:2972)
- org.apache.wicket.MarkupContainer#setDefaultModel(MarkupContainer.java:759)
- org.apache.wicket.MarkupContainer#setDefaultModel(MarkupContainer.java:98)
- org.apache.isis.viewer.wicket.ui.components.collectioncontents.multiple.CollectionContentsMultipleViewsPanel#onEvent(CollectionContentsMultipleViewsPanel.java:168)
- org.apache.wicket.settings.def.FrameworkSettings#dispatchEvent(FrameworkSettings.java:132)
- org.apache.wicket.ComponentEventSender#dispatchToComponent(ComponentEventSender.java:282)
- org.apache.wicket.ComponentEventSender#access$100(ComponentEventSender.java:36)
- org.apache.wicket.ComponentEventSender$ComponentEventVisitor#component(ComponentEventSender.java:329)
- org.apache.wicket.ComponentEventSender$ComponentEventVisitor#component(ComponentEventSender.java:306)
- org.apache.wicket.util.visit.Visits#visitChildren(Visits.java:144)
- org.apache.wicket.util.visit.Visits#visitChildren(Visits.java:162)
- org.apache.wicket.util.visit.Visits#visitChildren(Visits.java:162)
- org.apache.wicket.util.visit.Visits#visitChildren(Visits.java:123)
- org.apache.wicket.util.visit.Visits#visitChildren(Visits.java:192)
- org.apache.wicket.MarkupContainer#visitChildren(MarkupContainer.java:875)
- org.apache.wicket.ComponentEventSender#breadth(ComponentEventSender.java:160)
- org.apache.wicket.ComponentEventSender#send(ComponentEventSender.java:68)
- org.apache.wicket.Component#send(Component.java:4451)
- org.apache.isis.viewer.wicket.ui.pages.PageAbstract#onEvent(PageAbstract.java:410)
- org.apache.wicket.settings.def.FrameworkSettings#dispatchEvent(FrameworkSettings.java:132)
- org.apache.wicket.ComponentEventSender#dispatchToComponent(ComponentEventSender.java:282)
- org.apache.wicket.ComponentEventSender#exact(ComponentEventSender.java:94)
- org.apache.wicket.ComponentEventSender#send(ComponentEventSender.java:74)
- org.apache.wicket.Component#send(Component.java:4451)
- org.apache.isis.viewer.wicket.ui.components.collection.selector.CollectionSelectorPanel#setViewHintAndBroadcast(CollectionSelectorPanel.java:208)
- org.apache.isis.viewer.wicket.ui.components.collection.selector.CollectionSelectorPanel$1$1#onClick(CollectionSelectorPanel.java:130)
- org.apache.wicket.ajax.markup.html.AjaxLink$1#onEvent(AjaxLink.java:86)
- org.apache.wicket.ajax.AjaxEventBehavior#respond(AjaxEventBehavior.java:146)
- org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#onRequest(AbstractDefaultAjaxBehavior.java:641)
- sun.reflect.NativeMethodAccessorImpl#invoke0(null:-2)
- sun.reflect.NativeMethodAccessorImpl#invoke(null:-1)
- sun.reflect.DelegatingMethodAccessorImpl#invoke(null:-1)
- java.lang.reflect.Method#invoke(null:-1)
- org.apache.wicket.RequestListenerInterface#internalInvoke(RequestListenerInterface.java:258)
- org.apache.wicket.RequestListenerInterface#invoke(RequestListenerInterface.java:241)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#invokeListener(ListenerInterfaceRequestHandler.java:250)
- org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler#respond(ListenerInterfaceRequestHandler.java:236)
- org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor#respond(RequestCycle.java:890)
- org.apache.wicket.request.RequestHandlerStack#execute(RequestHandlerStack.java:64)
- org.apache.wicket.request.cycle.RequestCycle#execute(RequestCycle.java:261)
- org.apache.wicket.request.cycle.RequestCycle#processRequest(RequestCycle.java:218)
- org.apache.wicket.request.cycle.RequestCycle#processRequestAndDetach(RequestCycle.java:289)
- org.apache.wicket.protocol.http.WicketFilter#processRequestCycle(WicketFilter.java:259)
- org.apache.wicket.protocol.http.WicketFilter#processRequest(WicketFilter.java:201)
- org.apache.wicket.protocol.http.WicketFilter#doFilter(WicketFilter.java:282)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.isis.core.webapp.diagnostics.IsisLogOnExceptionFilter#doFilter(IsisLogOnExceptionFilter.java:52)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.apache.shiro.web.servlet.AbstractShiroFilter#executeChain(AbstractShiroFilter.java:449)
- org.apache.shiro.web.servlet.AbstractShiroFilter$1#call(AbstractShiroFilter.java:365)
- org.apache.shiro.subject.support.SubjectCallable#doCall(SubjectCallable.java:90)
- org.apache.shiro.subject.support.SubjectCallable#call(SubjectCallable.java:83)
- org.apache.shiro.subject.support.DelegatingSubject#execute(DelegatingSubject.java:383)
- org.apache.shiro.web.servlet.AbstractShiroFilter#doFilterInternal(AbstractShiroFilter.java:362)
- org.apache.shiro.web.servlet.OncePerRequestFilter#doFilter(OncePerRequestFilter.java:125)
- org.eclipse.jetty.servlet.ServletHandler$CachedChain#doFilter(ServletHandler.java:1650)
- org.eclipse.jetty.servlet.ServletHandler#doHandle(ServletHandler.java:583)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:143)
- org.eclipse.jetty.security.SecurityHandler#handle(SecurityHandler.java:577)
- org.eclipse.jetty.server.session.SessionHandler#doHandle(SessionHandler.java:223)
- org.eclipse.jetty.server.handler.ContextHandler#doHandle(ContextHandler.java:1125)
- org.eclipse.jetty.servlet.ServletHandler#doScope(ServletHandler.java:515)
- org.eclipse.jetty.server.session.SessionHandler#doScope(SessionHandler.java:185)
- org.eclipse.jetty.server.handler.ContextHandler#doScope(ContextHandler.java:1059)
- org.eclipse.jetty.server.handler.ScopedHandler#handle(ScopedHandler.java:141)
- org.eclipse.jetty.server.handler.ContextHandlerCollection#handle(ContextHandlerCollection.java:215)
- org.eclipse.jetty.server.handler.HandlerCollection#handle(HandlerCollection.java:110)
- org.eclipse.jetty.server.handler.HandlerWrapper#handle(HandlerWrapper.java:97)
- org.eclipse.jetty.server.Server#handle(Server.java:497)
- org.eclipse.jetty.server.HttpChannel#handle(HttpChannel.java:311)
- org.eclipse.jetty.server.HttpConnection#onFillable(HttpConnection.java:248)
- org.eclipse.jetty.io.AbstractConnection$2#run(AbstractConnection.java:540)
- org.eclipse.jetty.util.thread.QueuedThreadPool#runJob(QueuedThreadPool.java:610)
- org.eclipse.jetty.util.thread.QueuedThreadPool$3#run(QueuedThreadPool.java:539)
- java.lang.Thread#run(null:-1)
Powered by:
- Apache Isis ™ <http://isis.apache.org>
- About
<http://localhost:8080/wicket/wicket/bookmarkable/org.apache.isis.viewer.wicket.ui.pages.about.AboutPage>
On Wed, Dec 30, 2015 at 9:19 AM, Stephen Cameron <steve.cameron.62@gmail.com
> wrote:
> Hi Dan,
>
> I checked it on a test server (Tomcat8 on Amazon EC2) and cannot reproduce
> it there, but its still a problem on my dev laptop, using jetty to run it
> via maven jetty:run goal fro Eclipse.
>
> I am using 1.11.0-SNAPSHOT. I get same result with FF, IE and Chrome.
>
> If no one else is reporting a problem, and its working in test for me now,
> then its very low priority obviously. I will try to get more details on
> what is happening differently in my dev scenario.
>
> Thanks
>
> On Tue, Dec 29, 2015 at 2:13 AM, Dan Haywood <dan@haywood-associates.co.uk
> > wrote:
>
>> 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 <steve.cameron.62@gmail.com
>> >
>> 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 <
>> dan@haywood-associates.co.uk
>> > >
>> > wrote:
>> >
>> > > Interesting. OK, then, will look at that first.
>> > >
>> > > On 17 November 2015 at 20:30, Stephen Cameron <
>> > steve.cameron.62@gmail.com>
>> > > 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 <
>> > > > steve.cameron.62@gmail.com> 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
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: Gmaps addon
Posted by Stephen Cameron <st...@gmail.com>.
Hi Dan,
I checked it on a test server (Tomcat8 on Amazon EC2) and cannot reproduce
it there, but its still a problem on my dev laptop, using jetty to run it
via maven jetty:run goal fro Eclipse.
I am using 1.11.0-SNAPSHOT. I get same result with FF, IE and Chrome.
If no one else is reporting a problem, and its working in test for me now,
then its very low priority obviously. I will try to get more details on
what is happening differently in my dev scenario.
Thanks
On Tue, Dec 29, 2015 at 2:13 AM, Dan Haywood <da...@haywood-associates.co.uk>
wrote:
> 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 <st...@gmail.com>
> 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 <
> dan@haywood-associates.co.uk
> > >
> > wrote:
> >
> > > Interesting. OK, then, will look at that first.
> > >
> > > On 17 November 2015 at 20:30, Stephen Cameron <
> > steve.cameron.62@gmail.com>
> > > 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 <
> > > > steve.cameron.62@gmail.com> 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
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Gmaps addon
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
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 <st...@gmail.com>
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 <dan@haywood-associates.co.uk
> >
> wrote:
>
> > Interesting. OK, then, will look at that first.
> >
> > On 17 November 2015 at 20:30, Stephen Cameron <
> steve.cameron.62@gmail.com>
> > 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 <
> > > steve.cameron.62@gmail.com> 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
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
Re: Gmaps addon
Posted by Stephen Cameron <st...@gmail.com>.
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 <da...@haywood-associates.co.uk>
wrote:
> Interesting. OK, then, will look at that first.
>
> On 17 November 2015 at 20:30, Stephen Cameron <st...@gmail.com>
> 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 <
> > steve.cameron.62@gmail.com> 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
> > >
> > >
> > >
> > >
> > >
> >
>
Re: Gmaps addon
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Interesting. OK, then, will look at that first.
On 17 November 2015 at 20:30, Stephen Cameron <st...@gmail.com>
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 <
> steve.cameron.62@gmail.com> 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
> >
> >
> >
> >
> >
>
Re: Gmaps addon
Posted by Stephen Cameron <st...@gmail.com>.
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.62@gmail.com> 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
>
>
>
>
>
Re: Gmaps addon
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Thanks for this, Steve, will take a look.
On 17 November 2015 at 11:43, Stephen Cameron <st...@gmail.com>
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
>