Plugin: Web UI for v7

[Taddeusz]

Please bear with me. I'm new to Java EE development.

Is there documentation somewhere to get the development environment set up? I have the JDK, Eclipse, and Tomcat set up. I'm getting IDE errors relating to servlets as well as the SageApi. There doesn't seem to be a Targeted Runtime option in the project properties or am I barking up the wrong tree with Tomcat?

[Taddeusz]

Never mind, figured it out. Less of a n00b now.

[jreichen]

No problem. For anyone who comes along later... Tomcat is not needed. Jetty is the web server. You also need to copy the Sage jar file from your SageTV installation into the classpath in your IDE.

[Taddeusz]

Yeah, I figured out that I had to create the SAGE_JAR and SAGELIB variables.

[Taddeusz]

For anyone who is interested here is the css fix for the squared corners on hover over epg cells. Quite annoying looking when the corner radius gets all screwed up just by hovering over something. Works on IE, Edge, Chrome, and Firefox.

Just remove the .txt from the end and replace the file in the jetty folder structure and in the war file.

Edited: Forgive me. I noticed a bug in search results that caused the same issue. Now corrected the apparent redundancy in the css that was causing issue.

[Taddeusz]

I have a question. I'm trying to build/export the webserver JAR file. When I try to use the webserver.jardesc it says the main class is not valid. It doesn't like net.sf.sageplugins.webserver.Version. It says it's not included or does not have a main method.

What could I be doing wrong?

[troycheek]

I was using a program that used wget to obtain information from the Web UI running on my SageTV server called media-pc. Something like this:

wget "http://sage:frey@media-pc:8080/sage/Recordings?xml=yes" -O test.xml

In the past, even something like getting all the information for all the currently stored recorded shows took just a few seconds (even though that's 7 MB of information!). Recently, however, each query started taking more than a minute to complete. I stepped through the process manually and found that the delay was that wget (or Windows 7 or my router or the DNS server or something) was resolving "media-pc" to its IPv6 address as well as the IPv4 address. wget couldn't actually connect to this IPv6 address for whatever reason, so after a minute or so it would fall back to the IPv4 address, connect to that, and get the requested information. I "solved" the problem by adding the "-4" parameter to the wget command line like this:

wget -4 "http://sage:frey@media-pc:8080/sage/Recordings?xml=yes" -O test.xml

This tells wget to try to connect to the IPv4 address first, I assume. Just thought I'd pass that along in case anybody else had that problem.

Minor bug report/feature request: The WebUI's XML results returned above do not include information about which tuner encoded any particular recording. I think I've figured out how to scrape that information from one of the html pages. Still working on it. (Useful information if you have automated file conversions set up with different parameters depending on the encoder.)

The WebUI and wget are a powerful combination for anybody who wants to get information from Wiz.bin or otherwise interact with SageTV and has no idea how to use the Sage API(s) actually intended for this purpose.

[fidget]

I had everything working fine with Sage 7, running in Windows 7 with Java 8. When I updated the PC to Windows 10, I can no longer get a page back when I connect to Sage. There is no error in the web browser and I don't see any new errors in the log file. Does anyone have this working in Windows 10?

[wayner]

I am betting it is a Java issue - have you tried rolling back to 7?

[fidget]

Originally Posted by wayner

I am betting it is a Java issue - have you tried rolling back to 7?

Since that version has reached end of life, I'd rather not do that. I may do some mucking around with the firewall. I remember seeing it pop-up some warnings with Plex after the update.

[wayner]

The Windows installer for SageTV V9 that jusjoken is working on explicitly installs Java 7. If I remember correctly I believe the issue is that version of Jetty used with the web server doesn't work with Java 8.

[fidget]

Originally Posted by wayner

The Windows installer for SageTV V9 that jusjoken is working on explicitly installs Java 7. If I remember correctly I believe the issue is that version of Jetty used with the web server doesn't work with Java 8.

That is very strange, since the web server had been working with Jave 8 until I upgraded from Win 7 to 10. I'll let you know if I am able to get it working.

I am holding off updating to SageTV 9 for now. Once it gets a bit more stable, I'll move over.

[Monedeath]

Originally Posted by wayner

The Windows installer for SageTV V9 that jusjoken is working on explicitly installs Java 7. If I remember correctly I believe the issue is that version of Jetty used with the web server doesn't work with Java 8.

It works for some without issue, it is "quirky" for a few others, most other users seem to only encounter pain when they try it with Java8. So based on feedback from other posters, I will no longer claim it won't work with v8, it might. But the typical experience is it usually doesn't.

[Fuzzy]

Originally Posted by Monedeath

It works for some without issue, it is "quirky" for a few others, most other users seem to only encounter pain when they try it with Java8. So based on feedback from other posters, I will no longer claim it won't work with v8, it might. But the typical experience is it usually doesn't.

I honestly don't think anyone has even tried to track down specifically what part of the web interface breaks with java 8, just that it does - the general consensus seems to be that it's better to simply move the (or more accurately, create a whole new) web interface to the current version of Jetty, fully compatible with Java 8. Not sure if/when that will happen, and for now, it is recommended to use Java 7 for the server. MOST people run their server as a headless, or rarely interacted with appliance, in which case, an old version of java really shouldn't make any sort of difference.

[MattHelm]

I had a machine act weird on me when updating to 10. Had to reinstall VS2015, I think. I also added the web server to someones machine the other day, and SageTV stopped, but then started again. I forget what he needed to do to get it running. Will ask at lunch.

[MattHelm]

OK, ask my friend, and he did have to roll back to JAVA 7 to get the web interface running under Windows 10. All my servers still use 1.7.

[fidget]

I discovered that Win 10 installs an HTTP service. In order to free up port 80, I had to do the following from an administrator command prompt:

net stop http /y

Once that was done, Sage was able to create the server connection.

[wayner]

Originally Posted by fidget

I discovered that Win 10 installs an HTTP service. In order to free up port 80, I had to do the following from an administrator command prompt:

net stop http /y

Once that was done, Sage was able to create the server connection.

I don't see a service called http running on my Win 10 PCs - I have generally run all of my Sage/Jetty stuff through port 8080.

[fidget]

Originally Posted by wayner

I don't see a service called http running on my Win 10 PCs - I have generally run all of my Sage/Jetty stuff through port 8080.

Try this:
- Shut down Sage
- Open a command prompt with administrator privileges.
- From the command prompt, type 'netstat-a' and look to see if a process is using your desired port. I had a process listening on port 80.

With my current Sage,configuration, I am able to run Java 8 and still have the SageTV web server work correctly.

[Taddeusz]

I've noticed with the latest version of Chrome, v48, that the menus no longer open when hovered over. You must now click to open the menus. At least they still work. Just noticed the change in behavior.