-----Original Message-----
From: Adrian Crum [mailto:[email protected]]
Sent: Friday, June 10, 2011 7:26 PM
To: [email protected]
Subject: Re: Totally Newbie: is this a problem of screens.render? Please help me

Also, there should be a space between html-template and location.

-Adrian

On 6/10/2011 1:21 PM, Erwan de FERRIERES wrote:
> Le 10/06/2011 14:07, VuTheCuong a écrit :
>> Dear all
>> Currently I'm reading "apache ofbiz development the beginner's
>> tutorial".
>> I installed ofbiz 4.0 as required by the book and I had problem at
>> the section "Cleaning Up in the "party" Component".
>> To be hornest, I did exactly as same as the book guided as follow,
>> but the error still there, Please help me to solve this problem. I'm
>> really really stuck and need your help.
>> I attached related files for your reference. If you need other info,
>> please let me know.
>>
>> The Book guide:
>> ---------------------------------------
>> Cleaning Up in the "party" Component
>> We take the opportunity here to clean up the mess we made in the
>> party component in Chapter 2. Edit
>> ${component:learning}\widget\partymgr\OurPartyScreens.
>> xml and insert a new screen widget:
>> <screen name="editcontactmech.extend"> <section> <widgets>
>> <platform-specific><html>
>> <html-templatelocation="component://learning/webapp/
>>
>> partymgr/party/editcontactmech.extend.ftl"/>
>> </html></platform-specific>
>> </widgets>
>> </section>
>> </screen>
>
>>
>
> Hi,
>
> the error is in the stacktrace :
> Element type "html-templatelocation" must be followed by either
> attribute specifications, ">" or "/>".
>
> As you are in XML, you can't cut your text, it will insert spaces in it.
> So you should write:
>
> <platform-specific><html>
>
> <html-templatelocation="component://learning/webapp/partymgr/party/edi
> tcontactmech.extend.ftl"/>
>
> </html></platform-specific>
>
> and this should be good.
>
> Cheers,
>
Dear Adrian Crum and Erwan de FERRIERES
These worked for me. Thank you very much. I'm continuing my learning of the 
book.
Onece again, thank you.

Reply via email to