[ 
https://issues.apache.org/jira/browse/ORCHESTRA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575053#action_12575053
 ] 

Scott O'Bryan commented on ORCHESTRA-15:
----------------------------------------

Portlet's don't have the ability to have filters.  Well, at least not in the 
generic sense.  You can map a filter to the portlet's servlet if you are using 
a local portal.

I've talked several times about my commons configurator project.  The code is 
all but complete, I just have to get the poms working.  The configurators work 
off of a custom FacesContectFactory and will allow you to initialize the types 
of object automatically, thus replacing much of the logic in your filters.  
They work in both servlet and portlet environments.  Give me a week and I'll 
try to get something in the MyFaces commons package that you can begin 
prototyping with.

Or you can wait till Portlet 2.0 which does add fiter support.  The problem 
with Portlet 2.0 filters is that they may be called even if you don't have a 
faces request, so for most usecases, the configurators are still the most 
efficient way to go.

Scott

> Orchestra in Portal Environment
> -------------------------------
>
>                 Key: ORCHESTRA-15
>                 URL: https://issues.apache.org/jira/browse/ORCHESTRA-15
>             Project: MyFaces Orchestra
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: myfaces1.1.5, liferay portal4.3.3, orchestra-core1.0, 
> tomcat 5.5
>            Reporter: Rashmi
>            Priority: Blocker
>         Attachments: orchestraPortlet.zip, stacktrace.txt
>
>
> In the portlet environment ConversationManager is not getting initialized. 
> The FrameworkAdapter.getCurrentInstance() is as well NULL.
> The part of the exception is as follows:
> Caused by: java.lang.NullPointerException 
>         at 
> org.apache.myfaces.orchestra.conversation.ConversationManager.getInstance(ConversationManager.java:90)
>  
>         at 
> org.apache.myfaces.orchestra.conversation.ConversationManager.getInstance(ConversationManager.java:76)
>  
>         at 
> org.apache.myfaces.orchestra.conversation.spring.AbstractSpringOrchestraScope.getBean(AbstractSpringOrchestraScope.java:125)
>  
>         at 
> org.apache.myfaces.orchestra.conversation.spring.AbstractSpringOrchestraScope.get(AbstractSpringOrchestraScope.java:117)
>  
>         at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:285)
>  
>         at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
>  
>         at 
> org.springframework.aop.target.SimpleBeanTargetSource.getTarget(SimpleBeanTargetSource.java:33)
>  
>         at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.getTarget(Cglib2AopProxy.java:661)
>  
>         at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:611)
>  
>         at 
> de.seat.mitarbeiterinfo.view.mitarbeiterlist$$EnhancerByCGLIB$$4f90561b.getMitarbeiterListModel(<generated>)
>  
>         ... 125 more 
> The filter is not working as expected in Portlet environment but works 
> perfetly well in norman Servlet container. 
> Can myfaces-portlet-bridge be used in someway to configure the filter to run 
> in portlet environment?
> Thanks and Regards,
> Rashmi   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to