Bug 1150093
| Summary: | SOAP port has a different name than the default getCommandServicePort method uses | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> | ||||||
| Component: | Business Central | Assignee: | Shelly McGowan <smcgowan> | ||||||
| Status: | CLOSED EOL | QA Contact: | Ivo Bek <ibek> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.1.0 | CC: | etirelli, ibek, kverlaen | ||||||
| Target Milestone: | ER5 | ||||||||
| Target Release: | 6.1.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-03-27 19:34:03 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ivo Bek
2014-10-07 12:19:21 UTC
Hi Ivo, Should I change "CommandServiceClient" to be "CommandServicePort"? It's not clear to me what a good solution to this problem would be. Any suggestions would be great, thanks! Hi Marco, every option is good to me, whether you choose "CommandServiceClient" or "CommandServicePort" but both should be the same in the WSDL and in the generated client class. Perhaps "CommandServicePort" might be better, however that is just my opinion. Hence it should be enought to change this line of portName to "CommandServicePort": https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-remote/kie-remote-services/src/main/java/org/kie/remote/services/ws/command/CommandWebServiceImpl.java#L14 Thanks Ivo, Could you take another look at this? All classes are generated based on the WSDL. I'm not sure how a generated class could be different than what's in the WSDL. Also, could you attach the WSDL that you're seeing? Thanks! Created attachment 963384 [details] CommandService.wsdl in BPMS 6.1.0.ER2 I have still the same problem in BPMS 6.1.0.ER2 when I use: cws = client.getCommandServicePort(); org.apache.cxf.service.factory.ServiceConstructionException: Could not find definition for port {http://services.remote.kie.org/6.2.0.1/command}CommandServicePort. This is the method causing the issue: getCommandServicePort() { return super.getPort(new QName("http://services.remote.kie.org/6.2.0.1/command", "CommandServicePort"), CommandWebService.class); } To make it working I have to change it to: cws = client.getPort(new QName("http://services.remote.kie.org/6.2.0.1/command", "CommandServiceClient"), CommandWebService.class); However, I noticed that in the same class there is a field with correct name: private final static QName COMMANDSERVICECLIENT_QNAME = new QName("http://services.remote.kie.org/6.2.0.1/command", "CommandServiceClient"); I attached the WSDL that BPMS 6.1.0.ER2 provides at http://localhost:8080/business-central/ws/CommandService?wsdl Ivo, this might be related to the dependencies in the test. Could you provide a git link to the reproducer, so I can see which dependencies are being used? Also, kie-remote-services should never be used on the client side. The client side library for the command webservice is kie-remote-ws-wsdl-cmd and kie-remote-ws-common. As a result of another bug (involving authentication and security), this has been fixed. I believe that this test tests the issue: https://github.com/droolsjbpm/droolsjbpm-integration/blob/6.2.x/kie-remote/kie-remote-client/src/test/java/org/kie/remote/services/ws/command/CommandServiceTest.java Verified in BPMS 6.1.0.ER5 |