anonymous wrote : PS: If you would have posted the xhtml containing
Kundenverwaltung earlier, we could have made a phone call ;). It's really
weird how many guys are talking English to each other here (and often having
problems with it) though they could have it easier... in Thomas Heute's
Don't get confused by my last name, i am *very* French. Angry, stubborn and
such... ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3960650#3960650
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3960650
Remove @Valid annotation. s:validateAll does not require this. Pure hibernate
@Valid throws exception on invalid cases, that is not caught by the Seam. That
is why you will always get an exception page on invalid data.
View the original post :
Ops. I did not notice that was said already.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3960655#3960655
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3960655
___
jboss-user
Hi Gavin, you can checkout the facelet page i posted. i already use the
required=true attribute.
And the problem is not the check for nullability. The problem is that a new
database entity is created and the exisiting one is not updated when a
validaton fault appears.
View the original
I might be wrong, but I think the problem is that you use a STATELESS bean. And
this one forgets its state after invokation of a method. I.e. it forgets your
ClientPerson Entity and the id as well. So after every reload of the form a new
ClientPerson is generated - without an id - and so the
Hi bfo81m,
thanks for your tipps i am running through the same scope confusing. ;-)
i also tried to make my clientPersonAction component stateful, but the behavior
is the same.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3960273#3960273
Reply to the post
Hi petemuir,
anonymous wrote : make it conversational
what exactly? my clientPersonAction component or the newClientPerson member.
the whole form is limited to this one page. why should it be conversational?
I thougt a conversation is something like a sub-session for a whole bunch of
pages and
It's always useful to give an Editor Bean the Conversation Scope.
The method that's invoked by the preceding page (e.g. list page) should be
annotated with @begin(nested=true) and the method being called before leaving
the editor page (e.g. save) should be annotated with @end.
If you do so,
Ok, i will try this.
But: when i have a link in a template and a user doesnt press the save button
is the conversation still open?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3960351#3960351
Reply to the post :
Unfortunatley yes. But I think it's not likely that this will cause any
problems. If the user opens another editor page later then it will get its own
new conversation. The old conversation will remain in memory and get deleted
after a certain amount of time.
And there's even another problem
hi bfo,
I tried your approach but now i get no changes to my entity.
Steps:
1. I added a new entry
2. i click on the link and get on the edit page
3. i remove a property text that has a hibernate validator
4. i get the validator message
5. i fill in a new value
6. i click on the save button and
First: Forget what I just said about @Conversational. When clicking the back
button the browser loads the page from its cache.
Ok, now back to your prob. Maybe your list isn't up to date. Try it like this:
EditBean:
public String save() {
| ...
|
The list component is a stateless session bean.
| @Stateless
| @Name(clientPersonService)
| public class ClientPersonServiceImpl implements ClientPersonService {
|
| @PersistenceContext
| private EntityManager em;
|
| public List ClientPerson
Couldnt it be a Scope problem with the property?
| @In(required=false)
| @Out(scope=ScopeType.PAGE,required=false)
| @Valid
| private ClientPerson newClientPerson;
|
i have no clue.
View the original post :
Maybe. I only use @In(required=false) and @Out(required=false). If that doesn't
help, post your current code ;).
btw: @Valid is half-deprecated. So try s:validate(All) in the JSF instead.
That's what Gavin said ;).
View the original post :
hey bfo, when i remove the @Valid field i get curiouse class loader exceptions.
But i think here is a big confusion about the scope of objects (components and
their properties).
I thougt that my property is annotated with scope=ScopeType.PAGE because it
lives as long as i (or the user) is on
The Page Scope is shorter than you think. And it's got nothing to do with the
JSF page you're on. This was confusing to me, too ;).
The code on the first page isn't all I need. And it's been changed. In
particular I'd like to see the list page cause it should start the edit
conversation.
View
So this is something I hate about JSF validation. A JSF validator cannot be
used to test nullability.
You need to say h:inputText required=true /
Sucks, huh?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3959974#3959974
Reply to the post :
19 matches
Mail list logo
