RE: RE : [Springframework-developer] Theme issue

[<jue...@we...>]

Spring seems to have so many features that hardly anyone knows of all of =
them anymore ;-)

Regarding PagedList: I completely agree with your focus. It should show =
some advanced web stuff, while PetClinic should be a simple but full =
database application. If you manage to polish this till the end of the =
week, we'll already include it in the upcoming 0.9.1 release.

Juergen


-----Original Message-----
From: JP Pawlak [mailto:jp....@ti...]
Sent: Wednesday, July 02, 2003 8:30 PM
To: j=FCrgen h=F6ller [werk3AT]
Cc: 'springframework-developer'
Subject: RE : [Springframework-developer] Theme issue


Thanks for explanation. Very nice, generally I have now only to put the
specific AttributeCSV for the views as the URL is the template one. It
works fine and I missed this ;-).

I will also integrate this beside others things in PagedList to
transform it as a web advanced demo, letting petclinic more focused on
database side.=20

-----Message d'origine-----
De=A0: spr...@li...
[mailto:spr...@li...] De la
part de j=FCrgen h=F6ller [werk3AT]
Envoy=E9=A0: mercredi 2 juillet 2003 17:45
=C0=A0: jp....@ti...
Cc=A0: springframework-developer
Objet=A0: RE: [Springframework-developer] Theme issue

Hi JP,

Bean parents already work, e.g.:

  example.class=3Dcom.interface21.web.servlet.view.JstlView
  example.requestContextAttribute=3Drc

  example1.parent=3Dexample
  example1.url=3D/example1.jsp

  example2.parent=3Dexample
  example2.url=3D/example2.jsp

There's even a defaultParentView property in ResourceBundleViewResolver,
so that you can omit the ".parent=3D" lines above, e.g.:

  <bean id=3D"viewResolver"
class=3D"com.interface21.web.servlet.view.ResourceBundleViewResolver">
    <property name=3D"basename"><value>views</value></property>
    <property =
name=3D"defaultParentView"><value>example</value></property>
  </bean>

Both solutions should make RequestContext setup quite convenient.

Regards,
Juergen