@Observer does not work in booking example

[consuelofranky]

I am working with the current seam-booking example (jboss-seam-1.0.0.CR2), running in jboss-4.0.4.CR2.

I observe that when the user registers a new hotel booking, his list of bookings is not refreshed.

The service that registers the new booking (insert in the database) raises a new event and the service that refreshs the booking list (select from the database) has an @Observer annotation of this event, but this second service is not executed.

Somebody has some solution for this problem? Must I do some additional configuration to the example ?

Thanks

Maria Consuelo Franky
[e-mail]

[gavin.king]

Please report this in JIRA. Thanks.

[consuelofranky]

Excuse me: I do not what is JIRA and how to post a problem in JIRA.

Can you give me a link to JIRA ?

Thanks

Maria Consuelo Franky

[gavin.king]

http://jira.jboss.com/jira/browse/JBSEAM

[consuelofranky]

Hi:

I have not reported in JIRA because I have found the cause of the problem that I have shown before.

When in the seam-booking example I changed the datasource Hypersonic by a datasource Postgresql, I oberved 2 problems:

- the word "User" is reserverd in Postgresql; I must changed the name of this table to "Usr"

- when the user registers a new hotel booking, his list of bookings is not refreshed.

Specially the second problem does not happen in the example with Hypersonic.

The solution that I have found and that runs fine in Postgresql is the following:

the method with the @Observer annotation must have also the annotation @TransactionAttribute(REQUIRED)
in order to participate in the same transaction that raises the event
(otherwise the insert effect can not be observed by the select of the list in the database).

Regards

Maria Consuelo Franky
[e-mail]

[kh2ouija]

I just noticed that when annotating a method of a SFSB as @Observer for a certain standard event, I can't raise that event in the same bean as the method, as it will cause this:

javax.ejb.EJBException: Application Error: no concurrent calls on stateful beans

. Instead of raising that event, you have to call the observer method specifically.