Fwd: [portal] Multiple Portal Configurations in cocoon.xconf

[Alex Romayev <ro...@yahoo.com>]

I posted this on the users list last week and got no
reply, so I've decided to try it here as well.

-Alex

--- Alex Romayev <ro...@yahoo.com> wrote:
> Date: Thu, 11 Mar 2004 07:48:54 -0800 (PST)
> From: Alex Romayev <ro...@yahoo.com>
> Subject: [portal] Multiple Portal Configurations in
> cocoon.xconf
> To: users@cocoon.apache.org
> 
> Hi,
> 
> I'd like to be able to create my own portal
> configuration and install it using XConfToolTask
> into
> cocoon.xconf (unless there is a better option).
> 
> Is it possible to have multiple portal
> configurations?
>  I've looked at portal.samplesxconf and
> authportal.samplesxconf.  It seems that the place to
> define portals is here:
> 
> <portals>
>   <!-- Configure your portals here: -->
>   <portal name="portal">           
>
<profile-manager>org.apache.cocoon.portal.profile.ProfileManager/Auth</profile-manager>
>   </portal>
> </portals>
> 
> If I want to use the same ProfileManager class,
> should
> I create a different role here?
> 
> Now, I don't understand how various portal
> components,
> like renderers, coplets, etc are linked to the
> specific portal configuration.  Unless the idea is
> to
> use them across portals?
> 
> Thanks,
> -Alex
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
> 

RE: [portal] Multiple Portal Configurations in cocoon.xconf

[Carsten Ziegeler <cz...@s-und-n.de>]

Alex Romayev wrote:
> > No, just another entry:
> > <portal name="anotherportal">           
> 
> OK, where is this name going to be used?  Is it the name of 
> the application in sitemap or application's configuration?
> 
Both: the name of the application configuration in the sitemap
for the authentication and each sitemap component that requires
a "portal-name" parameter (portal generator etc.)

> 
> One thing I wanted to do was to have both the sample portal 
> and my portal available in development env and only my portal 
> available in production env.  I understand, if I don't build 
> samples in production, portal configuration will not be 
> available.  
Yes.

> At the same time if I have my own configuration, 
> then in development it will be conflicting with the sample 
> one.  Is this correct?  
Yes :(

> Any ideas on how to get around this?
> 
Give the components you want to use in your portal an own/unique
name, so that this name doesn't conflict with the demo portal.
For example, give every renderer you use a different name etc.

Carsten

RE: [portal] Multiple Portal Configurations in cocoon.xconf

[Alex Romayev <ro...@yahoo.com>]

--- Carsten Ziegeler <cz...@s-und-n.de> wrote:
> Alex Romayev wrote:
> > Is it possible to have multiple portal
> configurations?
> Yes, it should be, though I've never tested it :)

Great, I'll give it a show then :-)

> 
> >  I've looked at portal.samplesxconf and 
> > authportal.samplesxconf.  It 
> > seems that the place to define portals is here:
> > 
> > <portals>
> >   <!-- Configure your portals here: -->
> >   <portal name="portal">           
> >
> >
>
<profile-manager>org.apache.cocoon.portal.profile.ProfileManag
> > er/Auth</profile-manager>
> >   </portal>
> > </portals>
> > 
> > If I want to use the same ProfileManager class,
> should I create a 
> > different role here?
> No, just another entry:
> <portal name="anotherportal">           

OK, where is this name going to be used?  Is it the
name of the application in sitemap or application's
configuration?

> 
> 
>
<profile-manager>org.apache.cocoon.portal.profile.ProfileManag
>  er/Auth</profile-manager>
> </portal>
> 
> > 
> > Now, I don't understand how various portal
> components, like 
> > renderers, 
> > coplets, etc are linked to the specific portal 
> > configuration.  Unless 
> > the idea is to use them across portals?
> > 
> Yes, this is the current idea - all components
> should be usable in
> each portal (to make the configuration a little bit
> easier :) ). So
> declaring a portal like listed above and using that
> portal in the
> sitemap should do it (hopefully).

One thing I wanted to do was to have both the sample
portal and my portal available in development env and
only my portal available in production env.  I
understand, if I don't build samples in production,
portal configuration will not be available.  At the
same time if I have my own configuration, then in
development it will be conflicting with the sample
one.  Is this correct?  Any ideas on how to get around
this?

Thanks,
-Alex

> 
> Carsten
> 

RE: [portal] Multiple Portal Configurations in cocoon.xconf

[Carsten Ziegeler <cz...@s-und-n.de>]

Alex Romayev wrote:
> Is it possible to have multiple portal configurations?
Yes, it should be, though I've never tested it :)

>  I've looked at portal.samplesxconf and 
> authportal.samplesxconf.  It 
> seems that the place to define portals is here:
> 
> <portals>
>   <!-- Configure your portals here: -->
>   <portal name="portal">           
>
> <profile-manager>org.apache.cocoon.portal.profile.ProfileManag
> er/Auth</profile-manager>
>   </portal>
> </portals>
> 
> If I want to use the same ProfileManager class, should I create a 
> different role here?
No, just another entry:
<portal name="anotherportal">           

 <profile-manager>org.apache.cocoon.portal.profile.ProfileManag
 er/Auth</profile-manager>
</portal>

> 
> Now, I don't understand how various portal components, like 
> renderers, 
> coplets, etc are linked to the specific portal 
> configuration.  Unless 
> the idea is to use them across portals?
> 
Yes, this is the current idea - all components should be usable in
each portal (to make the configuration a little bit easier :) ). So
declaring a portal like listed above and using that portal in the
sitemap should do it (hopefully).

Carsten