Plugin: Jetty Starter 1.6

[jreichen]

The Jetty Starter plugin provides integration of the Jetty web server within SageTV. It enables running one web server engine inside the SageTV process that can host multiple web applications.

The first application written to run in Jetty was the mobile web interface. Early support for this plugin was provided in the thread that requested the mobile web interface. A separate thread is now being created here to support developers who are writing other applications to run in Jetty. See the download page and wiki for more information including installation instructions. Source code is available on SourceForge.

Please Note: any questions regarding the upgrade of the Jetty plugin from SageTV V6 to SageTV V7 should be posted in the thread over in the SageTV V7 Customizations forum. Questions regarding Jetty 2.0, which adopts the SageTV V7 Plugin Manager, should be posted to its thread, also in the SageTV V7 Customizations forum.

[geogecko]

Linky for download has an extra http...

Thanks again for your work on this!

[jreichen]

Fixed. Thanks!

[jreichen]

Since each application must have a unique context root, I created a wiki page to track them.

[stuckless]

Since each application must have a unique context root, I created a wiki page to track them.

I just added /smt (Sage Media Tools - Web Front End for Batch Metadata Tools). And thanks for adding the /sagex for me

[beerandt]

Hi- I'm fairly new to the world of sagetv and was playing around trying to install jetty starter. I'm not sure if this is something I'm doing wrong or not, so I figured I ask.

The JettyStarter.properties file and realm.properties files that I downloaded don't seem to have any line breaks in them. I also checked the license text files, and it seem to be the same thing.

Is there something wrong with the files, or am I doing something wrong?

Thanks

[stuckless]

jreichen probably created them in linux. They should still work fine. you can try to edit them with wordpad instead of notepad, since wordpad support unix line feeds.

[beerandt]

That worked! Thanks for the quick reply. I knew it was probably something simple like that, but I got nervous editing a file that lacked any -visible- formatting.

Thanks!

[jreichen]

stuckless is right, I use Linux. I modified the build script so the build process will convert the line feeds to Windows format starting with the next release. The web server will work either way but it's easier for Windows users to read and edit the files if the line feeds are in Windows format.

[bcjenkins]

Jason,

How do you add support for http://server/ file usage?

TIA

B

[jreichen]

Do you mean Serving other files with Sage Web Server, but with the Jetty server rather than nielm's web server?

I'm not positive, but I don't remember nielm's using a servlet, so it's probably down in the server code, meaning I can't just configure a reference to a servlet of his (that probably wouldn't work in the root context anyway).

I think you can put files in the jetty/webapps folder and serve them up, but in order to point to somewhere else on the file system, I'd have to research how Jetty handles the root context and override it.

[bcjenkins]

Specifically, I am having issues with serving http://server/crossdomain.xml. I am getting a 404. The file is in webapps and in /remote as well. I am not familiar enough with Jetty to understand the syntaxing, but a quick trip to Google with "jetty crossdomain.xml" does turn up some hits. It's not for Jetty though, some variant of it.

B

[jreichen]

I have the same problem but haven't found a fix today. I'll put it on my todo list.

[jreichen]

The Jetty Plugin version 1.5 has been released and can be downloaded here. This addresses bcjenkins' crossdomain.xml file issue as well as a couple other things.

• Serve static files from the jetty/static directory. Required for the crossdomain.xml file for shadeblue's remote control.
• Convert end-of-line characters from LF (Linux) to CRLF (Windows). Most people use the Windows platform plus Linux editors handle the Windows format better than Windows Notepad handles the Linux format.
• Expose version number

If you are using stuckless' remote APIs, you'll need to upgrade to version 6.4.8-12 to get his new sagex.xml context file - especially if you're using shadeblue's Flash remote control and need the crossdomain.xml file.

Jason

EDIT: Added download link.

[bcjenkins]

danke

[Skirge01]

I just spent the past 3 days trying to figure out how I hosed my Jetty installation on my WHS box and believe I've finally figure out the cause: IE8. I uninstalled and reinstalled everything I could possibly think of and then decided to remove IE8 and it's associated single update and now things are right back to where they were: working!

Basically, I could no longer connect to SJQ's interface, the Mobile Web Interface, or even nielm's Webserver. The Webserver issue could very well mean it's not only Jetty or that I managed to break it during my Jetty troubleshooting. So, take that part for what it's worth. I also had issues getting the SJQTaskClient service to stay running while IE8 was installed. I was getting "error code 1" messages.

Has anyone else noticed something similar? I'm not pointing a finger at Jetty or even at Microsoft at this point, but wanted to see if anyone else noticed anything that might help pinpoint the issue or a possible remedy (other than uninstalling IE8--not that I wanted it in the first place).

[Skirge01]

By the lack of responses, I guess I'm the only idiot who installed IE8.

In case anyone else tries to uninstall IE8, you may wind up with the following Windows Event errors:

Source: Userenv
TimeGenerated: 5/5/2009 1:50:45 PM
InstanceId: 3221226513
Catagory: (0)
CatagoryNumber: 0
EntryType: Error
Message: Windows cannot query DllName registry entry for {7B849a69-220F-451E-B3FE-2CB811AF94AE} and it will not be loaded. This is most likely caused by a faulty registration.
----

Source: Userenv
TimeGenerated: 5/5/2009 1:50:45 PM
InstanceId: 3221226513
Catagory: (0)
CatagoryNumber: 0
EntryType: Error
Message: Windows cannot query DllName registry entry for {CF7639F3-ABA2-41DB-97F2-81E2C5DBFC5D} and it will not be loaded. This is most likely caused by a faulty registration.

If you see the above error messages after uninstalling IE8, just search for the registry entries above and delete them. Obviously, the usual "back up your system before making changes to the registry" applies here.

[GollyJer]

Is IE8 really a barrier to getting this working? I'm running Neil's Web Interface without problems using IE8 but can't seem to get Jetty working. It won't run in Chrome or Firefox either. I find it hard to believe the browser makes a difference at the OS.

[Edit]
Never mind. This is working fine with IE8. I was going to the wrong URL.
I'm pretty sure IE8 didn't have anything to do with Skirge01's problem.

[Skirge01]

If that's the case, then I sure would like to know what caused the issue. As far as I can recall, my WHS box had no other changes, except for installing IE8 on it and that's when it stopped working. I uninstalled IE8 and Jetty worked again. I really have no need for IE8 on my WHS box, so I won't bother trying it again unless (until?) Microsoft decides to lock users out of updates based on the IE browser version they have installed.

[iolaus]

jreichen,

Thanks for the awesome Jetty SageTV plugin. Quick question for you... is there an easy way to enable HTTP compression with the plug-in? I looked around for some documentation but wasn't knowledgeable enough about Jetty to easily piece together a solution from what I found.

The main motivation for this is that I'm using Stuckless's SageX APIs (hosted by Jetty) and I would like to test compression of the API call results to see if it would provide any speed increase.

Thanks!