Hi Vivian,
the response is completely empty (no tags at all) ?
Do you have the smx log file ?
Regards
JB
Madesclair Vivian wrote:
Hello,
Any updates about this issue?
Regards,
Vivian
-----Message d'origine-----
De : Madesclair Vivian [mailto:[email protected]]
Envoyé : mardi 23 juin 2009 17:13
À : [email protected]
Objet : RE: http-component, wsdl forwarding
Gert,
I couldn't download SoapUI, but I managed to get firebug (thx for the hint btw)
and firefox gets a response with no content. So the client.html is fine, the
response is lost before. Is it a bug? If so, why does it occur only in my case?
I'm not sure I can save some time to get in smx's code...
Regards,
Vivian
-----Message d'origine-----
De : Madesclair Vivian [mailto:[email protected]]
Envoyé : mardi 23 juin 2009 16:34
À : [email protected]
Objet : RE: http-component, wsdl forwarding
Gert,
Ok, thanks! I though about SoapUI too, but we have firewall that seems to
prevent downloads of more than a few Mo here. I'll see what I can do and keep
you updated.
Best Regards
Vivian
-----Message d'origine-----
De : Gert Vanthienen [mailto:[email protected]]
Envoyé : mardi 23 juin 2009 16:24
À : [email protected]
Objet : Re: http-component, wsdl forwarding
Vivian,
This all looks fine to me too. Just wonder if it isn't a problem with our
client.html file or something. Could you try with SoapUI to see what that
says? Or otherwise install Firebug in Firefox so you can see the actual
request/reponse that's going over the wire?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/6/23 Madesclair Vivian <[email protected]>
Gert,
Yes you are right. I am new to servicemix (and this is the first ESB I
try in fact) so I am first using it as a proxy for an axis webservice,
before I add more services and logic. You can find attached the
current versions of my xbeans. (Do not pay attention to the comments,
I tried a lot of things and I am just keeping track there.)
I switched the org.apache.servicemix level value to DEBUG (in the file
conf/log4j.xml). I hope that is what you wanted. I attached the smx output.
It start just after I deployed my SA. I reshaped the text so it should
be quite readable. The response of my axis service appear there and it
is right. I don't know where it gets lost.
It seems to me smx is returning STATUS 200 (and only that) because
that's what the client.html displays to me as a response. I get the
STATUS 500 (+ many other things in xml) when I plug this client.html
directly into my axis service, and not into servicemix (port 8080 for
tomcat instead of 8192 for smx).
Regards,
Vivian
-----Message d'origine-----
De : Gert Vanthienen [mailto:[email protected]]
Envoyé : mardi 23 juin 2009 14:43
À : [email protected]
Objet : Re: http-component, wsdl forwarding
Vivian,
Could you post us the configuration of your http consumer and provider
endpoint (because I guess that's what you're doing here, right, using
ServiceMix as a proxy for the Axis service?). My first guess would
have been an InOnly MEP as well. Could you enable debug logging and
make sure that all the MEPs are correct? Also, is the ServiceMix
service returning STATUS 200 and you get STATUS 500 when invoking the
Axis service directly or where do you see those two statuses?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/6/23 Madesclair Vivian <[email protected]>:
Thank you very much! I can now see the wsdl at the service adress
and it
seems to work.
I just have one issue now : I get no response, only "STATUS 200". I
am
using the client.html from the wsdl-first example to test this service
and it seems to work exept for this response. I checked the MEP of
http component and in the servicemix documentation, it says that it is
defaulted to in-out. Any idea?
My axis service is working, but I noticed I can't get a correct
response when using the client.html (I get a STATUS 500 so it seems
to me it is not what is causing my problem)
Also I have to mention for people who might read this topic later
that
the wsdl can contain several namespace. The hint of Gert was perfectly
clear and right for me, but you might have to use the other namespaces
(for example, in my soap requests, I had to use the targetNamespace
from the <schema> tag).
Best regard,
Vivian
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
