You use request and session scoped Spring beans in WebSocket request
because such requests are not processed by Servlet filters and Spring has
no chance to set its proxy objects as request/session attributes.

But in Spring bean code you can do:
Application app = Application..get("myFilterName");
WebSocketSettings wsSettings = WebSocketSettings.Holder.get(app);
IWebSocketConnectionRegistry registry = wsSettings.getConnectionRegistry();
WebSocketPushBroadcaster broadcaster = new
WebSocketPushBroadcaster(registry);
broadcaster....

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Tue, Oct 7, 2014 at 11:31 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> To be fair I haven't tried :(
> I thought I will have "no session/application bound to current thread"
> exceptions :(
> I'll test and let you know
>
> On 7 October 2014 15:21, Martin Grigorov <mgrigo...@apache.org> wrote:
>
> > Hi,
> >
> > I think it should work.
> > What kind of problems do you face ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Fri, Oct 3, 2014 at 4:55 PM, Maxim Solodovnik <solomax...@gmail.com>
> > wrote:
> >
> > > Hello All,
> > >
> > > I wonder is it possible to send IWebSocketPushMessage from Spring bean?
> > (I
> > > can access Spring beans from wicket pages, now I need "backward
> > > compatibility")
> > >
> > > Thanks in advance for your help!
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> > >
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>

Reply via email to