-
1. Re: Problems begining with seam
joe May 14, 2008 1:56 AM (in response to ashvini)May be an issue with the query returning an empty set. Does the table render if you do the following
rendered="#{not empty addressBook.resultList}
If not, then most likely your query is returning an empty list. Confirm your ejbql returns results and then it should work.
-
2. Re: Problems begining with seam
ashvini May 14, 2008 3:25 PM (in response to ashvini)thanks for the prompt reply.
Actually the control does not go into the method which is fetching the list, i wrote some println before and after the createQuery method, but its printing neither.
The query is working fine as this code was working before without seam.
hencei feel there is some other configuration which i am probably missing out.
Any suggesstions on this.Thanks once again
-
3. Re: Problems begining with seam
joe May 14, 2008 7:46 PM (in response to ashvini)Okay, where is your list being created? Is the backing SLSB properly annotated with @Name? If so, then how are you calling it from the JSF page? I've found @DataModel to be a helpful seam tool for populating JSF tables. Check out the seam documentation for details. I hope this helps...
-
4. Re: Problems begining with seam
ashvini May 14, 2008 8:13 PM (in response to ashvini)My list is getting created in SLSB and is properly annotated.
Also i am using a @DataModel and @factory to display the same.
Thanks a lot for your help.
-
5. Re: Problems begining with seam
ashvini May 14, 2008 11:25 PM (in response to ashvini)instead of printing a datalist, i have made an input paramter and i am just checking if i am able to read the input in SLSB.
I am getting following error
org.apache.jasper.el.JspPropertyNotFoundException
Target unreacheble, indentifier manualTag resolved to null.manualTag is @name for the entity bean ManualTag.
Why is the entity bean resolved to null??
can someone please point out why this could be??