Cocoon and Clustering

2004-07-27 Thread Stefan Eichenhofer

Hi, 

has anyone experience with deploying cocoon on a Tomcat 5 or WebSphere
5 Cluster?
According to the Tomcat 5 documentation
all you have to do is:
" All your
session attributes must implement java.io.Serializable"
It doesn't look this is already the case in cocoon 2.1.5,
but sounds easy enough to implement. 

thnx for help

Stefan 



Stefan Eichenhofer ist außer Haus.

2004-05-05 Thread Stefan Eichenhofer




Ich werde ab  06.05.2004 nicht im Büro sein. Ich kehre zurück am
17.05.2004.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.


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



Coplet configuration

2004-02-26 Thread Stefan Eichenhofer

Hi everyone, 

i'm trying to configure the status of
coplets, like minimized, maximized , visible
There used to be a  tag
in the portal-fw, but that doesn't seem to be working any more. In the
wiki is a example using the  tag, same effect. 
Could someone point me in the right
direction?

The next step will be to enable users
to edit and save the portal configuration. Any hints regarding that would
be greatly aprectiated. 

thnx

Stefan 

btw, does anyone know what "layout-renderer-name"
does in this context?
 

How to access http-request parameters in a coplet

2004-01-20 Thread Stefan Eichenhofer

Hi everyone, 

is there a possibilty to directly access
the http request parameters from within a coplet? Or, more generally, how
are params passed to a coplet?

thnx for help 

stefan


events in the portal engine

2003-12-17 Thread Stefan Eichenhofer

Hi all, 

one more portal-question: How does a
coplet subsribe itself to events? 
I've created a simple "Hello World"
coplet class (implementing CopletAdapter) and successfully registered it
into the portal. This is working so far, but now i want the coplet to be
informed if another coplet creates an event. 
What i can see from the URICopletAdapter
is that the coplet has to implement the Interface Subscriber.
But how is the connection to DefaultEventManager
established? The DefaultEventManager calls the getEventType() and inform()
methods of the URICopletAdapter class, but where does it get the information
to do so?

thnx for help!

stefan



Antwort: RE: Portal Engine Security

2003-12-16 Thread Stefan Eichenhofer

thnx, i've tried that and it works :)
now im looking for the file to configure
- restricted access to coplets according
to role or user
- status of the coplets (mandatory,
sizeable, minimized/maximized .)

stefan
 



"Carsten Ziegeler" <[EMAIL PROTECTED]>
schrieb am 15.12.2003 10:45:38:

> The new portal engine has the same concept /user/role/global as the
old
> portal-framework.
> The profiles for roles/user have currently the name ...-role-xy and
> ...-user-xy.
> 
> HTH
> Carsten
> -Original Message-
> From: Stefan Eichenhofer [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 15, 2003 10:15 AM
> To: [EMAIL PROTECTED]
> Subject: Portal Engine Security
> 
> 
> 
> Hi,
> 
> i'm trying to find my way around the portal-engine. Looking at the
example i
> was able to figure out how the layout and skin of the portal works.
> What i couldn't find is where the allocation useroles/user to portlet
takes
> place.
> Is there something similar to the user/role/global deltas that where
used in
> the portal-framework ?
> 
> thnx for any help
> 
> Stefan
> 
> btw. im somebody knows where to find some documentation on the new
> portal-engine
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


Portal Engine Security

2003-12-15 Thread Stefan Eichenhofer

Hi, 

i'm trying to find my way around the
portal-engine. Looking at the example i was able to figure out how the
layout and skin of the portal works. 
What i couldn't find is where the allocation
useroles/user to portlet takes place. 
Is there something similar to the user/role/global
deltas that where used in the portal-framework ?

thnx for any help

Stefan 

btw. im somebody knows where to find
some documentation on the new portal-engine 




Antwort: portal-fw: problems setting up a new konfiguration

2003-12-02 Thread Stefan Eichenhofer

found the problem: the entry 

is needed in cocoon.roles.


Stefan Eichenhofer <[EMAIL PROTECTED]>
schrieb am 01.12.2003 19:29:48:

> 
> Hi, 
> 
> i'm trying to create a eclipse project to develop a portal. 
> what i did so far: 
> - downloaded cocoon 2.1.3 
> - ran build.bat, played with the examples, decided this is great stuff

> - then i build the target eclipse-project an createt a eclipse 
> project according to a wiki-doc i found at cocoon.apache.org (LoadInEclipse)

> - started tomcat via eclipse/sysdeo plugin 
> - tried a simple pipline 
> 
> so far everything works great. 
> 
> when i try to set up a sitemap with a 
the 
> problems start. basically i just want to protect a sample file to

> see how everything works. 
> so i copied stuff from the portal-fw sitemap to my sitemap and tried
> to protect the above mentioned simple pipeline. 
> this works in the webapp that was created by build.bat, but not in

> the webapp created by build eclipse project. 
> the error: 
> 
> Could not find component (key [org.apache.cocoon.webapps.
> authentication.AuthenticationManager]) (Key='org.apache.cocoon.
> webapps.authentication.AuthenticationManager') 
> 
> so i guess i'm probably not making the right connections between the
> configuration files. 
> my sitemap seems to be right, works in the sample webapp. i'm 
> probably missing some avalon configuration parameters in cocoon.
> xconf, but can't really find them. 
> 
> could somebody please point out what i'm obviously overlooking? 
> 
> thnx 
> 
> Stefan 
> 
> 
> sitemap: 
> 
>  
> 

>  
>  
>         
> webapps.authentication.acting.AuthAction"/> 
>         
> webapps.authentication.acting.LoginAction"/> 
>         
> webapps.authentication.acting.LogoutAction"/> 
>         
> webapps.authentication.acting.LoggedInAction"/> 
>  
>  
>         
> apache.cocoon.webapps.portal.generation.PortalGenerator"/>

>         
> apache.cocoon.webapps.portal.generation.ConfigurationGenerator"/>

>  
>  
>  
> 
> 
> this works 
>  
>         

>                 
>                 
>                 

>          
>  
> 
>  
>          
>          
>                  
>                  
>                  
>                 

> <---snip> 
>                 

>                 

>          
>          
>  
> 
> this causes the exception 
>  
>         

>         

>          
>         
>         
>          
>          
>          
>  
> 
> 
>  
>  
> 
> 
> 
> 
> 
> 
> Exception complete: 
> 
> WARN    (2003-12-01) 19:07.54:361   [sitemap] 
> (/c231/officenet/HelloWorldSicher) 
> Thread-8/ExcaliburComponentManager: ComponentLocator exception from

> parent CM during lookup. 
> org.apache.avalon.framework.component.ComponentException: Could not

> find component (key [org.apache.cocoon.webapps.authentication.
> AuthenticationManager]) 
>         at org.apache.avalon.excalibur.component.
> ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:297)

>         at org.apache.cocoon.components.CocoonComponentManager.
> lookup(CocoonComponentManager.java:324) 
>         at org.apache.avalon.excalibur.component.
> ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:226)

