[
https://issues.apache.org/jira/browse/EDGENT-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere closed EDGENT-249.
----------------------------------
Resolution: Cannot Reproduce
I'm not seeing an exception with current Edgent code (~v1.1.0) and a trivial
sample app.
A browser on OSX pointed at the console's port on the Pi works great;
everything renders fine.
However when I started a browser on the Pi, several things didn't render.
I'm closing this "NPE" defect. I've created EDGENT-392 to track the
rendering-on-Pi issue.
> DevelopmentProvider on PI gets NPE
> ----------------------------------
>
> Key: EDGENT-249
> URL: https://issues.apache.org/jira/browse/EDGENT-249
> Project: Edgent
> Issue Type: Bug
> Components: Console, Runtime
> Reporter: Dale LaBossiere
>
> A user contacted me about a NPE they were getting when starting an app that
> uses the DevelopmentProvider on a Raspberry PI. The code runs fine on a
> non-PI system. They said it was a vintage 24Aug copy of the code.
> The NPE was occurring in ServerUtil.getTopDirFilePath() on the line:
> return jarFile.getParentFile().getParentFile().getParentFile();
> Don't know what ServerUtil.getPath() is returning on the PI but it didn't
> satisfy the expectations above. They were going to try to get me additional
> output (the path returned by getPath()) but I haven't heard back yet.
> The edgent java8 release image was installed on the PI as demonstrated by the
> successful workaround I was able to give them to get them going:
> Workaround: add a JVM system property when you launch your app:
> -Dedgent.test.top.dir.file.path=<root-of-the-edgent-java8-dir>
> e.g.,
> -Dedgent.test.top.dir.file.path=/edgent/java8
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
