I've had this problem with jboss 3.2.3. You'll need to replace all the
old common collection jars. Do a search for the *collections*, it
shows up in multiple locations (default, all, etc.).
Cheers,
Eric
On Jun 24, 2004, at 2:07 PM, Mike Kienenberger wrote:
> Leonardo Queiroz Antunes <Leonardo.Antune..r-tcs.com> wrote:
>> Iīm trying to update the commons-collections on JBoss-3.2.3 but
>> havenīt
> success.
>>
>> De: Andrus Adamchik [mailto:andru..bjectstyle.org]
>> Enviada: qui 24/6/2004 12:49
>> Para: cayenne-use..bjectstyle.org
>> Assunto: Re: RES:
> org.apache.commons.collections.IteratorUtils.singletonIterator
>>
>> Yes, as Cayenne itself relies on 3.0 API.
>>
>> I think Mike Kienenberger had this problem a while ago, and he was
>> able
>> to upgrade collections used by Struts in his application with no
>> problems. That's when we decided that rolling back to collections-2.1
>> is not worth it.
>
> Yes, Struts 1.1 appears to work fine with collections 3.0. I haven't
> run
> into any problems with it after several months.
>
> Unfortunately, I don't use JBoss so I can't help you.
>
> However, you can try to identify where the older classes are being
> picked up
> from.
>
> Under unix, lsof might work for you.
> Under Windows, you can try FileMon or Handle.
>
> One of our programmers also wrote a simple jsp page that outputs all
> of the
> classpath info for a running struts application, but unfortunately I
> access
> to that right now. I recall it outputs the classpath for each of the
> classpath loaders.
>
> -Mike
>
This archive was generated by hypermail 2.0.0 : Thu Jun 24 2004 - 14:24:03 EDT