Yes, I recently upgraded the tip to 7.1.4. It's not at all certain but
it looks like that introduced a whole pile of new problems that I'm
still trying to nail down. :-(

bleeding edge is sharp and painful,
Anthony

On Wed, Jul 7, 2010 at 17:07, andreas <[email protected]> wrote:
> With the current tip it is not possible to apply the patch:
>
> compile:
>    [javac] Compiling 906 source files to /home/ahorst/FedOneWSFix/
> build/core
>    [javac] /home/ahorst/FedOneWSFix/src/org/eclipse/jetty/websocket/
> WebSocketConnection.java:77: cannot find symbol
>    [javac] symbol  : method getTimeoutTask()
>    [javac] location: class
> org.eclipse.jetty.io.nio.SelectChannelEndPoint
>    [javac]
> scep.getSelectSet().scheduleTimeout(scep.getTimeoutTask(),_maxIdleTimeMs);
>
> [javac]                                                             ^
>    [javac] /home/ahorst/FedOneWSFix/src/org/eclipse/jetty/websocket/
> WebSocketConnection.java:80: cannot find symbol
>    [javac] symbol  : method getTimeoutTask()
>    [javac] location: class
> org.eclipse.jetty.io.nio.SelectChannelEndPoint
>    [javac]
> scep.getSelectSet().scheduleTimeout(scep.getTimeoutTask(),_maxIdleTimeMs);
>    [javac]                                                     ^
>    [javac] Note: Some input files use or override a deprecated API.
>    [javac] Note: Recompile with -Xlint:deprecation for details.
>    [javac] Note: Some input files use unchecked or unsafe operations.
>    [javac] Note: Recompile with -Xlint:unchecked for details.
>    [javac] 2 errors
>
> Looks like the patch uses parts of jetty that are no longer in 7.1.4?
> Anyway I thought the websocket problems were already included in the
> current tip.
>
> Andreas
>
> On 30 Jun., 02:57, Anthony Baxter <[email protected]> wrote:
>> Does the patch 
>> inhttp://groups.google.com/group/wave-protocol/msg/f696b902ae059f09
>> help? It looks like fromhttp://download.eclipse.org/jetty/that 7.1.4
>> is out, I'll try to look at switching to that.
>>
>> Anthony
>>
>>
>>
>>
>>
>> On Wed, Jun 23, 2010 at 03:59, andreas <[email protected]> 
>> wrote:
>> > Hey James,
>>
>> > are there any news regarding the Chromium/Chrome WebSocket problem?
>>
>> > I ran into the same problem running FedOne on Ubuntu Lucid and Chrome
>> > Dev (6.0.437.3) from Ubuntu and Windows 7. How can one get the simple
>> > web client working again?
>>
>> > Andreas
>>
>> > On 27 Mai, 10:18, James Purser <[email protected]> wrote:
>> >> On Thu, May 27, 2010 at 6:13 PM, tyler gillies <[email protected]> 
>> >> wrote:
>> >> > is there an online demo?
>>
>> >> Once I confirm the chromium bug I'll set something up tonight
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Wave Protocol" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to 
>> > [email protected].
>> > For more options, visit this group 
>> > athttp://groups.google.com/group/wave-protocol?hl=en.
>>
>> --
>> Anthony Baxter, [email protected]
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/wave-protocol?hl=en.
>
>



-- 
Anthony Baxter, [email protected]

-- 
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en.

Reply via email to