RE: [Springframework-developer] Giving up

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

Hi Lars,

I'm glad that you finally succeeded in making it work :-)

> I've change the MySQL stuff to Postgres - no problem. At this point I =
do
NOT provide the database table for the example object.  The application
starts up fine and does not tell me anything about a mapping problem.
Is this the default behaviour ?

Yes, this is *Hibernate's* default behavior. It prepares the respective =
statements on startup but does not valdidate them. You will detect =
mapping syntax errors but not inconsistencies with the data model.

> Another question about WebWork (2). I know the difference about Spring =
and
WebWork and that it's 'no problem' to combine the two frameworks.=20
But does it make any sense ? Is WebWork MVC superior ?
IMO it does make more sense to stay with Spring alone so you don't have
to deal with two technologies.

You're right, of course - I don't *recommend* a WebWork/Spring combo. =
Most people that do such combos with Struts or WebWork have investments =
in the latter, possibly migrating existing applications.

WebWork uses a specific command-style programming model for actions =
while Spring recommends singleton-style reusable controllers. Spring =
supports both models, though: You can achieve the command-style model =
through declaring your Spring controllers as prototypes (<bean id=3D".." =
singleton=3D"false").

Struts obviously has a lot of tag libraries and code generation tools, =
so that may be another reason to choose it besides existing investments. =
I'm not a great fan of Struts' programming model (Action, ActionForm) =
though, so I recommend Spring's web MVC if there aren't any other =
reasons involved.

Juergen