Apache Wicket 8.x Reference Guidefollowing entities already implement both these two interfaces (i.e. they can be either sender or receiver): Component, Session, RequestCycle and Application. IEventSource exposes a single method named which takes in input three parameters: • sink: an implementation of IEventSink that will be the receiver of the event. • broadcast: a Broadcast enum which defines the broadcast method used to dispatch0 码力 | 350 页 | 9.95 MB | 1 年前3- Apache Wicket 7.x Reference Guidefollowing entities already implement both these two interfaces (i.e. they can be either sender or receiver): Component, Session, RequestCycle and Application. IEventSource exposes a single method named which takes in input three parameters: • sink: an implementation of IEventSink that will be the receiver of the event. • broadcast: a Broadcast enum which defines the broadcast method used to dispatch0 码力 | 346 页 | 10.00 MB | 1 年前3
- Apache Wicket 10.x Reference Guidefollowing entities already implement both these two interfaces (i.e. they can be either sender or receiver): Component, Session, RequestCycle and Application. IEventSource exposes a single method named which takes in input three parameters: • sink: an implementation of IEventSink that will be the receiver of the event. • broadcast: a Broadcast enum which defines the broadcast method used to dispatch0 码力 | 336 页 | 7.16 MB | 1 年前3
- Apache Wicket 9.x Reference Guidefollowing entities already implement both these two interfaces (i.e. they can be either sender or receiver): Component, Session, RequestCycle and Application. IEventSource exposes a single method named which takes in input three parameters: • sink: an implementation of IEventSink that will be the receiver of the event. • broadcast: a Broadcast enum which defines the broadcast method used to dispatch0 码力 | 335 页 | 7.15 MB | 1 年前3
共 4 条
- 1