Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: MOBI-Components
-
Labels:None
-
Environment:HideICEfaces4 trunk rev# 40043
Browsers: FF27, IE10, Chrome32 (behavior appears to be different for each browser?)
App server: Tomcat7.0.27
Test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/geolocationShowICEfaces4 trunk rev# 40043 Browsers: FF27, IE10, Chrome32 (behavior appears to be different for each browser?) App server: Tomcat7.0.27 Test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/geolocation
Description
http://localhost:8080/geolocation/geolocationAceTable.jsf
http://localhost:8080/geolocation/geolocationTable.jsf
http://localhost:8080/geolocation/geolocationRepeat.jsf
Only the geolocation component from the last table row is updated with location coordinates. This is not an issue in Firefox27.
2) Nested ace:dataTables (all browsers):
http://localhost:8080/geolocation/geolocationNestedAceTables.jsf
The geolocation components from the ace:dataTable inside the first row of the outside ace:dataTable fail to get locations - see attached screen shot.
This is not an issue for the geolocation component inside nested h:dataTables in Firefox27.
Also, warnings are visible in tomcat log:
Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)
Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)
Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)
Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)
Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)
3) Nested h:dataTables (Chrome32, IE10):
http://localhost:8080/geolocation/geolocationNestedTables.jsf
Only the geolocation component from the last row of the last nested h:dataTable displays the location coordinates. Not an issue in Firefox27.
Also the same warnings appear in tomcat log.
For this testing I enabled the browsers to always allow to track my location.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | Capture.PNG [ 16696 ] |
| Fix Version/s | 4.0 [ 11382 ] | |
| Fix Version/s | 4.0.BETA [ 10770 ] | |
| Assignee | Ted Goddard [ ted.goddard ] | |
| Affects Version/s | 4.0.BETA [ 10770 ] |
| Description |
1) Nested ace:dataTables (all browsers):
http://localhost:8080/geolocation/geolocationNestedAceTables.jsf The geolocation components from the ace:dataTable inside the first row of the outside ace:dataTable fail to get locations - see attached screen shot. This is not an issue for the geolocation component inside nested h:dataTables in Firefox27. Also, warnings are visible in tomcat log: Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) 2) Nested h:dataTables (Chrome32, IE10): http://localhost:8080/geolocation/geolocationNestedTables.jsf Only the geolocation component from the last row of the last nested h:dataTable displays the location coordinates. Not an issue in Firefox27. Also the same warnings appear in tomcat log. For this testing I enabled the browsers to always allow to track my location. |
1) Geolocation inside ace:dataTable or h:dataTable (Chrome32, IE10):
http://localhost:8080/geolocation/geolocationAceTable.jsf http://localhost:8080/geolocation/geolocationTable.jsf Only the geolocation component from the last table row is updated with location coordinates. This is not an issue in Firefox27. 2) Nested ace:dataTables (all browsers): http://localhost:8080/geolocation/geolocationNestedAceTables.jsf The geolocation components from the ace:dataTable inside the first row of the outside ace:dataTable fail to get locations - see attached screen shot. This is not an issue for the geolocation component inside nested h:dataTables in Firefox27. Also, warnings are visible in tomcat log: Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) 3) Nested h:dataTables (Chrome32, IE10): http://localhost:8080/geolocation/geolocationNestedTables.jsf Only the geolocation component from the last row of the last nested h:dataTable displays the location coordinates. Not an issue in Firefox27. Also the same warnings appear in tomcat log. For this testing I enabled the browsers to always allow to track my location. |
| Summary | mobi:geolocation inside nested dataTables fails to update location | mobi:geolocation inside dataTables fails to update location |
| Description |
1) Geolocation inside ace:dataTable or h:dataTable (Chrome32, IE10):
http://localhost:8080/geolocation/geolocationAceTable.jsf http://localhost:8080/geolocation/geolocationTable.jsf Only the geolocation component from the last table row is updated with location coordinates. This is not an issue in Firefox27. 2) Nested ace:dataTables (all browsers): http://localhost:8080/geolocation/geolocationNestedAceTables.jsf The geolocation components from the ace:dataTable inside the first row of the outside ace:dataTable fail to get locations - see attached screen shot. This is not an issue for the geolocation component inside nested h:dataTables in Firefox27. Also, warnings are visible in tomcat log: Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) 3) Nested h:dataTables (Chrome32, IE10): http://localhost:8080/geolocation/geolocationNestedTables.jsf Only the geolocation component from the last row of the last nested h:dataTable displays the location coordinates. Not an issue in Firefox27. Also the same warnings appear in tomcat log. For this testing I enabled the browsers to always allow to track my location. |
1) Geolocation inside ace:dataTable or h:dataTable or ui:repeat (Chrome32, IE10):
http://localhost:8080/geolocation/geolocationAceTable.jsf http://localhost:8080/geolocation/geolocationTable.jsf http://localhost:8080/geolocation/geolocationRepeat.jsf Only the geolocation component from the last table row is updated with location coordinates. This is not an issue in Firefox27. 2) Nested ace:dataTables (all browsers): http://localhost:8080/geolocation/geolocationNestedAceTables.jsf The geolocation components from the ace:dataTable inside the first row of the outside ace:dataTable fail to get locations - see attached screen shot. This is not an issue for the geolocation component inside nested h:dataTables in Firefox27. Also, warnings are visible in tomcat log: Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) Feb 20, 2014 8:13:46 AM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode WARNING: Empty Location string in GEOLocation upload (position not found yet?) 3) Nested h:dataTables (Chrome32, IE10): http://localhost:8080/geolocation/geolocationNestedTables.jsf Only the geolocation component from the last row of the last nested h:dataTable displays the location coordinates. Not an issue in Firefox27. Also the same warnings appear in tomcat log. For this testing I enabled the browsers to always allow to track my location. |
| Assignee | Ted Goddard [ ted.goddard ] | Arturo Zambrano [ artzambrano ] |
| Assignee Priority | P3 [ 10012 ] |
IF4 trunk rev# 40402:
An error is seen in tomcat terminal when testing geolocation inside h:dataTable/ace:dataTable/ui:repeat on iPhone4S/iOS7.1/Safari (error does not occur when testing on desktop browsers) :
Mar 25, 2014 3:16:48 PM org.icefaces.mobi.component.geolocation.GeolocationRenderer decode
WARNING: Error decoding geo-location request paramaters.
javax.el.PropertyNotFoundException: /geolocationTableBottom.xhtml @49,80 direction="#
": Property 'direction' not writable on type double
at com.sun.faces.facelets.el.TagValueExpression.setValue(TagValueExpression.java:133)
at org.icefaces.mobi.component.geolocation.GeolocationBase.setDirection(GeolocationBase.java:241)
at org.icefaces.mobi.component.geolocation.GeolocationRenderer.decode(GeolocationRenderer.java:90)
at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:831)
at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1225)
at javax.faces.component.UIData.iterate(UIData.java:2024)
at javax.faces.component.UIData.processDecodes(UIData.java:1176)
at javax.faces.component.UIForm.processDecodes(UIForm.java:225)
at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1220)
at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1220)
at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:929)
at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: javax.el.PropertyNotFoundException: Property 'direction' not writable on type double
at javax.el.BeanELResolver$BeanProperty.write(BeanELResolver.java:293)
at javax.el.BeanELResolver$BeanProperty.access$100(BeanELResolver.java:253)
at javax.el.BeanELResolver.setValue(BeanELResolver.java:140)
at com.sun.faces.el.DemuxCompositeELResolver._setValue(DemuxCompositeELResolver.java:255)
at com.sun.faces.el.DemuxCompositeELResolver.setValue(DemuxCompositeELResolver.java:281)
at org.apache.el.parser.AstValue.setValue(AstValue.java:204)
at org.apache.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:257)
at com.sun.faces.facelets.el.TagValueExpression.setValue(TagValueExpression.java:131)
... 30 more
| Fix Version/s | 4.1 [ 11375 ] | |
| Fix Version/s | 4.0 [ 11382 ] |
Tested with ICEfaces 4 trunk r43806. Tomcat 7, IE11, FF33, Chrome 39.
Issue 1 still failing in all browsers including FF.
Issue 2 still failing in all browsers including FF, however now only the last row from the last nested table is updated. Server warnings still seen.
Issue 3 still failing in all browsers including FF. Server warnings still seen.
Server warning from previous comment when testing with Safari on ios device still seen.
| Assignee Priority | P3 [ 10012 ] | |
| Fix Version/s | EE-4.1.0.GA [ 12171 ] | |
| Fix Version/s | 4.1 [ 11375 ] |
| Fix Version/s | 4.2 [ 12870 ] | |
| Fix Version/s | EE-4.1.0.GA [ 12171 ] |
| Assignee | Arturo Zambrano [ artzambrano ] | Ken Fyten [ ken.fyten ] |
| Fix Version/s | 4.2 [ 12870 ] |
Tested with ICEfaces 4 trunk r50737. All scenarios as reported above are still failing.
| Fix Version/s | EE-4.2.0.GA [ 13071 ] |
| Security | Private [ 10001 ] |
| Assignee | Ken Fyten [ ken.fyten ] | Arturo Zambrano [ artzambrano ] |
r51536: modified mobi:geolocation client-side code to support multiple instances of the component
Previously, it was assumed that there was going to be only once instance on the page.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #51536 | Tue May 16 15:48:53 MDT 2017 | art.zambrano | |
| Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/mobi/component/resources/org.icefaces.component.geolocation/geolocation.js
|
Verified ICEfaces 4 trunk r51548, tomcat 8, MS Edge, IE 11, 10, 9, 8, Chrome 57, FF 47, android 6.0.1, ios 10.2
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Similar warnings occur when clicking the "Locate" button on the Geolocation demo from showcase/showcase-mobile.jsf (IF4 trunk rev# 40049, FF27); location coordinates fail to update:
Feb 20, 2014 6:13:03 PM org.icefaces.mobi.component.geolocation.GeolocationRende
rer decode
WARNING: Empty Location string in GEOLocation upload (position not found yet?)