On 02.Mar.2002 -- 02:48 PM, Matthew Langham wrote:
> Are other things perhaps in the scratchpad that are causing this?

> From: Christian Haul [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 02, 2002 11:21 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: portal source of my problems?
> 
> 
> On 02.Mar.2002 -- 10:54 AM, Christian Haul wrote:
> > On 01.Mar.2002 -- 06:45 PM, Vadim Gritsenko wrote:
> > > > From: Christian Haul [mailto:[EMAIL PROTECTED]]
> > > >
> > > > On 01.Mar.2002 -- 01:36 PM, Vadim Gritsenko wrote:
> > > > > > From: Christian Haul [mailto:[EMAIL PROTECTED]]
> > > >
> > > > > > I had trouble setting up the datasources with today's CVS. Is
> > > yours
> > > > > > better? (see my mail on "datasources / start sequence" or
> > > something
> > > > > > like that)
> > > >
> > > > > Fresh Cocoon checkout should work just fine, with all SQL samples.
> > > Just
> > > > > yesterday I was checking some of these.
> 
> > Vadim, just a little update -- you're right. But I'm right as well: The
> > problem occurs when using "-Dinclude.scratchpad.libs=yes"
> > Will investigate further.
> 
> More specifically: if I remove the portal components from cocoon.xconf
> all seems well again! So could someone knowledgeable of the initialization
> process have a look at what's going on here or give some pointers?

Things are getting odder and odder. My conclusion was premature. It
looks like removing any three component categories from cocoon.xconf
solves my problems... are there any known limits?

How is cocoon.xconf processed anyway? Is it completely under the control
of Avalon Excalibur? So would this be an Avalon issue, then?

Oh, I'm running SuSE Linux 7.3-i386 (2.4.18rc4), jdk 1.3 (ibm 1.3,
blackdown 1.3.1, sun 1.3.1, sun 1.3.1_02), tomcat 4.0.1, cocoon HEAD as
of today.

        Chris.

-- 
C h r i s t i a n       H a u l
[EMAIL PROTECTED]
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to