you signal the tokens.... it does not matter they are in the DB. jBPM is workflow, so state oriented (persisted in DB), it is not a 'threading machine'. It's like asking how do I wake someone up.... by poking your finger somewhere... :-).... no just kidding. A token in a state that was signalled and faild will go back to that state (unless you progtamm otherwise) you have to retrigger them again.... the documention has info on this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005926#4005926
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005926
Hi,
Thanks very much for the help. However i have managed all along in the development of my application to survive with the normal EJB style @PersistenceContext declaration on my entity manager instances in my bean. Does it mean that now that i need to make use of selectitems, i have to change all of them to use a seam managed persistence context, or can i just configure a seam managed persistence context and make that available to selectitems in my selectitems config? I pray u say the latter.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005922#4005922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005922
The following code works fine:
| public List<Review> getReviews() {
| return reviews;
| }
|
| public void setReviews(List<Review> reviews) {
| this.reviews = reviews;
| }
|
in my jsf page, I have:
| <h:outputText value="#{review.title}" />
|
However, if I change List to Set, it says can't find property #{review.title}. I don't understand why this happens. Has anyone seeing the same problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005919#4005919
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005919