Home/ Questions/Q 3274888
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T19:05:11+00:00

I want to build an MVC app using Spring (first timer here). As such

  • 0

I want to build an MVC app using Spring (first timer here).

As such I want to embed Jetty as the servlet engine. Jetty however doesn’t stricly follow the java beans pattern, so I can’t launch some classes from Spring (they use overloaded setters or non setter init methods like addXYZ).

What is the accepted/recommended practice for structuring this project? Obviously all my code fits nicely in the MVC model, but for Jetty:

  • Do I encapsulate all of Jetty (or any
    other non-bean friendly component) in
    my own Spring-friendly bean?
  • Do I try to instantiate as much of it as
    possible in spring and just extend
    classes that aren’t bean con-formant
    to make them act like proper beans?
  • Is there
    another option?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally speaking, I’m for the 2nd point – i.e. try to use spring utilities like factory-method, init-method, <constructor-arg> and things like that to overcome the fact that something is not entirely spring-friendly. It is rarely the case that it’s impossible to configure beans with spring. And for the cases when it is impossible, create wrappers

    You can also instantiate the 3rd party beans programatically:

    • 0