When Locating the Markup for a Page, I want to know the corresponding class
(associated with the page/markup).
Currently Im directing Wicket to my Custom Markup location with the
following code in "Application":

...
final IResourceStreamLocator defaultLocator =
super.getResourceSettings().getResourceStreamLocator();
return new ResourceStreamLocator(){
                @Override
            public IResourceStream locate(final Class<?> clazz, final String
path) {
               ...
               //Figure alternate path by reading path
               ....
               //if valid URL not found use the defaultLocator
               ...
            }
...


I want to get the associated Component class. I know the String "path"
represents the ClassPath, but its still a String and contains Locale Junk &
an extension with it. 
Is there someway I can get Class<?> directly so I don't have to do String
manipulations?


Another thing I want is, when the dynamicPage (which --extends-->
TemplatePage --extends-->  WebPage) appears it knows its associated
"Template" DataStructure details.
TemplatePage - Wicket Component
Template - Data Structure

TemplatePage <---> Template

When Mounting, on init() in Application:
application.mount(new QueryStringUrlCodingStrategy(pagePath, [Templace
Class] ));

During the mount itself, is there anyway for me to associate/pass models to
the pages which will be constructed?
Wicket uses no-arg Contstructors for WebPage, but what if I want to pass a
WebPage contexutal info specific to the Page while mounting? (Can i do
this?) --> I believe this would be efficient


-----
Software documentation is like sex: when it is good, it is very, very good; and 
when it is bad, it is still better than nothing!
--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Advanced-Mounting-Markup-Location-tp3705032p3705032.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to