Observer issues - multiple calls + async

[damianharvey]

I've just implemented the Manager Component pattern as outlined in the docs using @Unwrap and @Observer and it's working a treat.

Two small issues with it though:

1. When using incremental hot deploy (ie. WEB-INF/dev) the Event is fired as many times as it's been since you last did a full deploy. For instance, if I start up my server and cause an event to fire, do an incremental hot deploy, cause the event to fire again; Then I will get the event firing twice on the second fire. If I do a full undeploy/redeploy it 'resets' the number of times it fires and all is good.

2. Can @Observer be used with @Asynchronous? I've tried but I get the following exception:

Caused by: java.lang.NoSuchMethodException: java.util.ArrayList.rebuildTradeRoute()
 at java.lang.Class.getMethod(Class.java:1581)
 at org.jboss.seam.async.AsynchronousInvocation.call(AsynchronousInvocation.java:45)

If I remove the @Async then it's fine.

Cheers,

Damian.

[pmuir]

1) This sounds like a bug. If you can file a jira issue, preferably with an example and instructions to reproduce, we can take a look.

2) You can use Events.raiseAsynchronousEvent - but I guess this syntax

@Asynchronous @Observer public void observe() {
 ...

is something we should support, so please raise an issue for this too.

[damianharvey]

Thanks Pete. I'll give raiseAsynchronousEvent a whirl.

1. http://jira.jboss.org/jira/browse/JBSEAM-2281

2. http://jira.jboss.org/jira/browse/JBSEAM-2280

Cheers,

Damian.

[damianharvey]

Issue #1 also seems to apply to Quartz jobs - ie. if I do a few hot deploys before a Quartz job is scheduled then it will run a number of times consecutively.

Cheers,

Damian.

[damianharvey]

More interesting behviour around Issue #1. If you do multiple hot deploys you can end up with an error (which looks suspiciously like the error when you do the Async)

Caused by: java.lang.IllegalArgumentException: method not found: sayHelloBack for component: testObserver
 at org.jboss.seam.Component.callComponentMethod(Component.java:2105)
 at org.jboss.seam.core.Events.raiseEvent(Events.java:83)

Doing a full undeploy/reploy resolves this.

A bit frustrating until I figured that one out.

Cheers,

Damian.