Actually it doesn't have anything to do with timestamps. Class equivalence in Java is
based on the class and the class loader. Think
of the class loader id as a prefix for the class's name to give a completely qualified
class name.
All this behaviour rises from the way servlet engines spawn new
Tomcat after making changes, see if everything works?
- Original Message -
From: "Cory L Hubert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 29, 2001 11:56 PM
Subject: RE: Wierd Casting Problem. Tomocat Bug?
> The casting itself isn't
changes, see if everything works?
- Original Message -
From: "Cory L Hubert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 29, 2001 11:56 PM
Subject: RE: Wierd Casting Problem. Tomocat Bug?
> The casting itself isn't the problem. The
port on
Win32. Which I am pretty sure is a development environment for most of us.
-Original Message-
From: Warren Crossing [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 5:19 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Wierd Casting Problem. Tomocat Bug?
Hi,
I have
: [EMAIL PROTECTED]
Subject: Re: Wierd Casting Problem. Tomocat Bug?
I posted the same problem yesterday but totally solved it on my case
two things
Technically Java should only allow you to cast an object to a superclass or
subclass of the class, so if member is not inherited from Object then t
-
From: Ivan [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Wierd Casting Problem. Tomocat Bug?
I posted the same problem yesterday but totally solved it on my case
two things
Technically Java should only allow you to cast an object to a
To: [EMAIL PROTECTED]
Subject: RE: Wierd Casting Problem. Tomocat Bug?
Are any of the classes you are using defined outside of the web app. That
is, are you using any libraries, or class files which you specify on the
classpath prior to tomcat starting, which may also be in your web-app. It
is situat
ubert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 29, 2001 11:13 AM
Subject: RE: Wierd Casting Problem. Tomocat Bug?
> I found out the problem. This looks like an extreme hack though.
>
> <$=((member) ((Object)e.nextElement()) ).getFname()%>
>
&g
: Cory L Hubert [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: RE: Wierd Casting Problem. Tomocat Bug?
Casting could happen in a regular fashion if you just restart. Wierd. Is
anyone planning on fixing this issue, no developer should have
, April 29, 2001 11:29 AM
To: [EMAIL PROTECTED]
Subject: RE: Wierd Casting Problem. Tomocat Bug?
When I restart that little trick doesn't work anymore. I have a feeling
it's defenaitley a bug. Can anyone confirm?
-Original Message-
From: Cory L Hubert [mailto:[EMAIL PROTEC
When I restart that little trick doesn't work anymore. I have a feeling
it's defenaitley a bug. Can anyone confirm?
-Original Message-
From: Cory L Hubert [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 11:14 AM
To: [EMAIL PROTECTED]
Subject: RE: Wierd Casti
I found out the problem. This looks like an extreme hack though.
<$=((member) ((Object)e.nextElement()) ).getFname()%>
Works. But why do I have to cast to an Object before I cast it back to
it's appropiate type. My only guess is that the Servlet DownCast the
Vector t
12 matches
Mail list logo
