http://blog.gmane.org/gmane.text.xml.axis.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.text.xml.axis.user/82359 <pre>Hi, I would like to upgrade our Axis2 version from 1.3 to 1.6.2 to fix a bug that we are experiencing. We currently have this dependency in our project: &lt;groupId&gt;org.apache.axis2&lt;/groupId&gt; &lt;artifactId&gt;axis2&lt;/artifactId&gt; &lt;version&gt;1.3&lt;/version&gt; If I change the version to 1.6.2, are there any backwards compatibility issues or new configurations needed that I should be aware of? I can't find anything on the Axis2 website that address these concerns. Would it be as easy as replacing the version number in our POM, and the transition would be seamless? Thanks in advance, Dana CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.</pre> DeVice, Dana 2012-05-25T17:19:55 http://comments.gmane.org/gmane.text.xml.axis.user/82358 <pre>Hello, I'm using axis 1.6.1. Is there a way that I can have an exception message get through to the client? All I get is a notification that there was an exception, but it does not contain the actual message of the exception, even though the response shows an exception. Here's an example response, in which an axis generated client (from WSDL) does not display the actual message returned. We just receive a stack trace with no actual message. &lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;soapenv:Body&gt; &lt;soapenv:Fault&gt; &lt;faultcode&gt;soapenv:Server&lt;/faultcode&gt; &lt;faultstring&gt;java.sql.SQLException: ORA-02291: integrity constraint (SATURN.SYS_C0065841) violated - parent key not found ORA-06512: at "WEBBANNER.WEB_EXAMS", line 447 ORA-06512: at line 1 &lt;/faultstring&gt; &lt;detail&gt; &lt;ns:ExamRequestUpdateSQLException xmlns:ns="http://update.request.exam.athabascau.ca"&gt; &lt;SQLException xmlns="http://up</pre> Trenton D. Adams 2012-05-24T16:46:39 http://comments.gmane.org/gmane.text.xml.axis.user/82357 <pre>Hi, This is one of those things.. that worked before. Now I am trying to generate stub from a WSDL file as below. I have tried tweaking configuration files unders \axis2\conf as well. If some one has an answer, can you please share. C:\ax2-1.6.0BD\bin&gt;WSDL2Java -uri C:\tryStubs\CARDCLOS.wsdl -p com.com.xx.wsclient.closeCard -d adb -s -Eosv Using AXIS2_HOME: C:\ax2-1.6.0BD Using JAVA_HOME: C:\j2skd1.6_27 Retrieving document at 'C:\tryStubs\CARDCLOS.wsdl'. log4j:WARN No appenders could be found for logger (org.apache.axis2.description. WSDL11ToAllAxisServicesBuilder). log4j:WARN Please initialize the log4j system properly. Thanks, Nandeesh </pre> Nandeesh Kaggere 2012-05-23T13:53:45 http://comments.gmane.org/gmane.text.xml.axis.user/82355 <pre>&lt;p&gt;&lt;a href="http://sabdekho.com/lastnews/28MarkMacdonald/"&gt;http://sabdekho.com/lastnews/28MarkMacdonald/&lt;/a&gt;&lt;/p&gt; </pre> Antonio Bocci 2012-05-23T05:30:29 http://comments.gmane.org/gmane.text.xml.axis.user/82349 <pre>Hi, I tried both JDOM and now JDOM2. For JDOM2, XPathFactory xpfac = XPathFactory.instance(); XPathExpression xp = xpfac.compile("//foo/bar"); The xp is null. For JDOM, XPath xp = XPath.newInstance("//foo/bar"); The xp is null. Both work in the simple java application. I tried to putting the JDOM jar in webapps/axis2/WEB-INF/lib along with Jaxen - doesn't do a thing. Any ideas? Best regards, -a </pre> aaron.stromas< at >rsa.com 2012-05-22T15:41:02 http://comments.gmane.org/gmane.text.xml.axis.user/82347 <pre>Hello all, I just upgraded my webservices client from Axis1 to Axis2. With Axis1 I was able to log the HTTP requests and responses just by adding the following line to my log4j.properties log4j.logger.org.apache.axis.transport.http=DEBUG and it created nice logs where all the body of the http request was shown using just one log (The content could be multiline, but there was just one call to the logger) 8C499036B8A58B99B6BDB01792F3C2897CD828A7 2012-04-17 08:26:28,575 DEBUG org.apache.axis.transport.http.HTTPSender - Enter: HTTPSender::invoke 8C499036B8A58B99B6BDB01792F3C2897CD828A7 2012-04-17 08:26:28,745 DEBUG org.apache.axis.transport.http.HTTPSender - XML sent: 8C499036B8A58B99B6BDB01792F3C2897CD828A7 2012-04-17 08:26:28,745 DEBUG org.apache.axis.transport.http.HTTPSender - --------------------------------------------------- 8C499036B8A58B99B6BDB01792F3C2897CD828A7 2012-04-17 08:26:28,745 DEBUG org.apache.axis.transport.http.HTTPSender - POST /aa HTTP/1.0 Content-Type: text/xml; charset=utf-8 Ac</pre> JOSE L MARTINEZ-AVIAL 2012-05-22T03:01:12 http://comments.gmane.org/gmane.text.xml.axis.user/82346 <pre>Hi, I'm having some trouble adding an attachment to my response after attempting to follow the instructions here: http://axis.apache.org/axis2/java/core/docs/mtom-guide.html# The example from that url I am following is:         OMElement imageElement = fac.createOMElement("image", omNs);         // Creating the Data Handler for the file.  Any implementation of         // javax.activation.DataSource interface can fit here.         javax.activation.DataHandler dataHandler = new javax.activation.DataHandler(new FileDataSource("SomeFile"));         //create an OMText node with the above DataHandler and set optimized to true         OMText textData = fac.createOMText(dataHandler, true);         imageElement.addChild(textData); I suspect I am making a mistake in the creation of OMElement and OMNameSpace in my code below.       OMFactory factory = OMAbstractFactory.getOMFactory();       OMNamespace omNs = factory.createOMNamespace("I put the targetNamespace from the wsdl </pre> eric johnson 2012-05-21T20:10:35 http://comments.gmane.org/gmane.text.xml.axis.user/82338 <pre> Please help!!! Does anyone know how to change the Axis 2 Handler plugins (of an existing Axis 2 Handler) in order to call the JDOM parser before calling the web services???? Any recommendations??? </pre> josephina 2012-05-17T22:47:16 http://comments.gmane.org/gmane.text.xml.axis.user/82337 <pre>Hi, I've set up file caching for attachments by following these instructions: http://axis.apache.org/axis2/java/core/docs/mtom-guide.html#a4 I need a way to programmatically know what the name of the file that was created is so that in my web services skeleton I can process the file. How can this be accomplished? I have seen the files that are generated have names such as: axiomfc4c46332e06dfee16108281aab8ab7c5f1685e8d6ea7ca8.att Thanks, Eric </pre> eric johnson 2012-05-17T22:21:21 http://comments.gmane.org/gmane.text.xml.axis.user/82335 <pre>Hi java-user(s), I have a question related to the bug here: https://issues.apache.org/jira/browse/AXIS2-4445 We're trying to use Axis2 to generate a service from a WSDL that uses the wrapped array pattern. wsdl2java does its half of the job fine, but while trying to deploy the AAR Axis2 gives a stack trace virtually identical to the one at the above link. I notice this bug hasn't been fixed since 2009 so does anybody know a workaround that doesn't involve forking Axis2 or having to maintain custom patches? Thanks in advance, Oli </pre> Oliver Heard 2012-05-11T09:59:54 http://comments.gmane.org/gmane.text.xml.axis.user/82333 <pre>Hi there, I am trying to use wsdl2ejava Axis-1.6.2 generated stubs and including Rampart-1.6.2 for the WS-Sec. I have copied in to my application all the required Axis/Rampart jars, modules and created the required directory structure when building it. All my web services and generated code clients are deployed, visible and ready to go. But here is what I am experiencing when I try to invoke a client stub and make him engage 'rampart' module to pass the WCF exposed service with UsernameToken security. "Unable to engage module : rampart" Hmm, looked at the code and this seems to make sense even though all axis2 and rampart modules are deployed during startup form the WarBasedAxisConfigurator. When the stub's service client is configured a null ConfigurationContext is used as in previous versions but here the check for if (MessageContext.getCurrentMessageContext() == null) always is true and new ConfigurationContext is created from file system which uses the default axis2.xml and since a repository location</pre> Asen 2012-05-10T16:34:30 http://comments.gmane.org/gmane.text.xml.axis.user/82330 <pre>Hello, Could somebody provide me please some feedbacks regarding the AXIS2-5290&lt;https://issues.apache.org/jira/browse/AXIS2-5290&gt; issue ? Best Regards. </pre> COURTAULT Francois 2012-05-10T09:43:08 http://comments.gmane.org/gmane.text.xml.axis.user/82329 <pre>Hi all I have generated a client stub to call a 3rd party web service using Wsdl2Java. The provided WSDL (and XSDs imported it) includes a number of faults which are generated and returned by Axis2 as exceptions (all as per usual so far). However, the actual Soap message returned by the web service when a fault is encountered also includes some handy information outside of the Detail element, namely in the Reason element. An example is below: &lt;s:Body&gt; &lt;s:Fault&gt; &lt;s:Code&gt; &lt;s:Value&gt;s:Sender&lt;/s:Value&gt; &lt;/s:Code&gt; &lt;s:Reason&gt; &lt;s:Text xml:lang="en-AU"&gt;The RegistrationEndDateTime has an invalid datetime format. Check that it does not specify timezone information or have more than seconds precision.&lt;/s:Text&gt; &lt;/s:Reason&gt; &lt;s:Detail&gt; &lt;InvalidDateTimeFormatFaultDetail xmlns="http://schemas.xyz/faults" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;ErrorNumber&gt;50016&lt;/ErrorNumber&gt; &lt;ErrorReferenceId&gt;7f2f1085-9c7e-44a8-b1b7-2a995d0a4e0f&lt;/ErrorReferenceId&gt; &lt;RequestProcessedByEnvironment&gt;Discovery&lt;/Requ</pre> mflem70< at >gmail.com 2012-05-10T07:43:55 http://comments.gmane.org/gmane.text.xml.axis.user/82328 <pre>Hello all, We want to generate an Axis2 client (1.6.1) client for an old Axis1 service. The service is a plain POJO, and the server-config.wsdd is as follows: &lt;service name="ValuationsXMLGenerator" provider="java:RPC" style="document" use="literal"&gt; &lt;parameter name="wsdlTargetNamespace" value="urn:xml.generator.ws"/&gt; &lt;parameter name="schemaUnqualified" value="urn:xml.generator.ws"/&gt; &lt;parameter name="className" value="com.bpi.stmts.generacion.WSGenerator"/&gt; &lt;parameter name="extraClasses" value="com.bpi.stmts.generacion.vo.XMLRequestBase"/&gt; &lt;parameter name="allowedMethods" value="generateCurrentXML"/&gt; &lt;operation name="generateCurrentXML" qname="generateCurrentXML" returnQName="CurrentXMLResponse" returnType="rtns:XMLResponse" xmlns:rtns="urn:xml.generator.ws" soapAction="generateCurrentXML"&gt; &lt;parameter qname="CurrentXMLRequest" xmlns:pns="urn: xml.generator.ws" type="tns:CurrentXMLRequest" xmlns:tns="urn: xml.generator.ws"/&gt; &lt;/operat</pre> JOSE L MARTINEZ-AVIAL 2012-05-09T03:16:40 http://comments.gmane.org/gmane.text.xml.axis.user/82325 <pre>Hi, I am using Axis2 v 1.6 for invoking 3rd party WS calls. Things were fine but the new requirement is, I need to be making secured calls (Https) and the existing code throws the following exception. Can you please tell me how/what changes should be made or point me to the right resource? Caused AxisFault 05/07/2012 14:02:46 +1 NULL response from Web Service 05/07/2012 14:02:46 +1 getMessage --&gt; Connection has been shutdown: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Thanks for your help. Nandeesh </pre> Nandeesh Kaggere 2012-05-07T20:01:38 http://comments.gmane.org/gmane.text.xml.axis.user/82319 <pre>The Apache Axis2 team is pleased to announce the general availability of the following releases: - Axis2 1.6.2 - Sandesha2 1.6.2 - Rampart 1.6.2 Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in "modules" that extend its functionality for features such as security and reliability. Apache Rampart is an Axis2 module that implements the specifications in the WS-Security stack. Apache Sandesha2 provides WS-ReliableMessaging support for Axis2. Axis2 1.6.2 is a maintenance release that contains more than 45 fixes. Rampart 1.6.2 is a maintenance release containing number of bug fixes and compatible with the Axis2 1.6.2 release. Sandesha2 1.6.2 is a maintenance release that is compatible with the Axis2 1.6.2 release. The new versions are available for download at the following locations: http://axis.apache.or</pre> Sagara Gunathunga 2012-05-04T04:44:42 http://comments.gmane.org/gmane.text.xml.axis.user/82311 <pre>Hi, When is Rampart 1.6.2 released? I see Axis2 1.6.2 is released. I tried it will Rampart 1.6.3-snapshot but received an error. Rampart 1.6.1 doesn't work - see my earliest message. James Infoshare Ltd Millennium House 21 Eden Street Kingston upon Thames Surrey KT1 1BL United Kingdom Phone: + 44 (0) 20 8541 0111 Support:+ 44 (0) 20 8481 4760 Web:www.infoshare-is.com E-mail:info&lt; at &gt;infoshare-is.com Infoshare Ltd is registered in England and Wales. Registered Office as above. Registered Number 2877612 VAT Number GB 678 1443 10 The content of this e-mail (and any attachment to it) is confidential. Any views or opinions do not represent the views or opinions of Infoshare Ltd. If you have received this e-mail in error please notify the sender and delete it. You may not use, copy or disclose the information in any way. Infoshare Ltd monitors incoming and outgoing e-mails. Please consider the environment. Do you really need to print this email? </pre> James Annesley 2012-04-30T14:48:28 http://comments.gmane.org/gmane.text.xml.axis.user/82309 <pre>Can someone explain the purpose of wss10/wss11 assertions in a security policy? I thought their purpose was to express some kind of requirement. But my tests failed to confirm that. I am using a symmetric binding (with derived keys) and the only wss11 assertion I have found to be absolutely critical is sp:MustSupportRefEncryptedKey. Without this assertion, my web service requests will fail. On the other hand, my client is free to send requests with sp:RequireIssuerSerialReference even if my server policy specifies sp:Wss11/wsp:Policy/sp:MustSupportRefThumbprint. Thank you, </pre> Philippe A. 2012-04-27T14:53:37 http://comments.gmane.org/gmane.text.xml.axis.user/82303 <pre> Hello When would be the expected release of Axis2 1.7 ? Regards </pre> Ningashetty, Kumar * 2012-04-26T17:01:21 http://comments.gmane.org/gmane.text.xml.axis.user/82302 <pre>Say I have an operation receiving a long list of individual records via MTOM (cached). The entire file takes 30 seconds to be transferred. Does Axis force me to wait until the entire file is received before I can start processing records? </pre> Philippe A. 2012-04-26T15:49:22 http://comments.gmane.org/gmane.text.xml.axis.user/82299 <pre>Hi I'm trying to get my SOAP web service to run using mapped JSON instead of XML. Because it is not that obvious when moving to JSON, what works and what does not, I had to do some drilling down in to the code. I got a sample Service running based in an org.apache.axis2.receivers.RawXMLINOutMessageReceiver. But that's not the way to implement web services in these days. Basically, as AXIS is designed, we should be able to use databinding, as soon as we get the JSON stuff properly converted in to XML. This seams not to be the case at the moment (namespace mismatch) So i though about writing a wrapper around my generated skeleton and adding the correct namespaces myself, based on the prefixes used in the mapped JSON. Now it is where i get confused. In the documentation is mentioned to us a full stop "." to separate namespace-pefix from element name. http://axis.apache.org/axis2/java/core/docs/json_support.html When i look at the code, I see, that there a colon ":" is expected to separate the</pre> gerber< at >slf.ch 2012-04-26T12:59:04 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.text.xml.axis.user