[CVE-2020-11976] Apache Wicket information disclosure vulnerability

[svenmeier]

Severity: Important

Vendor:
The Apache Software Foundation

Versions Affected:
Apache Wicket 7.16.0, 8.8.0 and 9.0.0-M5

Description:

By crafting a special URL it is possible to make Wicket deliver 
unprocessed HTML templates.
This would allow an attacker to see possibly sensitive information 
inside a HTML template that is usually removed during rendering.
For example if there are credentials in the markup which are never 
supposed to be visible to the client:


  
 some secret
  

The application developers are recommended to upgrade to:
- Apache Wicket 7.17.0

- Apache Wicket 8.9.0

- Apache Wicket 9.0.0


Credit:
The vulnerability has been found and reported by Mariusz Popławski from 
Afine.


Apache Wicket Team

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: FormComponents and feedback messages inside a listview

[svenmeier]

http://cwiki.apache.org/WICKET/listview-and-other-repeaters.html#ListViewandotherrepeaters-Usingformcomponentsinarepeater


Wim Vandenhaute wrote:
> 
> Hello List,
> 
> I have ran a couple of times whilst developing some pages using wicket
> into
> the following issue.
> The page will contain a Form, containing a ListView of FormComponents
> The FormComponents are created within the ListView with a feedback panel
> attached to each of em.
> The feedback panels are attached to the FormComponents using a
> ComponentFeedbackMessageFilter.
> 
> On submit, validation fails for some FormComponents, and the feedback
> messages are generated ok, but are nevered rendered due to the original
> FormComponent not being found.
> This is understandable as they are created inside the ListView so when
> wicket tries to find the reporter of the feedback message, it does not
> find
> it anymore, new FormComponents were created.
> So the solution to this is to create them outside the listview so they
> dont
> get regenerated on each rendering.
> 
> I was wondering if this is the correct way to handle such a situation, or
> should I be using a different approach to not fall into this?
> 
> Kind regards,
> Wim.
> 
> 

-- 
View this message in context: 
http://old.nabble.com/FormComponents-and-feedback-messages-inside-a-listview-tp27604968p27606028.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: add javascript after AjaxLazyLoadPanel finishes rendering - (was: onAfterRender called twice in AjaxLazyLoadPanel)

[svenmeier]

class SomePanel extends Panel implements IHeaderContributor
{
public SomePanel(String id)
{
super(id);
}
 
public void renderHead(IHeaderResponse response)
{
response.renderOnDomReadyJavascript("alert('hello');");
}
}
 
Sven


Steve Swinsburg-3 wrote:
> 
> Hi Lionel,
> 
> Thanks and yes, thats what I am trying to do, attach some javascript after
> something has rendered. So I attached an AjaxEventBehaviour to it and now
> have this:
> 
> add(new AjaxLazyLoadPanel("myPanel") {
> 
>   @Override
>  public Component getLazyLoadComponent(String markupId) {
>   return new SomePanel(markupId);
>  }
> }.add(new AjaxEventBehavior("onload"){
> protected void onEvent(AjaxRequestTarget target){
>   target.appendJavascript("alert('hello)';");
> }
> }));
> 
> but the javascript is never fired.
> 
> Any more ideas?
> 
> cheers,
> Steve
> 
> 
> On 21/01/2010, at 3:09 PM, Lionel Port wrote:
> 
>> Hi Steve,
>> 
>> Are you trying to do this..
>> 
>> http://cwiki.apache.org/WICKET/adding-javascript-from-wicket.html
>> 
>> with an onload event instead of onblur, or do I misunderstand.
>> 
>> regards,
>> Lionel
>> 
>> On Thu, Jan 21, 2010 at 2:56 PM, Steve Swinsburg
>>  wrote:
>>> So  overriding onAfterRender for a component doesn't just override it
>>> for that instance of the component?
>>> 
>>> Also I can see the markup is being added to the end of the page after
>>> the closing HTML. However, the Javadocs say it is meant to be called
>>> after after the actual component is finished rendering. So it look s
>>> like onAfterRender is not what I need.
>>> 
>>> Can I attach to a different phase in the render lifecycle to call the
>>> javascript when that specific panel has just finished rendering?
>>> 
>>> thanks,
>>> Steve
>>> 
>>> 
>>> 
>>> 
>>> On 21/01/2010, at 2:52 PM, Igor Vaynberg wrote:
>>> 
 you are writing out javascript after every component render...
 
 perhaps you should keep a boolean flag that marks if you rendered the
 js yet or not.
 
 alternatively you can add a behavior to the panel with istemporary() {
 return true; }
 
 -igor
 
 On Wed, Jan 20, 2010 at 7:24 PM, Steve Swinsburg
  wrote:
