Hi.,
Let me see if I can answer to some of your questions:
#1: It has no special meaning for open-source community. These are just some markers used internally that are removed when the AWL template is parsed to memory anyway.
#2: This has several answers.
AWL - is just a template that takes bindings so you do not have to do all in JAVA and concat string you want to render to the UI
Look at for example at examples/Demo/components/RatingBar.
-You can either have all the HTML code in the AWL and not in the Java file here,
-Or you can have all in java as well check out the AWString where you override renderResponse.
- Or you can combine which is the best. You leave HTML to AWL and logic to java
- Depending on the situation and complexity. But if you define for each of your AWL component java file even if this java is empty you are OK.
do not forget to prefix your defined component with <x:
- If you can not find that element than try to prefix with AW like AWClientSideScript the AW is removed when using namespaces.
#3. Check out the renderPhase(). (AWComponentActionRequestHandler.handleRequest() => requestContext.generateResponse(); )Once this phase is called each corresponding component is called and content is rendered.
Its like a tree and it traverse down and ask each component to render its piece.
#4. yes you can combine HTML and AWL. AWL is just HTML
- AribaBasicPageWrapper is special case cuz this one defines the core layout you use in ariba web and since its defined as BrandingComponent, you can place your version AribaBasicPageWrapper.html into your resources /docroot/config/branding
and the system will pickup your version where you can define completely new layout
-> In this case to not mix AWL and html extensions in this branding folder this component is called .html - you can see there is overridden method shortTemplateName() that return custom name.
You can create as many components as you want ;-) There are no limits.
-FK