You should be able to add as many additional configuration files as you want.
With respect to referencing the bean from the JSP, you should refer to the Spring documentation (which will most likely be more accurate than any information I would give you) On Mon, Jun 9, 2014 at 8:55 AM, Zac Harvey <[email protected]> wrote: > I want a custom org.my.FizzBuzz Java class that I need to configure in > CAS’ applicationContext.xml and would like to have access to it in the > casLogoutView.jsp page. So in the app context, the wiring might look > something like: > > > > <bean id=”fizzBuzz” class=”org.me.FizzBuzz”> > > <property name=”foo” ref=”foo” > > </bean> > > > > etc. And then in the casLogoutView.jsp, something like: > > > > <% > > FizzBuzz fizzBuz = > (FizzBuzz)applicationContext.getBean(“fizzBuzz”); > > > > // Do stuff with fizzBuzz. > > %> > > > > My questions: > > > > (1) In my spring-configuration/ directory, there is no > applicationContext.xml. If I add one, and only define this one FizzBuzz > bean (and its dependencies), will that “blow out” all of the other beans > that CAS is defining/injecting underneath the hood? If so, how can I > define my FizzBuzz (in any XML) so that it’s available to the JSP? > > > > (2) How can I obtain a reference to applicationContext and/or my FizzBuzz > bean inside the JSP? > > > > Thanks in advance! > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