> I have an AjaxLazyLoadPanel and want some javascript to fire after its
> loaded it's contents:
> 
> I assumed I could override onAfterRender and add my javascript like
> so:
> 
> add(new AjaxLazyLoadPanel("myPanel") {
> 
>@Override
>public Component getLazyLoadComponent(String markupId) {
>return new SomePamel(markupId);
>}
> 
>@Override
>protected void onAfterRender() {
>JavascriptUtils.writeJavascript(getResponse(),
> "alert('hello');");
>super.onAfterRender();
>}
> 
> });
> 
> Except it is called twice, it looks like once when the page is loading
> and then again when the actual panel has been loaded.
> 
> Is there another way to achieve what I want?
> 
> thanks,
> Steve
> 
> 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>> 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>> 
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/onAfterRender-called-twice-in-AjaxLazyLoadPanel-tp27252299p27253924.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: correct way to call necessary javascript initialization when a component is added via ajax

[svenmeier]

Why so complicated?

@Override
public void renderHead(IHeaderResponse response) {
response.renderOnDomReadyJavascript(init_slider_js());
} 


Peter Ross-6 wrote:
> 
> On Wed, Nov 11, 2009 at 3:48 PM, Jeremy Thomerson
>  wrote:
>> On Tue, Nov 10, 2009 at 10:38 PM, Peter Ross
>> wrote:
>>
>>> Hi,
>>>
>>> I'm implementing a control which consists of an integer field and a
>>> slider where the slider comes from jquery UI.
>>>
>>> My question is that whenever the component is refreshed via ajax, you
>>> need to call the js initialization function.
>>>
>>> I've done this by adding a behaviour which determines the request
>>> target, if it's an AjaxRequestTarget it adds the init js to the target
>>> otherwise it outputs it in the header.
>>>
>>> Is this the correct way to do it?  Is there a simpler way?
>>>
>> Yes - this looks fine.  There are multiple ways of accomplishing it, but
>> this one is fine.
>>
> Could you elaborate on what some of the other ways are?
> 
> Just enough key words so that I can do the google search would be fine :)
> 
> Peter
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/correct-way-to-call-necessary-javascript-initialization-when-a--component-is-added-via-ajax-tp26295973p26297483.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: another serialization question

[svenmeier]

Then just keep the criteria to get those items in your components?


samb0057 wrote:
> 
> The value objects are not simple attributes of an entity. Let me explain
> what they do (a little simplified but the fundamentals are there).
> 
> We have a research module that performs pricing research.
> 
> ResearchItem
>   CellPhoneResearchItem
>   IPodResearchItem
>   LaptopResearchItem
>   Etc
> 
> Since the identity of these research items is defined solely by their
> attributes they are implemented as value objects. I know this is different
> from your everyday value object (eg Address) Does this sound like maybe a
> problem that should be addressed in the domain model?
> Value objects were chosen since it makes it much easier in many other
> areas to just create a new research item, rather than call repositories to
> load old ones (impossible in some places). No point in loading something
> you know all the attributes of.
> 
> The only way to get them reliably is to call
> ResearchItemGenerationService.generateResearchItems()
> 

-- 
View this message in context: 
http://old.nabble.com/another-serialization-question-tp26295325p26297467.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Combination CompoundPropertyModel and ChoiceRenderer on DropDownChoice gives problems

[svenmeier]

You want to select one value from a list of values, so obviously everything
has to have the same type.

These 'IdDescrBeans' smell like Struts, such constructs are not needed.
What's wrong with the following:

  List genders = new ArrayList();
  list.add("M");
  list.add("F");
  form.add(new DropDownChoice("gender", genders) {
protected boolean localizeDisplayValues() {
  return true;
}
  });

Creating an enum would be a nice alternative to strings though.
Put the following keys in you page's property file:

  gender.M = male
  gender.F = female

i18n for free.

Sven


