RE: axis2 nightly build
A couple of days ago I tried building the war from HEAD (in windows) and could not get passed some unit tests. Does anybody have the new war to give me? Kosta Tachtevrenidis FileNet Developer (253) 924-4862 http://www.weyer.com/dmg -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 01, 2006 11:02 AM To: axis-user@ws.apache.org Subject: Re: axis2 nightly build Hi, You can simply replace the axis2-* jars in the WEB-INF/lib directory with the latest ones. *BUT* ... you will run into a problem in doing so since we have changed the structure of the repository (The sub-dirs that is expected to be there in the WEB-INF dir) and the dependant jars. As a possible solution that *MIGHT* work, you can try the following steps: - create a directory named 'conf' in the WEB-INF dir of the expanded directory of the war in the servlet container (E.g. Tomcat : webapps/axis2/WEB-INF/) - move the axis2.xml file in the WEB-INF dir into WEB-INF/conf (The directory that you just created) - Copy all the jars from here : [1] to WEB-INF/lib - Remove WSS4J-SNAPSHOT.jar from WEB-INF/lib - Restart the servlet container. If you don't want to go through this hassle you can simply build the war yourself from the SVN head, which will have everything setup properly :-) AND the recommended solution is to use the new war. HTH Thanks, Ruchith [1] http://cvs.apache.org/repository/ws-commons/jars/ On 3/1/06, Tachtevrenidis, Kosta [EMAIL PROTECTED] wrote: Sure but now the question becomes, how can I use those instead of the ones that come with the 0.94 war I deployed? Kosta Tachtevrenidis FileNet Developer (253) 924-4862 http://www.weyer.com/dmg -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 01, 2006 3:03 AM To: axis-user@ws.apache.org Subject: Re: axis2 nightly build I'm not sure whether you are looking for jars or the whole dist. But if you are looking for just nightly jars, they are here : http://cvs.apache.org/repository/axis2/jars/ -- Chinthaka Tachtevrenidis, Kosta wrote: dear group, is there a way to get a nightly build of axis2 (the binary). I know I can build it but sometimes having a nightly binary is handy. thanks Kosta
axis2 nightly build
dear group, is there a way to get a nightly build of axis2 (the binary). I know I can build it but sometimes having a nightly binary is handy. thanks Kosta
RE: how to debug Axis2 WSDL2Java
Greg, I have gotten that a lot too. What I do to get an idea of what is going on is to use the wsewsdl3.exe tool to try to generate code for .NET, which have a pretty good error message capability. Just my thoughts. Kosta Tachtevrenidis http://www.weyer.com/dmg From: Greg Michalopoulos [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 1:49 PMTo: axis-user@ws.apache.orgSubject: how to debug Axis2 WSDL2Java I am getting exceptions when running WSDL2Java in Axis2, is there any way to get feedback from the application what might be wrong with my WSDL? Thanks, Greg
Invalid URI reported by .NET Client (WSE 3.0)
Title: Invalid URI reported by .NET Client (WSE 3.0) I have been struggling with this for a while. I have a basic service that receives an OMElement and returns one. Here is an example of what it return (with header info ommitted). createContentResponseresultHello/result/createContentResponse Using WSE3.0 I pass it a string and everything is good, I can manipulate it on the server side just fine. When my axis2 service returns the soap response, me .NET client reports this: System.UriFormatException : Invalid URI: The format of the URI could not be determined. at Microsoft.Web.Services3.AsyncResult.End(IAsyncResult result) at Microsoft.Web.Services3.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope) at Microsoft.Web.Services3.Messaging.SoapClient.SendRequestResponse(String methodname, Object obj) Here is my service: public OMElement createContent (OMElement elem) { String resultText; OMElement resultElem; OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace namespace = fac.createOMNamespace(http://tempuri.org, ns1); OMElement theResult = fac.createOMElement(result, namespace); resultText = Hello; theResult.setText(resultText); resultElem = fac.createOMElement(createContentResponse, namespace); resultElem.addChild(theResult); return resultElem; } } I know the correct response is generated because I can see it through the TcpTunnelGUI. Why can't WSE 3.0 interpret it? Can somebody tell me what I am doing wrong or whatever other information I need to provide for better troubleshooting. Thanks! Kosta Tachtevrenidis