I think you are simply missing some @In tags here.
Actually you are just outjecting the page data to the conversation, but you
don't use them for calculating the values for the next page. Therefore you use
the data in the session-scoped SFSB for calculation.
View the original post :
http://www
Thanks Norman, actually the method has not been called, as I annotated and
posted the wrong method.
Annotating the right method works like a charm.
Maybe I should stop working over christmas. :)
/closed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996226#3
Actually I have a "view" directory.
And I actually want to be redirected to the same page, but with ending the old
and starting a new long running conversation.
I thought @End(beforeRedirect=true) would exactly do thatm but as stated before
I am just redirected to the same page with the old con
I forgot to mention I got a begin/create method in the same SFSB:
@Create
| @Begin
| public void init() {
| ,
| ,
| ,
| }
So what I really expected is:
1. I hit the Link.
2. updateDistributionList() is executed
3 the conversation is ended before the redirect
4. red
I have got a facelet-page named cc_distribution.xhtml
And a SFSB with one action method triggered by a commandLink from this page.
| @End(beforeRedirect=true)
| public String updateDistributionList() {
| .
| .
| .
| return "cc_distribution";
| }
Usi
You're right (thanks for reminding me of that)
anonymous wrote : I really, really don't think its a good idea to try and
update the db from *any* kind of timeout.
and you're right
anonymous wrote : Are you trying to implement some kind of offline pessimistic
lock?
View the original post :
http:
Thanks Gavin.
I need to "unbound" some entity from the current user (i.e. change a status in
the database), if his conversation times out, to be able to distribute that
entity to another user again.
Is there any actual "SEAM-way" to be notified when the conversation really
times out, or am I l
I need to change the status of an entity at the end of a conversation (even a
timed out one).
Here is the SFSB that should do that:
@Stateful
| @Scope(ScopeType.CONVERSATION)
| @Name("callCenterAddressAction")
| public class CallCenterAddressAction implements CallCenterAddressLocal
| {
What exactly is the correct behaviour?
What I am heading at:
Is the conversation destroyed after a timeout, when the user the conversation
belongs to does something again?
Or is the conversation destroyed after a timeout, when any user does something?
View the original post :
http://www.jboss.c
For everybody interested in this watch the ICEfaces forum entry:
http://www.icefaces.org/JForum/posts/list/3180.page
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994432#3994432
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
Thanks Gavin, I'll do that.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994431#3994431
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994431
___
jboss-user mailing list
jbo
I was wondering if there is a possible configuration solution, that allows me
to use ICEfaces only for dedicated JSF pages?
The only thing I came up with is using separate url-patterns in the web.xml for
the ICEfaces Servlets and the normal JSF Servlet.
But this would leave me with the problem o
Propably this is more of a JSF question, but is there any chance to avoid the
jsf error message, which will be shown when the input field is emtpy and
required="true" ?
With s:validate and required="true" you actually get a "two-step" validation:
First all fields with required="true" are checked
That's the way I would use @Rollback too.
The problem is that the I have no chance of state refreshing after the rollback.
Actually I have got a page which displays a list of customers and one customer
in detail, so that I can create, update and delete customers on one page.
The update could lazi
14 matches
Mail list logo
