tomstrummer wrote : I understand that I can't keep state in my SLSB, but I
thought the point was that you could biject stateful values into your SLSBs.
See
http://books.google.com/books?id=h1madTvupB8Cpg=PA162vq=listing+6-2sig=gedSD8Cnzsm8Oj-tDxPWs7pmvkk
Yes, correct.
You explicitly set the
I expect Seam to re-initialize the value when it goes out of scope.
How does Seam know when a context variable goes out of scope? If Seam sees a
@Out variable go out of scope, then it sees the bijected field with no
factory... It should just ignore it and leave whatever value happened to be
Hi Pete -- thanks for your reply.
[EMAIL PROTECTED] wrote : 1) If you have an @Stateless bean it can't have any
fields on it. read about what @Stateless *really* means (this probably explains
your values changing)
I understand that I can't keep state in my SLSB, but I thought the point was
1) If you have an @Stateless bean it can't have any fields on it. read about
what @Stateless *really* means (this probably explains your values changing)
2) This is because you are outjecting into EVENT scope. So, the process is this
whilst rendering the page
Try to access boolean value, not
