here's the qout from Gavin...
anonymous wrote : But the reality is that a SESSION scoped persistence context
is always a bad thing (it is a memory leak, to begin with), and you should
never do that.
|
I guess I don't understand.
View the original post :
http://www.jboss.com/index.html?mod
"CptnKirk" wrote : @Out's scope defaults to the scope of the enclosing
controller, in this case the SLSB. SLSB have a stateless scope. I think that
Seam may actually promote the outjection of context variables of stateless
components to event scope for you (but I'm not positive).
|
| Even
I have this client vs. server error, too. I have to use client state saving,
since if I use server state saving the login button doesn't work. Could you
solve the problem?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976028#3976028
Reply to the post :
ht
I'm using (as far as I know) the latest released versions of facelets, my
faces, and tomahawk. However, I could try the CVS versions to see if they
fixed the problem.
The jury's still out (in my head anyway) on server vs. client. The usual
tradeoff - server means that I don't have to send as
...or maybe that was an earlier version of facelets (or both). Try upgrading
those if you need server side state saving.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970222#3970222
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
My guess is the client vs server state saving problem is due to a bug in ealier
versions of MyFaces that JBoss may still ship with.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970220#3970220
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
I'm using "client" state saving. Funny you should ask - I tried switching to
"server" to see what would happen, and all of my "commandButton" and
"commandLink" controls stopped working (s:link still worked). I don't know why
they quit working, but I quickly reset it back to "client".
View th
"CptnKirk" wrote : Well it just doesn't make sense for a stateless component to
outject anything, because it wouldn't go anywhere.
And this isn't strictly true either. There are a whole class of problems where
you want to have a stateless component (like a SearchManager) to outject into
anothe
Well it just doesn't make sense for a stateless component to outject anything,
because it wouldn't go anywhere. *IF* (I'm still not sure) Seam is nice and
automatically outjects objects from stateless components into event scope, then
the examples were likely written in a time where Seam didn't
Just curious. What JSF state saving technique are you using? If you change
this to client, does page scope work?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970214#3970214
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=rep
I'm noticing that some of the Seam examples use EVENT for the scope of Session
Beans. Maybe I should be using that instead of @Stateless for my session
bean...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970212#3970212
Reply to the post :
http://www.jb
Well EVENT obviously won't work because state is destroyed at the end of the
request, so it won't be available across redirects (which have 2 requests).
PAGE on the other hand I'm not 100% sure about. I'll admit I don't use page
scope. I was under the impression that this was like a mini-sessi
Well, this was just a test example. My application has all sorts of the usual
cross-page navigation.
In the example above, the page navigates to itself. The first time you load it
(.../test.seam), there's no "bean" in any context, so it's blank. When you
click the button, it goes to the acti
How many pages do you have? You list some xhtml but don't tell where it came
from. What is your desired navigation?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970204#3970204
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
I guess I truly don't understand how contexts really work.
In the case of my example, I still don't understand why EVENT and PAGE scope
didn't work (when I tried setting the @Out scope). You mentioned something
about using navigation, but I'm not clear on how I could change the example
above s
Well this is kind of core to bijection and contextual components. @Out is a
general concept supported by all components over six searchable contexts.
Where did you think your object was going? I'm not trying to be mean, rather
trying to figure out where any new documentation should go. Is t
BTW, Was there something obvious in the manual that I missed that would have
cleared this up? It seems like the kind of thing that lots of people would
have trouble with (I'm trying not to feel like an idiot). Maybe it's a good
candidate for the problems FAQ?
View the original post :
http:/
I didn't knowingly use any navigation. I do have a pages.xml file, but the
"test.xhtml" page is not included in it since I was navigating there "directly"
by returning "/test.xhtml" from the seam action. Still, as long as I can use
CONVERSATION scope and everything works, I'm happy!
Thanks fo
@Out's scope defaults to the scope of the enclosing controller, in this case
the SLSB. SLSB have a stateless scope. I think that Seam may actually promote
the outjection of context variables of stateless components to event scope for
you (but I'm not positive).
Event scope is like JSP request
That worked perfectly!
Was it actually defaulting to "STATELESS" scope? I seem to remember that
somewhere.
BTW, what are EVENT and PAGE scope useful for (since they didn't work for me in
this example)?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970160
my guess is that you would have to outject to at least a conversation scope.
| try @Out(scope=ScopeType.CONVERSATION)
| private Bean bean;
| {/code]
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970153#3970153
Reply to the post :
http://www.jboss.com/
21 matches
Mail list logo
