Bug 1035849 - SwitchYardTestKit throws NPE when it depends on BPEL component
Summary: SwitchYardTestKit throws NPE when it depends on BPEL component
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 15:58 UTC by Andrej Podhradsky
Modified: 2023-05-15 19:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If you add the switchyard-component-bpel dependency to a service, the SwitchYardTestKit throws a null-pointer exception. To work around this, you need to add bpel.properties.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Project example (9.94 KB, application/zip)
2014-10-30 11:57 UTC, Andrej Podhradsky
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1866 0 Major Resolved SwitchYardTestKit throws NPE when it depends on BPEL component 2016-01-06 12:10:24 UTC

Description Andrej Podhradsky 2013-11-28 15:58:55 UTC
Description of problem:
When I add a switchyard-component-bpel dependency, the SwitchYardTestKit throws NPE. By removing this dependency everything works fine.

Now, I see that I need bpel.properties. But this fact should be mentioned in exception message. Btw why bpel settings are needed if I don't test bpel? (in my case, the bpel dependency was added by mistake)

Version-Release number of selected component (if applicable):
ER6

How reproducible:
always

Comment 1 Andrej Podhradsky 2014-10-30 11:57:29 UTC
Created attachment 952069 [details]
Project example

Comment 2 Andrej Podhradsky 2014-10-30 11:58:28 UTC
In the attached project example try to remove (or rename) bpel.properties

Comment 3 tcunning 2015-06-15 20:40:25 UTC
Should be in first 6.2.1 build.


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