You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2010/08/19 11:26:16 UTC
[jira] Created: (TAP5-1251) Spring integration should not assume
the external context is successfully initalized
Spring integration should not assume the external context is successfully initalized
------------------------------------------------------------------------------------
Key: TAP5-1251
URL: https://issues.apache.org/jira/browse/TAP5-1251
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-spring
Affects Versions: 5.1.0.5
Reporter: Robert Munteanu
Priority: Minor
In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
{code}
ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
{code}
but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
The resulting error is
{code}
Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
Error Code: 500
Target Servlet: /business/Main.jsp
Error Stack:
java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
{code}
The lookup should be ajusted to use WebApplicationContextUtils.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1251) Spring integration should not assume
the external context is successfully initialized
Posted by "Robert Munteanu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated TAP5-1251:
----------------------------------
Summary: Spring integration should not assume the external context is successfully initialized (was: Spring integration should not assume the external context is successfully initalized)
Original Estimate: 0h
Remaining Estimate: 0h
Description:
In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
{code}ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
{code}
but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
The resulting error is
{code}
Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
Error Code: 500
Target Servlet: /business/Main.jsp
Error Stack:
java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
{code}
The lookup should be ajusted to use WebApplicationContextUtils.
was:
In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
{code}
ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
{code}
but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
The resulting error is
{code}
Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
Error Code: 500
Target Servlet: /business/Main.jsp
Error Stack:
java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
{code}
The lookup should be ajusted to use WebApplicationContextUtils.
> Spring integration should not assume the external context is successfully initialized
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1251
> URL: https://issues.apache.org/jira/browse/TAP5-1251
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-spring
> Affects Versions: 5.1.0.5
> Reporter: Robert Munteanu
> Priority: Minor
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
> {code}ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
> {code}
>
> but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
> The resulting error is
> {code}
> Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
> Error Code: 500
> Target Servlet: /business/Main.jsp
> Error Stack:
> java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
> at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
> at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
> at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
> at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
> {code}
> The lookup should be ajusted to use WebApplicationContextUtils.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1251) Spring integration should not assume
the external context is successfully initialized
Posted by "Robert Munteanu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated TAP5-1251:
----------------------------------
Summary: Spring integration should not assume the external context is successfully initialized (was: Spring integration should not assume the external context is successfully initalized)
Original Estimate: 0h
Remaining Estimate: 0h
Description:
In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
{code}ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
{code}
but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
The resulting error is
{code}
Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
Error Code: 500
Target Servlet: /business/Main.jsp
Error Stack:
java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
{code}
The lookup should be ajusted to use WebApplicationContextUtils.
was:
In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
{code}
ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
{code}
but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
The resulting error is
{code}
Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
Error Code: 500
Target Servlet: /business/Main.jsp
Error Stack:
java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
{code}
The lookup should be ajusted to use WebApplicationContextUtils.
> Spring integration should not assume the external context is successfully initialized
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1251
> URL: https://issues.apache.org/jira/browse/TAP5-1251
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-spring
> Affects Versions: 5.1.0.5
> Reporter: Robert Munteanu
> Priority: Minor
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> In SpringModuleDef , the following code assumes that the Spring context is successfully initialized:
> {code}ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
> {code}
>
> but the javadoc of that attribute states that "If the startup of the root context fails, this attribute can contain an exception or error as value. Use WebApplicationContextUtils for convenient lookup of the root WebApplicationContext. "
> The resulting error is
> {code}
> Error Message: javax.servlet.ServletException: Filter [tapestryFilter]: could not be initialized
> Error Code: 500
> Target Servlet: /business/Main.jsp
> Error Stack:
> java.lang.ClassCastException: org.springframework.beans.factory.BeanCreationException incompatible with org.springframework.web.context.ConfigurableWebApplicationContext
> at org.apache.tapestry5.internal.spring.SpringModuleDef.locateExternalContext(SpringModuleDef.java:61)
> at org.apache.tapestry5.internal.spring.SpringModuleDef.<init>(SpringModuleDef.java:83)
> at org.apache.tapestry5.spring.TapestrySpringFilter.provideExtraModuleDefs(TapestrySpringFilter.java:34)
> at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:76)
> {code}
> The lookup should be ajusted to use WebApplicationContextUtils.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.