Everything Java Apache Geospatial Open Source. Hello Shinning Stars!!! Vincent Massol, Raphael Luta, Santiago Gala, Carsten Z.
Sunday, October 23, 2005
Implicit versus explicit application development. Creating a application that relies on implicit configuration or rules is a bad idea. I came across a struts configuration in Jetspeed that made me think of this subject. A $M$P pattern indicated that pages exist with the /module/path. Although this case is not an implicit declaration programming with out explicitly declaring classes, configuration, or properties will only create confusion and hard to debug applications.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2005
(84)
-
▼
October
(8)
- I am going to write a MapServer portlet. The mapse...
- MapServer 4.6 requests can probably be broken down...
- Implicit versus explicit application development. ...
- Another short tutorial on the Jetspeed portlet.Cre...
- Please read QuickstartForTheImpatient before befor...
- I see that in Jetspeed's demo portlets the web.xml...
- Seems there are some patches to do for Jetspeed.de...
- I am writing a JetSpeed 2 quickstart development g...
-
▼
October
(8)
No comments:
Post a Comment