code prole

Icon

coding for the proletariat since 1977

Eclipse Project Dependencies

Until now my J2EE project development experience has consisted of single project applications. My currently client has a tiered application architecture that splits application interfaces from business services, and business services from persistent services. This is all well and good. The resulting project structure in WebSphere Studio Application Developer (WSAD) or Eclipse consists of three parts: Common to house the framework, a Java project to hold the persistence and business layers, and a web project for the application interface itself.

WSAD allows you to define supplier projects to eliminate the need to replicate code in multiple projects. Nifty. Eclipse (being the underpinnings of WSAD) also allows project dependencies. In the Forte world we called these relationships “supplier plans.” In the J2EE world its known as the project classpath. Get your classpath setup correctly and magic happens. Miss a dependency and misery ensues.

Advertisements

Filed under: Eclipse

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: