It is slightly ironic. Java, when we change default behaviour - we annotate
methods with @Override.
Its not a dissimilar solution. I can appreciate both decisions.
Same same but different.
What's the "norm" coding wise - what's more convenient? - I think when the
answer is "depends" - you can
Now I know what's going on. You are using a Redhat/CentOS/Mandriva Linux with
gcj (Gnu Java Compiler) installed. It because of the logs you sent:
>at gnu.java.nio.channels.FileChannelImpl.open(libgcj.so.7rh)
>at gnu.java.nio.channels.FileChannelImpl.(libgcj.so.7rh)
>at gnu.java.nio.ch
I created a JIRA issue (with trivial patch).
https://issues.apache.org/jira/browse/WICKET-1991
Regards,
Sebastiaan
Antoine van Wel wrote:
agree with Sebastiaan and Michael here
when a user types a wrong url, you're not going to log that
404 -> client error, file not found -> no fixes necessar
gnu.java.nio.channels?
Hey!... that's NOT Sun's JDK!!!
On Mon, Dec 22, 2008 at 12:01 PM, Pierre Gilquin wrote:
> Timm, I did what you suggested.
> I used Wicket 1.3.5 and I recompile with JDK 1.4.2
> Look like it goes farther but finaly not succefully.
> First, I get the same FileNotFoundExceptio
agree with Sebastiaan and Michael here
when a user types a wrong url, you're not going to log that
404 -> client error, file not found -> no fixes necessary, so not logged
500 -> server error -> log it, needs to be fixed
so instead of implementing the filter, I prefer waiting for a Wicket
patch.
Here is my Ajax debug output:
INFO: focus set on linkida
INFO:
INFO: Initiating Ajax POST request on
?wicket:interface=:3:reqTabs:panel:insurance-edit-form:primaryBillingPanel:billingRecord-edit-form:insuranceLookupPanel:insurance-lookup:lookup-form:menuBar:menubarlinks:0:menuitemul:menuitemlink
Done (hope I did at the right place;-)
https://issues.apache.org/jira/browse/WICKET-1990
Best,
Ernesto
Erik van Oosten wrote:
> Ah :) IMHO it should be added. It might be a small thing in the
> larger Wicket picture, but it is a big deal for some applications.
>
> Care to open a issue?
>
>
the thing is that 404 is a client error. I'd only log server errors (i.e.
errors in the code) as Error. Of course a 404 can also happen due to a error
in the code, but logging 404 as errors will flood your log file ...
just my two cents
Jeremy Thomerson-5 wrote:
>
> A 404 is an error - so on
A 404 is an error - so on the one hand you say it is an error, but on the
other, you say it isn't. I think it should remain an error.
Just my 0.02 though.
On Mon, Dec 22, 2008 at 7:56 AM, Sebastiaan van Erk wrote:
> Pointbreak wrote:
>
>> Not an answer to your question, but why fight this kind
Ah :) IMHO it should be added. It might be a small thing in the larger
Wicket picture, but it is a big deal for some applications.
Care to open a issue?
Erik.
Ernesto Reinaldo Barreiro wrote:
Hi Erik,
Still one question remains... Should that feature be added to [1]? Or it is
small enou
Hi Erik,
Still one question remains... Should that feature be added to [1]? Or it is
small enough to be discarded...
Best,
Ernesto
[1]-http://wicket.apache.org/features.html
On Mon, Dec 22, 2008 at 4:46 PM, Erik van Oosten wrote:
> Glad that is out of the way :)
>
> Wicket and Seam are freque
Timm, I did what you suggested.
I used Wicket 1.3.5 and I recompile with JDK 1.4.2
Look like it goes farther but finaly not succefully.
First, I get the same FileNotFoundException but it continues until the
exception :
NoSuchMethodError: method
java.lang.management.ManagementFactory.getPlatformMB
Glad that is out of the way :)
Wicket and Seam are frequently compared. But I think it is not a
fair/possible comparison. We might as well compare TestNG with Mockito,
both are about testing but in an entirely different league.
Seam's goal (as far as my humble knowledge goes) is targeted at
Yeah as I mentioned not all browsers support that css3 function..
However I was surprised to see that IE8 did'nt pick it up, I guess m$
just havent gotten around to it yet.
Jim Pinkham wrote:
FYI - I was curious about that so I ran:
http://browsershots.org/http://www.css3.info/preview/round
Ned Collyer wrote:
Ok - so I investigated a bit more - turns out I had a greasemonkey script
messing with it. DOH.
It looks beautiful :) - all works now. (and turns out safari is ok - i was
under the impression example 7 was misbehaving).
Sorry for the confusion.
Ok good to hear, I were st
That's a pity - in my situation I would like the absence of the wicket:extend
tag to mean the child wants to be completely encapsulated by it's parent.
It's useful because you can have your java class extend a parent without
having to modify the html, in my case the grand parent has the important
What I would like to know?
If Wicket supports multi-window/tap (beginning a new (what I can call?) a
conversation)?
Well, yes, it does
http://wicketstuff.org/wicket13doc/org/apache/wicket/settings/IPageSettings.html
Multi-window/tap isn't the gem of Seam, one of them
:)
We need to do more marketi
FYI - I was curious about that so I ran:
http://browsershots.org/http://www.css3.info/preview/rounded-border/
-- Jim Pinkham
On Mon, Dec 22, 2008 at 5:19 AM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> On Mon, Dec 22, 2008 at 11:14 AM, Steve Swinsburg
> wrote:
> > or the simple CSS
Apart from letting you guess what a page map is (a collection of visited
pages) I think Ernesto gave a very decent response. So lets turn this
around:
What would you like to know?
Regards,
Erik.
PS. If that really is /the/ gem of Seam, you're in for a treat with
Wicket! ;)
HHB wrote:
Pointbreak wrote:
Not an answer to your question, but why fight this kind of stuff? It's
an invalid request, so it should result in an error.
I actually prefer it would result in a 404 for the client and nothing
more. Perhaps, when enabling DEBUG, it can log the message + exception
it is curr
Hi Ernesto,
Yes, thanks for your input, I guess the way to go is to wrap components into
combined Wicket Panels, and then use repeaters.
Thanks again!
reiern70 wrote:
>
> Hi,
>
>> Component: TextField
>> Required: True
>> Type: String
>> Length:30
>> Order: 2
On Mon, Dec 22, 2008 at 2:35 PM, HHB wrote:
>
> This effects all the Wicket pages in the application, right?
> Seam folks advertise this feature as one of the gems of Seam framework, why
> Wicket doesn't shed more light on it?
> Common Wicket, no need to be humble this time :)
I'm just a user
Well, you can try catching the event in textfields' onMouseDown and
then either set e.ignore=true on it or make it stop propagate.
-Matej
On Fri, Dec 19, 2008 at 11:07 PM, lesterburlap wrote:
>
>
> Matej Knopp-2 wrote:
>>
>> it doesn't seem likely for me that the prelight would cause this. But
>
Hmm, actually you have a point.
Errors we've caught until now where mis-constructed URLs for pages;
those could be user errors too so we wanted to identify all places
where it could break and present a good feedback message to the user.
But in this particular case something/someone is clearly mess
Hmm, actually you have a point.
Errors we've caught until now where mis-constructed URLs for pages;
those could be user errors too so we wanted to identify all places
where it could break and present a good feedback message to the user.
But in this particular case something/someone is clearly mess
This effects all the Wicket pages in the application, right?
Seam folks advertise this feature as one of the gems of Seam framework, why
Wicket doesn't shed more light on it?
Common Wicket, no need to be humble this time :)
reiern70 wrote:
>
> See Application.getPageSettings().getAutomaticMulti
Not an answer to your question, but why fight this kind of stuff? It's
an invalid request, so it should result in an error.
If you don't want these entries in your log, you could just add a filter
to your logger (e.g. filtering out error messages from
org.apache.wicket.request.target.resource.Shar
Heya,
we're trying to catch all errors caused by hack & search-bots on our
wicket-app. AFAIK these bots take existing links, chop 'em up in
smaller chunks and try to append all kind of . We've caught most
of the errors which result due to these bots, but this one still
stands:
XXX.XXX.XXX.XXX
See Application.getPageSettings().getAutomaticMultiWindowSupport() and the
explanation given at javadoc.
On Mon, Dec 22, 2008 at 11:39 AM, HHB wrote:
>
> Hey,
> Seam framework supports the multi-tab / multi-window operations, it
> isolates
> each process from the other out-of-the-box.
> Does Wick
Mike,
The phonebook example from wicket-stuff (currently down?) shows how to
use the wicket-extra filters.
Regards,
Erik.
Mike wrote:
Is there a way to create filter for numeric types in DataTable column
that
would allow user to enter/choose value for filter state object and
choose if
v
Ok - so I investigated a bit more - turns out I had a greasemonkey script
messing with it. DOH.
It looks beautiful :) - all works now. (and turns out safari is ok - i was
under the impression example 7 was misbehaving).
Sorry for the confusion.
--
View this message in context:
http://www.nab
can you put it here somewhere appropriate i'll correct it to a working
state then::
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/artwork-parent/artwork
Gerolf Seitz wrote:
i think i have an integration for the latest nifty libs [0] lying around
haven't
Yeah it's good. But depends highly on your use case.. In most of my
cases we cant afford to miss too many people..
Most people just don't care what browser they have, they just want the
sites they visit to look good, and if their browser just not happen to
support css 3 then they do not believ
Hey,
Seam framework supports the multi-tab / multi-window operations, it isolates
each process from the other out-of-the-box.
Does Wicket offer the same thing?
Thanks.
--
View this message in context:
http://www.nabble.com/Multi-tap-operations-in-Wicket-tp21125698p21125698.html
Sent from the Wic
On Mon, Dec 22, 2008 at 11:14 AM, Steve Swinsburg
wrote:
> or the simple CSS you can apply yourself.
> .roundedThing {
> -moz-border-radius: 5px;
> -webkit-border-radius: 5px;
> }
> however that may not be 100% across all browsers.
Which is great: it rewards users that have up-to-date browsers th
Hi,
yep, JDK 1.5 can be the problem, but don't need to be.
If you use generics, you have to remove them first. The other thing is that
you must compile your code for JDK 1.4. You need to set the
Parameter "-source 1.4" to compile the code.
If the compiler is going through without any error, t
The liquidcanvas seems to be working fine on Safari 3.2.1. I'm all for
a jQuery plugin as they generally seems to be more cross browser
compatible.
There is also jQuery corners:
http://www.atblabs.com/jquery.corners.html
or the simple CSS you can apply yourself.
.roundedThing {
-moz
i think i have an integration for the latest nifty libs [0] lying around
haven't looked at it in quite a while, so maybe it's not that good anyway :)
gerolf
[0] http://www.html.it/articoli/niftycube/index.html
On Fri, Dec 19, 2008 at 9:31 PM, Nino Martinez wrote:
> Im fed up with all the di
Hello,
I don't know of any stock component that does this but it should be
straight forward to create a component that supports it.
What I'd do for this case is create a text field for the value input,
drop down choice for the less than, greater than and equals options.
The model containing
Thanks Timms,
I developed my app with this version without any problem.
Now I am trying to change hosting.
I have developed for JDK 1.5 and my new host is 1.4.2.
Could this be also a problem ?
Pierre
My Web.xml
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/TR/xmlschema-1/";
40 matches
Mail list logo
