Hi Martin ++> my comment below. -----Ursprüngliche Nachricht----- Von: Marcin Wieczorek [mailto:mar...@clockwork-bits.pl] Gesendet: Mittwoch, 11. September 2013 11:57 An: java-user@axis.apache.org Betreff: Re: AW: [AXIS2] Installing Axis 1.6.2 in Tomcat
W dniu 2013-09-11 10:03, Stadelmann Josef pisze: > Did you manage to build run and understand the simple axis2 samples? > Are they running? No and yes. I didn't build samples but I think I understand them. ++> I would build some of them, you learn a lot and it will demonstrate the problems of deploying if any. > Is the axis2 happyness page at > http://integ1:8080/axis2/axis2-web/HappyAxis.jsp > showing proper information? > > Can you see your deployed service using > http://integ1:8080/axis2/services/listServices ? That's the thing. I do not want to build service. I just want to use (consume) remote SOAP service from inside already running web application. ++> OK, so your web service is in fact an agent, a service for your client and a client for the remote SOAP service. ++> Now I think to make progress you should make that more simple to start. ++> I would suggest that you build an AXIS2 client, generate a stub using the WSDL information provided by the running remote SOAP service, and only if this client is running, go and integrate it into your service to make your service behaving as an agent. All I need Axis2 to do for me is take my POJ convert to SOAP, send, receive, convert back. ++> I would not start with a POJO but with a stub generated by AXIS2 WSDL to JAVA tools ++> if your client runs after all, you can take the tcpmonitor and look about what gets exchanged. Then build your POJO to exchange the same. Without setting up listening services, without Axis2 admin page etc. I use SOAP in other languages so I know how SOAP works. It's just I need to do it in JavaEE. I tried to use Apache CXF first but unfortunately SOAP service I have to use (and have no control over) uses wrong type of message encapsulating (the old unsupported one). So I turned to Axis2. ++>maybe you can even ask the remote service provider about how the service is implemented. Given it is a MS ASP .Net web service you may have problems with that as well. So again: make it short and simple. Maybe just use i.e Visual Studio or any other toos to generate a stub, i.e. to add a service reference with VS, this is created by svutil and then use it from you i.e. VB or C# client. And you can do the same using the wsdl2java from the running service. Once you have the stub just call it from your client code. And only if that is running go and integrate that code into your own service. I think even if your own service is based on EE, you can still call from EE the generated stub and this calls then the remote SOAP web service. <++ > how is your solution packaged? > what and where did you deploy your solution to /tomcat_home/webapps? I intended to not use Axis2 as a separate WAR. I try to compile it together with the rest of my code to single WAR. So far I can see Axis2 libraries included in my compiled WAR together with other libraries. ++> if you make the JAX-WS / JAXB samples running then you will get a service which is packaged into .WAR, i you deploy that and if that is running you can then see the .jar's form axis2 used > given your solution is packaged in mysolution.war, > can you see a directory /tomcat_home/webapps/mysolution ? Yes. > given your solution is packaged in mysolution.aar, > can you see a directory /tomcat_home/webapps/axis2/web-inf/services > containing mysolution.aar? No. > Is the service.xml provided and deployed properly? > Probably not. Because I did not setup one yet. All I did is I included dependencies for Maven and one Axis2-generated java class in my working web app and after that my web app stopped working. This web app is unrelated to Axis2. By unrelated I mean it does some stuff for user already and it's working. It's just I need to use SOAP to use external service in the background. I didn't configure Axis2 in any other way. That's why my question is about default behaviour of Axis2. Once again (because it probably wasn't clear in my first post): I need fast, simple and lightweight way to use existing remote SOAP service. Just send some messages and get some response. No running services, no Axis admin pages, no hassle. I have read a lot of documentation from Axis2 page and from other sources. Unfortunately it looks like my needs are not that popular. Most of docs are for people needing standalone desktop app consuming SOAP or for apps running in containers but also exposing services. And I need something in between. ++> again, if you master to create a simple client consuming the remote SOAP web service then you know have made a big step toward a working solution. i.e. given your remote SOAP web service is based on AXIS2 as well and uses i.e. addressing, then it is absolute important that you engage the addressing module on the client side as well. How to do that can be find in axis2 sample and documentation. But again: if you master that your simple web service client can talk to the remote SOAP web service then your over the hill in my mind. Thanks for your answer. Sorry about my English, I am not a native speaker. ++> No problem, I am Swiss German and my English is as it is. Marcin. -- Clockwork Bits Software Marcin Wieczorek http://clockwork-bits.pl/ REGON: 100800499, NIP: 7281735575 Łódź 93-363, ul. Osobliwa 6 --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