Xavier López-2 wrote:
> 
> Hi Ann,
> 
> I've also encountered this problem, but with RadioChoice instead of
> DropDownChoice.
> 
> This is the thread I started about it:
> 
> http://mail-archives.apache.org/mod_mbox/wicket-users/200911.mbox/browser
> 
> After all this thread, I still don't know what should I do to model, for
> instance, a gender radioChoice which would be backed by a String property
> ("M" of "F"), providing a list of choices (multilingual) with IdDescrBeans
> like you propose.
> Should I change my bean's 'String gender' property to 'IdDescrBean gender'
> ?
> Why should I store description's information on my model entity ?
> 
> Although I agree with having same object's on choices and model when it's
> about more complex data...
> 
> Possible solutions I've thought of so far:
> 
>- Ideally, do not use different object types in compundpropertymodel's
>bean and choice List. Use same object type instead.
>- When using RadioChoice, it works if you substitute it with a
> RadioGroup
>and Radio's, using the 'id' property as the Radio's model and the
>'description' property as the label's model. However, when it's about
>DropDownChoice, I'm clueless about it at the moment (already having
> problems
>with them).
>- Provide a list of choices in which each element is an Id, and then
>provide a ChoiceRenderer display expression such that gets the proper
>description (I don't like that at all).
>- Modify IdDescrBean so that it returns the 'id' property in its
>'toString' method, and, assuming the compundpropertymodel's bean
> related
>property is String, provide an implementation for some useless method
>('trim' for example), so that it returns the desctiption. Then, in the
>ChoiceRenderer, you can set the displayExpression to 'trim()', which
> will
>ensure that when the component model's object is a String, this error
> will
>not happen (also, it will return the trimmed id as description, but
> that
>will have no effect). But there is more to it, in order to achieve
>AbstractSingleSelectChoice's getModelValue() to identify the selected
> choice
>element, it calls 'indexOf' on the Choice List, using the
>compundpropertymodel's bean related property value. That is, it
> searches in
>a List of IdDescrBean a String. Problem is 'indexOf' invokes
>'searchedElement.equals(choices[i])', which will never return true. I
> got it
>to work overriding 'getModelObject' and doing this search with the
> opposite
>comparation (choices[i].equals(searchedElement), and providing a
> suitable
>implementation of 'equals' in the IdDescrBean class... But that's
> extremely
>hacky and ugly, and... it would not work for ListMultipleChoice, as
>getModelValue is final...
> 
> 
> 
> 2009/11/9 Ann Baert 
> 
>> I've created a jira issue with more information and an example for this
>> problem:
>> https://issues.apache.org/jira/browse/WICKET-2565
>>  DISCLAIMER 
>>
>> http://www.tvh.com/newen2/emaildisclaimer/default.html
>>
>> "This message is delivered to all addressees subject to the conditions
>> set forth in the attached disclaimer, which is an integral part of this
>> message."
>>
> 
> 
> 
> -- 
> "To err is human; to make real mess, you need a computer."
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Combination-CompoundPropertyModel-and-ChoiceRenderer-on-DropDownChoice-gives-problems-tp26262235p26266089.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wicket Wizard Functionality (Extensions)

[svenmeier]

See https://issues.apache.org/jira/browse/WICKET-2542


Corbin, James-2 wrote:
> 
> Hi Sven,
> 
> What exactly am I supposed to implement in the
> AjaxFormSubmittingBehavior.onSubmit(...)?  I've tried everything I can
> think of and the popup still dismisses(closes) when I press the "Next"
> button after completing step 1.
> 
> J
> 
> -Original Message-
> From: Sven Meier [mailto:s...@meiers.net] 
> Sent: Saturday, October 24, 2009 11:35 AM
> To: users@wicket.apache.org
> Subject: Re: Wicket Wizard Functionality (Extensions)
> 
> Hi James,
> 
> regretfully the standard Wicket dialog doesn't support non-AJAX request 
> - perhaps this restriction applies to the YUI version too?
> 
> You'll have to ajax-ify the wizard - see Wizard#newButtonBar(). I've 
> done it for our project but I don't have the code available at the
> moment.
> 
> Regards
> 
> Sven
> 
> Corbin, James wrote:
>> Hi Sven,
>>
>> I'm running the wizard in a modal popup (YUI).
>>
>> One other thing that is happening is when I press the next button in
> the
>> wizard that should take me to the next step, my dialog closes.  I'm
> not
>> sure what would cause the dialog to dismiss/close in this manner.
>>
>> J.D.
>>
>> -Original Message-
>> From: Sven Meier [mailto:s...@meiers.net] 
>> Sent: Saturday, October 24, 2009 8:32 AM
>> To: users@wicket.apache.org
>> Subject: Re: Wicket Wizard Functionality (Extensions)
>>
>> Hi James,
>>
>>  >but Wicket's implementation seems to only evaluate the condition at
>> step
>>  >creation and not when I'm changing the state of my radios.
>>
>> see NextButton#isEnabled() and FinishButton#isEnabled(). As far as I
> can
>>
>> see these method should support your usecase. Implementing ICondition
> as
>>
>> you did seems right to me.
>>
>> I assume you're notifying changes of the current radio choice to the 
>> server via AJAX? Are you adding the whole wizard to the request so the
> 
>> button bar is re-rendered?
>>
>> Sven
>>
>> Corbin, James wrote:
>>   
>>> I am writing a two step wizard using wicket's wizard implementation
>>> 
>> and
>>   
>>> having some issues.
>>>
>>> I am using Wicket 1.4.1.
>>>
>>> My first wizard step contains a RadioChoice with 3 options. 
>>>
>>> I would like the Finish Button to be enabled on Wizard Step 1 if
>>> 
>> either
>>   
>>> the first or second radio choice is selected.  Also, if the first or
>>> second radio is selected, then the next button should not be enabled.
>>>
>>> If the 3rd Radio Choice is selected, then I want the Finish Button to
>>> 
>> be
>>   
>>> DISABLED, and the next button to be enabled so the user can go to the
>>> final step.
>>>
>>> My question
>>>
>>> I'm not sure how to set this up in wicket's wizard implementation.  I
>>> tried specifying an ICondition on step two, to only make that step
>>> available if the selected type is Radio Choice Option 3 from step
> one,
>>> but Wicket's implementation seems to only evaluate the condition at
>>> 
>> step
>>   
>>> creation and not when I'm changing the state of my radios
>>> 
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>   
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Wizard-Functionality-%28Extensions%29-tp26035189p26057485.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Tree-table css/layout problem when the label of the tree-node is long

[svenmeier]

Hi Zoltan,

this is a known limitation of Wicket's tree implementation.

Please take a look at http://code.google.com/p/wicket-tree/ for an
alternative solution.

Sven


zoltan luspai wrote:
> 
> Dear Wicketeers,
> 
> I am using the wicket's "standard" tree-table widget, and it works fine; 
> except when a tree-node has longer (wider) text which does not fit to 
> the available space, then this text becomes invisible. Any ideas how to 
> fix this, preferably using some css alterations? The label should 
> appear, but it should be just clipped (no scrollbars etc...).
> 
> Thanks in advance.
> 
> Zoltan
> 
-- 
View this message in context: 
http://www.nabble.com/Tree-table-css-layout-problem-when-the-label-of-the-tree-node-is-long-tp25765663p25766102.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Conversation scope in wicket

[svenmeier]

What is this 'conversation' all about?

It doesn't seem to be a known concept in any GUI guideline I know (e.g.
Apple's Human Interface Guidelines). Neither does wikipedia list it under
http://en.wikipedia.org/wiki/GUI_widget.

This is what wikipedia is saying about Seam's conversation: 'The default
Seam context is conversation which can span multiple pages and usually spans
the whole business flow, from start to finish.'
This seems to describe a http://en.wikipedia.org/wiki/Wizard_(software) .

IMHO 'conversation' is a buzzword invented for those who still think a web
UI consists of a sequence of HTML pages only.
Back in 2000 the same guys invented 'mvc-2' and told us that a UI can be
built on actions only.

Just my rant (worth 2 cents or less).

Back to Wicket and wizards:
For a wizard I'd suggest to use a single Wicket page, replacing components
as you step through it.
Note that Wicket extensions provide a wizard component, but you can easily
roll your own implementation.

Sven

> Hican this functionality added to the standard wicket?
> actually much of seam popularity came from supporting conversation
> scope...,
> so i think that adding explicit wicket support will have momentum
> i think that having just a store for conversation objects will be a good
> begin
> then we may add apis like beginConversation, endConversation
> ,joinConversation,mergeConversation
> ,suspendConversation,resumeConversation
> and other concepts like workspace
> what do u think?
> Joe

-- 
View this message in context: 
http://www.nabble.com/Conversation-scope-in-wicket-tp24078377p24088943.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Twenty Six Wicket Tricks

[svenmeier]

I'd like to review your Wicket tricks too.

Regards

Sven


Jonathan Locke wrote:
> 
> 
> Thanks, I appreciate the offer to review. I will get back to you in some
> number of weeks. ;-)
> 
> Yeah, the JavaOne talk I submitted is indeed on Wicket.
> 
> Jon
> 
> 
> jWeekend wrote:
>> 
>> Jonathan,
>> 
>> We're finally starting work on a more advanced jWeekend Wicket
>> course/workshop to complement our existing Wicket training so we would
>> certainly look into buying several copies of such a book. 
>> 
>> Our Wicket courses have been running for 18 months and for much of that
>> time we have been buying Martijn & Eelco's  http://manning.com/dashorst
>> Wicket In Action  (since the WiA MEAPs) as gifts for most attendees and
>> also occasionally for our  http://jweekend.co.uk/dev/LWUGReg/ London
>> Wicket Event  delegates (next event on Feb 4, BTW - registration
>> page/details coming soon). 
>> Once we've reviewed the contents, we would certainly consider buying
>> licences for the PDF of your new book for students attending our Wicket
>> training. 
>> 
>> If you need reviewers, I am sure we can help with that here, and can no
>> doubt also get some meaningful feedback to you from our more advanced
>> London Wicket Event delegates if you like.
>> 
>> Regards - Cemal
>>  http://www.jWeekend.co.uk jWeekend 
>> 
>> PS  Is your JavaOne talk on Wicket?
>>  
>> 
>> Jonathan Locke wrote:
>>> 
>>> Well, over the break here I've started something I swore I would never
>>> do again (well, two things, if you include the JavaOne talk I'm working
>>> on). I'm writing a (hopefully relatively short) book. It's called
>>> "Twenty-Six Wicket Tricks". Each trick in the book (lettered from A-Z)
>>> demonstrates something that people typically want to do and in the
>>> process builds a reusable and educational component. I've got 13 tricks
>>> coded up now and ideas for a handful more, but if there are any requests
>>> out there, please let me know. I'd also be interested in getting some
>>> idea how many people would be interested in this book (would provide
>>> some fuel for me to get it done). It does not cover any of the same
>>> ground as Wicket in Action (which you should buy if you have not
>>> already!), BTW. It's more of a companion to that book.
>>> 
>>> Happy Holidays!
>>> 
>>> Best,
>>> 
>>>Jonathan
>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p21220309.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Stuff devs - teamcity is open for registration

[svenmeier]

Time to do some cleaning up:

username: svenmeier
project: wicketstuff-prototype

Thanks

Sven


Martijn Dashorst wrote:
> 
> We have moved our build server to run on teamcity. Our previous
> software was not up to par. I have picked Teamcity because it was the
> quickest to setup securely at 1am in the morning (yes I've looked at
> hudson), several of the core committers use the product in their
> companies and we don't have a problem with using commercial software
> for free :)
> 
> You can register yourself on our teamcity server:
> 
> http://wicketstuff.org/teamcity
> 
> This doesn't give you the ability to add projects/build
> configurations, but it will make our lives much easier to grant you
> that ability.
> 
> Registration is available to all project maintainers on Wicket Stuff
> and other Wicket related open source projects (Wicket Web Beans comes
> to mind).
> 
> Add your account and reply in this thread when you are done. Please
> provide the projects you are maintaining or want to maintain (this
> gives me an overview of who does what). One of the teamcity admins
> will grant you the ability to manage your own build configuration.
> 
> I'm sorry that all the effort that went into configuring bamboo is now
> naught, however I am confident that teamcity will help us throughout
> 2008 and beyond in managing our builds.
> 
> Martijn
> 
> -- 
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.3 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Stuff-devs---teamcity-is-open-for-registration-tp17057370p19115815.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WebPage markup error with latest trunk

[svenmeier]

Did somebody create a jira issue already?

I'm experiencing the same log statement since upgrading to 1.3.4.

Perhaps the fix for Wicket-1636 is the reason why the header check was never
performed previously?

I have  and  in my page's markup.

Sven


igor.vaynberg wrote:
> 
> quickstart and jira please
> 
> -igor
> 
> On Mon, May 26, 2008 at 10:54 AM, Jan Kriesten
> <[EMAIL PROTECTED]> wrote:
>>
>> Hi Igor,
>>
>>> are you sure the markup of the child page that you are trying to
>>> render is inside wicket:extend tags?
>>
>> yes, I am. And also the application didn't show this behavior before with
>> trunk from two days ago...
>>
>>> what happens if you remove the transparent resolver, does the error go
>>> away?
>>
>> Yep, when I remove it, the error is gone.
>>
>> --- Jan.
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WebPage-markup-error-with-latest-trunk-tp17467363p18087509.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]