On 6/24/02 7:07 PM, "Vadim Gritsenko" <[EMAIL PROTECTED]> wrote:
>> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
>>
>> I quickly hacked a if(includes!=null) {} around the problem (should
>> rather have setup something for cache validation for the pipeline...if
>> I could only understand this!).
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
...
> Next try was to get 2.0.3 and install it, this time using Xerces+Xalan
> right from the start.
> This resulted in:
> java.lang.NullPointerException
> at org.apache.cocoon.components.xslt.XSLTProcessorImpl
> .resolve(XSLTProcessorImp
Ovidiu Predescu wrote:
> I am sure people on this list would like to hear more of your tales,
> hopefully not as horrid as your last experience. Please let us know what's
> your experience.
Ok, the tale continues. First, some non-Cocoon issues
lead me through some recursive problems including
rei
On 6/13/02 5:07 PM, "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Ovidiu Predescu wrote:
>> You didn't tell us how the story ended? Did you succeed in running C2 with
>> Saxon+AElfred?
>
> I finally succeeded and got a page. Within a few hours,
> I got all the interesting bits from my home grown
Ovidiu Predescu wrote:
> You didn't tell us how the story ended? Did you succeed in running C2 with
> Saxon+AElfred?
I finally succeeded and got a page. Within a few hours,
I got all the interesting bits from my home grown framework
and had the first pages up.
Then I hit the obnoxious null resolv
J.Pietschmann wrote:
> What's the general stance wrt using XML tools other than Xerces?
Clarification: I don't mind whether Cocoon requires a writable
DOM or not (would be nice if it were documented somewhere though)
What really worries me is that there was not the faintest hint
that the ominous
Vadim Gritsenko wrote:
> BTW, this is done via DOM API in the XConfToolTask.java. If you use
> AElfred for Cocoon build, and if AElfred's DOM is read-only... How this
> task will work?
It didn't work, obviously. The build suceeded anyway.
What's the general stance wrt using XML tools other than
> From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]]
>
> On 6/11/02 1:53 PM, "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
...
> > - Next access still bombs because the sitemap cannot be compiled
> > org.apache.avalon.framework.parameters.ParameterException:
> >The parameter 'compiler' does n
You can use Saxon's -X option to force saxon to use Xerces as the xml
parser. For command line it's something like:
java com.icl.saxon.StyleSheet -x org.apache.xerces.parsers.SAXParser
I don't know how to translate it to Cocoon instructions
Carlos
On 6/11/02 1:53 PM, "J.Pietschmann" <[EMAIL P
Hi,
This was a very entertaining reading, although I bet for you the whole
experience was very frustrating! See below for some comments.
On 6/11/02 1:53 PM, "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Hi,
> I set out for the quest of installing Tomcat+Cocoon with Saxon
> instead of the usual X
10 matches
Mail list logo