[JBoss Seam] - Session-Variable in Conversation Context (or so...)
by dschaedl
Hi
I'm new to seam.
I'd like to have a List of object on one page and a second page to edit/create these object.
For now I have my List of objects - using @Datamodel and dataTable for display. Additionaly I have a List (@out, @in) to locally store the Objects in my Session.
To edit an Object I pass it to the editClass, edit it and save it - as a new conversation (@Begin, @End). I use the same list of Objects as before here.
I also use the same class to create new object and then add them to my list of object.
All work fine so far (most of it...)
My problem is the mixture of Session and Conversation-Context. The List of objects in the editClass is not the same as in the display-class. If I add a new Object to to object list in the conversation context it will not be displayed in my List-view because this uses the list from the Session context. (somehow clear what I'd like to say?)
hm.... I'd still like to use the conversation for the edit. Can they be merged into the session again? can I access a Session-variable in the Conversation?
How do I solve this the clean-Seam-way?
greatful for any hint
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062116#4062116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062116
18Â years, 9Â months
property from @OrderBy clause not found: Ruleset.number
by Burghard Britzke
I try to write a persistent unit
in Ruleset I wrote
public class Ruleset implements Serializable
{
...
@OneToMany(cascade={ PERSIST, REMOVE })
@OrderBy ("number ASC")
private List<Rule> rules;
my Class Rule looks like
public class Rule implements Serializable
{
...
private BigDecimal number;
during deployment I get the above error message.
I tried remove the @OrderBy anotation. but the error still remains.
even when I change the Order to "id asc" (id is a valid property of
both classes).
when I changed the Order to "ddddddd ASC", i got the above error
message for the property Ruleset.ddddddd.
when I changed back to "id asc" the error changed back to Ruleset.number
what does it mean?
18Â years, 9Â months