[
http://jira.codehaus.org/browse/MWAS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171284#action_171284
]
Chris Graham commented on MWAS-38:
----------------------------------
I installed WID 6.1.2 and found the class, ServiceDeployTask which is now in
com.ibm.soacore.runtime_6.1.0.jar, not wpsanttasks.jar as it was in 6.0.2.
Looking at the code, it has the same error that needed the same workaround: The
underlying java.setFailonerror is set by the ignoreErrors flag, not it's
opposite, as it needs to be.
Can you set debug = true (and/or verbose as well) and send me the output.
As a note however, I did have some modes of failure, where setting ignoreErrors
= true _did_ appear to change the processing of ServiceDeploy, in that it
reported issues, but swallowed the other errors, so an error was not passed
back from ws_ant and so could not be detected by the was6-maven-plugin.
You error, appears to be in the same category.
The only way that I got it to work was to apply the IBM patch. Then
ServiceDeploy will error correctly, and the Ant Java Task will catch the error
and correctly rethrow it to the maven plugin can correct it.
Your only solution in this case is to raise a new PMR for 6.1.
Please reference: PMR 78051,999,616 and/or the above APAR JR32145 and have the
same fix applied to 6.1/6.2.
-Chris
> ServiceDeploy failOnError ignored
> ---------------------------------
>
> Key: MWAS-38
> URL: http://jira.codehaus.org/browse/MWAS-38
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Bug
> Affects Versions: 1.1, 1.1.1
> Environment: Maven 2.0.9
> WID 6.1.2.2
> Reporter: Jason Pell
> Assignee: David J. M. Karlsen
> Priority: Critical
> Attachments: ServiceDeployMojo.java.patch
>
>
> A servicedeploy error which fails to generate the EAR file does not cause the
> maven build process to fail.
> [INFO] [servicedeploy] A warning message was reported during deployment:
> [INFO]
> [INFO] [servicedeploy] Severity: [warning]
> [INFO] [servicedeploy] Description: CWLBS0003E: The monitored map is not
> found.
> [INFO] [servicedeploy] Resource: RetrieveAccountMap_map.mon
> [INFO] [servicedeploy] Folder: AccountService
> [INFO] [servicedeploy] Location: 2
> [INFO]
> [INFO] [servicedeploy] An error message was reported during deployment:
> [INFO]
> [INFO] [servicedeploy] Severity: [error]
> [INFO] [servicedeploy] Description: The process does not implement the
> operation 'ValidateCardNumber' of the port type
> 'http://someurl.com/Service/0.5/AccountService:AccountServicePortType'.
> [INFO] [servicedeploy] Resource: AccountServiceProcess.bpel
> [INFO] [servicedeploy] Folder: AccountService
> [INFO]
> [INFO] [servicedeploy] Due to errors,
> /home/developr/Projects/trunk/sca/AccountServiceApp/target/AccountServiceApp-0.1-SNAPSHOT.ear
> was not created. Run with -ignoreErrors to override.
> [INFO] [servicedeploy] Deployment has completed
> [INFO] [servicedeploy] Waiting for background jobs
> [INFO] [servicedeploy] Deleting workspace
> [ERROR] [servicedeploy] Java Result: 2
> [INFO]
> [INFO] BUILD SUCCESSFUL
> [INFO] Total time: 1 minute 5 seconds
> [INFO] Return code: 0
> My suggestion would be to apply the same fix as for ejbdeploy
> Verify that the outputApplication exists
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
