I'm having some namespace problems when using RequestCycle.getPage() in
Tapestry 4.0 beta 3.
In my application specification file, I'm referencing a library - we'll call
it "libraryA". The library specification file for this library includes a
second library - "libraryB". LibraryB includes a page named "ExamplePage"
and that page is declared in the libraryB's spec file.
The problem I'm having occurs when a page in LibraryA tries to call
getRequestCycle().getPage("libraryB:ExamplePage"). The error I get is,
"Library 'libraryB' not found in application namespace". If I a reference to
LibraryB directly into the application specification file I get a different
error - "Library 'libraryB' not found in namespace 'libraryB'."
Application Spec:
<application name="exampleApp">
<library id="libraryA"
specification-path="/com/example/libraryA.library"/>
</application>
LibraryA Spec:
<library-specification>
<library id="libraryB"
specification-path="/com/example/libraryB/libraryB.library"/>
</library-specification>
LibraryB Spec:
<library-specification>
<page name="ExamplePage" specification-path="ExamplePage.page"/>
</library-specification>
Hope my explanation of the problem wasn't too confusing, I tried to simplify
it as much as possible.
Thanks in advance for the help,
John Barton
