Apache Maven is a software tool for building and managing Java-based projects. WebLogic Server provides support for Maven through the provisioning of plug-ins that enable you to perform various operations on WebLogic Server from within a Maven environment.
The weblogic-maven-plugin
provides enhanced functionality to install, start and stop servers, create domains, execute WLST scripts, and compile and deploy applications. With the weblogic-maven-plugin
, you can install WebLogic Server from within your Maven environment to fulfill the local WebLogic Server requirement.
The following sections describe using weblogic-maven-plugin
:
See Developing Applications Using Continuous Integration for additional Maven documentation. In particular, see the section "Building Java EE Projects for WebLogic Server with Maven."
Before you can use the weblogic-maven-plugin
plug-in, you must first have a functional Maven installation and a Maven repository. WebLogic Server supports Maven 3.0.4 and later.
A distribution of Maven 3.0.4 is included with WebLogic Server in the following location: ORACLE_HOME
\oracle_common\modules\org.apache.maven_3.0.4
. This is a copy of the standard Maven 3.0.4 release, without any modifications.
Run the ORACLE_HOME
\wlserver\server\bin\setWLSEnv
script to configure Maven.
Alternatively, you can download and install your own copy of Maven from the Maven Web site: http://maven.apache.org
. Make sure you set any required variables as detailed in that documentation, such as M2_HOME
and JAVA_HOME
.
The weblogic-maven-plugin
sets the Java protocol handler to weblogic.net
. To use the default JDK protocol handlers, specify the system property -DUseSunHttpHandler=true
in the JVM that executes Maven. To do this, override the environment variable MAVEN_OPTS
inside the mvn.bat
or mvn.sh
files to set the appropriate value. For example: set MAVEN_OPTS="-DUseSunHttpHandler=true"
.
For detailed information on installing and using Maven to build applications and projects, see the Maven Users Centre at http://maven.apache.org/users/index.html
.
The weblogic-maven-plugin
plug-in is provided as a pre-built JAR file and accompanying pom file.
Follow these steps for installing and configuring weblogic-maven-plugin
:
Install the Oracle Maven sync plug-in and run the push goal:
Change directory to ORACLE_HOME
\oracle_common\plugins\maven\com\oracle\maven\oracle-maven-sync\12.1.2
.
mvn install:install-file -DpomFile=oracle-maven-sync.12.1.2.pom -Dfile=oracle-maven-sync.12.1.2.jar
.
mvn com.oracle.maven:oracle-maven-sync:push -Doracle-maven-sync.oracleHome=c:\oracle\middleware\oracle_home\
.
You can validate whether you have successfully installed the plug-in using the Maven help:describe
goal. See the Apache help plug-in describe goal documentation for additional information.
mvn help:describe -DgroupId=com.oracle.weblogic -DartifactId=weblogic-maven-plugin -Dversion=12.1.2-0-0
There are two ways to invoke the goals in the WebLogic Maven plug-in:
From a Maven project POM.
From the command line.
The appc, ws-jwsc, ws-wsdlc, and ws-clientgen goals require a POM.
Other goals will work either way. For example, install, wlst, start-server, or stop-server work either from a POM or the command line.
The preferred and recommended way is to use a Maven POM file.
To invoke a WebLogic Maven plug-in goal from a POM file, do the following:
Add a build section to your POM if you do not already have one.
Add a plug-in section to the build section for the WebLogic Maven plug-in.
Add an execution section to the WebLogic Maven plug-in's plugin
section for each goal that you want to execute. This section must provide the necessary parameters for the goal, and map the goal to a phase in the Maven Lifecycle.
Example 3-1 shows an example of the necessary additions, including a few goals. The detailed descriptions of each goal later in this section present the details for parameters and examples for each goal.
If you map multiple goals to the same lifecycle phase, they are typically executed in the order you list them in the POM.
Example 3-1 Modifying the POM File
<build>
<plugins>
<plugin>
<!-- This is the configuration for the
weblogic-maven-plugin
-->
<groupId>com.oracle.weblogic</groupId>
<artifactId>weblogic-maven-plugin</artifactId>
<version>12.1.2-0-0</version>
<configuration>
<middlewareHome>/fmwhome/wls12120</middlewareHome>
</configuration>
<executions>
<!-- Execute the appc goal during the package phase -->
<execution>
<id>wls-appc</id>
<phase>package</phase>
<goals>
<goal>appc</goal>
</goals>
<configuration>
<source>${project.build.directory}/${project.name}.${project.packaging}</source>
</configuration>
</execution>
<!-- Deploy the application to the WebLogic Server in the
pre-integration-test phase
-->
<execution>
<id>wls-deploy</id>
<phase>pre-integration-test</phase>
<goals>
<goal>deploy</goal>
</goals>
<configuration>
<!--The admin URL where the app is deployed.
Here use the plugin's default value t3://localhost:7001-->
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<!--The location of the file or directory to be deployed-->
<source>${project.build.directory}/${project.build.finalName}.${project.packaging}</source>
<!--The target servers where the application is deployed.
Here use the plugin's default value AdminServer-->
<targets>AdminServer</targets>
<verbose>true</verbose>
<name>${project.build.finalName}</name>
</configuration>
</execution>
<!-- Stop the application in the pre-integration-test phase -->
<execution>
<id>wls-stop-app</id>
<phase>pre-integration-test</phase>
<goals>
<goal>stop-app</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<name>${project.build.finalName}</name>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Table 3-1 lists the phases in the default Maven lifecycle.
Table 3-1 Maven Lifecycle Phases
Phase | Description |
---|---|
validate |
Validates the project is correct and all necessary information is available. |
compile |
Compiles the source code of the project. |
test |
Tests the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed. |
package |
Takes the compiled code and package it in its distributable format, such as a JAR. |
integration-test |
Processes and deploys the package if necessary into an environment where integration tests can be run. |
verify |
Runs any checks to verify the package is valid and meets quality criteria. |
install |
Installs the package into the local repository, for use as a dependency in other projects locally. |
deploy |
In an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects. |
Table 3-2 shows the most common mappings of goals to phases
Table 3-2 Common Mapping of Goals to Phases
Phase | Goal |
---|---|
validate |
ws-clientgen, ws-wsdlc |
compile |
ws-jwsc |
test |
NA |
package |
appc |
pre-integration-testFoot 1 |
install, create-domain, start-server, distribute-app, deploy, redeploy, update-app, start-app, stop-app, wlst, and list-apps |
post-integration-testFoot 2 |
undeploy, stop-server, uninstall |
verify |
NA |
install |
NA |
deploy |
NA |
Footnote 1 The integration-test phase has pre sub-phases that are executed before the actual execution of any integration tests, respectively.
Footnote 2 The integration-test phase has post sub-phases that are executed after the actual execution of any integration tests, respectively.
Example 3-2 illustrates a basic Java EE 6 Web application pom.xml file that demonstrates the use of the weblogic-maven-plugin appc goal.
Example 3-2 Basic Configuration pom.xml File
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>demo.sab</groupId>
<artifactId>maven-demo</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>war</packaging>
<name>maven-demo</name>
<properties>
<endorsed.dir>${project.build.directory}/endorsed</endorsed.dir>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>com.oracle.weblogic</groupId>
<artifactId>weblogic-server-pom</artifactId>
<version>12.1.2-0-0</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
</dependencies>
<build>
<plugins>
...
...
<!-- WebLogic Server 12c Maven Plugin -->
<plugin>
<groupId>com.oracle.weblogic</groupId>
<artifactId>weblogic-maven-plugin</artifactId>
<version>12.1.2-0-0</version>
</plugin>
<configuration>
</configuration>
<executions>
<execution>
<id>wls-appc</id>
<phase>package</phase>
<goals>
<goal>appc</goal>
</goals>
<configuration>
source>${project.build.directory}/${project.name}.
${project.packaging}</source>
</configuration>
</execution>
</executions>
</plugins>
</build>
</project>
Table 3-3 lists all the weblogic-maven-plugin
goals. Each goal is described in detail in the sections that follow.
Goal Name | Description |
---|---|
Generates and compiles the classes needed to deploy EJBs and JSPs to WebLogic Server. Also validates the deployment descriptors for compliance with the current specifications at both the individual module level and the application level. |
|
Creates a domain for WebLogic Server using a domain template. This goal supports specifying the domain directory (the last directory determines the domain name) and the administrative username and password. For more complex domain creation, use the |
|
Deploys WebLogic Server applications and modules. Supports all deployment formats; for example, WAR, JAR, and such. |
|
Prepares deployment files for deployment by copying deployment files to target servers and validating them. |
|
Deprecated. Use the standard Maven help plug-in instead. |
|
Installs WebLogic Server. |
|
Lists the deployment names for applications and standalone modules deployed, distributed, or installed in the domain. |
|
Redeploys a running application or part of a running application. |
|
Starts an application deployed on WebLogic Server. |
|
Starts WebLogic Server. This goal starts WLS by running a local start script. For starting remote servers using the node manager, use the wlst goal instead. |
|
Stops an application. |
|
Stops WebLogic Server. This goal stops WLS by running a local start script. For stopping remote servers using the node manager, use the wlst goal instead. |
|
Undeploys the application from WebLogic Server. Stops the deployment unit and removes staged files from target servers. |
|
Uninstalls WebLogic Server. Currently works only for servers installed using the Zip installer. |
|
Updates an application's deployment plan by redistributing the plan files and reconfiguring the application based on the new plan contents. |
|
WLST wrapper for Maven. |
|
Generates client Web service artifacts from a WSDL. |
|
Generates a set of artifacts and a partial Java implementation of the Web service from a WSDL. |
|
Builds a JAX-WS Web service. |
com.oracle.weblogic:weblogic-maven-plugin:appc
Generates and compiles the classes need to deploy EJBs and JSPs to WebLogic Server. Also validates the deployment descriptors for compliance with the current specifications at both the individual module level and the application level. Does not require a local server installation.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the path to an alternative Java EE application deployment descriptor. |
|
|
false |
Specifies the path to an alternative WebLogic Server application deployment descriptor. |
|
|
false |
When true, does not include deployment descriptors in client JARs generated for EJBs. |
|
|
false |
This parameter is deprecated in this release and ignored. Use the standard Maven dependency model instead to manipulate the effective CLASSPATH during a build. |
|
|
false |
Specifies a directory where generated client JARs will be written. |
|
|
false |
This parameter is deprecated in this release. |
|
|
false |
Specifies the Java compiler for compiling class files from the generated Java source code. The Java compiler program should be in your |
|
|
false |
The class that invokes the compiler. |
|
|
false |
When true, continues compilation even when there are errors in the JSP files. |
|
|
false |
When true, compiles debugging information into class files. |
|
|
false |
When true, warns about the use of deprecated methods in the generated Java source file when compiling the source file into a class file. |
|
|
false |
Specifies the directory where compiled class files are written. Use this parameter to place compiled classes in a directory that is already in your |
|
|
false |
This parameter is deprecated in this release. |
|
|
false |
When true, forces the generation of EJB and JSP classes. Otherwise, the classes will not be regenerated if it is determined to be unnecessary. |
|
|
false |
When true, generates IDL for EJB remote interfaces. |
|
|
false |
Specifies the directory where IDL files will be written. |
|
|
false |
When true, generates factory methods for valuetypes. |
|
|
false |
Specifies the method signatures used to trigger IDL code generation. |
|
|
false |
When true, does not generate abstract interfaces and methods or attributes that contain them. |
|
|
false |
Does not generate valuetypes or the methods and attributes that contain them. |
|
|
false |
When true, generates IDL somewhat compatible with Orbix 2000 2.0 C++. |
|
|
false |
When true, overwrites existing IDL files. |
|
|
false |
When true, displays additional status information for IDL generation. |
|
|
false |
When true, generates IDL somewhat compatible witih Visibroker 4.5 C++. |
|
|
false |
When true, ignores the plan file if it does not exist. |
|
|
false |
When true, generates CORBA stubs for EJBs. |
|
|
false |
Specifies the directory where IIOP stub files will be written. |
|
|
false |
When true, preserves the generated |
|
|
false |
A comma-separated list of libraries. |
|
|
false |
Registers all the files in the specified directory as libraries. |
|
|
false |
When true, adds JSP line numbers to generated class files to aid in debugging. |
|
|
false |
This parameter is deprecated in this release. Use the standard Maven mechanism to specify the Manifest during packaging. |
|
|
false |
Specifies the maximum number of generated Java files to be compiled at one time. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, does not exit from the execution of the |
|
|
false |
This parameter is deprecated in this release. |
|
|
false |
When true, suppresses compiler warnings. |
|
|
false |
This parameter is deprecated in this release. |
|
|
false |
When true, compiles with optimization on. |
|
|
false |
Specifies an alternate output archive or directory. When not set, the output is placed in the source archive or directory. |
|
|
false |
Specifies the path to an optional deployment plan. |
|
|
false |
When true, turns off output except for errors. |
|
|
false |
Passes a list of options to the compiler. |
|
|
false |
This parameter is deprecated in this release and ignored. Use the standard Maven dependency model instead to manipulate the effective CLASSPATH. |
|
|
false |
Specifies the path to the source files. |
|
|
false |
Limits the compatibility of the Java files to a JDK no higher than specified. For example "1.5". |
|
|
false |
This parameter is deprecated in this release and ignored. Use the standard Maven dependency model instead to add the target classes to the effective CLASSPATH during a build. |
|
|
false |
Specifies the minimum level of the JVM required to run the compiled class files. For example, "1.5". |
|
boolean |
false |
When true, displays additional status information during the compilation process. |
|
|
false |
When true, enables verbose output from the Java compiler. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, writes out the descriptors with inferred information including annotations. |
The appc
goal executes the WebLogic Server application compiler utility to prepare an application for deployment.
<execution> <id>wls-appc</id> <phase>package</phase> <goals> <goal>appc</goal> </goals> <configuration> <source>${project.build.directory}/${project.name}.${project.packaging}</source> </configuration> </execution>
Example 3-3 shows typical appc
goal output.
$ mvn com.oracle.weblogic:weblogic-maven-plugin:appc -Dsource=target/basicWebapp.war -DforceGeneration=true [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building basicWebapp 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:appc (default-cli) @ main-test --- [INFO] Running weblogic.appc on /home/oracle/src/tests/main-test/target/basicWebapp.war [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7.901s [INFO] Finished at: Wed May 15 10:52:46 EST 2013 [INFO] Final Memory: 26M/692M [INFO]
com.oracle.weblogic:weblogic-maven-plugin:create-domain
Creates a domain for WebLogic Server using a domain template. This goal supports specifying the domain directory (the last directory determines the domain name) and the administrative username and password. For more complex domain creation, use the wlst
goal.
Table 3-5 create-domain Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
true |
Specifies the directory to use for creating the domain. This goal takes the name of the last subdirectory specified as the domain name and sets the new domain's name to that value. For example, domainHome=/weblogic/domains/MyNewDomain causes the domain name to be set to 'MyNewDomain'. |
|
|
false |
Specifies the domain template file to use to create the domain. The default domain template included with WebLogic Server is used when this parameter is not specified. |
|
|
false |
When |
|
|
true |
The path to the Oracle Middleware install directory. |
|
|
true |
Specifies the administrative password. |
|
|
false |
This parameter is deprecated and ignored in this release. |
|
|
true |
Specifies the administrative user name. |
|
|
false |
This parameter is deprecated and ignored in this release. |
|
|
false |
Specifies whether to run the wlst.sh script from |
Use the create-domain
goal to create a WebLogic Server domain from a specified WebLogic Server installation. You specify the location of the domain using the domainHome
configuration parameter.
When creating a domain, a user name and password are required. You can specify these using the user
and password
configuration parameters in your POM file or by specifying them on the command line.
The domain name is taken from the last subdirectory specified in domainHome
.
<execution>
<id>wls-create-domain</id>
<phase>pre-integration-test</phase>
<goals>
<goal>create-domain</goal>
</goals>
<configuration>
<middlewareHome>c:/dev/wls12120</middlewareHome>
<domainHome>${project.build.directory}/base_domain</domainHome>
<user>weblogic</user>
<password>password</password>
</configuration>
</execution>
Example 3-4 shows typical command output from the execution of the create-domain
goal.
mvn com.oracle.weblogic:weblogic-maven-plugin:create-domain -DdomainHome=c:\oracle\middleware\oracle_home\user_projects\domains\maven-domain -DmiddlewareHome=c:\oracle\middleware\oracle_home -Duser=weblogic -Dpassword=password [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2-0-0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:create-domain (default-cli) @ weblogic-maven-plugin --- [INFO] [create-domain]Domain creation script: readTemplate(r'C:/oracle/middleware/oracle_home/wlserver/common/templates/wls/wls.jar') set('Name', 'maven-domain') cd('/Security/maven-domain/User/weblogic') set('Name', 'weblogoc') set('Password', '***') writeDomain(r'c:/oracle/middleware/oracle_home/user_ projects/domains/maven-domain') [INFO] [wlst]script temp file = C:/Users/user/AppData/Local/Temp/test6066166061714573929.py [INFO] [wlst]Executing: [cmd:[C://windows\\system32\\cmd.exe, /c, C:\oracle\middleware\oracle_home\wlserver\common\bin\wlst.cmd C:\Users\user\AppData\Local\Temp\test6066166061714573929.py ]] [INFO] Process being executed, waiting for completion. [INFO] [exec] [INFO] [exec] Initializing WebLogic Scripting Tool (WLST) ... [INFO] [exec] [INFO] [exec] Welcome to WebLogic Server Administration Scripting Shell [INFO] [exec] [INFO] [exec] Type help() for help on available commands [INFO] [exec] [INFO] [wlst][cmd:[C:\\windows\\system32\\cmd.exe, /c, C:\oracle\middleware\oracle_home\wlserver\common\bin\wlst.cmd C:\Users\user\AppData\Local\Temp\test6066166061714573929.py ]] exit code=0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18.276s [INFO] Finished at: Wed May 01 13:13:25 EDT 2013 [INFO] Final Memory: 9M/23M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:deploy
Deploys WebLogic Server applications and modules to a running server. Supports all deployment formats; for example, WAR, JAR, RAR, and such. Does not require a local server installation.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
When true, enables validation of security data. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, indicates that the user wants to copy the application in the server staging area externally or using a third-party tool. When specified, WebLogic Server looks for the application under |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, does not copy the deployment files to target servers, but leaves them in a fixed location, specified by the |
|
|
false |
When true, ignores all version related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the path to the deployment plan. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds before WebLogic Server undeploys the currently-running version of this application or module so that clients can start using a new version. When not specified, a graceful retirement policy is assumed. |
|
|
false |
Specifies the security model to be used for this deployment, overriding the default security model for the security realm. Possible values are: |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Archive file or exploded archive directory to deploy. You can omit the option and supply only the file or directory to deploy. |
|
|
false |
When true, indicates that the application needs to be copied into the target server staging area before deployment. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. The default is AdminServer. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
When true, copies the source files to the Administration Server's upload directory prior to deployment. Use this setting when running the plug-in remotely (using the |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use this goal to deploy an application.
<execution>
<id>wls-deploy</id>
<phase>pre-integration-test</phase>
<goals>
<goal>deploy</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<source>${project.build.directory}/${project.build.finalName}
.${project.packaging}</source>
<targets>AdminServer</targets>
<verbose>true</verbose>
<name>${project.build.finalName}</name>
</configuration>
</execution>
Example 3-5 shows typical deploy
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:deploy -Dsource=C:\webservices\MySimpleEjb.jar -Dpassword=password -Duser=weblogic [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2-0-0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:deploy (default-cli) @ weblogic-mave n-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - deploy -user weblogic -source C:\webservices\MySimpleEjb.jar -targets AdminServe r <May 1, 2013 1:41:09 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiati ng deploy operation for application, MySimpleEjb [archive: C:\webservices\MySimp leEjb.jar], to AdminServer .> Task 0 initiated: [Deployer:149026]deploy application MySimpleEjb on AdminServer . Task 0 completed: [Deployer:149026]deploy application MySimpleEjb on AdminServer . Target state: deploy completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.042s [INFO] Finished at: Wed May 01 13:41:11 EDT 2013 [INFO] Final Memory: 10M/25M
com.oracle.weblogic:weblogic-maven-plugin:distribute-app
Prepares deployment files for deployment by copying deployment files to target servers and validating them. Does not require a local server installation.
Table 3-7 distribute-app Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
When true, enables validation of security data. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, indicates that the user wants to copy the application in the server staging area externally or using a third-party tool. When specified, WebLogic Server looks for the application under |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, does not copy the deployment files to target servers, but leaves them in a fixed location, specified by the |
|
|
false |
When true, ignores all version related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the path to the deployment plan. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds before WebLogic Server undeploys the currently-running version of this application or module so that clients can start using a new version. When not specified, a graceful retirement policy is assumed. |
|
|
false |
Specifies the security model to be used for this deployment, overriding the default security model for the security realm. Possible values are: |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the archive file or exploded archive directory to deploy. This can be one of the following: a file, directory, or exploded archive on the local system, or a colon (:) separated list of Maven coordinates of the form ( |
|
|
false |
When true, indicates that the application needs to be copied into the target server staging area before deployment. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. When not specified, all configured targets are used. For a new application, the default target is the Administration Server. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
When true, copies the source files to the Administration Server's upload directory prior to deployment. Use this setting when running the plug-in remotely (using the |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use this goal to prepare deployment files for deployment.
<execution>
<id>wls-distribute-app</id>
<phase>pre-integration-test</phase>
<goals>
<goal>distribute-app</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<source>${project.build.directory}/${project.build.finalName}
.${project.packaging}</source>
<targets>cluster1</targets>
<verbose>true</verbose>
<name>${project.build.finalName}</name>
</configuration>
</execution>
Example 3-6 shows typical distribute-app
goal output.
$ mvn com.oracle.weblogic:weblogic-maven-plugin:distribute-app -Dadminurl=t3://localhost:7001 -Dstage=true -DmiddlewareHome=/maven/wls12120 -Dname=cluster-test -Duser=weblogic -Dpassword=welcome1 -Dtargets=cluster1 -Dsource=target/cluster-test-1.0-SNAPSHOT.war [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building cluster-test 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:distribute-app (default-cli) @ cluster-test --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 -distribute -user weblogic -name cluster-test -source /home/oracle/src/tests/uber-test/cluster-test/ target/cluster-test-1.0-SNAPSHOT.war -targets cluster1 -stage <May 15, 2013 2:09:58 PM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating distribute operation for application, cluster-test [archive: /home/oracle/src/tests/uber-test/cluster-test/ target/cluster-test-1.0-SNAPSHOT.war], to cluster1 .> Task 0 initiated: [Deployer:149026]distribute application cluster-test on cluster1. Task 0 completed: [Deployer:149026]distribute application cluster-test on cluster1. Target state: distribute completed on Cluster cluster1 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.953s [INFO] Finished at: Wed May 15 14:10:00 EST 2013 [INFO] Final Memory: 15M/429M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:help
Deprecated. Use the standard Maven help plug-in instead.
Lists all the goals supported by the weblogic-maven-plugin
.
com.oracle.weblogic:weblogic-maven-plugin:install
Installs WebLogic Server.
Name | Type | Required | Description |
---|---|---|---|
|
|
true |
Specifies the address of the installation. The address can be one of the following: a colon (:) separated list of Maven coordinates of the form: |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Installs the product with an executable installer. The following macros are supported: |
|
|
true |
The location to install the server. For the zip installer, the equivalent of middlewareHome is |
Use this goal to install WebLogic Server into a local directory so it can be used to execute other goals, as well as to create a WebLogic Server domain for deploying and testing the application represented as the Maven project.
Note:
The install goal creates a single managed server called myserver
, and does not create a domain. Most other goals, including create-domain, use a default server name of AdminServer
. You therefore need to override the default AdminServer
server name in your POM.
This goal installs WebLogic Server using a specified installation distribution. You specify the location of the distribution using the artifactLocation
configuration parameter, which can be the location of the distribution as a file on the file system; an HTTP URL which can be accessed; or a Maven coordinate of the distribution installed in a Maven repository. Specify the artifactLocation
configuration element in the weblogic-maven-plugin
section of the pom.xml
file, or by using the –DartifactLocation
property when invoking Maven.
For example, if you want to install a WebLogic Server ZIP file distribution, you can specify the location of the ZIP distribution as one of the following:
A local file reference—For a local file reference, specify the path on the local file system.
A URL reference.
A Maven artifact—In this case, the distribution is retrieved from the local Maven repository itself. This means that it needs to have been previously installed into the local repository or pulled over from a remote repository.
artifactLocation
can be a URL, a file path, or a Maven coordinate of the form groupId:artifactId:packaging:version
or groupId:artifactId:packaging:classifier:version
. For example, com.oracle.weblogic:weblogic-server-installer:zip:12.1.2-0-0
.
<execution> <id>wls-install-server</id> <phase>pre-integration-test</phase> <goals> <goal>install</goal> </goals> <configuration> <installDir>c:/dev</installDir> <artifactLocation>c:/temp/wls1212_dev.zip</artifactLocation> </configuration> </execution>
Example 3-7 shows typical install
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:install -DartifactLocation=wls1212.zip -DinstallDir=c:\oracle\middleware [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Stub Project (No POM) 1 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:install (default-cli) @ standalone-p om --- [INFO] Installing wls1212.zip into the location: c:\oracle\middleware [INFO] Installing the product, this may take some time. [INFO] [install]installHome = c:\oracle\middleware [INFO] [install]middlewareHome = c:\oracle\middleware\wls12120 [INFO] Executing: [cmd:[C:\\windows\\system32\\cmd.exe, /c, configure.cmd -silen t]] [INFO] Process being executed, waiting for completion. [INFO] [configure script] exit code: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2:43.223s [INFO] Finished at: Thu May 09 15:57:22 EDT 2013 [INFO] Final Memory: 6M/17M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:list-apps
Lists the deployment names for applications and standalone modules deployed, distributed, or installed in the domain. Does not require a local server installation.
Table 3-10 list-apps Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, ignore all version-related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of -1 means wait forever. |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the list-apps goal to list the deployment names.
<execution>
<id>wls-list-apps</id>
<phase>pre-integration-test</phase>
<goals>
<goal>list-apps</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
</configuration>
</execution>
Example 3-8 shows typical list-apps
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:list-apps -Duser=weblogic -Dpassword=password [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:list-apps (default-cli) @ weblogic-m aven-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - listapps -user weblogic SamplesSearchWebApp stockBackEnd ajaxJSF asyncServlet30 singletonBean webFragment examplesWebApp mainWebApp annotation MySimpleEjb stockFrontEnd jsfBeanValidation programmaticSecurity entityBeanValidation faceletsJSF bookmarkingJSF stockAdapter noInterfaceViewInWAR jdbcDataSource.war asyncMethodOfEJB calendarStyledTimer cdi jaxrs criteriaQuery portableGlobalJNDIName multipartFileHandling elementCollection Number of Applications Found : 27 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 8.656s [INFO] Finished at: Fri May 03 11:33:51 EDT 2013 [INFO] Final Memory: 11M/28M [INFO] ------------------------------------------------------------------------ C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib>
com.oracle.weblogic:weblogic-maven-plugin:redeploy
Redeploys a running application or part of a running application. Does not require a local server installation.
Table 3-11 redeploy Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
Removes the files specified in this parameter while leaving the application activated. This parameter is valid only for unarchived deployments. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the path to the deployment plan. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds before WebLogic Server undeploys the currently running version of this application or module so that clients can start using a new version. When not specified, a graceful retirement policy is assumed. |
|
|
false |
Specifies the number of seconds in the grace period for RMI requests during graceful shutdown. Can be used only when the |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Archive file or exploded archive directory to deploy. You can omit this option and supply only the file or directory to deploy. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. The default target is AdminServer. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of -1 means wait forever. |
|
|
false |
When true, copies the specified source files to the Administration Server's |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information during the deployment process. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the redeploy goal to redeploy an application or part of that application.
<execution>
<id>wls-redeploy</id>
<phase>pre-integration-test</phase>
<goals>
<goal>redeploy</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<source>${project.build.directory}/${project.build.finalName}.${project.packaging}</sour
ce>
<name>${project.build.finalName}</name>
</configuration>
</execution>
Example 3-9 shows typical redeploy
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:redeploy -Dsou rce=C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib\MySimpleEjb.jar -Duser =weblogic -Dpassword=password -Dname=ExampleEJB [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:redeploy (default-cli) @ weblogic-ma ven-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - redeploy -user weblogic -name ExampleEJB -source C:\Oracle\Middleware\Oracle_Hom e\wlserver\server\lib\MySimpleEjb.jar -targets AdminServer <May 3, 2013 12:38:02 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiat ing redeploy operation for application, ExampleEJB [archive: C:\Oracle\Middlewar e\Oracle_Home\wlserver\server\lib\MySimpleEjb.jar], to AdminServer .> Task 3 initiated: [Deployer:149026]deploy application ExampleEJB on AdminServer. Task 3 completed: [Deployer:149026]deploy application ExampleEJB on AdminServer. Target state: redeploy completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.322s [INFO] Finished at: Fri May 03 12:38:02 EDT 2013
com.oracle.weblogic:weblogic-maven-plugin:start-app
Starts an application deployed on WebLogic Server. Does not require a local server installation.
Table 3-12 start-app Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
When true, switches the application to administration mode so that it accepts only administration requests via a configured administration channel. When false, production mode is assumed. |
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
Specifies the version identifier of the application. When not specified, the currently active version of the application is assumed. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, ignores all version-related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
password |
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the version of the deployment plan. When not specified, the currently active version of the application's deployment plan is assumed. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds before WebLogic Server undeploys the currently running version of this application or module so that clients can start using a new version. When not specified, a graceful retirement policy is assumed. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. When not specified, all configured targets are used. For a new application, the default target is the Administration Server. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information during the deployment process. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the start-app goal to starts an application.
<execution>
<id>wls-start-app</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start-app</goal>
</goals>
<configuration>
<adminurl>t3://localhost:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<name>${project.build.finalName}</name>
</configuration>
</execution>
Example 3-10 shows typical start-app
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:start-app -Duser=weblogic -Dpassword=password -Dname=ExampleEJB [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:start-app (default-cli) @ weblogic-m aven-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - start -user weblogic -name ExampleEJB -retiretimeout -1 <May 3, 2013 12:44:15 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiat ing start operation for application, ExampleEJB [archive: null], to configured t argets.> Task 5 initiated: [Deployer:149026]start application ExampleEJB on AdminServer. Task 5 completed: [Deployer:149026]start application ExampleEJB on AdminServer. Target state: start completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.053s [INFO] Finished at: Fri May 03 12:44:16 EDT 2013 [INFO] Final Memory: 10M/26M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:start-server
Starts WebLogic Server from a script in the current working directory.
Table 3-13 start-server Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the script to start WebLogic Server. If this parameter is not specified, it will default to either |
|
|
false |
Specifies the path to the WebLogic Server domain. |
|
|
false |
Specifies the URL that, when pinged, will verify that the server is running. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies in seconds, the timeout for the script. Valid when the |
|
|
false |
This parameter is deprecated in this release and ignored. |
The start-server
goal executes a startWebLogic
command on a given domain, starting the WebLogic Server instance.
<execution> <id>wls-wlst-start-server</id> <phase>pre-integration-test</phase> <goals> <goal>start-server</goal> </goals> <configuration> <domainHome>${project.build.directory}/base_domain</domainHome> </configuration> </execution>
Example 3-11 shows typical start-server
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:start-server -DdomainHome=c:\oracle\middleware\oracle_home\user_projects\domains\wl_server [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2-0-0 [INFO] ------------------------------------------------------------------------[INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:start-server (default-cli) @ weblogic-maven-plugin --- .[INFO] Starting server in domain: c:\oracle\middleware\oracle_home\user_projects\domains\wl_server [INFO] Check stdout file for details: c:\oracle\middleware\oracle_home\user_projects\domains\wl_server\server-2183114106972126386.out [INFO] Process being executed, waiting for completion. ............. [INFO] Server started successful [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 37.725s [INFO] Finished at: Wed May 01 14:25:45 EDT 2013 [INFO] Final Memory: 8M/23M
com.oracle.weblogic:weblogic-maven-plugin:stop-app
Stops an application. Does not require a local server installation.
Table 3-14 stop-app Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
When true, switches the application to administration mode so that it accepts only administration requests via a configured administration channel. When false, production mode is assumed. |
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
Specifies the version identifier of the application. When not specified, the currently active version of the application is assumed. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
When true, stops the application after existing |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
When true, ignores pending |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, ignores all version-related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the version of the deployment plan. When not specified, the currently active version of the application's deployment plan is assumed. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds in the grace period for RMI requests during graceful shutdown. Can be used only when the |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. When not specified, all configured targets are used. For a new application, the default target is the Administration Server. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the stop-app goal to stop an application.
<execution> <id>wls-start-app</id> <phase>pre-integration-test</phase> <goals> <goal>start-app</goal> </goals> <configuration> <adminurl>t3://localhost:7001</adminurl> <user>weblogic</user> <password>password</password> <name>${project.build.finalName}</name> </configuration> </execution>
Example 3-12 shows typical stop-app
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:stop-app -Dus er=weblogic -Dpassword=password -Dname=ExampleEJB [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:stop-app (default-cli) @ weblogic-ma ven-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - stop -user weblogic -name ExampleEJB <May 3, 2013 12:46:27 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiat ing stop operation for application, ExampleEJB [archive: null], to configured ta rgets.> Task 6 initiated: [Deployer:149026]stop application ExampleEJB on AdminServer. Task 6 completed: [Deployer:149026]stop application ExampleEJB on AdminServer. Target state: stop completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.028s [INFO] Finished at: Fri May 03 12:46:27 EDT 2013 [INFO] Final Memory: 10M/29M [INFO] ------------------------------------------------------------------------ C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib>
com.oracle.weblogic:weblogic-maven-plugin:stop-server
Stops WebLogic Server from a script in the current working directory.
Table 3-15 stop-server Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
Specifies the script to stop WebLogic Server. This will default to |
|
|
false |
Specifies the path to the WebLogic Server domain. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the log file to which the script output will be redirected. When not specified, it defaults to |
|
|
true |
Specifies the administrative password. |
|
|
false |
Specifies, in seconds, the timeout for the script. This is valid when the |
|
|
true |
Specifies the administrative user name. |
|
|
false |
When true, the plug-in should wait for the script to complete. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the working directory for the script. If you do not specify this attribute, it defaults to the current working directory. |
The stop-server
goal stops a server instance using the stopWebLogic
script in the specified domain.
<execution>
<id>wls-wlst-stop-server</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop-server</goal>
</goals>
<configuration>
<domainHome>${project.build.directory}/base_domain</domainHome>
<user>weblogic</user>
<password>password</password>
<adminurl>t3://localhost:7001</adminurl>
</configuration>
</execution>
Example 3-13 shows typical stop-server
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:stop-server -DdomainHome=c:\oracle\middleware\oracle_home\userprojects\domains\wl_server -DworkingDir=c:\oracle\middleware\oracle_home\user_projects\domains\wl_server -Duser=weblogic -Dpassword=password [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2-0-0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:stop-server (default-cli) @ weblogic -maven-plugin --- [INFO] Stop server in domain: c:\oracle\middleware\oracle_home\user_projects\dom ains\wl_server [INFO] Process being executed, waiting for completion. [INFO] [exec] Stopping Weblogic Server... [INFO] [exec] [INFO] [exec] Initializing WebLogic Scripting Tool (WLST) ... [INFO] [exec] [INFO] [exec] Welcome to WebLogic Server Administration Scripting Shell [INFO] [exec] [INFO] [exec] Type help() for help on available commands [INFO] [exec] [INFO] [exec] Connecting to t3://localhost:7001 with userid weblogic ... [INFO] [exec] Successfully connected to Admin Server "AdminServer" that belongs to domain "wl_server". [INFO] [exec] [INFO] [exec] Warning: An insecure protocol was used to connect to the [INFO] [exec] server. To ensure on-the-wire security, the SSL port or [INFO] [exec] Admin port should be used instead. [INFO] [exec] [INFO] [exec] Shutting down the server AdminServer with force=false while connec ted to AdminServer ... [INFO] [exec] WLST lost connection to the WebLogic Server that you were [INFO] [exec] connected to, this may happen if the server was shutdown or [INFO] [exec] partitioned. You will have to re-connect to the server once the [INFO] [exec] server is available. [INFO] [exec] Disconnected from weblogic server: AdminServer [INFO] [exec] Disconnected from weblogic server: [INFO] [exec] [INFO] [exec] [INFO] [exec] Exiting WebLogic Scripting Tool. [INFO] [exec] [INFO] [exec] Done [INFO] [exec] Stopping Derby Server... [INFO] [exec] Derby server stopped. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 23.270s [INFO] Finished at: Wed May 01 14:33:47 EDT 2013 [INFO] Final Memory: 9M/23M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:undeploy
Undeploys the application from WebLogic Server. Stops the deployment unit and removes staged files from target servers. Does not require a local server installation.
Table 3-16 undeploy Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
Specifies the version identifier of the application. When not specified, the currently active version of the application is assumed. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
When true, stops the application after existing |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
When true, ignores pending |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, ignores all version-related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the version of the deployment plan. When not specified, the currently active version of the application's deployment plan is assumed. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds in the grace period for RMI requests during graceful shutdown. Can be used only when the |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. When not specified, all configured targets are used. For a new application, the default target is the Administration Server. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information during the deployment process. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the undeploy goal to undeploy an application from WebLogic Server.
<execution>
<id>wls-undeploy</id>
<phase>post-integration-test</phase>
<goals>
<goal>undeploy</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<name>${project.build.finalName}</name>
</configuration>
</execution>
Example 3-14 shows typical undeploy
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:undeploy -Duser=weblogic -Dpassword=password -Dname=ExampleEJB [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:undeploy (default-cli) @ weblogic-ma ven-plugin --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 - undeploy -user weblogic -name ExampleEJB -targets AdminServer <May 3, 2013 12:48:15 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiat ing undeploy operation for application, ExampleEJB [archive: null], to AdminServ er .> Task 7 initiated: [Deployer:149026]remove application ExampleEJB on AdminServer. Task 7 completed: [Deployer:149026]remove application ExampleEJB on AdminServer. Target state: undeploy completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.114s [INFO] Finished at: Fri May 03 12:48:15 EDT 2013 [INFO] Final Memory: 9M/26M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:uninstall
Uninstalls WebLogic Server using the Zip installer. This goal requires a Zip installer-installed WebLogic Server installation
Table 3-17 uninstall Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
true |
The Oracle Middleware installation directory. |
Use the uninstall goal to uninstall WebLogic Server.
<execution> <id>wls-uninstall-server</id> <phase>post-integration-test</phase> <goals> <goal>uninstall</goal> </goals> <configuration> <middlewareHome>c:/dev/wls12120</middlewareHome> </configuration> </execution>
Example 3-15 shows typical uninstall
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:uninstall -DmiddlewareHome=C:\Oracle\Middleware\Oracle_Home [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WebLogic Server Maven Plugin 12.1.2.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:uninstall (default-cli) @ weblogic-m aven-plugin --- [INFO] Attempting to uninstall from : C:\Oracle\Middleware\Oracle_Home [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 27.886s
com.oracle.weblogic:weblogic-maven-plugin:update-app
Updates an application's deployment plan by redistributing the plan files and reconfiguring the application based on the new plan contexts. Does not require a local server installation.
Table 3-18 update-app Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the listen address and listen port of the Administration Server. |
|
|
false |
When true, prints advanced usage options. |
|
|
false |
Specifies the version identifier of the application. When not specified, the currently active version of the application is assumed. |
|
|
false |
When true, displays debug-level messages to the standard output. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
When true, displays examples of how to use this plug-in. |
|
|
false |
When true, forces the Mojo to fail the build upon encountering an error if it would otherwise just log the error. |
|
|
false |
Specifies an optional, user-supplied, unique deployment task identifier. |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies the deployment name to assign to a newly-deployed application or standalone module. |
|
|
false |
When true, ignores all version-related code paths on the Administration Server. |
|
|
false |
When true, initiates multiple tasks and then monitors them later with the |
|
|
false |
Specifies the administrative password. |
|
|
false |
Specifies the location of the deployment plan. |
|
|
false |
Specifies the version of the deployment plan. When not specified, the currently active version of the application's deployment plan is assumed. |
|
|
false |
When true, eliminates retired deployment tasks. |
|
|
false |
When true, specifies that the plug-in is not running on the same machine as the Administration Server. In this case, the |
|
|
false |
Specifies the number of seconds in the grace period for RMI requests during graceful shutdown. Can be used only when the |
|
|
false |
This parameter is deprecated in this release and ignored. |
|
|
false |
Specifies JMS Server targets for resources defined within a JMS application module. |
|
|
false |
Specifies a comma-separated list of targets for the current operation. When not specified, all configured targets are used. For a new application, the default target is the Administration Server. |
|
|
false |
Specifies the maximum number of seconds WebLogic Server will wait for the deployment task to complete. The default value of |
|
|
false |
When true, copies the source files to the Administration Server's upload directory prior to deployment. Use this setting when running the plug-in remotely (using the |
|
|
false |
Specifies the administrative user name. |
|
|
false |
Specifies the location of a user configuration file to use for the administrative user name and password instead of specifying the user name and password directly in plain text. |
|
|
false |
Specifies the location of a user key file to use for encrypting and decrypting the user name and password stored in the user configuration file. |
|
|
false |
When true, displays additional status information. |
|
|
false |
When true, prints the version information. |
|
|
false |
This parameter is deprecated in this release and ignored. |
Use the update-app goal to update an application's deployment plan.
<execution>
<id>wls-update-app</id>
<phase>pre-integration-test</phase>
<goals>
<goal>update-app</goal>
</goals>
<configuration>
<adminurl>t3://127.0.0.1:7001</adminurl>
<user>weblogic</user>
<password>password</password>
<name>${project.build.finalName}</name>
<plan>${basedir}/misc/myplan.xml</plan>
</configuration>
</execution>
Example 3-16 shows typical wlst
goal output.
$ mvn com.oracle.weblogic:weblogic-maven-plugin:update-app -Duser=weblogic -Dpassword=password -Dadminurl=t3://localhost:7001 -Dplan=misc/myplan.xml -Dname=basicWebapp [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building basicWebapp 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:update-app (default-cli) @ main-test --- weblogic.Deployer invoked with options: -noexit -adminurl t3://localhost:7001 -update -user weblogic -plan /home/oracle/src/tests/main-test/misc/myplan.xml -name basicWebapp -targets AdminServer <May 15, 2013 2:30:34 PM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating update operation for application, basicWebapp [archive: null], to AdminServer .> Task 10 initiated: [Deployer:149026]update application basicWebapp on AdminServer. Task 10 completed: [Deployer:149026]update application basicWebapp on AdminServer. Target state: update completed on Server AdminServer [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.651s [INFO] Finished at: Wed May 15 14:30:34 EST 2013 [INFO] Final Memory: 18M/435M [INFO] ------------------------------------------------------------------------
com.oracle.weblogic:weblogic-maven-plugin:wlst
WLST wrapper for Maven.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies a string value containing command-line arguments to pass to the WLST Python interpreter. The arguments are delimited by spaces. An argument that contains embedded spaces should be quoted either with single quotes or with escaped double quotes. For example, here is a string for args that contains two parameters: "'Thomas Paine' \"Now is the time that tries men's souls.\"" |
|
|
false |
When true, displays additional status information. Default value is: |
|
|
false |
When true, specifies whether a script, if supplied, executes before or after the file, if supplied. Either a file or a script is required, and both are allowed. See Default value is: |
|
|
false |
When true, the Maven build fails if the Default value is: |
|
|
false |
Specifies the file path of the WLST Python script to execute. Either a |
|
|
true |
The path to the Oracle Middleware install directory. |
|
|
false |
Specifies the path to a Java properties file. The property names become defined variables in the WLST Python interpreter and are initialized to the values supplied. For example, if the properties file contains the line |
|
|
false |
Specifies an inline WLST Python script, for example, " |
|
|
false |
This parameter is deprecated and ignored in this release. |
|
|
false |
This parameter is deprecated and ignored in this release. |
|
|
false |
Specifies whether to run the wlst.sh script from |
The wlst
goal enables the WebLogic Scripting Tool (WLST) to be used to execute scripts that configure resources or perform other operations on a WebLogic Server domain. The wlst
Maven goal uses the WebLogic Server WLST standard environment so you can use it with all your existing WLST scripts.
You can use the wlst
goal to execute an external WLST script specified with the fileName
configuration parameter or you can specify a sequence of WLST commands within the pom.xml
file using the script
configuration element.
<execution>
<id>wls-wlst-server</id>
<phase>post-integration-test</phase>
<goals>
<goal>wlst</goal>
</goals>
<configuration>
<middlewareHome>c:/dev/wls12120</middlewareHome>
<fileName>${project.basedir}/misc/configure_resources.py</fileName>
<args>t3://localhost:7001 weblogic password AdminServer</args>
<script>
print('This is a WLST inline script\n')
print('Next, we run a WLST script to create JMS resources on the server\n')
</script>
<executeScriptBeforeFile>true</executeScriptBeforeFile>
</configuration>
</execution>
Example 3-17 shows typical wlst
goal output.
mvn com.oracle.weblogic:weblogic-maven-plugin:wlst -DfileName=create-datasource.py [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building maven-demo 1.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:wlst (default-cli) @ maven-demo --- [INFO] ++====================================================================++ [INFO] ++ weblogic-maven-plugin: wlst ++ [INFO] ++====================================================================++ *** Creating DataSource *** Connecting to t3://localhost:7001 with userid weblogic ... Successfully connected to Admin Server 'AdminServer' that belongs to domain 'mydomain'. Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead. Location changed to edit tree. This is a writable tree with DomainMBean as the root. To make changes you will need to start an edit session via startEdit(). For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your changes once you are done. Activating all your changes, this may take a while ... The edit lock associated with this edit session is released once the activation is completed. Activation completed Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root. For more help, use help(serverRuntime) **** DataSource Details **** Name: cp Driver Name: Oracle JDBC driver DataSource: oracle.jdbc.xa.client.OracleXADataSource Properties: {user=demo} State: Running [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS
By default, the wlst
goal is bound to the pre-integration-test phase. To override the default phase binding for a goal, you can explicitly bind plug-in goals to a particular life cycle phase, for example, to the post-integration-test phase, as shown below. The pom.xml
file binds the wlst
goal to both the pre- and post-integration-test phases (a dual phase target). As shown, you can run different scripts in different phases, overriding the default settings, and make modifications according to your needs.
Example pom.xml
file
<project> .... <executions> <execution> <id>WLS_SETUP_RESOURCES</id> <phase>pre-integration-test</phase> <goals> <goal>wlst</goal> </goals> <configuration> <fileName>src/main/wlst/create-datasource.py</fileName> </configuration> </execution> <execution> <id>WLS_TEARDOWN_RESOURCES</id> <phase>post-integration-test</phase> <goals> <goal>wlst</goal> </goals> <configuration> <fileName>src/main/wlst/remove-datasource.py</fileName> </configuration> </execution> </executions> .... </project>
com.oracle.weblogic:weblogic-maven-plugin:ws-clientgen
Maven goal to generate JAX-WS client Web service artifacts from a WSDL.
The ws-clientgen
goal provides a Maven wrapper for the "clientgen" Ant task, which is described in WebLogic Web Services Reference for Oracle WebLogic Server.
Note:
The ws-clientgen
goal does not work with the JAX-RPC-only JWS annotations described in "WebLogic-Specific Annotations."
Table 3-20 briefly describes the ws-clientgen
parameters. These parameters are more fully described in Table 2-3 "WebLogic-specific Attributes of the clientgen Ant Task" in WebLogic Web Services Reference for Oracle WebLogic Server.
Table 3-20 ws-clientgen Parameters
Name | Type | Required | Description |
---|---|---|---|
binding bindings |
|
false |
Specifies one or more customization files that specify JAX-WS and JAXB custom binding declarations or SOAP handler files. If there is only one binding element, both See Table 3-21 for a description of |
|
|
false |
Specifies an external XML catalog file to resolve external entity references. For more information about creating XML catalog files, see "Using XML Catalogs" in Developing JAX-WS Web Services for Oracle WebLogic Server |
|
boolean |
false |
Controls where the WSDL should be copied in the ws-clientgen goal 's destination dir. |
|
boolean |
false |
Turns on additional debug output. |
|
boolean |
false |
Uses Ant debug levels. |
|
|
true |
Specifies the directory into which the ws-clientgen goal generates the client source code, WSDL, and client deployment descriptor files. You must specify either the |
|
boolean |
false |
Specifies whether the ws-clientgen goal continues executing in the event of an error. The default value is True. |
|
boolean |
false |
Specifies whether to execute javac using the JDK compiler externally. The default value is false. |
|
boolean |
false |
Specifies whether the ws-clientgen goal should generate the XML catalog artifacts in the client runtime environment. This value defaults to true. |
|
boolean |
false |
Specifies whether to include the Ant run-time libraries in the classpath. |
|
boolean |
false |
Specifies whether to include the default run-time libraries from the executing VM in the classpath. |
|
JMSTransportClient |
false |
Invoking a WebLogic Web service using JMS transport. Table 3-23 describes the parameters of the |
|
|
false |
Specifies the package name into which the generated client interfaces and stub files are packaged. |
produce produces |
FileSet List<FileSet> |
false |
There is only one FileSet. There is more than one FileSet. |
|
boolean |
false |
Turns on verbose output |
|
|
true |
Specifies a full path name or URL of the WSDL that describes a Web service (either WebLogic or non-WebLogic) for which the client component files should be generated. |
|
|
false |
Controls the value of the wsdlLocation attribute generated on the |
|
|
false |
Specifies the authorization file. |
|
|
false |
Not used. |
Table 3-21 describes the parameters of the bindings
parameter.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies a customization file that contains JAX-WS and JAXB custom binding declarations or SOAP handler files. |
Table 3-22 describes the parameters of the xmlCatalog
parameter.
Table 3-22 xmlCatalog Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the directories (separated by semi-colons) that the |
Table 3-23 describes the parameters of the jmstransportclient
parameter.
Table 3-23 jmstransportclient Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
JNDI name of the destination queue or topic. Default value is |
|
|
false |
Valid values include: QUEUE or TOPIC. Default value is QUEUE. |
|
|
false |
JNDI name of the JMS destination to which the response message is sent. |
|
|
false |
Port component name of the Web service. |
|
|
false |
Name of the initial context factory class used for JNDI lookup. Default value is |
|
|
JNDI name of the connection factory that is used to establish a JMS connection. Default value is |
|
|
|
JNDI provider URL. Default value is |
|
|
|
Delivery mode indicating whether the request message is persistent. Valid values are PERSISTENT and NON_PERSISTENT. Default value is PERSISTENT. |
|
|
long |
false |
Lifetime, in milliseconds, of the request message. Default value is 180000L. |
|
int |
false |
JMS priority associated with the request and response message. Default value is 0. |
|
|
false |
JNDI properties, in a format like: someParameterName1=someValue1 , someParameterName2=someValue2. |
|
|
false |
Version of the SOAP JMS binding. Default value is 1.0. |
|
|
false |
Principal used to run the listening MDB. |
|
|
false |
Role used to run the listening MDB. |
|
|
false |
Message type to use with the request message. Valid values are |
|
boolean |
false |
Boolean flag that specifies whether to publish the WSDL through HTTP. Default value is true. |
|
boolean |
false |
Boolean flag that specifies whether to create one listening message-driven bean (MDB) for each requested destination. Default value is true. |
|
|
false |
Activation configuration properties passed to the JMS provider. |
|
|
false |
The deployed context of the web service. |
|
|
false |
Web service URI portion of the URL. |
|
|
false |
The name of the port in the generated WSDL. |
The ws-clientgen
goal generates client Web service artifacts from a WSDL.
This goal benefits from the convention-over-configuration approach, allowing you to execute it using the defaults of the project.
There are two ways to run the ws-clientgen goal:
From the command line. For example, after you define an alias:
mvn –DvariableName1=value1 –DvariableName2=value2 com.oracle.weblogic:weblogic-maven-plugin:ws-clientgen
By specifying the Maven generate-resources
life cycle phase. Then run mvn generate-resources
in the same directory of pom.xml.
To do this, modify the pom.xml
file to specify the generate-resources
life cycle phase, the ws-clientgen
goal, and include any parameters you need to set. Consider the following example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>maven_plugin.simple</groupId> <artifactId>maven_plugin_simple</artifactId> <version>1.0</version> <build> <plugins> <plugin> <groupId>com.oracle.weblogic</groupId> <artifactId>weblogic-maven-plugin</artifactId> <version>12.1.2-0-0</version> <executions> <execution> <id>clientgen</id> <phase>generate-resources</phase> <goals> <goal>ws-clientgen</goal> </goals> <configuration> <wsdl>${basedir}/AddNumbers.wsdl</wsdl> <dest${project.build.outputDirectory}</destDir> <packageName>maven_plugin.simple.client</packageName> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
Example 3-18 shows typical ws-clientgen
goal output.
mvn -f C:\maven-doc\jwsc-test-2\clientgen_pom.xml generate-resources [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building maven_plugin_simple 1.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:ws-clientgen (clientgen) @ maven_plugin_sim ple --- [INFO] Executing standalone... [INFO] Executing Maven goal 'clientgen'... calling method public static void weblogic.wsee.tools.clientgen.MavenClientGen.e xecute(org.apache.maven.plugin.logging.Log,java.util.Map) throws java.lang.Throw able [INFO] Consider using <depends>/<produces> so that wsimport won't do unnecessary compilation [WARNING] parsing WSDL... [WARNING] [WARNING] [WARNING] [WARNING] Generating code... [WARNING] [WARNING] [WARNING] Compiling code... [WARNING] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS
com.oracle.weblogic:weblogic-maven-plugin:ws-wsdlc
Maven goal to generate a set of artifacts and a partial Java implementation of the Web service from a WSDL.
The ws-wsdlc
goal provides a Maven wrapper for the "wsdlc" Ant task, which is described in WebLogic Web Services Reference for Oracle WebLogic Server.
Table 3-24 briefly describes the ws-wsdlc
parameters. These parameters are more fully described in Table 2-3 "WebLogic-specific Attributes of the clientgen Ant Task" in WebLogic Web Services Reference for Oracle WebLogic Server.
Table 3-24 ws-wsdlc Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies an external XML catalog file. For more information about creating XML catalog files, see "Using XML Catalogs" in Developing JAX-WS Web Services for Oracle WebLogic Server |
|
boolean |
false |
Specifies the flag to set when debugging the process. Default value is false. |
|
|
false |
Uses Ant debug levels. |
|
|
false |
Specifies the directory into which the stubbed-out JWS implementation file is generated. |
|
|
false |
Specifies the directory into which the Javadoc that describes the JWS interface is generated. |
|
|
true |
Specifies the directory into which the JAR file that contains the JWS interface and data binding artifacts should be generated. |
|
boolean |
false |
Specifies the flag to set if you want exploded output. Defaults to true. |
|
boolean |
false |
Specifies whether the ws-clientgen goal continues executing in the event of an error. The default value is true |
|
boolean |
false |
Specifies whether to execute javac using the JDK compiler externally. The default value is false. |
|
boolean |
false |
Specifies whether to include the Ant run-time libraries in the classpath. The default value is true. |
|
boolean |
false |
Specifies whether to include the default run-time libraries from the executing VM in the classpath. The default value is false. |
|
boolean |
false |
Specifies the flag to set if you want optimization. Defaults to true. |
|
|
false |
Specifies the package into which the generated JWS interface and implementation files should be generated. |
|
|
false |
Specifies the name of the WSDL port from which the JWS interface file should be generated. Set the value of this parameter to the value of the The |
|
|
false |
Specifies the name of the Web service from which the JWS interface file should be generated. |
|
|
true |
Specifies the name of the WSDL from which to generate the JAR file that contains the JWS interface and data binding artifacts. |
|
boolean |
false |
Specifies the flag to set if you want verbose output. Default value is false. |
The ws-wsdlc
goal generates a set of artifacts and a partial Java implementation of the Web service from a WSDL.
This goal benefits from the convention-over-configuration approach, allowing you to execute it using the defaults of the project.
There are two ways to run the ws-wsdlc
goal:
From the command line. For example, after you define an alias:
mvn –DvariableName1=value1 –DvariableName2=value2 com.oracle.weblogic:weblogic-maven-plugin:ws-wsdlc
By specifying the Maven generate-resources
life cycle phase.
To do this, modify the pom.xml
file to specify the generate-resources
life cycle phase, the ws-wsdlc
goal, and include any parameters you need to set. Then run mvn generate-resources
in the same directory of pom.xml.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>maven_plugin.simple</groupId> <artifactId>maven_plugin_simple</artifactId> <version>1.0</version> <build> <plugins> <plugin> <groupId>com.oracle.weblogic</groupId> <artifactId>weblogic-maven-plugin</artifactId> <version>12.1.2-0-0</version> <executions> <execution> <id>wsdlc</id> <phase>generate-resources</phase> <goals> <goal>ws-wsdlc</goal> </goals> <configuration> <srcWsdl>${basedir}/AddNumbers.wsdl</srcWsdl> <destJwsDir>${project.build.directory}/jwsImpl</destJwsDir> <destImplDir>${project.build.directory}/output</destImplDir> <packageName>maven_plugin.simple</packageName> <verbose>true</verbose> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
Example 3-19 shows typical ws-wsdlc
goal output.
mvn -f wsdlc_pom.xml generate-resources [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building maven_plugin_simple 1.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:ws-wsdlc (wsdlc) @ maven_plugin_simple --- [INFO] Executing standalone... [INFO] Executing Maven goal 'wsdlc'... calling method public static void weblogic.wsee.tools.wsdlc.MavenWsdlc.execute(o rg.apache.maven.plugin.logging.Log,java.util.Map) throws java.lang.Throwable Catalog dir = C:\Users\maven\AppData\Local\Temp\_ckr59b Download file [AddNumbers.wsdl] to C:\Users\maven\AppData\Local\Temp\_ckr59b srcWsdl is redefined as [ C:\Users\maven\AppData\Local\Temp\_ckr59b\AddNumber s.wsdl ] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS
com.oracle.weblogic:weblogic-maven-plugin:ws-jwsc
Maven goal to build a JAX-WS web service.
The ws-jwsc
goal provides a Maven wrapper for the "jwsc" Ant task, which is described in WebLogic Web Services Reference for Oracle WebLogic Server.
Note:
The ws-jwsc
goal does not work with the JAX-RPC-only JWS annotations described in "WebLogic-Specific Annotations."
Nested Configuration in module Elements
The ws-jwsc
goal supports nested configuration elements, as shown in bold in Example 3-20. See Introduction to the POM for information on Maven projects with multiple modules.
Example 3-20 Nested Configuration Elements
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>com.test.ws</groupId> <artifactId>test-ws-jwsc1</artifactId> <version>1.0</version> <build> <plugins> <plugin> <groupId>com.oracle.weblogic</groupId> <artifactId>weblogic-maven-plugin</artifactId> <version>12.1.2-0-0</version> <executions> <execution> <id>first-jwsc</id> <phase>generate-resources</phase> <goals> <goal>ws-jwsc</goal> </goals> <configuration> <srcDir>${basedir}/src/main/java</srcDir> <destDir>${project.build.directory}/jwscOutput /${project.build.finalName}</destDir> <listfiles>true</listfiles> <debug>true</debug> <module> <name>pocreate</name> <contextPath>mypub</contextPath> <compiledWsdl>D:\maven-test\order_wsdl.jar</compiledWsdl > <jws> <file>examples/wsee/jwsc/POCreateImpl.java</file> <transportType> <type>WLHttpTransport</type> <serviceUri>POCreate</serviceUri> <portName>POCreatePort</portName> </transportType> </jws> <jws> … </jws> <descriptors> <descriptor>"resources/web.xml"<descriptor/> <descriptor>"resources/weblogic.xml"<descriptor /> </descriptors> </module> <module> … </module> </modules> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
These nested configuration elements for ws-jwsc
have the following conditions:
You must use at least one of the following elements: jws
, jwses
, module
, or modules
.
Collection elements such as jwses
and modules
elements can be omitted.
If there is only one child element within the collection element, the collection element can also be removed.
For example, if there is only one jws
element, use jws
. If there are multiple jws
elements, add all of the jws
elements under a jwses
element.
As with the JWSC ant task, if module
has only one jws
child element, then other sub elements of module
can be nested into jwsc
and jwsc/transportType
.
Example 3-21 shows an example without a module element
in which the jws
parameter is a child of ws-jwsc
.
Example 3-21 jws Element as Child of ws-jwsc Goal
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>com.test.ws</groupId> <artifactId>test-ws-jwsc</artifactId> <version>1.0</version> <build> <plugins> <plugin> <groupId>com.oracle.weblogic</groupId> <artifactId>weblogic-maven-plugin</artifactId> <version>12.1.2-0-0</version> <executions> <execution> <id>first-jwsc</id> <phase>compile</phase> <goals> <goal>ws-jwsc</goal> </goals> <configuration> <srcDir>${basedir}/src/main/java</srcDir> <destDir>${project.build.directory}/jwscOutput/ ${project.build.finalName}</destDir> <jws> <!-- no parent <module> --> <file>examples/wsee/jwsc/POCreateImpl.java</file> <compiledWsdl>${project.build.directory}/purchaseorder_wsdl.jar> <transportType> <type>WLHttpTransport</type> </transportType> </jws> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
Table 3-25 briefly describes the ws-jwsc
parameters. These parameters are more fully described in Table 2-3 "WebLogic-specific Attributes of the clientgen Ant Task" in WebLogic Web Services Reference for Oracle WebLogic Server.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
Specifies the full name and path of the application.xml deployment descriptor of the Enterprise Application. If you specify an existing file, the ws-jwsc goal updates it to include the Web services information. However, jwsc does not automatically copy the updated application.xml file to the destDir; you must manually copy this file to the destDIR. If the file does not exist, jwsc creates it. The ws-jwsc goal also creates or updates the corresponding weblogic-application.xml file in the same directory. If you do not specify this attribute, jwsc creates or updates the file destDir/META-INF/application.xml, where destDir is the jwsc attribute. |
|
boolean |
false |
Turns on additional debug output. |
|
|
true |
Specifies the full pathname of the directory that will contain the compiled JWS files, XML Schemas, WSDL, and generated deployment descriptor files, all packaged into a JAR or WAR file. |
|
|
false |
Specifies the character encoding of the output files, such as the deployment descriptors and XML files. Examples of character encodings are SHIFT-JIS and UTF-8. The default value of this attribute is UTF-8. |
|
Jws |
false |
There is only one <jws> element. See Table 3-26 for a description of |
|
Jws |
false |
It contains more than one< jws> element. |
|
boolean |
false |
Specifies whether the Java source files and artifacts generated by this goal should be regenerated if they already exist. If you specify false, new Java source files and artifacts are always generated and any existing artifacts are overwritten. If you specify true, the goal regenerates only those artifacts that have changed, based on the timestamp of any existing artifacts |
|
boolean |
false |
Specifies whether to list all of the files. |
|
Module |
false |
It contains one <module> element. See Table 3-27 for a description of |
|
Module |
false |
It contains more than one <module> element. |
|
boolean |
false |
Specifies the flag to set when optimization is required. Defaults to true. |
|
|
true |
The full pathname of top-level directory that contains the Java files referenced by the JWS file, such as JavaBeans used as parameters or user-defined exceptions. |
|
|
true |
Specifies the full pathname of the top-level directory that contains the JWS file you want to compile. |
|
|
false |
Specifies the character encoding of the input files, such as the JWS file or configuration XML files. Examples of character encodings are SHIFT-JIS and UTF-8. The default value of this attribute is the character encoding set for the JVM. |
|
boolean |
false |
Specifies verbose output |
As described in "jws", the jws
parameter specifies the name of a JWS file that implements your Web service and for which the ws-jwsc
goal should generate Java code and supporting artifacts, and then package them into a deployable WAR file inside of an Enterprise Application.
You can specify the jws
parameter in two ways:
An immediate child element of the ws-jwsc
goal. In this case, ws-jwsc
generates a separate WAR file for each JWS file. You typically use this method if you are specifying just one JWS file to the ws-jwsc
goal.
A child element of the module
parameter, which in turn is a child of the ws-jwsc
goal. In this case, ws-jwsc
generates a single WAR file that includes all the generated code and artifacts for all the JWS files grouped within the module parameter.
This method is useful if you want all JWS files to share supporting files, such as common Java data types.
Table 3-26 describes the child parameters of the jws
parameter. The description specifies whether the parameter applies in the case that jws
is a child of the ws-jwsc
goal, is a child of module
, or both.
Name | Type | Required | Description | Child of ws-jwsc, module, or both |
---|---|---|---|---|
|
|
false |
Specifies the full pathname of the JAR file generated by the Only required for the "starting from WSDL" use case. |
both |
|
|
false |
Specifies the deployed context of the web service. |
ws-jwsc |
|
boolean |
false |
Specifies the flag to set when you want exploded output. Defaults to true. |
ws-jwsc |
|
|
true |
The name of the JWS file that you want to compile. The ws-jwsc goal looks for the file in the srcdir directory. |
both |
|
boolean |
true |
Specifies whether the generated WAR file includes the WSDL file in the WEB-INF directory. Default value is false. |
both |
|
boolean |
false |
Use JMS transport for Web services. It can be omitted. See Table 3-30 for a description of |
ws-jwsc |
|
|
false |
Specifies the name of the generated WAR file (or exploded directory, if the explode attribute is set to true) that contains the deployable Web service. |
ws-jwsc |
|
transportType |
false |
Used when it contains only one transport See Table 3-29 for a description of |
both |
|
transportType |
false |
Used when it contains more than one transport See Table 3-29 for a description of |
both |
|
boolean |
false |
Specifies that only a WSDL file should be generated for this JWS file. The default value is false. |
ws-jwsc |
As described in "module", the module
parameter groups one or more jws
parameters together so that their generated code and artifacts are packaged in a single Web application (WAR) file. The module
parameter is a child of the ws-jwsc
goal.
Table 3-27 describes the parameters of the module parameter.
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
There is only one <clientgen> element. It can be omitted. |
|
|
false |
There is more than one <clientgen> element. It can be omitted. |
|
|
false |
Specifies the deployed context of the Web service. |
|
|
false |
Specifies the web.xml descriptor to use if a new one should not be generated. The path should be fully qualified. The files should be separated by ", ". |
|
boolean |
false |
Specifies whether to package EJB-based Web services in a WAR file instead of a JAR file. |
|
boolean |
false |
Specifies the flag to set when you want exploded output. Defaults to true. |
|
FileSet |
false |
Used when it contains one FileSet element. It can be omitted. |
|
FileSet |
false |
Used when it contains more than one FileSet element. It can be omitted. |
|
boolean |
true |
Specifies whether the generated WAR file includes the WSDL file in the WEB-INF directory. Default value is false. |
|
Jws |
false |
Used when it contains one jws element. It can be omitted. |
|
Jws |
false |
Used when it contains more than one jws element. It can be omitted. |
|
|
false |
Specifies the name of the WAR to use when evaluating the ear file. |
|
boolean |
false |
Specifies that only a WSDL file should be generated for this JWS file. The default value is false. |
zipfileset |
|
false |
There is only one <zipfileset> element. |
As described in "fileset", the FileSet
parameter specifies one or more directories in which the ws-jwsc
goal searches for JWS files to compile. The list of JWS files that ws-jwsc
finds is then treated as if each file had been individually specified with the jws
parameter of module
.
The FileSet
parameter is a child of the ws-jwsc
goal.
Table 3-28 describes the parameters of the FileSet parameter.
Name | Type | Required | Description |
---|---|---|---|
|
|
true |
Specifies the directories (separated by semi-colons) that the ws-jwsc goal should search for JWS files to compile. |
|
|
false |
Prefix to use. |
|
|
false |
Specifies the explicit includes-list for the file set. |
|
|
false |
Specifies the explicit excludes-list for the file set. |
As described in "WLHttpTransport", "WLHttpsTransport", and "WLJMSTransport", you use transport parameters to specify the transport type, context path, and service URI sections of the URL used to invoke the Web service, as well as the name of the port in the generated WSDL.
The ws-jwsc
goal combines these transport parameters into one, TransportType
.
Table 3-28 describes the parameters of the transportType
parameter.
Table 3-29 transportType Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
true |
Specifies the value is WLHttpTransport, WLHttpsTransport, or WLJMSTransport. Default value is WLHttpTransport. |
|
|
false |
Specifies the Web service URI portion of the URL. |
|
|
false |
Specifies the deployed context of the Web service. |
|
|
false |
Specifies the name of the port in the generated WSDL. |
Table 3-30 describes the parameters of the jmstransportservice
parameter.
Table 3-30 jmstransportservice Parameters
Name | Type | Required | Description |
---|---|---|---|
|
|
false |
JNDI name of the destination queue or topic. Default value is |
|
|
false |
Valid values include: QUEUE or TOPIC. Default value is QUEUE. |
|
|
false |
JNDI name of the JMS destination to which the response message is sent. |
|
|
false |
Port component name of the Web service. |
|
|
false |
Name of the initial context factory class used for JNDI lookup. Default value is |
|
|
JNDI name of the connection factory that is used to establish a JMS connection. Default value is |
|
|
|
JNDI provider URL. Default value is |
|
|
|
Delivery mode indicating whether the request message is persistent. Valid values are PERSISTENT and NON_PERSISTENT. Default value is PERSISTENT. |
|
|
long |
false |
Lifetime, in milliseconds, of the request message. Default value is 180000L. |
|
int |
false |
JMS priority associated with the request and response message. Default value is 0. |
|
|
false |
JNDI properties, in a format like: someParameterName1=someValue1 , someParameterName2=someValue2. |
|
|
false |
Version of the SOAP JMS binding. Default value is 1.0. |
|
|
false |
Principal used to run the listening MDB. |
|
|
false |
Role used to run the listening MDB. |
|
|
false |
Message type to use with the request message. Valid values are |
|
boolean |
false |
Boolean flag that specifies whether to publish the WSDL through HTTP. Default value is true. |
|
boolean |
false |
Boolean flag that specifies whether to create one listening message-driven bean (MDB) for each requested destination. Default value is true. |
|
|
false |
Activation configuration properties passed to the JMS provider. |
|
|
false |
The deployed context of the web service. |
|
|
false |
Web service URI portion of the URL. |
|
|
false |
The name of the port in the generated WSDL. |
The ws-jwsc
goal builds a JAX-WS web service.
This goal benefits from the convention-over-configuration approach, allowing you to execute it using the defaults of the project.
To run the ws-jwsc
goal, specify the Maven generate-resources
phase.
To do this, modify the pom.xml
file to specify the generate-resources
phase, the ws-jwsc
goal, and include any pa parameters you need to set. Then run mvn generate-resources
in the same directory of pom.xml.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>maven_plugin.simple</groupId> <artifactId>maven_plugin_simple</artifactId> <version>1.0</version> <build> <plugins> <plugin> <groupId>com.oracle.weblogic</groupId> <artifactId>weblogic-maven-plugin</artifactId> <version>12.1.2-0-0</version> <executions> <execution> <id>jwsc</id> <phase>generate-resources</phase> <goals> <goal>ws-jwsc</goal> </goals> <configuration> <destDir>${project.build.directory}/jwscOutput/ <listfiles>true</listfiles> <debug>true</debug> <jws> <!-- no parent <module> --> <file>examples/wsee/jwsc/POCreateImpl.java</file> <compiledWsdl>${project.build.directory}/purchaseorder_wsdl.jar> <transportType> <type>WLHttpTransport</type> </transportType> </jws> <verbose>true</verbose> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
Example 3-22 shows typical ws-jwsc
goal output.
mvn -f jwsc_pom.xml generate-resources INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building maven_plugin_simple 1.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- weblogic-maven-plugin:12.1.2-0-0:ws-jwsc (jwsc) @ maven_plugin_simple --- [INFO] Executing standalone... INFO] Executing Maven goal 'jwsc'... calling method public static void weblogic.wsee.tools.jws.MavenJwsc.execute(org.apache.maven.plugin.logging.Log, java.util.Map) throws java.lang.Throwable [EarFile] Application File : C:\maven-doc\jwsc-test-2\output\META-INF\application.xml [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS