I've tested it last night and did not find any bug. It seems to work
with pages, borders, panels and all other basic components. It has
something to do with headers (again). Are you trying to disable a
component with header component? Is it a header in-side component
which you try to disable?
Juer
Jim McBeath wrote:
In my simple test app I have a form with a button in it. The button
works properly in 1.1-b4, but when I compile and run using 1.1-rc1,
the button is functional but has no label in it.
The source html for the button:
The generated html for the button in 1.1-rc1:
The ge
I've tested it last night and did not find any bug. It seems to work
for me. What are the details?
Juergen
-- Forwarded message --
From: SourceForge.net <[EMAIL PROTECTED]>
Date: Sep 13, 2005 8:10 AM
Subject: [Wicket-develop] [ wicket-Bugs-1289391 ] setVisible(false) no
longer pre
good question. I currently don't see any reason why we should change
it. But you never know. At least I'm not aware of any change which
will affect it.
Juergen
On 9/13/05, Phil Kulak <[EMAIL PROTECTED]> wrote:
> I just noticed that I'm now able to build the component tree on a page
> AFTER checkA
would you please open a bug for it. Thanks
Juergen
On 9/13/05, Todor Todorov <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I'm having hard time with borders and CSS today.
>
> I have a border component which contributes a CSS link in the header section
> of a page.
>
>
>
>
no. Providing the markup and java code however might help looking into it.
juergen
On 9/12/05, Justin Lee <[EMAIL PROTECTED]> wrote:
> Does anyone know what would cause me to get errors about multiple wicket
> borders when, as far as I can tell, I'm only adding one?
>
> --
> Justin Lee
> http://
Bug #1289391 has been filed for this issue.
Gili
Johan Compagner wrote:
ahh it seems that
public final boolean resolve(final MarkupContainer container,
final MarkupStream markupStream, final ComponentTag tag)
{
Component component = this.container.ge
It works, Thank your help !
It is great if API provides a convenient method like setDisabled(boolean) for all form components
instead of creating 3 object likes new AttributeModifier("disable", true, new Model("disable")))
On 9/13/05, Phil Kulak <[EMAIL PROTECTED]> wrote:
add(new TextField("tf")
add(new TextField("tf")
.add(new AttributeModifier("disable", true, new Model("disable";
Is that what you're looking for? I don't have to API by me, but that
should be close.
On 9/12/05, Ingram Chen <[EMAIL PROTECTED]> wrote:
> Is there any way to disable form component in java code ?
>
Is there any way to disable form component in java code ?
-- Ingram ChenJava [EMAIL PROTECTED]Institue of BioMedical Sciences Academia Sinica Taiwanblog:
http://www.javaworld.com.tw/roller/page/ingramchen
I just noticed that I'm now able to build the component tree on a page
AFTER checkAccess() instead of only in the constructor. This seems
great because I don't have to worry about state that's enforced in
checkAccess(). Is this intentional? Is this behavior going to remain
through future versions?
Hi there,
I'm having hard time with borders and CSS today.
I have a border component which contributes a CSS link in the header section of a page.
At runtime, this generates
Re: [Wicket-user] Add/Edit Strategy
Thanks, it looks like another good technique. And now that you remind
me, I remember running across that several weeks ago. Damn memory!
-- Scott
David Liebeherr wrote:
Just have a lock at an wiki-page i wrote a couple of weeks ago:
http://wicket.sourceforge.net/wiki/index.php/How_to_use_t
Just have a lock at an wiki-page i wrote a couple of weeks ago:
http://wicket.sourceforge.net/wiki/index.php/How_to_use_the_same_Form_for_editing_and_new
Cu,
Dave
Nick Heudecker wrote:
Kinda. I just call a different constructor that adds the components I
need.
On 9/12/05, *Scott Sauyet* <[E
Kinda. I just call a different constructor that adds the components I need.On 9/12/05, Scott Sauyet <[EMAIL PROTECTED]
> wrote:Thanks for the input Martijn and Nick.If you then need different components for Add versus Edit, do you simply
use an if-else? -- ScottMartijn Dashorst wrote:> Yep, this
Ah, thanks - I'd missed that possibility...
Just for the archives, I've got this sort of thing working...
private class TpmForm extends Form {
public TpmForm(String name) throws Exception {
super(name, new CompoundPropertyModel(new TpmModel()));
IModel vendorsModel = new Propert
In my simple test app I have a form with a button in it. The button
works properly in 1.1-b4, but when I compile and run using 1.1-rc1,
the button is functional but has no label in it.
The source html for the button:
The generated html for the button in 1.1-rc1:
The generated html for the
I was happy to find the wiki page on the wicket lifecycle, it helps
a lot in understanding how wicket works.
It seems the lifecycle page is missing two important things:
1) When is an object instantiated, serialized or deserialized?
2) How does form processing fit into the lifecycle?
Is there a
Hi,
I recently switched to PageableGridDataView. It's nice, thanks :)
I just wanted to recommend you provide more Javadoc for it. It isn't
clear from the example code sniplet in the Javadoc that the 1st Wicket
tag is user-defined and corresponds to the ID of the
PageableGridDataView
Thanks for the input Martijn and Nick.
If you then need different components for Add versus Edit, do you simply
use an if-else?
-- Scott
Martijn Dashorst wrote:
Yep, this is what I also use as a pattern, and also in conjunction with:
public class EditFoo extends WebPage {
public stati
Yep, this is what I also use as a pattern, and also in conjunction with:
public class EditFoo extends WebPage {
public static class FooModel extends LoadableDetachableModel {
private final Long id;
public FooModel(Foo f) {
this.id = f.getId();
}
publ
Not sure about doing this in Wicket, however, there is an article
explaining how to do this at
http://ensode.net/jasperreports_pdf_send_to_browser.html , the article
is geared towards JasperReports, I'm sure it can be adapted to whatever
report engine you might be using.
DavidOn 9/12/05, Nick Heud
see wicket stuff:
there is a jasper report integration.On 9/12/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
We're going to be generating PDF reports and streaming them down to the
client's browser. How do I go about doing this with Wicket?
Thanks for your time.
On 9/12/05, Fred Astaire <[EMAIL PROTECTED]> wrote:
> Hi!
> Seems very strange:
> My wicket jars are built from src: wicket-1.1-b4-src.tar.gz
> I run it on Jre 1.4.2_04. I also tried the lib coming with wicket-examples
> (Version 1.1-b2) with the same results. On the other hand the examples run
>
We're going to be generating PDF reports and streaming them down to the
client's browser. How do I go about doing this with Wicket?
Thanks for your time.
Oh, better make the interface this:
interface LinkOnClick {
public void onClick();
public String linkText(); // Text for the label in the link.
}
On 9/12/05, Phil Kulak <[EMAIL PROTECTED]> wrote:
> I would use a ListView that took a list of these guys:
>
> interface LinkOnClick {
>public
I would use a ListView that took a list of these guys:
interface LinkOnClick {
public void onClick();
}
Then just call the onClick from inside each Link's onClick.
On 9/12/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
> why must there be dynamic wicket ids?
> why do you need those? How woul
please try it with RC1On 9/12/05, Fred Astaire <[EMAIL PROTECTED]> wrote:
Hi!Seems very strange:My wicket jars are built from src: wicket-1.1-b4-src.tar.gzI run it on Jre 1.4.2_04. I also tried the lib coming with wicket-examples(Version 1.1-b2) with the same results. On the other hand the example
yes it is possible. you just have to send that 401 and set that authenticate header.
Where you would do that i don't know. Maybe in a base page. But maybe you could have youre own WebRequest/WebResponse objects
where you do the checking.
Don't know it yet would have to build it first.
On 9/12/05,
Hi!
Seems very strange:
My wicket jars are built from src: wicket-1.1-b4-src.tar.gz
I run it on Jre 1.4.2_04. I also tried the lib coming with wicket-examples
(Version 1.1-b2) with the same results. On the other hand the examples run
well (forminput example, guestbook, ...)
Greetz
S
why must there be dynamic wicket ids?
why do you need those? How would you target them in java?
On 9/12/05, leo <[EMAIL PROTECTED]> wrote:
i have a reusable MenuBar component that, among other things, contains a list of button implemented as Links (id=actionsList).
Now i would like to make this M
Hi Juergen,
I've looked at the examples, but they demonstrate cookie-based authentications.
I was wondering if Basic HTTP authentication (1) was possible in wicket.
Thanks for your answer anyway !
(1) http://www.ietf.org/rfc/rfc2617.txt
examples : http://frontier.userland.com/stories/storyReader
i have a reusable MenuBar component that, among other things, contains a list of button implemented as Links (id=actionsList).
Now i would like to make this MenuBar component reusable, so that
-among other things- buttons can be added & removed by parent
component (usually the page)
Each link mu
I'm still figuring this one out myself, but if I have an object Foo, I
have a Page class called EditFoo with the following constructors:
public EditFoo() {
Foo f = new Foo();
// ... whatever initialization i need for a new object
init(f);
}
public EditFoo(Foo f) {
init(f);
}
And the init(
I have a question about Wicket best practices.
Often enough, an application will have related Add and Edit pages for
some class of objects. These are so closely related that it seems silly
to have two separate HTML and two separate Java class to manage them.
If I use only one HTML file and m
just have the model of the choices for the second component depend on the first components selection (a model in model)
Then you are doing it completely in the data layer.On 9/12/05, Gwyn Evans <[EMAIL PROTECTED]> wrote:
I've got two drop-down choices, with the choices available in thesecond depend
ahh it seems that
public final boolean resolve(final MarkupContainer container,
final MarkupStream markupStream, final ComponentTag
tag)
{
Component component = this.container.get(tag.getId());
if (component != null)
{
comp
I've got two drop-down choices, with the choices available in the
second depending on the selected value of the first. Is there a way
to change the list used by the second component, or is it just a
matter of replacing it completely via replace() from form's
onSubmit(), for example?
/Gwyn
-
Does anyone know what would cause me to get errors about multiple wicket
borders when, as far as I can tell, I'm only adding one?
--
Justin Lee
http://www.antwerkz.com
AIM : evan chooly
720.299.0101
---
SF.Net email is Sponsored by the Better
Just for the record, I thought I'd let you know that I've made my override:
public boolean isVisible() {
return super.isVisible() && pageable.getPageCount() >= 2;
}
to take into account an explicit setVisible(false)
-S.
-Original Message-
From: [EMAIL PRO
Good point - thanks.
-S.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Vaynberg
Sent: 12 September 2005 16:49
To: wicket-user@lists.sourceforge.net
Subject: RE: [Wicket-user] Minimal contract for onRender() - Found word(s) list
error in the Text b
There is a little problem with the method below. If you reuse the page and
at some point your list will become longer then one page you wont see the
navigator because you only set visibility at construction time. A better way
would be to override the setVisible method:
public class EBSPagingNaviga
It looks like the problem lies with "TransparentWebMarkupContainer"
which I am not familiar with... Here is the full stack-trace:
desktopbeautifier.web.contactus.Page$1.onComponentTag(Page.java:74)
at wicket.Component.renderComponent(Component.java:1837)
at
wicket.markup.html
but that method can't be called because they go all through render()
and render checks for visibility:
if (!isVisible())
{
findMarkupStream().skipComponent();
}
else
{
So where does that call come from?On 9/12/05, Gili <[EMAIL PROTECTED]> wrote:
The testcases do pass, but the problem still remains. You should be
able to reproduce this on your end. Add a component into a page with
setVisible(false), then add a breakpoint inside its onComponentTagBody()
method and note that this will still get invoked and the tag will get
rendered by
hmm, don't find the test cases currently. I have to check it.
Juergen
On 9/12/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> sorry, no chance to join on irc; only mail is possible.
>
> Juergen
>
> On 9/12/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> > that is correct and based on th
sorry, no chance to join on irc; only mail is possible.
Juergen
On 9/12/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> that is correct and based on the test cases it should work. Do the
> test cases succeed on your pc?
>
> Juergen
>
> On 9/12/05, Gili <[EMAIL PROTECTED]> wrote:
> >
> >
that is correct and based on the test cases it should work. Do the
test cases succeed on your pc?
Juergen
On 9/12/05, Gili <[EMAIL PROTECTED]> wrote:
>
>I think you understood me. What I am saying is that a component with
> isVisible()==false still shows up on the page. This isn't suppos
Debugging shows that although onRender() is not being invoked,
onComponentTag() still is and the tag is showing up in the resulting
page... so, this is a bug right? If you can join IRC to discuss this, it
might go faster...
Thanks,
Gili
Gili wrote:
I think you understood me. What I a
I think you understood me. What I am saying is that a component with
isVisible()==false still shows up on the page. This isn't supposed to
happen, right?
Gili
Juergen Donnerstag wrote:
Not sure I understand what you. Previously setVisible did NOT prevent
the component from rendering. It si
Not sure I understand what you. Previously setVisible did NOT prevent
the component from rendering. It simply got written into a
NullResponse. Due to user requests (you included) we changed it.
Invisible components (incl. associated AttributeModifiers) don't get
rendered at all now.
Juergen
On 9/
Hi,
I've got a meta redirect tag. In older releases of Wicket, if I invoked
setVisible(false) on the tag, its nested AttributeModifier would become
invisible too. With RC1, the tag and its nested AttributeModifier are
rendering even though its state is:
redirectPage=[Component id = redirect
Johan Compagner wrote:
in the end MarkupComponent.renderNext() must be called
Because the stream must advance to the next position. So that the markup
stream pointer is set to the right position for the next one.
If you don't want a component to render just call setVisible(false) on it.
Okay
in the end MarkupComponent.renderNext() must be called
Because the stream must advance to the next position. So that the
markup stream pointer is set to the right position for the next one.
If you don't want a component to render just call setVisible(false) on it.
On 9/12/05, Scott Sauyet <[EMAIL
Thanks. The empty WebComponent did fine for the moment, although I
think I like the other solution better for long-term.
I'm still curious to know what needs to be done in onRender() to make a
component viable, but that's not top priority right now.
-- scott
Simon Berriman wrote:
I've
A clean-rebuild cycle seemed to have fixed the problem.
Gili
Gili wrote:
Hi,
I'm trying to upgrade to rc1 and header contribution no longer
works. I remember reading that we should replace addToHeader() by add(),
which I did, but now Wicket complains the markup refers to compone
I've done this... - both to them, actually! I constructed my own
PagingNavigator, like this:
public class EBSPagingNavigator extends PagingNavigator
{
public EBSPagingNavigator(String id, IPageable pageable)
{
this(id, pageable, null);
}
public EBS
Hi,
I'm trying to upgrade to rc1 and header contribution no longer works. I
remember reading that we should replace addToHeader() by add(), which I
did, but now Wicket complains the markup refers to components which are
never added on the Java end. Have any of you got this working on your
en
I guess there are really two questions here.
First, I wanted to create an empty component (more about why below) and
did what I thought was reasonable:
add(new Component("navigator") {
public void onRender() {}
});
but I get a wicket.markup.MarkupExcept
why do you really need it?
Do you really want the state pushed to the clients? (Like viewstate of .net)On 9/12/05, Eric Jain <[EMAIL PROTECTED]
> wrote:Eelco Hillenius wrote:> Not yet. Currently Wicket insists on creating session object. We want
> to take a look at this for 1.2, but that will take
Eelco Hillenius wrote:
Not yet. Currently Wicket insists on creating session object. We want
to take a look at this for 1.2, but that will take a couple of months
probably.
Thanks for the information. I'll keep an eye on Wicket then :-)
---
Not yet. Currently Wicket insists on creating session object. We want
to take a look at this for 1.2, but that will take a couple of months
probably.
Eelco
On 9/12/05, Eric Jain <[EMAIL PROTECTED]> wrote:
> Can Wicket be used for stateless web applications? (Or does it insist on
> creating sessi
Can Wicket be used for stateless web applications? (Or does it insist on
creating session objects?)
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practi
I've not used it myself (as it needs JDK 5) but I think that the
Wicket-Stuff wicket-contrib-examples-hibernate-3 module might be a
good starting point for that combination.
See http://wicket.sourceforge.net/wiki/index.php/Wicket-Stuff for info
on how to access the CVS repositry there.
/Gwyn
O
Yes - From what I hear, the IDEA PlugIn development environment
remains one where it's not straight-forward to determine what needs to
be done...
In this case, I'm still not sure if the additional integration/help
that the plugin could provide over just running Jetty via the Start
class would repa
And you have the danger of having to go for the lowest common dominator.
I think plugins should be tailored for what works best in the given environment.
Eelco
On 9/12/05, Joni Suominen <[EMAIL PROTECTED]> wrote:
> It could be ported. On the other hand the plugin contains necessarily
> quite a
It could be ported. On the other hand the plugin contains necessarily
quite a bit of eclipse specific code (setting project's build path,
integration to eclipse's extension points, code templates, ui in swt
etc.).
--
Joni Suominen <[EMAIL PROTECTED]>
On Thu, 2005-09-08 at 15:13 -0500, Nick Heude
