Plugin: Mobile Web Interface 1.2

[acrowe]

Originally Posted by jreichen

Did you upgrade to version 1.6 of the Jetty plugin?

Yep... Just checked the JAR versions vs the archive and they are all the same?

[jreichen]

Did you remove all the Jetty 6.1.11 jar files from the JARs folder?

Are there any other servlet-api*.jar files in the JARs folder?

If those look fine, could you post your log file?

[acrowe]

I thought I had removed all of them, but I had missed servlet-api-2.5-6.1.11.jar

I removed that and restarted sage, but still no luck (and at some point this evening I've managed to break nielms webserver too).

Here is the contents of my JARS directory:

 Directory of C:\Program Files\SageTV\SageTV\JARs

09/20/2008  12:47 AM    <DIR>          .
09/20/2008  12:47 AM    <DIR>          ..
09/12/2007  08:45 PM            54,829 activation.jar
07/26/2009  01:50 PM         1,034,049 ant-1.6.5.jar
07/12/2009  09:13 PM            46,725 commons-codec-1.3.jar
07/28/2007  03:55 AM           279,383 commons-httpclient-3.0.jar
07/12/2009  09:13 PM           109,043 commons-io-1.4.jar
03/29/2006  10:26 AM           268,794 commons-jxpath-1.1.jar
07/12/2009  09:13 PM           261,809 commons-lang-2.4.jar
03/29/2006  10:26 AM            31,605 commons-logging.jar
07/28/2007  03:55 AM            38,015 commons-logging-1.0.4.jar
03/29/2006  10:26 AM            22,327 commons-logging-api.jar
07/12/2009  09:13 PM           373,438 commons-vfs-20070823.jar
07/26/2009  01:50 PM         3,566,844 core-3.1.1.jar
10/13/2008  09:46 PM            18,293 df_sageutils.jar
12/03/2007  01:35 PM           539,093 gkusnick.sagetv.jar
07/12/2009  09:13 PM           288,098 htmlparser.jar
11/26/2008  10:48 AM             3,527 imageutils.jar
01/02/2009  06:12 PM           263,903 jcifs-1.1.6.jar
03/23/2005  10:45 AM            72,906 jdic.jar
07/26/2009  01:50 PM           526,754 jetty-6.1.19.jar
07/26/2009  01:50 PM            30,205 jetty-ajp-6.1.19.jar
07/26/2009  01:50 PM            21,585 jetty-rewrite-handler-6.1.19.jar
07/26/2009  01:50 PM            18,376 jetty-sslengine-6.1.19.jar
07/26/2009  01:50 PM            16,612 jetty-starter.jar
07/26/2009  01:50 PM           173,609 jetty-util-6.1.19.jar
07/26/2009  01:50 PM         1,026,148 jsp-2.1.jar
07/26/2009  01:50 PM             4,899 jsp-2.1-jetty-6.1.19.jar
07/26/2009  01:50 PM           134,855 jsp-api-2.1.jar
09/12/2007  08:45 PM           358,085 log4j.jar
07/12/2009  09:13 PM           391,834 log4j-1.2.15.jar
07/12/2009  09:13 PM           665,686 lucene-core-2.3.2.jar
09/12/2007  08:45 PM           355,030 mail.jar
12/15/2007  06:27 PM            15,590 mailcheck.jar
07/12/2009  09:13 PM           392,184 metadata-updater.jar
04/30/2009  06:02 PM           107,221 miglayout-3.6.3-swing.jar
03/29/2006  10:26 AM           148,179 mx4j-impl.jar
03/29/2006  10:26 AM           261,135 mx4j-jmx.jar
03/29/2006  10:26 AM           167,500 mx4j-remote.jar
03/29/2006  10:26 AM           491,164 mx4j-tools.jar
09/20/2008  02:18 AM    <DIR>          NetFlix
08/10/2008  12:13 PM           120,255 netflix.jar
10/20/2005  03:00 PM            28,080 nielm_getrssnews.jar
07/06/2009  07:09 PM            52,780 nielm_sageimdb.jar
12/21/2007  09:46 PM            33,916 nielm_sagemenureader.jar
03/09/2009  03:10 PM            14,656 nielm_sageutls.jar
03/09/2009  03:10 PM           393,748 nielm_sagewebserver.jar
03/09/2009  03:10 PM            62,202 nielm_sagexmlinfo.jar
07/12/2009  09:13 PM           199,849 phoenix.jar
07/28/2007  03:55 AM            20,542 rsslib4j-0.2.jar
10/13/2008  09:46 PM            66,795 sagemc.jar
07/12/2009  09:13 PM           308,720 sagex.api.jar
03/29/2006  10:26 AM            89,764 sbbi-jmx-1.0.jar
05/04/2006  08:56 AM           109,503 sbbi-upnplib-1.0.3.jar
12/04/2005  06:25 PM            31,789 servlet.jar
07/26/2009  01:50 PM           134,133 servlet-api-2.5-6.1.19.jar
              53 File(s)     14,246,064 bytes
               3 Dir(s)   6,809,944,064 bytes free

I've attached my request logs, but for some reason even with debug on I'm not seeing the sagetv_0.txt file get created (unless it isn't in the sage root anymore?)?

[acrowe]

Also if it helps at all bmt's web interface is functioning properly.

[robogeek]

Originally Posted by acrowe

Also if it helps at all bmt's web interface is functioning properly.

Have you tried shutting down SageTV (or SageTV Service if running as service) and deleting the jetty\webapps\SageWebApp directory and then restarting SageTV? The SageWebApp directory should be recreated when SageTV is restarted. I had to do that to get 1.6 jetty web interface running.

[jreichen]

It looks like a versioning problem with some Java servlet classes. BMT may not be using any new APIs that would be missing from an old class.

I think the servlet.jar and servlet-api-2.5-6.1.19.jar files are different versions of the same classes. Take a look at them in WinZip to verify if they have similar classes in them. If they are, move servlet.jar off to a safe backup location outside the SageTV folder and restart SageTV.

[robogeek]

I have the same servlet.jar and don't have those issues. The only potential jar issue I can see though, would be the log4j.jar and log4j-1.2.15.jar. I think the log4j.jar should be removed, but I don't think keeping it there would cause these issues with jetty. I think stuckless includes the log4j-1.2.15.jar with BMT to replace the original log4j.jar.

[stuckless]

ironically I just updated to Jetty 1.6 tonight and I was having some issues (which I've resolved). My issue was that I was that even though I was no longer running on port 8081 (i switched to 8080), my bookmark was still pointing to 8081. When I clicked the bookmark, the UI actually loaded (with some errors) even though it was pointing to 8081 (which was no longer there) because of the browser cache. When I forced a refresh (shift + reload) I got a 404 page not found, and I realized that I was pointing to the totaly wrong port. After switching to the correct port, and forcing a shift + reload, it now works.

[jreichen]

Originally Posted by robogeek

I have the same servlet.jar and don't have those issues. The only potential jar issue I can see though, would be the log4j.jar and log4j-1.2.15.jar. I think the log4j.jar should be removed, but I don't think keeping it there would cause these issues with jetty. I think stuckless includes the log4j-1.2.15.jar with BMT to replace the original log4j.jar.

Is the timestamp on your servlet.jar December 4, 2005?

[robogeek]

Originally Posted by jreichen

Is the timestamp on your servlet.jar December 4, 2005?

Yes, it is. It's part of the nielm web server package and I'm running both the nielm web server and the jetty web server with the mobile web interface without issues.

[acrowe]

Originally Posted by robogeek

Have you tried shutting down SageTV (or SageTV Service if running as service) and deleting the jetty\webapps\SageWebApp directory and then restarting SageTV? The SageWebApp directory should be recreated when SageTV is restarted. I had to do that to get 1.6 jetty web interface running.

Yep did that first to see if it helped, no luck...

Originally Posted by jreichen

Is the timestamp on your servlet.jar December 4, 2005?

Yep thats the one...

[acrowe]

Originally Posted by jreichen

It looks like a versioning problem with some Java servlet classes. BMT may not be using any new APIs that would be missing from an old class.

I think the servlet.jar and servlet-api-2.5-6.1.19.jar files are different versions of the same classes. Take a look at them in WinZip to verify if they have similar classes in them. If they are, move servlet.jar off to a safe backup location outside the SageTV folder and restart SageTV.

Well I was pretty sure I had done this before...

BUT did it again just now and everything is up and running now! Both nielm's and mobile!

Thanks for the help folks!

[jreichen]

Originally Posted by acrowe

Well I was pretty sure I had done this before...

BUT did it again just now and everything is up and running now! Both nielm's and mobile!

Thanks for the help folks!

Great! Sorry it took so long to get you up and running. Classpaths and Jar versioning can be a headache sometimes.

[jreichen]

Originally Posted by robogeek

Yes, it is. It's part of the nielm web server package and I'm running both the nielm web server and the jetty web server with the mobile web interface without issues.

Not to drag this out longer, but could you post the versions of nielm's web, jetty, and mobile web that you're running?

[jreichen]

Originally Posted by KJake

I don't want to step on toes, but is there a reason that you aren't trying to integrate with the webserver that already exists?

The simple answer is that I wanted an easier way to write pages, and I also wanted to enable other plugin developers to have a way to create web-based applications. For those who are reading this and that's enough detail for you, feel free to stop reading now.

For those who are reading and are interested in a little more detail than that: The only way to generate dynamic content with the current web server is using servlets. It does not support JSPs. For the mobile web interface, I wasn't about to write more servlet code that generates HTML. Servlets are fine for backend logic (calling a Sage API to schedule a recording), but it's difficult to work with servlets that generate HTML (the page with the list of scheduled recordings). If you look at the mobile web interface code you'll see a better separation between model (Sage APIs and the wrapper tag library I generated), view (JSPs) and controller (mostly servlets).

The current web server also tightly integrates the "server" with the "application", so it won't run multiple apps. Running Mobile Web Interface, Sage Job Queue, Batch Metadata Importer, etc web apps on one port would not be possible. It would require a separate web server for each application, and as you can imagine that would not be good for developers or users. Hopefully at some point nielm's web interface can be modified/rewritten to run in Jetty, too - eliminating the mobile web server's dependencies on it in version 1.2 was the first step needed to do that.

After thinking through those problems, I went looking for an embeddable Java web server to support both JSP development and multiple apps and chose Jetty. There are other advantages as well, including running both an SSL and a non-SSL port at the same time and redeploying a web app without restarting Sage (though admittedly that doesn't work 100% of the time). The Jetty plugin is the Jetty server itself plus a little bit of code I wrote to hook Jetty into Sage.

I realized there would be some who would question the move to Jetty, but in the big picture (all web apps under one server) I felt it was a good move.

Originally Posted by KJake

For example, with a little javascript, you could detect for mobile phones or mobile browsers and load different styles or themes. That way, all you'd be doing is "skinning" the webserver site that already works.

Thanks for the sample. My comments will probably sound critical here on a forum post, but they're not intended to. I'm just commenting on what I see...

The sample looks like it's more like redirecting to iPhone-specific pages (essentially a 3rd web interface) rather than skinning the pages for iPhones. Ideally the existing pages would be modified to be more "skin-friendly" (I'd do this to the mobile web interface pages, the HTML is much simpler in those than in nielm's). They currently have stylesheet support, but not enough to be skinned. And rather than JavaScript, I'd probably determine the client's browser when building the jsp page on the server side and include the appropriate headers and stylesheets at that time.

To get all the advantages of iUI (animations, etc), though, in the end might require different pages. I wouldn't know for sure without prototyping. I have an iPhone, but maybe contrary to most others I prefer the Sage look on the pages. Aside from the iPhone, is there much interest out there for skinning/themes?

Originally Posted by KJake

I did this quickly to test if it would work for an iPhone...

Edited \webserver\webroot\sage\index.html and added:

<script lang="JavaScript">
<!--
if((navigator.userAgent.match(/iPhone/i)) || (navigator.userAgent.match(/iPod/i))) {
   if (document.cookie.indexOf("iphone_redirect=false") == -1) window.location.replace("iphone.html");;
}
-->
</script>

then placed iUI (from http://code.google.com/p/iui) in \webserver\webroot\sage\
then copied menu.html and renamed to iphone.html and reformated the ordered list as such:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
 <meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=0;"/>
 <link rel="apple-touch-icon" href="./iui/iui-logo-touch-icon.png" />
 <meta name="apple-touch-fullscreen" content="YES" />
 <style type="text/css" media="screen">@import "./iui/iui.css";</style>
 <script type="application/x-javascript" src="./iui/iui.js"></script>
 <script type="text/javascript">
    iui.animOn = true;
 </script>
 <link rel="Shortcut Icon" href="/favicon.ico" type="image/x-icon">
 <script type="text/javascript" src="sage.js"></script>
<title>SageTV iPhone Interface</title>
</head>
<body>
    <div class="toolbar">
        <h1 id="pageTitle"></h1>
        <a id="backButton" class="button" href="#"></a>
        <a class="button" href="#searchForm">Search</a>
    </div>
    <ul id="home" title="Home" selected="true">
        <li><a href="#SageTV">SageTV</a></li>
        <li><a href="#ScheduleRecordings">Schedule Recordings</a></li>
        <li><a href="#ProgramGuide">Program Guide</a></li>
        <li><a href="#MediaLibrary">Media Library</a></li>
    </ul>
    <ul id="SageTV" title="SageTV">
        <li><a href="Recordings">Sage Recordings</a></li>
        <li><a href="Search?searchType=TVFiles&sort1=title_asc&sort2=airdate_asc">Search Recorded TV files</a></li>
        <li><a href="webremote.html?context=SAGETV_PROCESS_LOCAL_UI&contextname=Local%20SageTV">Web Remote (Local Sage)</a></li>
        <li><a href="about.html">About</a></li>
    </ul>
    
    <ul id="ScheduleRecordings" title="Schedule Recordings">
        <li><a href="Recordings">Sage Recordings</a></li>
        <li><a href="Favorites">Favorites Manager</a></li>
        <li><a href="webremote.html?context=SAGETV_PROCESS_LOCAL_UI&contextname=Local%20SageTV">Timed Recording</a></li>
        <li><a href="Conflicts">Recording Conflicts</a></li>
    </ul>
    
    <ul id="ProgramGuide" title="Program Guide">
        <li><a href="EpgList">EPG List view</a></li>
        <li><a href="EpgGrid">EPG Grid view</a></li>
        <li><a href="Search">Search EPG</a></li>
        <li><a href="EpgGrid?starthr=18">Today PrimeTime</a></li>
        <li><a href="EpgGrid?starthr=18&startdate=1">Tomorrow PrimeTime</a></li>
        <li><a href="Search?TimeRange=48&Categories=film&Categories=movie&Categories=Movie&SearchString=">Upcoming movies</a></li>
        <li><a href="Search?TimeRange=48&favorite=set&SearchString=">Upcoming Favorites</a></li>
        <li><a href="Search?SearchString=&searchType=Airings&TimeRange=-999&watched=set&sort1=airdate_desc&sort2=none">Watched Shows</a></li>
        <li><a href="Search?SearchString=&searchType=Airings&TimeRange=-999&dontlike=set&sort1=title_asc&sort2=airdate_asc">Don't like Shows</a></li>
    </ul>
    
    <ul id="MediaLibrary" title="Media Library">
        <li><a href="Search?searchType=MediaFiles&DVD=on&sort1=title_asc&sort2=none">Search DVDs</a></li>
        <li><a href="Search?searchType=MediaFiles&Video=on&sort1=title_asc&sort2=none">Search Imported Videos</a></li>
        <li><a href="Search?searchType=MediaFiles&Music=on&search_fields=episode&sort1=episode_asc&sort2=none">Search Music by track Title</a></li>
        <li><a href="Search?searchType=MediaFiles&Music=on&search_fields=people&sort1=people_asc&sort2=episode_asc">Search Music by Artist</a></li>
        <li><a href="Search?searchType=MediaFiles&Music=on&search_fields=title&sort1=title_asc&sort2=episode_asc">Search Music by Album</a></li>
        <li><a href="Search?searchType=MediaFiles&Music=on&search_fields=category&sort1=title_asc&sort2=episode_asc">Search Music by Genre</a></li>
        <li><a href="Search?searchType=MediaFiles&Picture=on&sort1=title_asc&sort2=none">Search Picture Files</a></li>
        <li><a href="PlaylistGenerator?Command=list">Export Playlists</a></li>
    </ul>
    
    <form id="searchForm" class="dialog" action="Search">
        <fieldset>
            <h1>Music Search</h1>
            <a class="button leftButton" type="cancel">Cancel</a>
            <a class="button blueButton" type="submit">Search</a>
            
            <label>Artist:</label>
            <input id="artist" type="text" name="artist"/>
            <label>Song:</label>
            <input type="text" name="song"/>
        </fieldset>
    </form>
</body>
</html>

This then loads the iPhone menu when I visit from my iPod Touch or the normal interface when I visit from any other browser. Of course, none of the other pages are formatted, but couldn't that be done just as easily?

It can be done, but modifying a static menu is a pretty simple case. If the same steps are taken to modify or copy the servlets that generate the dynamic pages (I'm referring to nielm's web server here) it would take quite a bit of work up front to get it working plus those would have to be maintained with bug fixes and enhancements.

Originally Posted by KJake

I might give it a go, just as a challenge, but I'm probably going to have to start modding the java servlets...and I have zero experience there. If there were more of view/model separation of servlets doing the work and jsp's doing the i/o and formatting, then I'd have more hope.

After all that at the beginning about "why not use the existing server?", you essentially answered it yourself here

[robogeek]

Originally Posted by jreichen

Not to drag this out longer, but could you post the versions of nielm's web, jetty, and mobile web that you're running?

The nielm web interface says Sage Webserver version 2.23, but I have the last 2.24 update posted in the web server thread installed. I'm running the v1.6 jetty starter and v1.2 jetty SageWebApp. I installed everything from the following archives:

webserver_2_24.zip
jettystarter_1_6.zip
SageWebApp_1_2.zip

The servlet.jar was in webserver_2_24.zip/bin/jars. I have an apache web server (WAMP Server v2.0) running on port 80, nielms web server running on port 8080 and jetty running on port 8081.

[taylormadearmy]

Hi all,

I'm trying to install the Mobile web interface for the first time. I have installed the latest version of Jetty and the web interface from and believe I have followed the instructions fromt the wiki corerctly. I have left the password and port as the default ones for now. However I am unable to log in - I just keep being asked for the username and password.

Any idea as to what could be wrong? Any useful logs I could look at?

Thanks
T

[jreichen]

Originally Posted by taylormadearmy

Hi all,

I'm trying to install the Mobile web interface for the first time. I have installed the latest version of Jetty and the web interface from and believe I have followed the instructions fromt the wiki corerctly. I have left the password and port as the default ones for now. However I am unable to log in - I just keep being asked for the username and password.

Any idea as to what could be wrong? Any useful logs I could look at?

Thanks
T

What happens when you try it in a desktop browser (IE, FF, Safari)?

Turn on Sage's debug logging by setting debug=TRUE in Sage.properties. Make sure Sage is not running when modifying the properties file.

Also, uncomment the DEBUG and VERBOSE lines in JettyStarter.properties to enable Jetty's own debug logging. Messages will be written to Sage's log file. This requires a restart of Sage.

[taylormadearmy]

Originally Posted by jreichen

What happens when you try it in a desktop browser (IE, FF, Safari)?

I have tried FF and IE - both have the same issue.

Originally Posted by jreichen

Turn on Sage's debug logging by setting debug=TRUE in Sage.properties. Make sure Sage is not running when modifying the properties file.

Also, uncomment the DEBUG and VERBOSE lines in JettyStarter.properties to enable Jetty's own debug logging. Messages will be written to Sage's log file. This requires a restart of Sage.

I have tried this - but can't see a VERBOSE line in JettyStarter.properites - what should the line be?

What kind of thing should I then be looking for in the logs?

Many thanks for your help!
T

[jreichen]

Originally Posted by taylormadearmy

I have tried this - but can't see a VERBOSE line in JettyStarter.properites - what should the line be?

What kind of thing should I then be looking for in the logs?

Many thanks for your help!
T

It's similar to the DEBUG line:

VERBOSE=true

I'm not sure what to look for. One other user has reported that he was prompted for user/pwd for every request made while downloading a page (the page itself plus the stylesheet as well as any images).

Is there any kind of firewall on your network that might be blocking HTTP headers? Do you have cookies enabled?

If you're familiar with the Live HTTP Headers plugin in Firefox you could capture the request and response headers and post them here.