Hello all -

Perhaps this has already been addressed - if so, just please point me in
the right direction:

We're starting a new J2EE project, which will have a Web module and an EJB
module under an EAR deployment umbrella, so this is the perfect opportunity
to use Maven to set the project up correctly with the proper structure.   I
can setup the maven structure ok, but I'm having trouble getting BEA
Workshop 10 (based on Eclipse) to recognize this project as a web project
when I import it...  Here is the steps I followed:  I have run the
following mvn statements to create my Web module, which is the first in a
series:

1)  -- Create WAR PROJECT MODULE
mvn archetype:create \
  -DarchetypeGroupId=org.apache.maven.archetypes \
  -DarchetypeArtifactId=maven-archetype-webapp \
  -DarchetypeVersion=1.0 \
  -DgroupId=com.ibm.client.diamond.web \
  -DartifactId=diamond-web \
  -Dversion=2.0-SNAPSHOT

The mvn run is successful, producing the familiar structure, with the path:
src\main\webapp housing the WEB-INF sub-directory, and sample jsp resource.

2)  I proceed to prepare the new web project to be used with Eclipse, so I
run:  mvn eclipse:eclipse - which produces the .class and .project files as
a result.

3)  My next step is to import the newly created project into Webshop using
regular Import...   use Existing Project - it imports properly, but it has
an appearance of a Java project, not a DynamicWeb project at that point...
I think that's my problem.

4)  Finally, I creat an EnterpriseApplicationProject (EAR proj) to house my
diamond-web Web applicaiton.   I follow the wizzard and can add the web
project to the Ear project OK, but somehow the web module does NOT get
added to the application.xml config file in the EAR project - the BEA
Workshop seems to completely ignore the fact that this is a Web project
we're adding... thus it does not add it to the application.xml file and I
can't seem to convince it to treat my maven-created project as a Web
project.   I even tried this same approach with Eclipse 3.3 (Europa), but
had same exact experience.   Of course creating a dynamic web project
directl inside the workshop produces desired results, but the dir structure
that results is of course not in line with the maven structure... and so it
goes... :(

So, please help -  how can I get Maven and BEAWebShop to play nice
together?

Thanks,
James

Reply via email to