Step - 2 : Write CrUD operations for person entity.this is a code for createPracticePerson in services.xml
shows the how to do the createPraticeperson but leaves you go to write the update and delete It assumes you have read the documentation on the service engine and view the video on the framework. there are also many hits on google about updatePracticePerson ========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Patrick sent the following on 5/21/2010 9:25 AM: > Did you define it in services.xml? Did you create the function in the > file *Services.java ? Did you rebuild the project and restart ofbiz? > > > On Fri, May 21, 2010 at 7:44 AM, Matias Kainulainen <[email protected]> > wrote: >> Hi, >> >> I'm trying to finish the part 2 of the tutorial but I haven't found where >> the updatePracticePerson service is defined in the tutorial. Thus, I'm >> recieving the following error message when I try to open the personform >> page. >> >> org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen >> [component://practice/widget/CommonScreens.xml#CommonPracticeDecorator]: >> java.lang.RuntimeException: Error rendering included form named >> [ListPersons] at location [component://practice/widget/PracticeForms.xml]: >> java.lang.IllegalArgumentException: Error finding Service with name >> updatePracticePerson for auto-fields-service in a form widget (Error >> rendering included form named [ListPersons] at location >> [component://practice/widget/PracticeForms.xml]: >> java.lang.IllegalArgumentException: Error finding Service with name >> updatePracticePerson for auto-fields-service in a form widget) >> >> Can someone help me on how to define the service required in the tutorial? >> >> Thanks, >> Matias Kainulainen >> >
