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,
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 t
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
I made some test to see if Aaron request for a markup file with
fragments only can be supported. There doesn't seem to be a simple
solution. A page referencing fragments defined in a Panel which is
also added to the Page defnitely doesn't work. We'd need a more
fle
I did a little experiment. The code down below is all you need to
implement your requirement of finding the fragments markup snippet on
a markup stream directly associated with the class.
/**
* A special Fragment (WebMarkupContainer) which searches for the
fragment
* i
i have used it quiet a bit and it seems to work fine. so i would be +1 for
making it enabled by default.
I can confirm that :) +1 for enabling by default.
Eelco
---
Using Tomcat but need to do more? Need to support web services, security?
Ge
Yeah, but a good framework should not get in the way of what you are trying
to do, right? I spent 2-3 hours trying to figure out a way to do this with
fragments :)
Others will probably hit the same wall someday. Panels did work for my
solution, but in this situation loading fragments as a "stan
On Mon, 2006-05-08 at 00:52 -0700, Igor Vaynberg wrote:
On 5/8/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
because it hasn't been extensively tested. As far as I'm aware you are
almost the only user of it. If you think it is stable e
On 5/8/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
because it hasn't been extensively tested. As far as I'm aware you arealmost the only user of it. If you think it is stable enough anddoesn't interfere with any other features and/or functionalities thanit can be enabled by default.
i have us
because it hasn't been extensively tested. As far as I'm aware you are
almost the only user of it. If you think it is stable enough and
doesn't interfere with any other features and/or functionalities than
it can be enabled by default.
I made some test to see if Aaron request for a markup file wi
why dont we activate it by default?-IgorOn 5/8/06, Juergen Donnerstag <[EMAIL PROTECTED]
> wrote:On 5/8/06, Aaron Hiniker <[EMAIL PROTECTED]
> wrote:> >> edit> view
>> >> throws:>> Caused by: java.text.ParseException: Unkown tag name with Wicket namespace:> 'fragment'. Might be yo
On 5/8/06, Aaron Hiniker <[EMAIL PROTECTED]> wrote:
edit
view
throws:
Caused by: java.text.ParseException: Unkown tag name with Wicket namespace:
'fragment'. Might be you haven't installed the appropriate resolver?
at
wicket.markup.parser.filter.WicketTagIdentifier
edit
view
throws:
Caused by: java.text.ParseException: Unkown tag name with Wicket namespace: 'fragment'. Might be you haven't installed the appropriate resolver?
at wicket.markup.parser.filter.WicketTagIdentifier.nextTag(WicketTagIdentifier.java:104)
at
On 5/8/06, Aaron Hiniker <[EMAIL PROTECTED]> wrote:
I am trying to encapsulate Edit/View/Select markup into one Component. I
want to set the mode, then add the Fragment to the parent container.
My first attempts went something like this:
parent.add( component.getFragment( "markupId", Mode.
it should work w/out the namespacethe problem is that the fragment tag is outside of the panel, it should be insideso
try that and see if it does the trick.-IgorOn 5/7/06, Aaron Hiniker <[EMAIL PROTECTED]
> wrote:
Yes, the "fragment provider" is a Panel. The markup looks like this:
Yes, the "fragment provider" is a Panel. The markup looks like this:
...
...
Since the component is providing fragments only, the "main" markup content is empty and I really don't wish/need to render it. Only the fragments that the container selects (Edit/View/etc).
Btw.. wicket
the only components that can supply fragments are the ones that have markup themselves - ie a page, a panel, or a border because the fragment has to live in someone's markup and those are the only ones that have it.
so is your component a panel, a border, or a page?-IgorOn 5/7/06, Aaron Hiniker <[E
I am trying to encapsulate Edit/View/Select markup into one Component. I want to set the mode, then add the Fragment to the parent container.
My first attempts went something like this:
parent.add( component.getFragment( "markupId", Mode.Edit ) );
... and in the component#getFragment
18 matches
Mail list logo
