Bug 1014319 - more logging when creating JaxWS client in ServiceTaskHandler
Summary: more logging when creating JaxWS client in ServiceTaskHandler
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ER5
: 6.0.0
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 17:27 UTC by jbride@redhat.com
Modified: 2014-08-06 20:06 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:06:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description jbride@redhat.com 2013-10-01 17:27:15 UTC
Hi.
  i'm smoke testing the BPMN2 ServiceTaskHandler to invoke remote SOAP service.
  So far so good.
  Request I have is to allow an option for logging of a stack trace exception that could occur when attempting to parse a remote WSDL and instantiate a JaxWSClient.  There are all kinds of potential problems that can arise in creating the JaxWSClient (ie:  security, network, wrong service/port names, etc).  Currently, the ServiceTaskHandler workItemHandler buries these exceptions when attempting to create the JaxWSClient such that the only way to view the exception is through a debugger.
  Request that the following be addeded :

https://github.com/droolsjbpm/jbpm/blob/master/jbpm-workitems/src/main/java/org/jbpm/process/workitem/bpmn2/ServiceTaskHandler.java#L184

    184                         return client;
    185                     } catch (Exception e) {
    186                         if(logger.isDebugEnabled()){
    187                             e.printStackTrace();
    188                         }
    189                         continue;
    190                     }


thanks!  jeff

Comment 3 Marek Baluch 2013-12-04 07:23:11 UTC
Verified on ER5.


Note You need to log in before you can comment on or make changes to this bug.