That makes perfect sense. Luck for me by the time I use that feature,
it'll be on by default.
Thanks,
- Jason B.
Igor Vaynberg wrote:
you only need to set the setting if the fragment is going
to be rendererd by a different component then the one whose markup its
defined in.
for example, if you were going to use the fragment that is defiend in
your page to create a panel that you add to a column inside a datatable
- then you have to specify who the markup owner is - because the
component in charge of rendering the fragment ( in this case an Item
inside the datatable ) is not the same component in whose markup the
fragment is defined ( the page )
does that make any sense?
-Igor
On 5/9/06, JasonB
<[EMAIL PROTECTED]>
wrote:
Juergen
Donnerstag wrote:
> you need to register it. It is not yet activated by default
> application.getPageSettings().addComponentResolver(new
> FragmentResolver());
Strangely enough I just used fragments over the weekend and didn't have
to set this setting. What confused me was not having to add a component
to define that a fragment definition existed on the current page. After
I ignored that, using the fragment was amazingly simple.
- Jason B.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
|
