From the documents, you can see that the right way is to override the getId().
But it isn't correct to setId for the update() or remove()
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019152#4019152
Reply to the post :
I'm having the same problem, I'm starting with seam, using EntityHome, and as
far as I understand that only propagates the parameter to the page, still has
to be injected, I use
@RequestParameter Long userId ;
however my source is nearly identical to the one in the exaples of reference
For a working example, see examples/contactlist, or simply generate an
application using seam setup new-project generate-entities.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4015570#4015570
Reply to the post :
Finally i got it. pages
|page view-id=/search.xhtml
| param name=accountId value=#{accountHome.id}
converterId=javax.faces.Long /
|/page
| /pages
|
This means that the value of the accountId parameter will be set to the Id of
accountHome. This part was not obvious to
Hello
(3 questions at the body, please take a look)
I am interested if you are able to run any example with entityHome objects. For
me, the examples do not work (seam-pay,ui etc)
-
Could it be that i missunterstand the conzept?
So far i have used entityHome objects this way:
|
As Norman says, the applicaiton framework is just newer :) I use it
extensively, and mix and match between components.xml and extension when needed.
Baz - I use pages.xml to set the id - as described in the docs I believe.
View the original post :
anonymous wrote : Now, if we want to be able to display, update and delete
pre-existing Person entries in the database, we need to be able to pass the
entry identifier to the PersonHome. Page parameters are a great way to do that:
|
|
|
|
|
|
- that was the bit
anonymous wrote : to pass the entry identifier to the PersonHome
But than the example reads like:
pages
| page viewid=/editPerson.jsp
| param name=personId value=#{personHome.id}/
| /page
| /pages
If i understand it correctly, the personHome.id will be passed, not the entry
Sorry for jumping back in the middle here, but can you explain exactly the
problem you are having with the namespaced XML?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012606#4012606
Reply to the post :
I use the EntityHome exclusively and I can't live without it. It
significantely reduced my code and made everything much more maintainable. I
do have a lot of customer logic in my Class that extends EntityHome, but this
is expected. The main point is, I get full CRUD from one class and one
I'm going to start using them. Most of the grunt work is the same all over the
place so it would be cool if I can get it all from one class.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012645#4012645
Reply to the post :
Page parameters are now definitely the preferred approach. For example, the
redirect-to-login-and-then-redirect-back stuff depends upon page params.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012726#4012726
Reply to the post :
if i understand correctly there are two ways to set request parameter
1.annotation @RequestParameter
2. using page parameter in pages.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012723#4012723
Reply to the post :
Now i am really confused.
For me this is true
@RequestParameter in a java class says that something is injected that is a
Parameter. It never pass a parameter.
page parameter in pages.xml specify that a paramter should be passed.
So for me, they must be used in conjunction
To gavin: where is
anonymous wrote : My problem is to specify the id of an object. But i have
realized, that the possibility to set the id in components.xml is no more
there. With or without namespaces.
huh, why do you say that? use
View the original post :
hi gavin,
what was the rest of your posting?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012874#4012874
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4012874
___
jboss-user
Most of the examples were written before EntityHome came into existence. I
know I used it in seam-pay. There I subclassed EntityHome to add some custom
persistence logic and make use of the @RequestParameter. I also configured
some of the attributes in components.xml.
I think for
Hello,
Yes i use them. But only the Hibernate form.
For Seam 1.5.0 the application framework is described in chapter 10.
I was using them till the early beginning. The framework went to heavy
refactoring but it was usefull for me to follow. Now i am refactoring the code
to use the full power
18 matches
Mail list logo
