Difference between revisions of "IAM WTP support"

From Eclipsepedia

Jump to: navigation, search
(EAR support)
 
(5 intermediate revisions by one user not shown)
Line 7: Line 7:
 
=== WAR overlay  ===
 
=== WAR overlay  ===
  
In the last dev build (''0.10.1.200912091148'') IAM has support for WAR overlays.
+
From version ''0.11.0'' IAM has support for WAR overlays.
See [http://code.google.com/p/q4e/wiki/Installation Installation instructions] and use the development update site ''http://q4e.googlecode.com/svn/trunk/updatesite-dev/''
+
  
 
* A) war dependency in the repository
 
* A) war dependency in the repository
Line 29: Line 28:
 
When war:exploded is needed there's a penalty as Maven needs to be executed.
 
When war:exploded is needed there's a penalty as Maven needs to be executed.
  
TODO jars and classes in dependent wars may not be had into account when using Run As a Server in some cases, needs to be tested.
+
== EAR support  ==
 +
 
 +
EAR projects are supported from version ''0.12.0'' enabling deployment from Eclipse using WTP tooling (Run in Server)
 +
 
 +
Requirements:
 +
 
 +
* EAR dependencies must be opened in the workspace in order for the EAR to be started in the server with WTP
 +
* WAR names need to match PROJECT_NAME.war in WTP versions prior to 3.2.1 (org.eclipse.jst.j2ee 1.1.301.v201001272230 works properly)
 +
** Bug http://bugs.eclipse.org/bugs/show_bug.cgi?id=280416
 +
** You can add the <finalName>{project.artifactId}</finalName> tag to your WAR projects to work around the issue
 +
 
  
 
[[Category:IAM]]
 
[[Category:IAM]]

Latest revision as of 10:35, 18 August 2010

< To: IAM

[edit] WAR support

WAR projects are supported as WTP dynamic web modules. Allows IAM users to run Maven WAR projects from Eclipse using WTP support, such as running in a web container using Run As -> Server

[edit] WAR overlay

From version 0.11.0 IAM has support for WAR overlays.

  • A) war dependency in the repository
    • IAM will run war:exploded and add the target dir to the war source components, after the current project web source folders
    • if the war in the repository gets modified changes will not affect the project
    • if there are pom changes in the current project or dependent projects the exploded war folder will be deleted and war:exploded will be run again
      • this could be optimized to check if the changes really affect the WAR in the WarBuilderDelegate
  • B) war dependency in the workspace
    • IAM will link the other project webapp source folder from target/iam and add it to the current project web source folders
    • if there are pom changes in the current project or dependent projects the links will be recalculated
    • if the dependency also have war dependencies then war:exploded is run for it and the link target is the exploded war folder instead of the source war folder

If there's a mix of A and B the order is

  • Workspace dependencies
  • Repository dependencies

This would have an impact only if there's the same file in both the current project and the dependencies.

The cases where folders are linked from one project to another have no performance penalty. When war:exploded is needed there's a penalty as Maven needs to be executed.

[edit] EAR support

EAR projects are supported from version 0.12.0 enabling deployment from Eclipse using WTP tooling (Run in Server)

Requirements:

  • EAR dependencies must be opened in the workspace in order for the EAR to be started in the server with WTP
  • WAR names need to match PROJECT_NAME.war in WTP versions prior to 3.2.1 (org.eclipse.jst.j2ee 1.1.301.v201001272230 works properly)