Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1
-
Fix Version/s: 1.2
-
Labels:None
-
Environment:WAS 7.0 standalone server / Windows 32 bits.
-
Number of attachments :
Description
I ran the attached pom succesfully on an unsecured WAS 7.0 server.
The POM runs a jython script, uninstalls an EAR, installs it again and runs the jython script again. This works on WAS 7.0.
Once I secure the server the WsAdminMojo fails. The WsUninstallAppMojo and WsInstallAppMojo work.
The jython script is not special at this moment yet: it prints "hello world" to the console.
I have attached the following files:
- secured_run.txt - a run on a secured connection;
- unsecured_run.txt - a run on a unsecured connection;
- pom.xml - my pom;
IŽd like to run the jython script on a secured server to modify application scoped resources. This will allow us to run a nightly build, deploy, configire and jmeter test from maven.
I ran the pom in debug mode and I discovered that the user is null when it hits the WsAdminMojo. The other variables like password, host and so on are set.
I will see what I can do to set the user in the WsAdminMojo.