Will do. After I have feedback from Jetty folk (sent them an email with my research) I'll take the appropriate action for Felix.
----- Original Message ----- From: Richard S. Hall <[email protected]> To: [email protected] Sent: Tue, 19 Oct 2010 17:48:14 -0400 (EDT) Subject: Re: Is org.apache.felix.http.jetty compatible with CDC? On 10/19/10 14:54, Matt Tennant wrote: > Hi Richard and all, > > What I found is that Jetty claims to be CDC-compatible as long as a few > rules are followed. It is explained here: > > http://docs.codehaus.org/display/JETTY/J2ME+CDC > > Since we are following the rules (that apply), I believe I've simply > stumbled across an accidental usage within Jetty code of a method not in > the CDC. I am now attempting to get my hands on the Jetty code that > corresponds to different Felix Jetty bundles in order to verify that this > issue has or has not been fixed since the 1.0.0 bundle. Good. If you determine it is a bug in Jetty method usage, make sure you report it to them. If there is anything we need to do, then open a JIRA issue for us against http.jetty. Worst case for you for the time being is you might have to build it yourself. Thanks for looking into it. -> richard > Best, > Matt > > -----Original Message----- > From: Richard S. Hall [mailto:[email protected]] > Sent: Tuesday, October 19, 2010 10:12 AM > To: [email protected] > Subject: Re: Is org.apache.felix.http.jetty compatible with CDC? > > On 10/19/10 11:01, Matt Tennant wrote: >> Fair enough, I interpreted from your comment that there must be Jetty >> folks out there, and found a website that seems to be their home. I'll >> follow up there. >> >> Is there a more general answer for Felix bundles? > Typically, we try to make our bundles usable on a wide variety of > environments, but it isn't always possible to support everything. In the > HTTP case, we are dependent on what Jetty supports. Regardless, we are > always willing to make improvements to support other environments if you > have any suggestions. > > Please let us know what you find out. > > -> richard > >> Thanks, >> Matt >> >> -----Original Message----- >> From: Richard S. Hall [mailto:[email protected]] >> Sent: Tuesday, October 19, 2010 9:50 AM >> To: [email protected] >> Subject: Re: Is org.apache.felix.http.jetty compatible with CDC? >> >> On 10/19/10 10:42, Matt Tennant wrote: >>> Hi all, >>> >>> >>> >>> My question today is about the Felix's Jetty bundle. We ran across > this >>> stack trace recently: >>> >>> >>> >>> java.lang.NoSuchMethodError: java.lang.String: method >>> >>> split(Ljava/lang/String;)[Ljava/lang/String; not found >>> >>> at >>> org.mortbay.jetty.HttpConnection$RequestHandler.parsedHeader(Unknown >>> >>> Source) >>> >>> at org.mortbay.jetty.HttpParser.parseNext(Unknown Source) >>> >>> at org.mortbay.jetty.HttpParser.parseAvailable(Unknown Source) >>> >>> at org.mortbay.jetty.HttpConnection.handle(Unknown Source) >>> >>> at org.mortbay.jetty.bio.SocketConnector$Connection.run(Unknown >>> Source) >>> >>> >>> >>> We are using the org.apache.felix.http.jetty-1.0.0 bundle, downloaded >> some >>> time ago from Felix. Our JVM is Sun's PhoneME, which implements the >>> Connected Device Configuration (CDC). CDC does not include a "split" >>> method on the String class, as you can see here: >>> >>> >>> >>> > http://download.oracle.com/javame/config/cdc/ref-impl/cdc1.1.2/jsr218/java >>> /lang/String.html >>> >>> >>> >>> I've noticed that the latest version of the Jetty bundle is now 2.04. > I >>> plan to download it, and perhaps look over the code myself if > necessary, >>> but does anyone know if this bundle is intended to be CDC-compatible? >> Is >>> there any way to know which bundles are implemented to be >> CDC-compatible? >> >> It seems as if this is a question for the Jetty folks, no? >> >> -> richard >> >>> Thanks, >>> >>> Matt >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
