Bindings in <w:BasicPageWrapper> are being ignored for MetaUI/JPA application's landing page (front door)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create an .awl employing <w:BasicPageWrapper>; include bindings
(windowTitle="My Title", styles=..., etc)
2. Set the above awl to be the landing (or "front door") page for the
application (as the first listed, visible awl in the application.oss)
3. Launch the application

What is the expected output? What do you see instead?
Expected: Provided binding values (like windowTitle, above). 
Actual: "AribaWeb Demonstration"

Note: Related to this, but probably not the answer (I edited but it did not
fix): I believe there is an error in BasicPageWrapper.awl. Line 201:
windowTitle="$windowTitle" instead of windowTitle="$^windowTitle" (it
should be reading the parent binding, right?) If I change it to
$^windowTitle, it still does not read from my awl, but it does not show
"AribaWeb Demonstration".

What version of the product are you using? On what operating system?
AW 5.0 GA (p4)
Win32XPProSP3
Eclipse 3.5.2 JEE

Please provide any additional information below.
If I make an different awl the "front door" page, and, for example, launch
my awl from the "front door" page, the bindings work as expected.

Original issue reported on code.google.com by morton.t...@gmail.com on 25 May 2010 at 8:27

[GoogleCodeExporter]

Note: The ONLY way I have found to specify bindings for a MetaUI's front door 
page is
via application.oss. Example:
@module="LandingPage" {
  component="LandingPage";
  bindings:{
    windowTitle:"My Title"; 
    . . .
    };
  }

In addition, the MetaUI application seems to automagically wrap the front door 
page
in a BPW. (So, my provided BPW is essentially ignored via code in BPW.)

-Morton

Original comment by morton.t...@gmail.com on 25 May 2010 at 8:46

[GoogleCodeExporter]

Note: Line 201 of BasicPageWrapper.awl must be fixed per above to allow 
windowTitle
to be passed in via Application.oss bindings.

Original comment by morton.t...@gmail.com on 25 May 2010 at 9:11

[GoogleCodeExporter]

Note: Found requirement for bindings to work in awl: @module entry in 
Application.oss
for landing page MUST contain homePage:[home page (.awl)]! (Adding this made the
bindings work again . . . except windowTitle  -- the windowTitle binding in
BasicPageWrapper.awl still needs to be fixed.)

-Morton

Original comment by morton.t...@gmail.com on 26 May 2010 at 1:05

[GoogleCodeExporter]

The window title is not read from the binding at the top level.  It is fetch 
from the StringHandler for "applicationName"

See here for the reference:
http://code.google.com/p/aribaweb/source/browse/trunk/src/widgets/ariba/ui/widge
ts/PageWrapper.java#101

The string handler is implemented in MetaUI which exposing the pageTitle meta 
ui property on a module:
http://code.google.com/p/aribaweb/source/browse/trunk/src/metaui/ariba/ui/meta/c
ore/Initialization.java#110

Example usage:
@module=Home  {
   pageTitle:"AribaWeb - More App, Way Less Code!";
}

Original comment by kingsley...@gmail.com on 10 Mar 2011 at 12:06

• Changed state: Invalid