Where do i have to go to report a bug?
And are the informations from this email are enough for the report?
Cu,
Dave
Jonathan Locke wrote:
nah, an endless loop here is definitely a bug, whether we can or do fix
it or not.
i thought this was fixed long ago, but maybe that was just for the
It simply doesn't :-)
Phil Kulak wrote:
This is an unrelated question, but how does the error page get access
to the exception?
On 8/2/05, David Liebeherr [EMAIL PROTECTED] wrote:
Hi guys,
...
getPages().setInternalErrorPage(ErrorPage.class);
Btw: are there any other possible endless loop situations i should be
aware of?
An endlees loop on a production machine isn't funny :-(
Actually it means my customer will kill me :-(
Thanx,
Dave
Jonathan Locke wrote:
nah, an endless loop here is definitely a bug, whether we can or do fix
it
i think i will introduce an interface for the internal_error_page
that you can implement then i will call the method setError(Throwable)
johan
Phil Kulak wrote:
This is an unrelated question, but how does the error page get access
to the exception?
On 8/2/05, David Liebeherr [EMAIL
sf project page should have a link. just the basic info is fine...
David Liebeherr wrote:
Where do i have to go to report a bug?
And are the informations from this email are enough for the report?
Cu,
Dave
Jonathan Locke wrote:
nah, an endless loop here is definitely a bug, whether we
how the hell could anyone know that? the halting problem is unsolved,
afaik!!
David Liebeherr wrote:
Btw: are there any other possible endless loop situations i should be
aware of?
An endlees loop on a production machine isn't funny :-(
Actually it means my customer will kill me :-(
I like to use exceptions for anything that is exceptional, not just
something that signals a total disaster. If I can catch these things
in one place, I don't have to worry about dealing with them in 100
different places throughout my app. Use cases:
-Hibernate throws an ObjectNotFoundException()
On Aug 3, 2005, at 08:21, Jonathan Locke wrote:
yeah, InternalErrorPage was meant to be a user-facing page
without those kind of details...
i suppose that could be considered a flaw. one nice thing i've
seen done in some apps is
that a nice user-friendly error page can also contain an HTML
On Aug 2, 2005, at 23:49, Dariusz Wojtas wrote:
[..]
td width=3 height=3img wicket:id=imgLeftTop
src=imgLeftTop.gif alt=//td
td wicket:id=topBackground background=topBackground.gif/td
[..]
How do I use/specify the 2nd image when it is a background for the
TD element?
I would solve
Right, this will probably do the trick. My problem will be solved with this.
Thanks a lot.
But ... the question how to set background in components for TD or
other HTML elements is still open. No problem if this is done directly
in a HTML page (just use traditional link), but it is a problem if
ExceptionErrorPage shows the exception
That is not the idea in a deployment environment.
I don't want to show anything like a stacktrace.
But i want to have some information about the exception in my simple
error page so that i can
show message X or Y (with for example an email to or the
I think I finally understand what Johan (it was him right?) brought up
yesterday about static images.
Consider this: if a user hits a static image URL directly without going
through a Page, then he will get a broken link. As opposed to, if he
goes through the Page first, he can then hit
Hi,
Firefox console says:
Error: The stylesheet
http://localhost:8090/GC/mail/resources/wicket.extensions.markup.html.datepicker.DatePickerSettings/style/aqua/theme.css
was not loaded because its MIME type, content/unknown, is not text/css.
You can verify this problem at
I think it’s strange that a small/young project like Wicket has to wait
for IBM before it can make use of Java 5.
BTW, Hi!
I'm considering using Wicket for my next project. The main alternative
is Tapestry.
In conjunction with Wicket or Tapestry I’ll most likely use Hibernate,
but there is
It seems that UrlResourceStream is always initalized to
contentType=content/unknown, at least for *.js and *.css resources.
Jan
Jan Bares [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi,
Firefox console says:
Error: The stylesheet
Hi,
how can I customize the DatePicker class? For instance I would like to
override the DatePicker.getInitScript(), but I cannot, the method is
private. Almost everything in DatePicker is private.
Jan
---
SF.Net email is sponsored by:
Are you going to make it opensource? I would like to have a look at
Wicket in a serious application.
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Matej Knopp
Verzonden: woensdag 3 augustus 2005 0:23
Aan: wicket-user@lists.sourceforge.net
Onderwerp:
+1:-)
Peter Veentjer - Anchor Men wrote:
Are you going to make it opensource? I would like to have a look at
Wicket in a serious application.
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Matej Knopp
Verzonden: woensdag 3 augustus 2005 0:23
Hmm.. Although I am author, the license depends on departmen's decision
:). If they will agree, I'll open source it.
(I thing BSD or Apache license would be fine, GPL is too restrictive IMHO).
But I can't make any schedules, the application is still in a _very_
early stage of development and
Phil Kulak wrote:
I like to use exceptions for anything that is exceptional, not just
something that signals a total disaster. If I can catch these things
in one place, I don't have to worry about dealing with them in 100
different places throughout my app. Use cases:
-Hibernate throws an
Hi,
I read from the 1.1b2 release notes that there is Panel support for
TreeView.
I browsed the Javadoc but couldn't find any TreeView class. At first glance
it seems just like current panel support for ListView there is now one for
TreeView. Am I missing something here?
Regards,
Francis
Sorry 'bout that...
In my years of Borland VCL experience I've become accustomed to name
such a component 'TreeView'.
The Wicket counterpart is called 'Tree', and can be found in the
wicket.markup.html.tree package.
Martijn
[EMAIL PROTECTED] wrote:
Hi,
I read from the 1.1b2 release
Jonathan Locke wrote:
i don't think we need this johan. i think you can just set the
unexpectedExceptionDisplay
to SHOW_EXCEPTION_PAGE and then extend ExceptionErrorPage instead
of InternalErrorPage. the idea here, although it's not necessarily well
spelled out in the
documentation is that
http://www.springframework.org/docs/api/org/springframework/web/servlet/HandlerExceptionResolver.html
On 8/3/05, David Liebeherr [EMAIL PROTECTED] wrote:
I think you should not use Exceptions for application flow control.
USe it for File not found (IOException) and such things but using
http://en.wikipedia.org/wiki/Halting_problem
CS101 :)
Maybe you want to phrase your question differently:
Are there any other known Wicket bugs that result in looping pages?
Regards,
Adam.
- Original Message -
From: David Liebeherr [EMAIL PROTECTED]
To:
David Liebeherr
A, so now i understand what you mean, but i did not wanted
you to tell me what situations _i_ may produce that results
in endlees loop.
I just wanted to know if there are _known_ bugs in wicket
that will end in endless loop.
You can check the bug database and see for
Johan Compagner wrote:
what job doesn't it do exactly?
Johnatan said i can extend ExceptionErrorPage and then set SHOW_EXCEPTION_PAGE and my own
ExceptionErrorPage will be show. This does not work bc when SHOW_EXCEPTION_PAGE is set then the code
always uses the default ExceptionErrorPage.
yes i know that the SHOW_EXCEPTION_PAGE can't be overriden and it is
always the wicket exception page.
the only page you can specify youre self is the other one.
But with that one you won't get an exception to give you some more info.
johan
David Liebeherr wrote:
Johan Compagner wrote:
if you really want to display your own custom exception page, maybe it
should be overridable then... ?
Johan Compagner wrote:
yes i know that the SHOW_EXCEPTION_PAGE can't be overriden and it is
always the wicket exception page.
the only page you can specify youre self is the other one.
Hi!
The Wiki seems to be very very slow to me and often even retuls in error messages like cannot
access db or atal error: Call to a member function on a non-object in
/home/groups/w/wi/wicket/htdocs/wiki/includes/ObjectCache.php on line 409.
I want to get an overview of the wicket-tags.
Who is defining how many rows that it should display?
The ListView (or what ever component) or the Navigator?
Because defining how many rows there are are useless if you don't attach
a paging component...
We could say that all these things can go into the navigator
then we also need 3 methods
If I understand correctly, IPageable describes something that:
* represents some range of data
* data is divided into pages
* every page has some size (although it doesn't oblige that all
pages are of the same size)
* some component, or some user logic, may need to have access to the data
That is in my eyes the internal one. That can be set.
But then we have the same problem. How do we construct that Exception page?
Are we going to look for a Exception param constructor?
Or are we defining an interface: setException()
And if also EXCEPTION page is overridable. What is then
hmm of course then a ListView has also the setRowCount() method
Johan Compagner wrote:
Who is defining how many rows that it should display?
The ListView (or what ever component) or the Navigator?
Because defining how many rows there are are useless if you don't
attach a paging
What do you need an iterator()?
The Navigator component doesn't want the items of the list. It only
wants to set
which page the list should render now and then represent that in its
navigator links 1 2 3 4
johan
Dariusz Wojtas wrote:
If I understand correctly, IPageable describes
this is where we differ. my first guess is that a page has no size.
it's an abstract thing.
Dariusz Wojtas wrote:
If I understand correctly, IPageable describes something that:
* represents some range of data
* data is divided into pages
* every page has some size (although it doesn't
YES!!! that's it. the navigator just changes the current page. it
shouldn't even know
there's a list at all.
Johan Compagner wrote:
What do you need an iterator()?
The Navigator component doesn't want the items of the list. It only
wants to set
which page the list should render now and
ok. Then i do think we still need a PageableListView because if we let
ListView be pageable
then it is more or less PageableListView will become ListView.
But i like the idea. For example a Form could implement IPageable and
has a row per page of one
and then the navigator just let me scroll
yup yup
Johan Compagner wrote:
ok. Then i do think we still need a PageableListView because if we let
ListView be pageable
then it is more or less PageableListView will become ListView.
But i like the idea. For example a Form could implement IPageable and
has a row per page of one
and then
totally, dude. right on.
Phil Kulak wrote:
Because defining how many rows there are are useless if you don't attach
a paging component...
I disagree. So you're stuck on page one with no way to get to other
pages until you add a pager. What's the problem with that? I don't
think
You might want to take a look at the support forums for sf.net. There's
a whole list of projects suffering from this problem. We can't do
anything about it.
We just have to wait and see how/when this is solved. We are looking for
possible alternatives, but wish to keep everything as tight as
Everyone,
I have been using Wicket 1.0.1. The application worked fine using
Firefox. However, I ran across the infinite loop bug when using
RedirectPage and IE. I upgraded to 1.1.b2 hoping that it had been
fixed. After upgradeing, however, on a page that I have that uses the
PageableListView
I don't think it's a php related problem...
To mee it seems to be a problem of an db that is not responding properly or another external
resource which the wiki depends on.
I mean PHP is not as good as java, but there are project where you can do even
better with PHP.
And a wiki is such a
Hi,
I just tried to generate the javadoc for 1.1-b2. The packagenames
attribute needs to be changed to reflect the proper package:
javadoc use=true private=true destdir=${javadocdir}
author=true version=true sourcepath=src/java
packagenames=wicket.*
anywhere you need to do paging. whether in a page footer or a list view
navigation component or somewhere else. it's a general component
whereas the listview nav that knows about items and such is really not
quite general since it's tied to a certain idea of what does on the
pages that are
you did. it's not in IPageable. that's an /extra/ function of /some/
components that happen to implement IPageable. an important distinction.
i really did state this carefully if you were reading it:
i dunno. seems to me that the paging component should just change pages.
we ought to have
Thank you very much. Of course, this has to be fixed. Seems that I've
overlooked it.
This is exactly what I ment when I said that any button can be pressed. :)
If you found anything similiar (exception where they shouldn't be
(actually, they should be nowhere :)), pleas let me know.
-Matej
Hmm.. I agree with you.
The reason I'm not using wicket versioning is that it would (IMHO)
confuse inexperienced users. Because while it is possible to track model
changes, it's not possible (or at least easy) to track each database
change and make it undoable. So while user can undo some
48 matches
Mail list logo