>         at org.apache.cocoon.components.CocoonComponentManager.
> lookup(CocoonComponentManager.java:324) 
>         at org.apache.avalon.excalibur.component.
> ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:226)

>         at org.apache.cocoon.components.CocoonComponentManager.
> lookup(CocoonComponentManager.java:324) 
>         at org.apache.avalon.framework.service.
> WrapperServiceManager.lookup(WrapperServiceManager.java:106) 
>         at org.apache.cocoon.webapps.authentication.acting.
> AuthAction.act(AuthAction.java:99) 
>         at org.apache.cocoon.components.treeprocessor.sitemap.
> ActTypeNode.invoke(ActTypeNode.java:152) 
>         at org.apache.cocoon.components.treeprocessor.
> AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
>         at org.apache.cocoon.components.treeprocessor.sitemap.
> PreparableMatchNode.invoke(PreparableMatchNode.java:164) 
>         at org.apache.cocoon.components.treeprocessor.
> AbstractParentProcessingNode.
> invokeNodes(AbstractParentProcessingNode.java:108) 
>         at org.apache.cocoon.components.treeprocessor.sitemap.
> PipelineNode.invoke(PipelineNode.java:163) 
>         at org.apache.cocoon.components.treeprocessor.
> AbstractParentProcessingNode.
>

portal-fw: problems setting up a new konfiguration

2003-12-01 Thread Stefan Eichenhofer

Hi, 

i'm trying to create a eclipse project
to develop a portal. 
what i did so far: 
- downloaded cocoon 2.1.3
- ran build.bat, played with the examples,
decided this is great stuff
- then i build the target eclipse-project
an createt a eclipse project according to a wiki-doc i found at cocoon.apache.org
(LoadInEclipse)
- started tomcat via eclipse/sysdeo
plugin
- tried a simple pipline 

so far everything works great. 

when i try to set up a sitemap with
a  the problems start. basically i just want
to protect a sample file to see how everything works. 
so i copied stuff from the portal-fw
sitemap to my sitemap and tried to protect the above mentioned simple pipeline.

this works in the webapp that was created
by build.bat, but not in the webapp created by build eclipse project. 
the error: 

Could not find component (key [org.apache.cocoon.webapps.authentication.AuthenticationManager])
(Key='org.apache.cocoon.webapps.authentication.AuthenticationManager')

so i guess i'm probably not making the
right connections between the configuration files. 
my sitemap seems to be right, works
in the sample webapp. i'm probably missing some avalon configuration parameters
in cocoon.xconf, but can't really find them. 

could somebody please point out what
i'm obviously overlooking?

thnx 

Stefan 


sitemap: 





        
        
        
        


        
        





this works 

        
         
      
         
      
         
      
        



        
        
         
      
         
      
         
      

         
      
<---snip>
         
      
         
      
        
        


this causes the exception

        
        
        
        
        
        
        
        












Exception complete:

WARN    (2003-12-01) 19:07.54:361
  [sitemap] (/c231/officenet/HelloWorldSicher) Thread-8/ExcaliburComponentManager:
ComponentLocator exception from parent CM during lookup.
org.apache.avalon.framework.component.ComponentException:
Could not find component (key [org.apache.cocoon.webapps.authentication.AuthenticationManager])
        at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:297)
        at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:324)
        at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:226)
        at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:324)
        at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:226)
        at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:324)
        at
org.apache.avalon.framework.service.WrapperServiceManager.lookup(WrapperServiceManager.java:106)
        at
org.apache.cocoon.webapps.authentication.acting.AuthAction.act(AuthAction.java:99)
        at
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:152)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:163)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:152)
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:354)
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
        at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:133)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:163)
        at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
        at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:152)
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:354)
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(Tree