I had this problem when using Cocoon from within IntelliJ Idea and JDK 1.3. I can
confirm that this has fixed it.
Well done for fixing this. I can now debug in 1.3 again!
Regards, Upayavira
On 16 Jun 2003 at 9:07, Rob Johnston wrote:
> On Mon, 16 Jun 2003, Stephan Michels wrote:
>
> > Solving
On Mon, 16 Jun 2003, Stephan Michels wrote:
> Solving the problem was easy, I just recompile the package and everything
> works fine. So I will update the package this day.
>
> Stephan.
Stephan,
I grabbed today's latest CVS & compiled and everything works fine under
1.3.1p8 JDK on FreeBSD. Tha
Berin Loritsch wrote:
Rob Johnston wrote:
On Fri, 13 Jun 2003, Berin Loritsch wrote:
Okay, so you were actually able to verify the problem. Glad I'm not
going insane. :-) Is it too early to say if the problem is in the JDK
or in the ecm? Hopefully this will be a trivial fix...
I am not very
Rob Johnston wrote:
On Fri, 13 Jun 2003, Berin Loritsch wrote:
Okay, so you were actually able to verify the problem. Glad I'm not
going insane. :-) Is it too early to say if the problem is in the JDK
or in the ecm? Hopefully this will be a trivial fix...
I am not very familiar with the idiot-s
On Fri, 13 Jun 2003, Berin Loritsch wrote:
> Berin Loritsch wrote:
> >It seems unlikely, but it is possible.
> >
> >Could you print out the output of:
> >
> >$ java -version
> >
> >On one of the Apache boxes we have both JDK 1.3.1 and JDK 1.4.1, and
> >the results of JDK 1.3.1 is:
> >
> >java vers
On Fri, 13 Jun 2003, Berin Loritsch wrote:
> Rob Johnston wrote:
> >On Fri, 13 Jun 2003, Leo Sutic wrote:
> >
> >
> >>Do you run windows or linux?
> >
> >
> >FreeBSD. Which is the problem -- I think there is some incompatibility
> >between the ExcaliburComponentManager & the 1.3.1 JDK for FreeBSD
Berin Loritsch wrote:
Rob Johnston wrote:
On Fri, 13 Jun 2003, Leo Sutic wrote:
Do you run windows or linux?
FreeBSD. Which is the problem -- I think there is some incompatibility
between the ExcaliburComponentManager & the 1.3.1 JDK for FreeBSD (which
seems like a Major bug to me!)
It seem
Rob Johnston wrote:
On Fri, 13 Jun 2003, Leo Sutic wrote:
Do you run windows or linux?
FreeBSD. Which is the problem -- I think there is some incompatibility
between the ExcaliburComponentManager & the 1.3.1 JDK for FreeBSD (which
seems like a Major bug to me!)
It seems unlikely, but it is pos
On Fri, 13 Jun 2003, Leo Sutic wrote:
> Do you run windows or linux?
FreeBSD. Which is the problem -- I think there is some incompatibility
between the ExcaliburComponentManager & the 1.3.1 JDK for FreeBSD (which
seems like a Major bug to me!)
> Am thinking about doing a:
>
> WINDOWS:
> fo
Do you run windows or linux?
Am thinking about doing a:
WINDOWS:
for %i in (*.jar) do (echo %i && jar -tf %i) >> all.txt
LINUX:
--- some equivalent ---
and then checking the resulting file. You should find an
ExcaliburComponentManager
in some unexpected place.
/LS
> From: Rob Johnston
Leo,
Could you please see a previous email in this thread? I'm 110% sure
that this is a completely clean build, no CLASSPATH was set previous to
running "cocoon.sh servlet", so the only jars that are included in the
classpath are put there by the cocoon 2.1 build. (I've verified this in
WEB-INF/
The method has been gone for a while. Check your classpath and any
jars you may have in it. Somewhere, you probably have a very old
version of the ECM.
/LS
> From: Rob Johnston [mailto:[EMAIL PROTECTED]
On Thu, 12 Jun 2003, Stephan Michels wrote:
>
>
> On Wed, 11 Jun 2003, Berin Loritsch wrote:
>
> > Rob Johnston wrote:
> > > Is this a bug that I should report? I spoke to someone else who had the
> > > exact same problem with cocoon 2.1-dev under FreeBSD (over a month ago)
> > > & he said his
On 12 Jun 2003 at 9:58, Stephan Michels wrote:
>
>
> On Wed, 11 Jun 2003, Berin Loritsch wrote:
>
> > Rob Johnston wrote:
> > > Is this a bug that I should report? I spoke to someone else who
> > > had the exact same problem with cocoon 2.1-dev under FreeBSD (over
> > > a month ago) & he said
On Wed, 11 Jun 2003, Berin Loritsch wrote:
> Rob Johnston wrote:
> >Is this a bug that I should report? I spoke to someone else who had the
> >exact same problem with cocoon 2.1-dev under FreeBSD (over a month ago)
> >& he said his solution was to "not ship with support for FreeBSD" --
> >which i
Rob Johnston wrote:
Is this a bug that I should report? I spoke to someone else who had the
exact same problem with cocoon 2.1-dev under FreeBSD (over a month ago)
& he said his solution was to "not ship with support for FreeBSD" --
which isn't a viable option for us (even though the jdks for Free
Is this a bug that I should report? I spoke to someone else who had the
exact same problem with cocoon 2.1-dev under FreeBSD (over a month ago)
& he said his solution was to "not ship with support for FreeBSD" --
which isn't a viable option for us (even though the jdks for FreeBSD are
not "officia
17 matches
Mail list logo
