cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Fagnani-Bell <>
Subject Re: How to make custom XSP-like language??
Date Mon, 10 Jun 2002 09:26:24 GMT

   I'm having a problem getting my new language to work. I created my own 
MarkupLanguage class, core-logicsheet, and added this to my cocoon.xconf:

      <component-instance class="" 
        <parameter name="prefix" value="xko"/>
        <parameter name="uri" value=""/>
        <target-language name="java">
          <parameter name="core-logicsheet" 

and I'm getting this exception:

markup-languages: ComponentSelector could not access the Component for 
hint: xko

Any ideas? Does the name attribute for <component-instance> set the 
hint? If so then is my component not getting set for the right role? I 
don't know how that's done in Avalon, but I assume it's 
MarkupLanguage.ROLE that's used. is what is causing the exception with this 

markupLanguage = 

Any help is appreciated,

On Saturday, June 1, 2002, at 12:10 PM, Justin Fagnani-Bell wrote:

> On Saturday, June 1, 2002, at 11:40 AM, Vadim Gritsenko wrote:
>>> I'm pretty confused by the difference in the cocoon.xconf files that
>>> come with the Cocoon instalation and the file in the documentation and
>>> your example in this email.
>> What documentation?
> The cocoon.xconf example on this page:
>>> This snippet seems match the cocoon.xconf in the online documentation,
>>> but not the cocoon.xconf file that's packaged with the 2.0.2 
>>> installer.
>> What do you mean?
> The cocoon.xconf in ${cocoon}/WEB-INF/ is quite a bit different than in 
> the documentation just referenced. It uses tags like:
>   <xml-parser class="org.apache.avalon.excalibur.xml.JaxpParser" 
> logger="core.xml-parser">
> instead of:
>   <component role="org.apache.cocoon.components.parser.Parser"
>              class="org.apache.cocoon.components.parser.JaxpParser"/>
> which is in the documentation.
> You shed light on this below... I guess it's just my ignorance of 
> Avalon configurations, and I've already started reading the Avalon docs 
> and source and, however the differences between the docs 
> and distribution confused me a bit.
> Thanks a lot for your help.
> Justin
>> You will have to study Avalon to get deeper knowledge of syntax of 
>> xconf
>> file.
>> In short, you can use either <component-instance> tag or <myothertag>,
>> but latter must be defined then in the cocoon.roles file (inside
>> cocoon.jar).
>> Vadim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message