If I unite many web apps into one, will I save resources?
I’m comparing 2 different approaches of J2EE application architecture:
If I unite many web apps into one, will I save resources?
I’m comparing 2 different approaches of J2EE application architecture:
If I unite many web apps into one, will I save resources?
I’m comparing 2 different approaches of J2EE application architecture:
Where to store global enterprise properties?
I’m faced with a crowd of java applications, which need different global enterprise wide properties for operation, for example: hostname of the central RDBMS, hostname and location of the central self-service portal, host location of central LDAP, host location of central mail server etc.
Where to store global enterprise properties?
I’m faced with a crowd of java applications, which need different global enterprise wide properties for operation, for example: hostname of the central RDBMS, hostname and location of the central self-service portal, host location of central LDAP, host location of central mail server etc.
Preferred way for dealing with customer-defined data in enterprise application
Let’s say that we have a small enterprise web (intranet) application for managing data for car dealers. It has screens for managing customers, inventory, orders, warranties and workshops.
Preferred way for dealing with customer-defined data in enterprise application
Let’s say that we have a small enterprise web (intranet) application for managing data for car dealers. It has screens for managing customers, inventory, orders, warranties and workshops.
Preferred way for dealing with customer-defined data in enterprise application
Let’s say that we have a small enterprise web (intranet) application for managing data for car dealers. It has screens for managing customers, inventory, orders, warranties and workshops.
Preferred way for dealing with customer-defined data in enterprise application
Let’s say that we have a small enterprise web (intranet) application for managing data for car dealers. It has screens for managing customers, inventory, orders, warranties and workshops.
Multilayered enterprise application use of JAXB objects
I am asked to refactor and maintain an enterprise application. Normally I’m used to using the MVC design pattern. This time however, I’d like to separate everything into layers (multilayered architecture).
Something along the lines of (Microsoft Application Architecture Guide, 2nd Edition – October 2009):