Thanks Joao, that is very interesting. It is the inverse of what I was
trying to do. I hadn't thought to do it like that. I'm going to give
it a whirl.
Thanks for the input!
-Mike
Joao Nelas wrote:
Hi Mike!
I have something like that working.
I have a "base" project that has all hibernat
Hi Mike!
I have something like that working.
I have a "base" project that has all hibernate, user management, etc. And
other projects that work like plugins. I can drop the jars from one of those
projects in the war, and automatically get the functionality.
There are 2 important techniques that ma
Just one war file. They are stand alone projects in the sense that
there are two maven projectsI started down this path after reading:
http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html
I just realized that there is no corresponding feature for JARs. So my
Project B c
I am not quite clear - if that's the case, then project A and project
B aren't standalone projects.
In other words, how many WAR files will you be deploying to Tomcat (or
your container)?
Cheers,
Alex
On 17 Dec 2007, at 19:18, Mike Wille wrote:
I just realized that I have left something ou
I just realized that I have left something out. My end goal was to
generate one combined web app from project A and B using the jar/war
overlay feature. Does that change anything?
Thanks!
-Mike
Alexander Coles wrote:
I think so. I am offering this as a purely suggestion - the system I
am c
I think so. I am offering this as a purely suggestion - the system I
am currently working on -- with two WARs/web apps - is constrained by
exactly what you mentioned: Tomcat is the deployment environment for
the enterprise, so I don't have the full J2EE stack available to me.
Instead I've j
Yes, project A is also a stand alone project. It has both Core and Web
modules.
Thanks for the links. I will take a look. At first glance, it seems
that this creates an EAR file and would then require something more then
Jetty or Tomcat.
Thanks!
-Mike
Alexander Coles wrote:
Is Project A
Is Project A also a stand alone project, or does it just provide
infrastructure support?
If I am understanding your requirement rightly, you could create a
shared parent application context:
http://blog.interface21.com/main/2007/06/11/using-a-shared-parent-application-context-in-a-multi-war-
Hi All,
I'm looking for advice on setting up multiple projects. I've been using
the Spring MVC Modular archetype with appfuse and it works great.
Now I was thinking about trying it out on a larger scale. I'm setting
up a second project (multi module) that depends on the first.
Everything
