[ 
http://www.stripesframework.org/jira/browse/STS-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben Gunter closed STS-775.
--------------------------

    Resolution: Duplicate

Closing as a duplicate of STS-773. Please refer to that ticket for future 
discussion.

> Jboss 6.0 M5 & Stripes 1.5.2: No default handler could be found for ActionBean
> ------------------------------------------------------------------------------
>
>                 Key: STS-775
>                 URL: http://www.stripesframework.org/jira/browse/STS-775
>             Project: Stripes
>          Issue Type: Bug
>    Affects Versions: Release 1.5.2
>         Environment: Jboss 6.0 M5 & Stripes 1.5.2
>            Reporter: Aparna Rallabandi
>             Fix For: Release 1.5.5
>
>
> Issue "[Stripes-users] Jboss 6.0 M5 & Stripes 1.5.2" detailed in the 
> stripes-users forum.
> Deatils:
> -----------
> Our project UI using stripes 1.5.2 was working fine on Jboss 6.0 M2 Metro 
> stack.
> There is web services communications which used Metro stack and then there is 
> the UI part using stripes.
> Now we are trying to migrate to Jboss 6.0 M5 which has a CXF stack.
> Essential changes have been made to the code so that the code compiles, 
> deploys and web services stack communicates with the desired entities when 
> deployed on M5.
> When I bring up the UI with the M5 version (using 
> http://localhost:8080/<appContextRoot>, I get the following exception stack 
> on entering my login password. 
> The UI is a war (containing stripes jars) packaged inside the final ear which 
> is deployed in Jboss.  
> I can get the main login page to open up.
> This has a stripes:password field with a login button.
> As soon as I enter the password and hit signIn, I get the exception in the 
> browser and my Jboss window.
> Any help or pointers are appreciated.   
> ------------------------------
> HTTP Status 500 -  
> type Exception report
> message
> description The server encountered an internal error () that prevented it 
> from fulfilling this request.
> exception  
> net.sourceforge.stripes.exception.StripesServletException: No default handler 
> could be found for ActionBean of type: com.a.b.c.web.stripes.AbcBean     
> net.sourceforge.stripes.controller.AnnotatedClassActionResolver.getDefaultHandler(AnnotatedClassActionResolver.java:639)
>     
> net.sourceforge.stripes.controller.DispatcherHelper$2.intercept(DispatcherHelper.java:171)
>      
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:158)
>      
> com.a.b.c.web.stripes.extensions.XXXInterceptor.intercept(XXXInterceptor.java:27)
>      
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:155)
>      
> net.sourceforge.stripes.controller.BeforeAfterMethodInterceptor.intercept(BeforeAfterMethodInterceptor.java:113)
>      
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:155)
>      
> net.sourceforge.stripes.controller.ExecutionContext.wrap(ExecutionContext.java:74)
>      
> net.sourceforge.stripes.controller.DispatcherHelper.resolveHandler(DispatcherHelper.java:156)
>      
> net.sourceforge.stripes.controller.DispatcherServlet.resolveHandler(DispatcherServlet.java:246)
>      
> net.sourceforge.stripes.controller.DispatcherServlet.service(DispatcherServlet.java:144)
>      
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)     
> net.sourceforge.stripes.controller.StripesFilter.doFilter(StripesFilter.java:247)
>      
> org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63)
>   
> note The full stack trace of the root cause is available in the JBoss 
> Web/3.0.0-beta-6 logs. 
> ------------

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to