-
15. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
clerum Feb 16, 2010 11:13 AM (in response to ilya_shaikovsky)Any luck with the ear?
Not sure what else I can provide on this.
-
16. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
ilya_shaikovsky Feb 16, 2010 1:19 PM (in response to clerum)Finally we found the problem. It's caused by the fact that you duplicated richfaces-impl in war and ear libraries(which caused classloading problems already mentioned at forum and wiki faq). We removed unnesessary one from EAR and moved the car model class to web-inf classes. After that all started to works fine without any changes. Please consult documentation for more information. -
17. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
clerum Feb 16, 2010 1:43 PM (in response to ilya_shaikovsky)Thanks for the update. I'll dig into that.
It seems out of sync with what seam-gen sets up as everything gets complied and put into a jar inside the ear.
sandbox.ear/sandbox.jar
Your saying I need move these specific classes to
sandbox.ear/sandbox.war/WEB-INF/classes
Correct?
-
18. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
nbelaevski Feb 16, 2010 1:57 PM (in response to clerum)Yes, to sandbox.ear/sandbox.war/WEB-INF/classes. -
19. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
clerum Feb 16, 2010 2:10 PM (in response to nbelaevski)Isn't that going to cause me all kinds of other class loading issues since my entites which are displayed in the extendedDataTable will be in the ear/jar
Is it fair to say that the ExtendedDataTable isn't really compatiable with an ear deployment or am I missing something?
-
20. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
nbelaevski Feb 17, 2010 7:15 AM (in response to clerum)No, data model doesn't need to know what classes are really there. DataProvider takes care of this. -
21. Re: Retreiving Row Data w/ ExtendedDataTable Multi-Selection
clerum Mar 4, 2010 11:18 AM (in response to nbelaevski)What I ended up doing was placing all my libs for the ear into project.ear/lib/
That seems to be the easiest way to handle this with an ear project.