Hello all - I think I am missing something very si...
# lucee
m
Hello all - I think I am missing something very simple when converting an application from ACF to Lucee. When handling a very simple web service (being served by Lucee), I'm getting Axis errors.
Here are the combinations I have tried: 1: Hosted on ACF and called via <cfinvoke> ACF or Lucee -> Works fine 2: Hosted on Lucee and called via <cfinvoke> ACF or Lucee -> Axis error 3: Hosted on Lucee, manually create the SOAP XML and called via <cfhttp> -> Works fine Creating the component and calling the method works fine in all cases. Just the remote web services being hosted on Lucee. The WSDL is slightly different on Lucee than ACF, but returns normally.
Here is the simple web service
Here is what I get on Lucee. The top is the expected result, and it's from ACF. The bottom is what I am getting on Lucee.
And this is what I get on ACF when calling the same service on Lucee
One more piece of debug info. In all of these cases, SoapUI returns the regular, normal result. Same when I manually build the soap xml and use <cfhttp> (on either ACF or Lucee). Only seems to be a problem when hosting on Lucee and calling on ACF or Lucee with <cfinvoke>
s
I think Lucee only supports AXIS1, if that matters. On the rare and unfortunate occasions we need to process SOAP we get it via http and process it with CF's XML parsing functions and some wrappers to make that less unpleasant
The last time I tried to use Lucee to cfinvoke a SOAP web service it needed AXIS2 and I don't think Lucee does that
m
I did see that Lucee only has AXIS2, but was hoping for very simple web services, that wouldn't matter. You would think that Lucee could consume it's own web services though.
s
We've never used Lucee to offer webservices from the built-in UI. We just use Coldbox REST, no reason to have that stuff coupled to the engine
Even when we used ACF I don't think we'd have done the built-in webservices stuff
d
I (fortunately) have not had to do any SOAP stuff in a long time and never with Lucee, but is for internal tasks is there a specific reason you're trying to use SOAP? Why not just return JSON? That's way less complicated and has a lot less overhead and I would think would be much more fault tolerant and less likely to cause problems down the road. That said, Lucee should be able to communicate to itself. So either there's a bug in Lucee or something wacky in your install.
m
No, there isn't a need for internal tasks. I was just using that as a test. The real process is exposed web services to third party clients. When I couldn't consume from another ACF web service, I set up Lucee to call itself and that returned the same error as above.
What is really strange is that SoupUI can consume it fine. And, if I had roll the soap xml and call with <cfhttp> from ACF or Lucee, it also works fine.
Only when consuming from ACF/Lucee with <cfinvoke>