[JeffreyGetzin]

We are migrating from an old Weblogic environment using Java 1.4 to Glassfish using 1.6 and EE 6. We originally had one humongous project and generated a humongous EAR file. Since we are migrating, we’d like to use the time to add a little more intelligence to our set up.

Right now, we’re using MyEclipse 8.5 and we’ve set up two projects: an Enterprise Application project, which produces an EAR, and a Web Application project, which produces a WAR.

The Enterprise Application only has one module in it, namely the Web Application module. This has helped to reduce the complexity of the EAR set-up, but there’s still a lot of complexity we’d like to manage.

For instance, our Web Application project is *enormous* and there’s actually a lot of functionality that could logically be broken out into another Web Application. The problem is that there’s a lot of share classes and interfaces between them.

I don’t want to give the specifics of our work here, since it’s proprietary, but let’s say we had the following setup for the division of motor-vehicles.:

Enterprise Application: DMV

WebApplication: DMVWeb

Inside DMVWeb, we have a number of web pages. Some have to do with registering your car, others have to do with emissions standards, and others have to do with your driver’s license and any accidents you may have had.

Now, logically, I could break out the registration, emissions standards, and license information into separate Web Application projects, and load all these new Web Application modules into the Enterprise Application.

But the problem is that these various new projects would share a lot of common functionality, such as classes representing cars, classes representing drivers, classes representing licenses and representation, and so on. In addition, there might be a number of convenient formatting classes, or shared CSS files, or javascript libraries that I wouldn’t want to duplicate.

So is there a way to have something like the following:

DMV
– RegistrationWeb
– EmissionsWeb
– DriverWeb
– CommonLibrary

where each of the Web Applications WARs can access the classes and functionality in the CommonLibrary jar, and all of them would be packaged into the EAR file?

Thanks,
Jeff

[Author]

Posts