This is a GET request. Thus, it kind of looks to me like this is asking for
the WSDL or similar, not actually a request.
Check the value of:
NCPlusOnlineInquiryService.WSDL_LOCATION
to make sure it's either a location that is local (like file://....) or would
have ?wsdl appended or similar to actually point at the wsdl.
Dan
On Thu October 8 2009 9:30:26 am dave derry wrote:
> I get scared when I read "There really isn't any way that ..." ;-}
> But in this case you are correct. The data captured (edited for readability
> is:
>
> GET /NCPlusOnlineInquiryService/NCPlusOnlineInquiryServicePort/1.0.0.0
> HTTP/1.1..
> User-Agent: Java/1.5.0_09
> Host: devhost.ec.equifax.com:7965
> Accept: text/html, image/gif, image/jpeg, *;
> q= .2, */*; q=.2..
> Connection: keep- alive.
> Content-type: application/x-www-form-urlencoded..
>
>
> So it is *not* being sent as a SOAP message. After posting my original
> message I found the doc on creating a CXF configuration file, but that
> didn't make any difference. I then realized that although CXF was used to
> generate the skeleton for this app, the project has no dependencies on CXF.
> Here is the output of 'mvn dependency:tree' :
>
> [INFO] [dependency:tree]
> [INFO] com.efx.ncplus:NCPlusClient:jar:1.0-SNAPSHOT
> [INFO] +- stax:stax:jar:1.2.0:runtime
> [INFO] | \- stax:stax-api:jar:1.0.1:runtime
> [INFO] +- javax.xml.bind:jaxb-api:jar:2.2:compile
> [INFO] | +- javax.xml.stream:stax-api:jar:1.0-2:compile
> [INFO] | \- javax.activation:activation:jar:1.1:compile
> [INFO] +- javax.xml.ws:jaxws-api:jar:2.1-1:compile
> [INFO] | +- javax.xml.soap:saaj-api:jar:1.3:compile
> [INFO] | +- javax.annotation:jsr250-api:jar:1.0:compile
> [INFO] | \- javax.jws:jsr181-api:jar:1.0-MR1:compile
> [INFO] +- com.sun.xml.bind:jaxb-impl:jar:2.1.12:runtime
> [INFO] +- com.sun.xml.stream.buffer:streambuffer:jar:0.8:runtime
> [INFO] | \- org.jvnet.staxex:stax-ex:jar:1.2:runtime
> [INFO] | \- junit:junit:jar:3.8:runtime
> [INFO] +- com.sun.xml.bind:jaxb-xjc:jar:2.1.12:runtime
> [INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.1EA1:runtime
> [INFO] \- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:runtime
>
>
> And here is a portion of the client code:
>
> public final class
> NCPlusOnlineInquiryServicePortType_NCPlusOnlineInquiryServicePort_Client
> {
>
> private static final QName SERVICE_NAME = new
> QName("http://services.equifax.com/gds/ncplus/servicedefs";,
>
> "NCPlusOnlineInquiryService");
>
> private
> NCPlusOnlineInquiryServicePortType_NCPlusOnlineInquiryServicePort_Client()
> {
> }
>
> public static void main(String args[]) throws Exception
> {
> URL wsdlURL = NCPlusOnlineInquiryService.WSDL_LOCATION;
> // setting wsdlURL from args cut
>
> NCPlusOnlineInquiryService ss = new
> NCPlusOnlineInquiryService(wsdlURL, SERVICE_NAME);
> NCPlusOnlineInquiryServicePortType port =
> ss.getNCPlusOnlineInquiryServicePort();
>
> {
> System.out.println("Invoking getAccountsInformation at " +
> wsdlURL + "...");
> InquiryRequestType request = new InquiryRequestType();
> InquiryRequestHeaderType header = new
> InquiryRequestHeaderType();
> header.setCustRefField("1234");
> header.setSecCode("901");
> header.setMemberNbr("999EP00001");
> request.setInquiryRequestHeader(header);
> InquiryResponseType response =
> port.getAccountsInformation(request);
> System.out.println("getAccountsInformation.result=" +
> response);
>
> }
>
> System.exit(0);
> }
>
> }
>
>
> OK, clearly I've done something wrong, but being a newbie to CXF, I have no
> clue what it is.
>
> Dave
>
> dkulp wrote:
> > Any chance you could wireshark this to see what really is being sent on
> > the
> > wire. There really isn't any way that CXF should be sending that
> > content-
> > type for a soap message.
> >
> > Note: also update to 2.2.3 if possible. (and 2.2.4 will be out early next
> > week)
> >
> > Dan
>
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
