to make it compiling.
There is a warning that I do not understand :
The expression ${pom.artifactId} is deprecated. Please use ${project.artifactId} instead.
Any idea ?
thanks very much since your tuto had been very helpfull !

regards
cm

Thanks for your comment.

Concurrency is a common problem for web applications. My example is a bit outdated and was attempt to show how ejb 3.1 and jsf interact together in a pre-release of galssfish.

So the keyword to your problem could be locking / optimistic locking.

Perhaps the following article can help you.

Locking and Concurrency in Java Persistence 2.0
http://blogs.sun.com/enterprisetechtips/entry/locking_and_concurrency_in_java

or when your work with Hibernate
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/transactions.html

Regards

Matt

With regard to storing the book being edited in a session scoped bean:- it seems the faces session is equivalent to the HttpSession and therefore the user can only edit one book at a time?

Even worse, if the use opens two records for edit at the same time they can overwrite the wrong record!

I’ve noticed that if
- I open the list in two browsers tabs
- select book 1 in the first
- select book 2 in the second
- edit and save book 1 in the first
- then book 2 is actually updated with the data entered for book 1.

(complicated but, unfortunately, within the realms of possibility for the average user)

I’m new to JFS so I’m wondering if I’m missing something? Is there a way around storing the entity bean in the session?

I’ve been racking my brain for a way to start a transaction (txn) at the edit action, then pick up the same txn object at the save, delete actions? #{BookBean.txnBook.title} kind of thing?

Can you offer any guidance to a Noob?

Thanks,
Steve.

Cay said:
> In your example, you (or maybe Maven) put persistence.xml in
> two places,
> and it took me a while to find out where it needs to go. I put an
> example with an Ant script at
> http://weblogs.java.net/blog/cayhorstmann/archive/2009/02/towards_java_ee.html

message: Exception while deploying the app : java.lang.RuntimeExceptio
n: Invalid ejb jar [CRUD-GFv3]: it contains zero ejb.
Note:
1. A va
lid ejb jar requires at least one session, entity (1.x/2.x style), or
message driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and
please package them as library jar.
3. If the jar file contains vali
d EJBs which are annotated with EJB component level annotations (@Sta
teless, @Stateful, @MessageDriven), please check server.log to see wh
ether the annotations were processed properly.
exit-code: FAILURE

Any clue what might have changed?

Thanks,

Cay

I wrote a post about that here:
http://blog.jonasbandi.net/2008/12/simplistic-crud-application-with-grails.html

I only had a small problem that the updatetool did not list the JSF 2.0 update.
The admin-console however did list the update.
Could be this bug: https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=774

Thanks.

I’ve encountered the same compile error as Rogerio, and I have source and target compiler settings set to “1.6″:

org.apache.maven.plugins
maven-compiler-plugin

1.6
1.6

The cause is: javax.javaee dependency includes jsf-api-1.2 which doesn’t have parameterized classes. To make the project compile we need to exclude it from the dependency tree (so jsf-api-2.0.0-b05 takes effect):

org.glassfish
javax.javaee
3.0-Prelude
provided

javax.faces
jsf-api

I’m not sure but it seemed that the following declaration causes the error.


private DataModel books;


Do you have a least Java 5? Because this statement uses generics? I googled and I found some similar build failures which occurred when not at least a java 5 compiler was used.

Matt