[EMAIL PROTECTED] wrote : petekol wrote : [EMAIL PROTECTED] wrote :
longer scope does not work for Query component.it's DataModel handling
makes it not possible
| |
| | In what way? Yes, you need to refresh the datamodel of course.
|
| i mean not generally
[EMAIL PROTECTED] wrote : This is the JSF lifecycle, it is needed. You
could work around this by putting the query into a longer scope than
request/event. This problem occurs in normal queries too.
|
| We should probably merge the lazy loading code from seamdiscs into a seam
module and
seamdiscs example application is a good example how to implement pagination
with data lazy loading of readonly tables. I can see though that issued sqls
are far far from optimal:
seam-discs/discs.seam:
11:05:22,512 INFO [STDOUT] Hibernate: select count(*) as col_0_0_ from Disc
disc0_
I think that seam lookups objects by global names makes some problems specially
for not Jboss ASs.
Is there realy a reason for that? Yes, ejb name is no unique to EAR but to JAR.
Duaring seam scanning jars it can put this info in a component.
Are any plans to go to portable JDNI lookup
[EMAIL PROTECTED] wrote : All beans instantiated during a conversation go
into the current (ie. most nested) conversation.
it is clear -)
bean1:
showBean2 = false;
@Begin(join=true)
m1() {
some code here;
showBean2 = true;
}
bean2:
@Begin(nested=true)
m3() {
some code here;
}
sorry that i am a bit noisy here -)
how can a button/link end a nested conversation (by execution of a method with
@end) and then execute some method (refresh) in parent conversation in elegant
way?
View the original post :
[EMAIL PROTECTED] wrote : It is almost always wrong to use a constant
conversation id in @Begin. Have you actually properly understood the use of id
in @Begin?
Yes, I hope I understand it -), in this case it is for modal action of creating
a new entity but for test purpose anyway.
Can you
in ConversationInterceptor.endOrBeginLongRunningConversation
getOutcomeForConversationId is called before beginConversationIfNecessary that
is wrong because it calls updateCurrentConversationId on old conversation.
so i shifted beginConversationIfNecessary(method, result); up and it works now.
is not possible as far as i understand.
I would like to have possibility to have many nested conversations for
different regions of a page. Let's say parent - many children CRUD where a user
can edit many children simultaneously.
With current Seam model i can not come up with a
petekol wrote : @Begin(id=newEmp, nested = true, ifOutcome = newPage)
| kills it's parent conversation and creates two new conversations where
newEmp is a root one.
|
| @Begin( nested = true, ifOutcome = newPage) works without problems.
|
| could it be a bug?
sorry, seam does
so, a single request can not create new conversation with nested one, right?
may be this annotation should do it @Begin(join=true, nested=true)? -)
the problem i have then is how to say in what conversation a new beans go
View the original post :
how can i put bean2 in to nested context after a user press m1,m3 buttons so
that the bean is read-write?
bean1:
showBean2 = false;
@Begin(join=true)
m1() {
some code here;
showBean2 = true;
}
bean2:
@Begin(nested=true)
m3() {
some code here;
}
index.xhtml
h:form
i have found out that a component needs a @Name dummy annotation for
@DataModel
@DataModelSelection
@Logger and may be other to work properly if i create a component from
components.xml. i use jboss-seam-1.0.1.GA
View the original post :
@Begin(join=true)
m1() {
some code here;
m2
}
@Begin(nested=true)
m2() {
some code here;
create component here that belongs to nested conversation;
}
does not create nested conversation, should it?
View the original post :
the root of the problem i have is
1) why bean2 is created when the page is rendered first time indepandantly from
rendered property
2) why click on m1 does not create conversation + nested conversation
3) i do not know how to instanciate new bean2 in nested conversation
bean1:
showBean2 =
can anyone can comment on this? i still can not get @DataModel working for a
bean defined in components.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3958554#3958554
Reply to the post :
as my first seam sample appl i would like to create a CRUD component with
parent/child (or many configurable children) functionality.
If i use @DataModel in component the annotated property is not available on the
page. I can access methods and other props of the component thought. It does
17 matches
Mail list logo
