Plugin: Web UI for v7

[jreichen]

Originally Posted by Naylia

Thanks, that worked. Just had to tweak the instructions a bit. Looking at the context.xml for Nielm's web server it showed that it wanted the mime.types folder in the SageTV/webserver folder instead of in SageTV/jetty/users.

Glad it's working for you. The one in jetty/users will always be picked up. The setting you see in nielm's context xml additionally includes the legacy file for backward compatibility.

I'll see if I can fix that area of code in RssServlet to be more robust.

[jreichen]

Originally Posted by rrhorer

There may be some confusion on what a duplicate jar is. In my case, the file names, although not exact duplicates (they had different version numbering within the file names) were causing the problem as described. I removed all "functional" duplicates, refering to the install date for additional confirmation. It worked fine after removing these files.

Yeah that's informal shorthand for "different jars that have Java classes of the same name". I understand how users wouldn't understand the shorthand.

I'm curious what directions you followed that left you with duplicate jars so I can hopefully clear that up. The "Upgrading Jetty to Sage v7" thread, although admittedly more technical than a typical user would be interested in, mentions you need to either uninstall Jetty or upgrade to 1.6 before using the plugin manager to install/upgrade Jetty. The wiki does not mention this yet so maybe that's where the gap is.

[rrhorer]

Originally Posted by jreichen

I'm curious what directions you followed that left you with duplicate jars so I can hopefully clear that up. The "Upgrading Jetty to Sage v7" thread, although admittedly more technical than a typical user would be interested in, mentions you need to either uninstall Jetty or upgrade to 1.6 before using the plugin manager to install/upgrade Jetty. The wiki does not mention this yet so maybe that's where the gap is.

Sorry for not responding sooner -- I know work should not be an excuse for not doing the things we really like. Anyway, since I will be re-installing everything from scratch with a new OS (Win 7), I plunged ahead without taking the time to carefully read the instructions or check on my previous version, which I believed to be 1.6. Also, it may not have been running when I installed the V7 plugin for Jetty as a dependency to BMT's WEB UI (i.e., I installed the WEB UI and got Jetty with it.). This auto install feature may have the effect of sidestepping your instructions for migrating from 1.6 to a Sage V7 install. Hope this lengthy explanation helps.

[TR3 Driver]

I have installed the Jetty Web Server 2.0 and have everything working with the exception of the Web UI. When I select it I get the following error

HTTP ERROR 500

Problem accessing /sage/Home. Reason:

net/sf/sageplugins/sagexmlinfo/SageXmlWriter

Any ideas on what might be going on?

Regards.

[jreichen]

I'm not sure. Can you provide a log file? Enable SageTV's debug log and set Jetty's log level to VERBOSE in the plugin's config properties, then restart Sage and make the problem happen again.

[DRB]

http://yourserver:yourport/sage

Don't seem to work for me. I get "${error}" in red. When I drop the /sage I then get a genenic H2 loggin screen. Not sure how to use that.

DRB

[jreichen]

Can you provide some log files for me? Instructions are in my previous post.

[bikesquid]

Originally Posted by TR3 Driver

I have installed the Jetty Web Server 2.0 and have everything working with the exception of the Web UI. When I select it I get the following error

Any ideas on what might be going on?

Regards.

Same problem here. Any solution? I could swear that after upping to v7 it worked... I think....

[stuckless]

2 reasons that I've seen so far, that can affect the web ui during an upgrade....

