CDI events - strange behavior

Question

CDI events is a nice feature, but I discovered a strange behavior in Glassfish 3.1.1.
An event generated by a ApplicationScoped bean will not be propagated to all SessionScoped bean listener methods.
For example: supose that you call ‘fire(“text”)’ on Producer bean, and we have 2 instances of Consumer bean. The ‘fired’ method on Consumer bean will be invoked only for one instance. The second Consumer instance will not be notificated.
@Named
@ApplicationScoped
public class Producer {
@Inject @Any
private Event event;
public void fire(String message) {
event.fire(message);
@Named
@SessionScoped
public class Consumer {
public void fired(@Observes String event) {
// do something…
I think that there is something wrong. Maybe with Weld? I don't know yet. What do you think?
Edited by: user2048425 on 09/10/2011 07:14
Edited by: user2048425 on 09/10/2011 07:22

Answer 1

Kdcypher wrote:
We seem to have an intermittent problem with recurring events. It seems as though if the organizer of the event makes too many changes to an existing recurring event, it can cause the event to disappear from invitee's calendars, but not necessarily all of the invitee's calendars.What interface(s) are you using to edit the events e.g. Calendar Express, UWC/CE, Convergence, Outlook Connector, Lightning plugin?
What version of Calendar Server are you using (./showrev -p | grep ics5)?
We're in the process of experimenting with it on our test server and gathering information about this issue before submitting it to Sun support, but in the meantime, I thought I'd see if anyone here had heard of such a thing.This problem isn't ringing any bells. If you can duplicate the problem in your test environment that would be a good start.
Regards,
Shane.