Description of problem: Description Resource Path Location Type No bean is eligible for injection to the injection point [JSR-299 §5.2.1] OrderServiceBean.java /switchyard-quickstart-bean-service/src/main/java/org/switchyard/quickstarts/bean/service line 30 CDI Problem WS-I: (AP2901) A description uses neither the WSDL MIME Binding as described in WSDL 1.1 Section 5 nor WSDL SOAP binding as described in WSDL 1.1 Section 3 on each of the wsdl:input or wsdl:output elements of a wsdl:binding. OrderService.wsdl /switchyard-quickstart-bean-service/src/main/resources/wsdl line 59 WSDL Problem WS-I: (BP2402) The wsdl:binding element does not use a soapbind:binding element as defined in section "3 SOAP Binding." of the WSDL 1.1 specification. OrderService.wsdl /switchyard-quickstart-bean-service/src/main/resources/wsdl line 0 WSDL Problem
Description: Warnings/Errors found in JBDS "Problems" View, right after quickstart is imported as maven project. steps to reproduce: 1. Start JBDS 2. import existing maven project 3. Window / Show View / Problems 4. check for errors
The CDI error was resolved by prior fixes. Am looking into fixing the WSDL warnings.
We believe the two WSDL warnings are being reported erroneously by the Eclipse WSDL validator. We have created BZ 415786 at Eclipse to report the issue. We believe these messages are reported in error and that the validator isn't respecting SOAP 1.2 extensions for WSDL as documented here: http://www.w3.org/Submission/wsdl11soap12/ It seems to be looking for the SOAP 1.1 binding, which is not required. In the meantime we will need to accept the warnings for now or turn off WSDL validation. (Windows->Preferences, Validation, find the "WSDL Validator" entry and uncheck the Manual and Build boxes.
See previous comment. We need to report these warnings upstream.
Upstream warnings. Report bug against WTP if this is critical.