1. still have the old sagex.api.jar in the JARs folder (can be solved by running the bmt jar cleaner tool)
2. have the xerces.jar in the JARs folder (will not be fixed using the bmt jar cleaning tool, you'll need to manually remove it)

If you've upgraded, then I'd strongly check your JARs directory, and clean out the duplicate jars... but be careful, because you need to clean the right jars.

[bikesquid]

Have run the cleanup tool already, which was great.... Only sage-api.jar left, and nothing resembling xerces.jar in the folder. Any other ideas?
Thx.

[jreichen]

Nobody has provided me with logs and I really can't do anything without them. If you can, please post your logs. Instructions are in post 25 above.

[bikesquid]

Here's the log, let me know if there's anything else that would help.
Attachment 10459

[stuckless]

Originally Posted by bikesquid

Here's the log, let me know if there's anything else that would help.
Attachment 10459

You have xerces.jar in your classpath.

Thu 6/10 12:38:53.924 classpath=C:\Program Files (x86)\SageTV\SageTV\Sage.jar;C:\Program Files (x86)\SageTV\SageTV\xerces.jar;C:\Program Files (x86)\SageTV\SageTV\plugin.jar;C:\Program Files (x86)\SageTV\SageTV\;.;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip;JARs\ant-1.6.5.jar;JARs\commons-codec-1.3.jar;JARs\commons-dbutils-1.3.jar;JARs\commons-io-1.4.jar;JARs\commons-jxpath-1.1.jar;JARs\commons-lang-2.4.jar;JARs\commons-logging-1.1.1.jar;JARs\commons-logging-api-1.1.1.jar;JARs\commons-net-1.4.1.jar;JARs\core-3.1.1.jar;JARs\df_sageutils.jar;JARs\gkusnick.sagetv.jar;JARs\h2-1.2.135.jar;JARs\htmlparser-1.6.jar;JARs\jcifs-1.1.6.jar;JARs\jdic.jar;JARs\jetty-6.1.19.jar;JARs\jetty-ajp-6.1.19.jar;JARs\jetty-rewrite-handler-6.1.19.jar;JARs\jetty-sslengine-6.1.19.jar;JARs\jetty-starter.jar;JARs\jetty-util-6.1.19.jar;JARs\json.jar;JARs\jsp-2.1-jetty-6.1.19.jar;JARs\jsp-2.1.jar;JARs\jsp-api-2.1.jar;JARs\log4j-1.2.15.jar;JARs\lucene-core-2.4.1.jar;JARs\metadata-updater.jar;JARs\nielm_sageutls.jar;JARs\nielm_sagewebserver.jar;JARs\nielm_sagexmlinfo.jar;JARs\phoenix.jar;JARs\sagemc.jar;JARs\sageortus.jar;JARs\sagex-api.jar;JARs\sagex-h2.jar;JARs\sbbi-upnplib-1.0.3.jar;JARs\servlet-api-2.5-6.1.19.jar;JARs\servlet.jar;JARs\sqlitejdbc-v056.jar;JARs\vecmath.jar

[bikesquid]

ok, I'm not sure what to do about that... the file doesn't exist either where indicated in the classpath or anywhere else according to a harddisk search.

What can I do?

[robogeek]

Originally Posted by bikesquid

Here's the log, let me know if there's anything else that would help.
Attachment 10459

Looks like you have the old SageTV Web Server by nielm still installed. Try shutting down SageTV (or SageTVService if runinng in service mode), move the nielm_sagewebserver.jar out of the JARs directory, restart SageTV, and retest the web server address. There may also be a runnable class that you added to the SageTV properties file when installing the old nielm web server. If you did, you should probably remove that from the properties file (when SageTV is shutdown)...probably won't hurt anything if you leave it there, but I like to clean up old installs by undoing all changes made during the original installation.

The new plugin system should prevent these things from happening in the future. So, once people get past these minor glitches from their manually installed plugins from pre-V7 SageTV, plugin installs and upgrades should go much smoother

[bikesquid]

Originally Posted by robogeek

Looks like you have the old SageTV Web Server by nielm still installed. Try shutting down SageTV (or SageTVService if runinng in service mode), move the nielm_sagewebserver.jar out of the JARs directory, restart SageTV, and retest the web server address. There may also be a runnable class that you added to the SageTV properties file when installing the old nielm web server. If you did, you should probably remove that from the properties file (when SageTV is shutdown)...probably won't hurt anything if you leave it there, but I like to clean up old installs by undoing all changes made during the original installation.

Thanks for the suggestion, I moved the nielm_sagewebserver.jar out and made sure I didn't have the startup runnable class edit in the properties file, restarted and still getting the same error:
HTTP ERROR: 404

Problem accessing /Sage/Home. Reason:

NOT_FOUND

Powered by Jetty://

[robogeek]

If you copied and pasted the error from your web browser, then you misspelled the url. The sage web url is case sensitive. Be sure to use:

http://server:port/sage/Home

In the url, take note that sage is lowercase and Home is capitalized. If it's not spelled with the correct case, it will return a 404 Not Found error. You can also leave off the /Home part of the url and it will automatically redirect to the correct page.

Some other things that might cause that 404 error: The .war file isn't actually being deployed or is being erased after it is deployed. If it's not being deployed (it deploys to the Windows Temp directory), you'll have to enable Jetty logging to try to track down why...possibly an incomplete or corrupt download of the .war file? If it is being deployed, the Windows Disk Cleanup tool (and some other 3rd party disk maintenance tools) that clears out the Windows Temp directory may be erasing the deployed app if you run any of these Disk Cleanup tools regularly. That's about all I got...hope it helps.

[bikesquid]

Originally Posted by robogeek

If you copied and pasted the error from your web browser, then you misspelled the url. The sage web url is case sensitive. Be sure to use:

http://server:port/sage/Home

In the url, take note that sage is lowercase and Home is capitalized. If it's not spelled with the correct case, it will return a 404 Not Found error.

That was it! Thanks. I tried absolutely everything else, including all uppercase, all lower case, etc.
What a relief, it's such a useful addition and makes things easier for me. I appreciate it, but I do wonder if there's a reason it needs to mixed case, all lowercase would be much more consistent... I can't speak for all sage web apps but both bmt and sjq are accessed using lowercase. At least it's easy to convey... even to the unobservant like me... Just a thought. Thanks again for the help, I'm back in action!

[bikesquid]

another question, when viewing the EPG grid view is there a way to increase the number of rows? I'm showing 10 rows, but I'd love to get 20(ish) so I'm not scrolling so much... or even just one long list....

[robogeek]

Originally Posted by bikesquid

another question, when viewing the EPG grid view is there a way to increase the number of rows? I'm showing 10 rows, but I'd love to get 20(ish) so I'm not scrolling so much... or even just one long list....

Yup. At the bottom of the EPG grid, there should be a link labeled [Show Options]. You can use that to customize the grid to change things like how many hours to display, how many channels display, and some other options.