Wanted to post the solution I found to this here so that it will live on the
Internet for others to find with Google
For whatever reason...Java would not send my client certificate no matter
all the advice I managed to find on Google.
I had my JaxWsProxyFactoryBean already setup in an xml
Funny... You are attempting ERCOT
Here is my thread where I attempted CAISO
http://cxf.547215.n5.nabble.com/Best-CXF-client-approach-for-remote-WSDL-using-wsp-Policy-td5721874.html
FWIW, I did my ERCOT client a long time ago, and used Axis 1.4 with JAXB
bindingsit still works today
Finally got all the particulars of the request message worked out! Thanks
for all the help everyone!
Now I have another interesting problem. The code works fine on the nominal
path now.
When there is an error, I get the following:
javax.xml.ws.soap.SOAPFaultException: Unexpected element
Thanks. I did add that property and it did eliminate those extra statements.
Still got the Invalid Message error. :(
I am waiting on a reply back from their IT Group, which is ungodly slow of
course. While I'm waiting...
Is there a way to make the custom CWSHeader element to show up first in
Thanks for the help everyone! I really appreciate it. This stuff has me
stressed out to no end since its taking me so long.
I tried doing it manually with old Axis1 but that was a painful waste of
today, lol. So I'm back to CXF 2.7 which I prefer.
I found a sample request.xml in one of their
*sigh*
I was sure this was going to work
The XML request looks good to me:
Link: http://pastebin.com/DCCEts9q
Not sure why I am still getting Access Denied, Invalid Message back from
their server. :(
Is it possible the order of the elements in the SOAP Header matter? How
could I move the
] ml-node+s547215n5721924...@n5.nabble.com
To: Bob Ross supaphr...@yahoo.com
Sent: Monday, January 21, 2013 4:02 AM
Subject: Re: Best CXF client approach for remote WSDL using wsp:Policy
Hi Bob,
I am having trouble making a CXF client that works with the following
WSDL:
http://pastebin.com
I am having trouble making a CXF client that works with the following WSDL:
http://pastebin.com/9nCh5fBT (the actual location is client-SSL protected)
I have tried multiple approaches to generating a client that fulfills the
security policies it dictates, but I'm either encrypting too much or it
