cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: use my own configuration file for my avalon component
Date Wed, 27 Aug 2003 15:21:23 GMT
Sorry Antonio - I didn't read far enough...

> -----Original Message-----
> From: Ralph Goers 
> Sent: Wednesday, August 27, 2003 8:03 AM
> To: 'users@cocoon.apache.org'
> Subject: RE: use my own configuration file for my avalon component
> 
> 
> Your instructions do not configure a new component. They only 
> define a new
> role.  I found that to configure a new component I had to add it to
> cocoon.xconf by doing:
> 
>     <!-- This component builds a Properties object that other 
> components can
> reference by the role name -->
>     <component
> class="com.diginsite.services.presentation.cocoon.components.P
> ropertiesCompo
> nent"
>         logger="core.manager.properties"
>         role="com.diginsite.ib.busdelegate.AccountService">
>         <!-- java.naming.provider.url token will be replaced during
> deployment -->
>       <property name="java.naming.provider.url"
> value="@java.naming.provider.url@"/>
>       <property name="java.naming.factory.initial"
> value="weblogic.jndi.WLInitialContextFactory"/>
>     </component>
> 
> Ralph
> 
> > -----Original Message-----
> > From: Antonio Gallardo [mailto:agallardo@agsoftware.dnsalias.com]
> > Sent: Tuesday, August 26, 2003 8:09 PM
> > To: users@cocoon.apache.org
> > Subject: Re: use my own configuration file for my avalon component
> > 
> > 
> > maisonneuve nico dijo:
> > > i would use a configuration file (myconf.xconf) and no 
> > cocoon.xconf to
> > > configure this components.. but i don't know how do this..
> > 
> > Hi:
> > 
> > It is very easy :)
> > 
> > 1. You can edit your cocoon.xconf to "tell" him about your 
> > own config file
> > that address new roles:
> > 
> > <cocoon version="2.0" user-roles="myconf.xconf">
> >   ...
> > </cocoon>
> > 
> > 2. Your myconf.xconf can define new roles, for example:
> > 
> > <role-list>
> >    <role name="com.my.components.myOwnComponent"
> >     shorthand="mynewcomponent"
> >     default-class="com.my.components.myOwnComponentImplementation"/>
> > </role-list>
> > 
> > 3. Use your role inside cocoon.xconf:
> > 
> > <mynewcomponent>
> >    <parameter name="param1" value="value of param 1"/>
> >    <parameter name="param2" value="value of param 2"/>
> > </mynewcomponent>
> > 
> > 4. Restart Cocoon.
> > 
> > 5. Use this component as the others using lookup mynewcomponent.ROLE
> > 
> > Tha is all!
> > 
> > I hope this will help you.
> > 
> > Best Regards,
> > 
> > Antonio Gallardo
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message