You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Duong BaTien <du...@gmail.com> on 2005/04/05 19:13:38 UTC
Shale And Spring: Using Spring Dependency Injection With Shale
I reply to dev list but the mail was not accepted.
>BaTien
>
>
>
>>>Dear Wiki user,
>>>
>>>You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
>>>
>>>The following page has been changed by CraigMcClanahan:
>>>http://wiki.apache.org/struts/ShaleAndSpring
>>>
>>>New page:
>>>+++-- Shale And Spring: Using Spring Dependency Injection With Shale
>>>
>>>Since version 1.1.5 of Spring, that framework has included a convenient integration with JavaServer Faces that may be leveraged in a Shale based application. The integration includes a custom JSF {{{VariableResolver}}} implementation that is invoked first whenever a value binding or method binding expression is evaluated. In other words, the JSF managed beans facility behaves like this:
>>>
>>>* If there is a registered managed bean for the specified name, use the standard JSF facilities to create it (as usual).
>>>
>>>* If there is a configuration for this bean in the Spring WebApplicationContext, use Spring's BeanFactory to create it.
>>>
>>>* If neither of the above facilities recognizes the name, return {{{null}}}.
>>>
>>>This technique allows you to transparently use JSF value binding expressions (either in components, or through programmatic manipulation) that access beans managed by Spring instead of by the JSF managed beans facility.
>>>
>>>
>>>
>>Hello Craig:
>>
>>I make a quick test on my site.
>>
>>The current working condition has shale.jar, spring-core.jar,
>>spring-context.jar and spring-web.jar (1.1.5) . It works with or without
>>using org.springframework.web.jsf.DelegatingVariableResolver
>>
>>Now i add shale-spring.jar, it has the exception as in the enclosed
>>psi1.log. The exception happens with or without the inclusion of
>>org.springframework.web.jsf.DelegatingVariableResolver in faces config.
>>
>>BaTien
>>DBGROUPS
>>
>>
>>
>
>--------------010504080503040606030709
>Content-Type: text/plain;
> name="psi1.log"
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: inline;
> filename="psi1.log"
>
>2005-04-05 09:18:24,622 [main] DEBUG javax.faces.application.ApplicationF=
>actory - New ApplicationFactory instance created
>2005-04-05 09:18:24,677 [main] ERROR org.apache.myfaces.webapp.StartupSer=
>vletContextListener - Error initializing ServletContext
>java.lang.IllegalArgumentException: Class org.springframework.web.context=
>=2EWebApplicationContext is no javax.faces.el.VariableResolver
> at org.apache.myfaces.config.FacesConfigurator.getApplicationObject(Face=
>sConfigurator.java:535)
> at org.apache.myfaces.config.FacesConfigurator.configureApplication(Face=
>sConfigurator.java:481)
> at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurat=
>or.java:193)
> at org.apache.myfaces.webapp.StartupServletContextListener.initFaces(Sta=
>rtupServletContextListener.java:105)
> at org.apache.myfaces.webapp.StartupServletContextListener.contextInitia=
>lized(StartupServletContextListener.java:88)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContex=
>t.java:3827)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4=
>343)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>
> at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478=
>)
> at org.apache.catalina.core.StandardService.start(StandardService.java:4=
>80)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:231=
>3)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
>java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
>sorImpl.java:25)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Shale And Spring: Using Spring Dependency Injection With Shale
Posted by Duong BaTien <du...@gmail.com>.
Hello list:
I like to report that using today 20050407 shale.jar and
shale-spring.jar, shale and spring work togather as documented by Craig.
BaTien
DBGROUPS
==========================
Duong BaTien wrote:
> Thanks. I will find time to do it.
>
> BaTien
> DBGROUPS
>
>
> Craig McClanahan wrote:
>
>> Please try out the latest nightly version of the "use cases" sample
>> app. It uses Spring to provide the business logic object (and
>> associated DAO) for the login use case.
>>
>> Craig
>>
>> On Apr 5, 2005 10:13 AM, Duong BaTien <du...@gmail.com> wrote:
>>
>>
>>> I reply to dev list but the mail was not accepted.
>>>
>>>
>>>
>>>> BaTien
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>> Dear Wiki user,
>>>>>>
>>>>>> You have subscribed to a wiki page or wiki category on "Struts
>>>>>> Wiki" for change notification.
>>>>>>
>>>>>> The following page has been changed by CraigMcClanahan:
>>>>>> http://wiki.apache.org/struts/ShaleAndSpring
>>>>>>
>>>>>> New page:
>>>>>> +++-- Shale And Spring: Using Spring Dependency Injection With Shale
>>>>>>
>>>>>> Since version 1.1.5 of Spring, that framework has included a
>>>>>> convenient integration with JavaServer Faces that may be
>>>>>> leveraged in a Shale based application. The integration includes
>>>>>> a custom JSF {{{VariableResolver}}} implementation that is
>>>>>> invoked first whenever a value binding or method binding
>>>>>> expression is evaluated. In other words, the JSF managed beans
>>>>>> facility behaves like this:
>>>>>>
>>>>>> * If there is a registered managed bean for the specified name,
>>>>>> use the standard JSF facilities to create it (as usual).
>>>>>>
>>>>>> * If there is a configuration for this bean in the Spring
>>>>>> WebApplicationContext, use Spring's BeanFactory to create it.
>>>>>>
>>>>>> * If neither of the above facilities recognizes the name, return
>>>>>> {{{null}}}.
>>>>>>
>>>>>> This technique allows you to transparently use JSF value binding
>>>>>> expressions (either in components, or through programmatic
>>>>>> manipulation) that access beans managed by Spring instead of by
>>>>>> the JSF managed beans facility.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Hello Craig:
>>>>>
>>>>> I make a quick test on my site.
>>>>>
>>>>> The current working condition has shale.jar, spring-core.jar,
>>>>> spring-context.jar and spring-web.jar (1.1.5) . It works with or
>>>>> without
>>>>> using org.springframework.web.jsf.DelegatingVariableResolver
>>>>>
>>>>> Now i add shale-spring.jar, it has the exception as in the enclosed
>>>>> psi1.log. The exception happens with or without the inclusion of
>>>>> org.springframework.web.jsf.DelegatingVariableResolver in faces
>>>>> config.
>>>>>
>>>>> BaTien
>>>>> DBGROUPS
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------010504080503040606030709
>>>> Content-Type: text/plain;
>>>> name="psi1.log"
>>>> Content-Transfer-Encoding: quoted-printable
>>>> Content-Disposition: inline;
>>>> filename="psi1.log"
>>>>
>>>> 2005-04-05 09:18:24,622 [main] DEBUG
>>>> javax.faces.application.ApplicationF=
>>>> actory - New ApplicationFactory instance created
>>>> 2005-04-05 09:18:24,677 [main] ERROR
>>>> org.apache.myfaces.webapp.StartupSer=
>>>> vletContextListener - Error initializing ServletContext
>>>> java.lang.IllegalArgumentException: Class
>>>> org.springframework.web.context=
>>>> =2EWebApplicationContext is no javax.faces.el.VariableResolver
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.getApplicationObject(Face=
>>>> sConfigurator.java:535)
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.configureApplication(Face=
>>>> sConfigurator.java:481)
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurat=
>>>> or.java:193)
>>>> at
>>>> org.apache.myfaces.webapp.StartupServletContextListener.initFaces(Sta=
>>>> rtupServletContextListener.java:105)
>>>> at
>>>> org.apache.myfaces.webapp.StartupServletContextListener.contextInitia=
>>>> lized(StartupServletContextListener.java:88)
>>>> at
>>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContex=
>>>> t.java:3827)
>>>> at
>>>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4=
>>>> 343)
>>>> at
>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>>
>>>> at
>>>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
>>>> at
>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>>
>>>> at
>>>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478=
>>>> )
>>>> at
>>>> org.apache.catalina.core.StandardService.start(StandardService.java:4=
>>>> 80)
>>>> at
>>>> org.apache.catalina.core.StandardServer.start(StandardServer.java:231=
>>>> 3)
>>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
>>>> java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
>>>> sorImpl.java:25)
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: user-help@struts.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Shale And Spring: Using Spring Dependency Injection With Shale
Posted by Duong BaTien <du...@gmail.com>.
Hello list:
I like to report that using today 20050407 shale.jar and
shale-spring.jar, shale and spring work togather as documented by Craig.
BaTien
DBGROUPS
==========================
Duong BaTien wrote:
> Thanks. I will find time to do it.
>
> BaTien
> DBGROUPS
>
>
> Craig McClanahan wrote:
>
>> Please try out the latest nightly version of the "use cases" sample
>> app. It uses Spring to provide the business logic object (and
>> associated DAO) for the login use case.
>>
>> Craig
>>
>> On Apr 5, 2005 10:13 AM, Duong BaTien <du...@gmail.com> wrote:
>>
>>
>>> I reply to dev list but the mail was not accepted.
>>>
>>>
>>>
>>>> BaTien
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>> Dear Wiki user,
>>>>>>
>>>>>> You have subscribed to a wiki page or wiki category on "Struts
>>>>>> Wiki" for change notification.
>>>>>>
>>>>>> The following page has been changed by CraigMcClanahan:
>>>>>> http://wiki.apache.org/struts/ShaleAndSpring
>>>>>>
>>>>>> New page:
>>>>>> +++-- Shale And Spring: Using Spring Dependency Injection With Shale
>>>>>>
>>>>>> Since version 1.1.5 of Spring, that framework has included a
>>>>>> convenient integration with JavaServer Faces that may be
>>>>>> leveraged in a Shale based application. The integration includes
>>>>>> a custom JSF {{{VariableResolver}}} implementation that is
>>>>>> invoked first whenever a value binding or method binding
>>>>>> expression is evaluated. In other words, the JSF managed beans
>>>>>> facility behaves like this:
>>>>>>
>>>>>> * If there is a registered managed bean for the specified name,
>>>>>> use the standard JSF facilities to create it (as usual).
>>>>>>
>>>>>> * If there is a configuration for this bean in the Spring
>>>>>> WebApplicationContext, use Spring's BeanFactory to create it.
>>>>>>
>>>>>> * If neither of the above facilities recognizes the name, return
>>>>>> {{{null}}}.
>>>>>>
>>>>>> This technique allows you to transparently use JSF value binding
>>>>>> expressions (either in components, or through programmatic
>>>>>> manipulation) that access beans managed by Spring instead of by
>>>>>> the JSF managed beans facility.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Hello Craig:
>>>>>
>>>>> I make a quick test on my site.
>>>>>
>>>>> The current working condition has shale.jar, spring-core.jar,
>>>>> spring-context.jar and spring-web.jar (1.1.5) . It works with or
>>>>> without
>>>>> using org.springframework.web.jsf.DelegatingVariableResolver
>>>>>
>>>>> Now i add shale-spring.jar, it has the exception as in the enclosed
>>>>> psi1.log. The exception happens with or without the inclusion of
>>>>> org.springframework.web.jsf.DelegatingVariableResolver in faces
>>>>> config.
>>>>>
>>>>> BaTien
>>>>> DBGROUPS
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------010504080503040606030709
>>>> Content-Type: text/plain;
>>>> name="psi1.log"
>>>> Content-Transfer-Encoding: quoted-printable
>>>> Content-Disposition: inline;
>>>> filename="psi1.log"
>>>>
>>>> 2005-04-05 09:18:24,622 [main] DEBUG
>>>> javax.faces.application.ApplicationF=
>>>> actory - New ApplicationFactory instance created
>>>> 2005-04-05 09:18:24,677 [main] ERROR
>>>> org.apache.myfaces.webapp.StartupSer=
>>>> vletContextListener - Error initializing ServletContext
>>>> java.lang.IllegalArgumentException: Class
>>>> org.springframework.web.context=
>>>> =2EWebApplicationContext is no javax.faces.el.VariableResolver
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.getApplicationObject(Face=
>>>> sConfigurator.java:535)
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.configureApplication(Face=
>>>> sConfigurator.java:481)
>>>> at
>>>> org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurat=
>>>> or.java:193)
>>>> at
>>>> org.apache.myfaces.webapp.StartupServletContextListener.initFaces(Sta=
>>>> rtupServletContextListener.java:105)
>>>> at
>>>> org.apache.myfaces.webapp.StartupServletContextListener.contextInitia=
>>>> lized(StartupServletContextListener.java:88)
>>>> at
>>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContex=
>>>> t.java:3827)
>>>> at
>>>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4=
>>>> 343)
>>>> at
>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>>
>>>> at
>>>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
>>>> at
>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>>
>>>> at
>>>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478=
>>>> )
>>>> at
>>>> org.apache.catalina.core.StandardService.start(StandardService.java:4=
>>>> 80)
>>>> at
>>>> org.apache.catalina.core.StandardServer.start(StandardServer.java:231=
>>>> 3)
>>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
>>>> java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
>>>> sorImpl.java:25)
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: user-help@struts.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Shale And Spring: Using Spring Dependency Injection With Shale
Posted by Duong BaTien <du...@gmail.com>.
Thanks. I will find time to do it.
BaTien
DBGROUPS
Craig McClanahan wrote:
>Please try out the latest nightly version of the "use cases" sample
>app. It uses Spring to provide the business logic object (and
>associated DAO) for the login use case.
>
>Craig
>
>On Apr 5, 2005 10:13 AM, Duong BaTien <du...@gmail.com> wrote:
>
>
>>I reply to dev list but the mail was not accepted.
>>
>>
>>
>>>BaTien
>>>
>>>
>>>
>>>
>>>
>>>>>Dear Wiki user,
>>>>>
>>>>>You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
>>>>>
>>>>>The following page has been changed by CraigMcClanahan:
>>>>>http://wiki.apache.org/struts/ShaleAndSpring
>>>>>
>>>>>New page:
>>>>>+++-- Shale And Spring: Using Spring Dependency Injection With Shale
>>>>>
>>>>>Since version 1.1.5 of Spring, that framework has included a convenient integration with JavaServer Faces that may be leveraged in a Shale based application. The integration includes a custom JSF {{{VariableResolver}}} implementation that is invoked first whenever a value binding or method binding expression is evaluated. In other words, the JSF managed beans facility behaves like this:
>>>>>
>>>>>* If there is a registered managed bean for the specified name, use the standard JSF facilities to create it (as usual).
>>>>>
>>>>>* If there is a configuration for this bean in the Spring WebApplicationContext, use Spring's BeanFactory to create it.
>>>>>
>>>>>* If neither of the above facilities recognizes the name, return {{{null}}}.
>>>>>
>>>>>This technique allows you to transparently use JSF value binding expressions (either in components, or through programmatic manipulation) that access beans managed by Spring instead of by the JSF managed beans facility.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Hello Craig:
>>>>
>>>>I make a quick test on my site.
>>>>
>>>>The current working condition has shale.jar, spring-core.jar,
>>>>spring-context.jar and spring-web.jar (1.1.5) . It works with or without
>>>>using org.springframework.web.jsf.DelegatingVariableResolver
>>>>
>>>>Now i add shale-spring.jar, it has the exception as in the enclosed
>>>>psi1.log. The exception happens with or without the inclusion of
>>>>org.springframework.web.jsf.DelegatingVariableResolver in faces config.
>>>>
>>>>BaTien
>>>>DBGROUPS
>>>>
>>>>
>>>>
>>>>
>>>>
>>>--------------010504080503040606030709
>>>Content-Type: text/plain;
>>>name="psi1.log"
>>>Content-Transfer-Encoding: quoted-printable
>>>Content-Disposition: inline;
>>>filename="psi1.log"
>>>
>>>2005-04-05 09:18:24,622 [main] DEBUG javax.faces.application.ApplicationF=
>>>actory - New ApplicationFactory instance created
>>>2005-04-05 09:18:24,677 [main] ERROR org.apache.myfaces.webapp.StartupSer=
>>>vletContextListener - Error initializing ServletContext
>>>java.lang.IllegalArgumentException: Class org.springframework.web.context=
>>>=2EWebApplicationContext is no javax.faces.el.VariableResolver
>>> at org.apache.myfaces.config.FacesConfigurator.getApplicationObject(Face=
>>>sConfigurator.java:535)
>>> at org.apache.myfaces.config.FacesConfigurator.configureApplication(Face=
>>>sConfigurator.java:481)
>>> at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurat=
>>>or.java:193)
>>> at org.apache.myfaces.webapp.StartupServletContextListener.initFaces(Sta=
>>>rtupServletContextListener.java:105)
>>> at org.apache.myfaces.webapp.StartupServletContextListener.contextInitia=
>>>lized(StartupServletContextListener.java:88)
>>> at org.apache.catalina.core.StandardContext.listenerStart(StandardContex=
>>>t.java:3827)
>>> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4=
>>>343)
>>> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>
>>> at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
>>> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
>>>
>>> at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478=
>>>)
>>> at org.apache.catalina.core.StandardService.start(StandardService.java:4=
>>>80)
>>> at org.apache.catalina.core.StandardServer.start(StandardServer.java:231=
>>>3)
>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
>>>java:39)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
>>>sorImpl.java:25)
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>For additional commands, e-mail: user-help@struts.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Shale And Spring: Using Spring Dependency Injection With Shale
Posted by Craig McClanahan <cr...@gmail.com>.
Please try out the latest nightly version of the "use cases" sample
app. It uses Spring to provide the business logic object (and
associated DAO) for the login use case.
Craig
On Apr 5, 2005 10:13 AM, Duong BaTien <du...@gmail.com> wrote:
> I reply to dev list but the mail was not accepted.
>
> >BaTien
> >
> >
> >
> >>>Dear Wiki user,
> >>>
> >>>You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
> >>>
> >>>The following page has been changed by CraigMcClanahan:
> >>>http://wiki.apache.org/struts/ShaleAndSpring
> >>>
> >>>New page:
> >>>+++-- Shale And Spring: Using Spring Dependency Injection With Shale
> >>>
> >>>Since version 1.1.5 of Spring, that framework has included a convenient integration with JavaServer Faces that may be leveraged in a Shale based application. The integration includes a custom JSF {{{VariableResolver}}} implementation that is invoked first whenever a value binding or method binding expression is evaluated. In other words, the JSF managed beans facility behaves like this:
> >>>
> >>>* If there is a registered managed bean for the specified name, use the standard JSF facilities to create it (as usual).
> >>>
> >>>* If there is a configuration for this bean in the Spring WebApplicationContext, use Spring's BeanFactory to create it.
> >>>
> >>>* If neither of the above facilities recognizes the name, return {{{null}}}.
> >>>
> >>>This technique allows you to transparently use JSF value binding expressions (either in components, or through programmatic manipulation) that access beans managed by Spring instead of by the JSF managed beans facility.
> >>>
> >>>
> >>>
> >>Hello Craig:
> >>
> >>I make a quick test on my site.
> >>
> >>The current working condition has shale.jar, spring-core.jar,
> >>spring-context.jar and spring-web.jar (1.1.5) . It works with or without
> >>using org.springframework.web.jsf.DelegatingVariableResolver
> >>
> >>Now i add shale-spring.jar, it has the exception as in the enclosed
> >>psi1.log. The exception happens with or without the inclusion of
> >>org.springframework.web.jsf.DelegatingVariableResolver in faces config.
> >>
> >>BaTien
> >>DBGROUPS
> >>
> >>
> >>
> >
> >--------------010504080503040606030709
> >Content-Type: text/plain;
> > name="psi1.log"
> >Content-Transfer-Encoding: quoted-printable
> >Content-Disposition: inline;
> > filename="psi1.log"
> >
> >2005-04-05 09:18:24,622 [main] DEBUG javax.faces.application.ApplicationF=
> >actory - New ApplicationFactory instance created
> >2005-04-05 09:18:24,677 [main] ERROR org.apache.myfaces.webapp.StartupSer=
> >vletContextListener - Error initializing ServletContext
> >java.lang.IllegalArgumentException: Class org.springframework.web.context=
> >=2EWebApplicationContext is no javax.faces.el.VariableResolver
> > at org.apache.myfaces.config.FacesConfigurator.getApplicationObject(Face=
> >sConfigurator.java:535)
> > at org.apache.myfaces.config.FacesConfigurator.configureApplication(Face=
> >sConfigurator.java:481)
> > at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurat=
> >or.java:193)
> > at org.apache.myfaces.webapp.StartupServletContextListener.initFaces(Sta=
> >rtupServletContextListener.java:105)
> > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitia=
> >lized(StartupServletContextListener.java:88)
> > at org.apache.catalina.core.StandardContext.listenerStart(StandardContex=
> >t.java:3827)
> > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4=
> >343)
> > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
> >
> > at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
> > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)=
> >
> > at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478=
> >)
> > at org.apache.catalina.core.StandardService.start(StandardService.java:4=
> >80)
> > at org.apache.catalina.core.StandardServer.start(StandardServer.java:231=
> >3)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
> >java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
> >sorImpl.java:25)
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org