Blame Canada!
On 15-Apr-09, at 9:43 AM, Philip A. Chapman wrote:
The packets are probably getting frozen in the tubez while traveling
in Canada. I would suggest that you be patient for spring to thaw
them out. At that point, you should expect a vigorous rush of
freshly thawed email goodn
done
-igor
On Tue, Apr 14, 2009 at 6:31 PM, Craig Tataryn wrote:
> Ooops, my sf and ohloh account is ctataryn
>
> On Tue, Apr 14, 2009 at 8:26 PM, Craig Tataryn wrote:
>
>> Hi there, I have a component which is about ready and need commit access to
>> wicket-stuff's svn. Just finishing up some
http://www.nabble.com/Wicket-Stuff-commit-access-td23050947.html
On Wed, Apr 15, 2009 at 4:43 PM, Philip A. Chapman wrote:
> The packets are probably getting frozen in the tubez while traveling in
> Canada. I would suggest that you be patient for spring to thaw them out.
> At that point, you sh
The packets are probably getting frozen in the tubez while traveling in
Canada. I would suggest that you be patient for spring to thaw them
out. At that point, you should expect a vigorous rush of freshly thawed
email goodness into your mail box! (Beware that some sogginess is to be
expected
Depending on what client you use (i.e. gmail) - you may not see your own
messages as a received AND a sent message because it realizes they are the
same.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Apr 15, 2009 at 9:21 AM, Craig Tataryn wrote:
> Just testing to see if I'm really
Just testing to see if I'm really on the list, I didn't see my wicket-stuff
commit access message come through on this end.
Craig.
subset.add(type.cast(behavior)); unfortunately doesn't work because
type can be null. See javadoc for type parameter. I guess that can
only be changed in 1.5 though a convience method getBehaviors() -
without any parameters - already exists.
Juergen
On Wed, Apr 15, 2009 at 9:17 AM, Francis De Br
+1
-igor
On Tue, Apr 14, 2009 at 11:36 PM, Juergen Donnerstag
wrote:
> I'll to suggest the following improvement (generics)
>
> Today:
> protected List getBehvavior(Class type)
> Which leads to code like WindowClosedBehavior behavior =
> (WindowClosedBehavior)getBehaviors(WindowClosedBehavior.cl
subset.add((M)behavior);
can be replaced by
subset.add(type.cast(behavior));
and should help to get rid of that @SuppressWarnings, but then this
might decrease performance (not sure about that)
On Wed, Apr 15, 2009 at 9:05 AM, Johan Compagner wrote:
> Ohh wait, i didnt read the email fully, thi
Ohh wait, i didnt read the email fully, this should work find, i just
saw the supressed warning..
But that change would be fine
On 15/04/2009, Johan Compagner wrote:
> Hmm dont know about that.
> Because this would mean that class cast exceptions can easily be get
> even when from the outside yo
Hmm dont know about that.
Because this would mean that class cast exceptions can easily be get
even when from the outside you use generics all the way.
How does a user know that the first one is of that type? Maybe we
could add our own first our self.. This is just bad code if you ask me
On 15/04/
11 matches
Mail list logo
