You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ryan McKinley <ry...@gmail.com> on 2009/05/30 20:25:01 UTC

Help debugging why a component is not showing up...

Hello-

I am pulling my hair out trying to figure out why a component is not
showing up within a page.  When I run the app from eclipse in
development or deployment mode, it shows up just fine.  When I build a
package run that... no luck.  However it does include javascript
libraries added from the (not visible) components.

Is there an easy way to debug the component hierarchy on the page?

Perhaps some way to dump the current page tree to text or something?

Any pointers would be great!

thanks
ryan

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

Re: Help debugging why a component is not showing up...

Posted by Ryan McKinley <ry...@gmail.com>.
yup that helps!  Also just found:
WicketTesterHelper.getComponentData( getPage() )

thanks


On Sat, May 30, 2009 at 3:06 PM, jWeekend <jw...@cabouge.com> wrote:
>
> Ryan,
>
> Is PageView what you're looking for?
>
> Regards - Cemal
> http://jWeekend.com jWeekend
>
>
>
>
> ryantxu wrote:
>>
>> Hello-
>>
>> I am pulling my hair out trying to figure out why a component is not
>> showing up within a page.  When I run the app from eclipse in
>> development or deployment mode, it shows up just fine.  When I build a
>> package run that... no luck.  However it does include javascript
>> libraries added from the (not visible) components.
>>
>> Is there an easy way to debug the component hierarchy on the page?
>>
>> Perhaps some way to dump the current page tree to text or something?
>>
>> Any pointers would be great!
>>
>> thanks
>> ryan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Help-debugging-why-a-component-is-not-showing-up...-tp23796086p23796445.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

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

Re: Help debugging why a component is not showing up...

Posted by jWeekend <jw...@cabouge.com>.
Ryan,

Is PageView what you're looking for?

Regards - Cemal
http://jWeekend.com jWeekend 




ryantxu wrote:
> 
> Hello-
> 
> I am pulling my hair out trying to figure out why a component is not
> showing up within a page.  When I run the app from eclipse in
> development or deployment mode, it shows up just fine.  When I build a
> package run that... no luck.  However it does include javascript
> libraries added from the (not visible) components.
> 
> Is there an easy way to debug the component hierarchy on the page?
> 
> Perhaps some way to dump the current page tree to text or something?
> 
> Any pointers would be great!
> 
> thanks
> ryan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Help-debugging-why-a-component-is-not-showing-up...-tp23796086p23796445.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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