• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • hhuynh
  • Reporter: steve
  • April 09, 2007
  • 0
  • Watchers: 0
  • June 04, 2007
  • May 23, 2007

Description

Seems like we should take our one sample that uses jetty and have it use the latest one and take advantage of tims work to get a jetty config module in place.

Comments

Tim Eck 2007-04-09

to whoever this get assigned to – the sharedqueue sample app doesn’t need the jetty config plugin in it’s current form. The Jetty plugin only currently does instrumentation on Jetty’s class loaders which aren’t used unless Jetty is the main class, or you’re using a full fledged web app. I guess the test here is that (a) the latest jetty is in fact being used, and (b) the thing fails miserably if the jetty config plugin is not enabled in tc-config

Juris Galang 2007-04-27

As of rev 2754 the demo now uses jetty 6.1.1 I’d mark this one as resolve except for (from above):

(b) the thing fails miserably if the jetty config plugin is not enabled in tc-config

Why should it fail if the jetty plugin is not in the tc-config when it doesn’t even need it?

Fiona OShea 2007-05-14

Juris can you check with Steve on your comment above? thanks

Juris Galang 2007-05-22

Steve,

Could you please comment on these, or should I mark it as resolved already? Tnx

Juris

Steve Harris 2007-05-22

I didn’t understand your question about why it fails without the plugin but I think you can close it.

Fiona OShea 2007-05-30

verify that this is resolved, add test if necessary

Hung Huynh 2007-05-30

Doesn’t look like Juris and Steve have come to conclusion on this one.