gmane.text.xml.axis.user

Axis2 - Upgrading from 1.3 to 1.6.2

DeVice, Dana — 2012-05-25T17:19:55

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:
<groupId>org.apache.axis2</groupId>
<artifactId>axis2</artifactId>
<version>1.3</version>

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.

exception messages

Trenton D. Adams — 2012-05-24T16:46:39

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.

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
     <soapenv:Fault>
       <faultcode>soapenv:Server</faultcode>
       <faultstring>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
</faultstring>
       <detail>
         <ns:ExamRequestUpdateSQLException 
xmlns:ns="http://update.request.exam.athabascau.ca">
           <SQLException 
xmlns="http://update.request.exam.athabascau.ca" 
xmlns:ax29="http://rmi.java/xsd" xmlns:ax213="http://sql.java/xsd" 
xmlns:ax210="http://io.java/xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:type="ax213:SQLException">
             <ax213:SQLState xsi:nil="true"/>
             <ax213:errorCode>0</ax213:errorCode>
             <ax213:nextException xsi:nil="true"/>
           </SQLException>
         </ns:ExamRequestUpdateSQLException>
       </detail>
     </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

We get a stack trace like this...

ca.athabascau.exam.request.update.ExamRequestUpdateSQLExceptionException: ExamRequestUpdateSQLExceptionException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at 
ca.athabascau.exam.request.update.ExamRequestUpdateStub.update(ExamRequestUpdateStub.java:222)
at 
ca.athabascau.exam.request.transfer.cronjob.Main.updateRequest(Main.java:204)
at ca.athabascau.exam.request.transfer.cronjob.Main.main(Main.java:123)

Thanks.

Problem in generating client stub

Nandeesh Kaggere — 2012-05-23T13:53:45

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>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

Re: connecting AXIS 2 HANDLER with JDOM parser-Dissertation

Sagara Gunathunga — 2012-05-23T09:01:42

You may have to write a new Axis2 module to achieve your objective.
Handlers of a module execute before the service method also you can change
Handler execution order using module.xml file. This[1] help to you.

[1] - http://axis.apache.org/axis2/java/core/docs/modules.html

Thanks !

On Fri, May 18, 2012 at 4:17 AM, josephina <sifoula< at >hotmail.com> wrote:

(unknown)

Antonio Bocci — 2012-05-23T05:30:29

<p><a href="http://sabdekho.com/lastnews/28MarkMacdonald/">http://sabdekho.com/lastnews/28MarkMacdonald/</a></p>

RE: JDOM XPath does not work with Axis

2012-05-22T21:02:00

My application uses JDOM. I've asked the list hoping someone had the same problem and was more successful than me finding a solution. I suspect that at the problem is related to the way jaxen is loaded.

-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen< at >gmail.com] 
Sent: Tuesday, 22 May, 2012 15:41
To: java-user< at >axis.apache.org
Subject: Re: JDOM XPath does not work with Axis

Axis2 doesn't use JDOM, so it is not clear how your question is related to Axis2.

Andreas

On Tue, May 22, 2012 at 5:41 PM,  <aaron.stromas< at >rsa.com> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe< at >axis.apache.org
For additional commands, e-mail: java-user-help< at >axis.apache.org

Re: axis2 mtom attach document to response - help please

eric johnson — 2012-05-22T20:22:58

I am attempted to attach a binary file to my response and was hoping
to use mtom.  I am working with XMLBeans objects from generating code
via wsdl2java and using the
org.apache.axis2.receivers.AbstractInOutMessageReceiver implementation
that was generated.  Is this possible?

Now that I've found some more in depth examples for using SwA it looks
like I should avoid XMLBeans and should be using
org.apache.axis2.receivers.RawXMLINOutMessageReceiver so that I can
build and return an OMElement to my message receiver class.  Is that
correct?

On Tue, May 22, 2012 at 1:42 PM, Andreas Veithen
<andreas.veithen< at >gmail.com> wrote:

Re: axis2 mtom attach document to response - help please

Andreas Veithen — 2012-05-22T19:42:53

In that case you need to pass null as the OMNamespace when creating
the "document" element.


You need to provide a bit more information about exactly what you are
attempting to do.

Re: JDOM XPath does not work with Axis

Andreas Veithen — 2012-05-22T19:40:36

Axis2 doesn't use JDOM, so it is not clear how your question is
related to Axis2.

Andreas

On Tue, May 22, 2012 at 5:41 PM,  <aaron.stromas< at >rsa.com> wrote:

Re: axis2 mtom attach document to response - help please

eric johnson — 2012-05-22T16:36:48

Thanks - the elementFormDefault isn't declared and I believe the
default is unqualified.  I've played around quite a bit with those
arguments for creating the OMNamespace and am less certain that is the
cause of my error.

I'm not sure why I am not getting an attachment back from the call.
Is this even possible when working from the generated code in the
skeleton?  I have found no complete examples of anyone using mtom to
add an attachment to a response in this way.



On Tue, May 22, 2012 at 3:21 AM, Andreas Veithen
<andreas.veithen< at >gmail.com> wrote:

JDOM XPath does not work with Axis

2012-05-22T15:41:02

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

Re: axis2 mtom attach document to response - help please

Andreas Veithen — 2012-05-22T09:21:30

The answer depends on the elementFormDefault declared on the schema.

Andreas

On Mon, May 21, 2012 at 10:10 PM, eric johnson <ejjohnson< at >gmail.com> wrote:

[Axis2] Log of soap messages creates mutiple logs, instead of just one.

JOSE L MARTINEZ-AVIAL — 2012-05-22T03:01:12

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
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: 180.213.103.133:83
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "aa:query:Query_6_0"
Content-Length: 1878
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body>*** hidden
***</soapenv:Body></soapenv:Envelope>

On Axis2 I changed the line to:

log4j.logger.org.apache.axis2.transport.http=DEBUG

But now Axis2 is using a bunch of calls to the logger to show the HTTP
request and responses

590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,007 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,007 DEBUG
httpclient.wire.content  - <<
"</ns1:reasonDescription><ns1:statusCode>200</ns1:statusCode></ns1:statusHeader></ns1:queryReturn></ns1:queryResponse>"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "[\r]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "2"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "2"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "[\r]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,009 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "</soapenv:Body></soapenv:Envelope>"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\r]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "0"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\r]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\r]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.content  - << "[\n]"
590AEACBF7F76E6912414FD0ED1AB0187543A98B 2012-05-21 21:59:47,010 DEBUG
httpclient.wire.header  - << "[\r][\n]"


Is there any way to make it behave like it did with Axis1?

Thanks

axis2 mtom attach document to response - help please

eric johnson — 2012-05-21T20:10:35

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 here", "ns");
      OMElement documentElement = factory.createOMElement("document", omNs);
      OMText textData = factory.createOMText(documentDataHandler, true);

      documentElement.addChild(textData);

So what should I be using for the URI and prefix values?  (I realize
this is probably web services 101, but this is all new to me and a bit
overwhelming).

The document element is really part of a GetDocumentResponse type
defined in my wsdl as:
      <xs:element name="GetDocumentResponse"
type="tns:GetDocumentResponseType" />

      <xs:complexType name="GetDocumentResponseType">
        <xs:sequence>
          <xs:element name="mimeType" type="xs:string" minOccurs="1"
maxOccurs="1"/>
          <xs:element name="documentName" type="xs:string"
minOccurs="1" maxOccurs="1"/>
          <xs:element name="storageTimestamp" type="tns:sDateTime"
minOccurs="1" maxOccurs="1"/>
          <xs:element name="document" type="xs:base64Binary"
minOccurs="1" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>

should I use "tns:GetDocumentResponse" for the prefix when creating
the OMNamespace object?

Should I be using the soap:address from the wsdl:service/wsdl:port as the uri?

Is there anything besides the code example I need to do to complete
the addition of the attachment?

Thanks!

Eric

Re: Axis2-1.6.2 generated stubs fails to use module rampart

Asen — 2012-05-21T18:56:22

Solved:

1. I have set two system properties from my startup servlet.

System.setProperty(org.apache.axis2.Constants.AXIS2_CONF,
config.getServletContext().getRealPath("/WEB-INF/conf/axis2.xml"));
System.setProperty(org.apache.axis2.Constants.AXIS2_REPO,
config.getServletContext().getRealPath("/WEB-INF"));

2. added  <module ref="rampart"/> to axis2.xml and added the rampart
modules to the WEB-INF/modues dir of Tomcat.

3. I have created the configuration context only ones and have reused
it when creating a new client

MyStub stub = new MyStub(MyConfigFactory.getConfigCtx());

Is that sounds like the right way of doing it?




On Fri, May 18, 2012 at 1:53 PM, Kishanthan Thangarajah
<kshanth2101< at >gmail.com> wrote:

Re: AxisFault: An unknown transport called https exists when using asynchronous API

Christopher Legan — 2012-05-21T18:25:05

Nevermind.  I got it.

    <transportReceiver name="http"
                       class="org.apache.axis2.transport.http.AxisServletListener">
        <parameter name="port">8080</parameter>
    </transportReceiver>
    <transportReceiver name="https"
                       class="org.apache.axis2.transport.http.AxisServletListener">
        <parameter name="port">8443</parameter>
    </transportReceiver>


Christopher Legan
Sr Software Engineer | Lextech Global Services
christopher.legan< at >lextech.com
M. 815.630.7635

www.lextech.com | Apps for a Mobile Workforce
Twitter/LextechApps



On May 21, 2012, at 11:43 AM, Christopher Legan wrote:

AxisFault: An unknown transport called https exists when using asynchronous API

Christopher Legan — 2012-05-21T16:43:34

I create the Stub with useSeparateListener = true

I have these in axis2.xml, which is loaded into ConfigurationContext when creating the Stub.

    <transportSender name="http"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>

    <transportSender name="https"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>
    </transportSender>

When I call an operation with https endpoint, I get this:

org.apache.axis2.AxisFault: An unknown transport called https exists.
at org.apache.axis2.description.ClientUtils.inferInTransport(ClientUtils.java:118)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:183)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)

The synchronous calls do work OK.

What am I doing wrong?

Thanks,


Christopher Legan
Sr Software Engineer | Lextech Global Services
christopher.legan< at >lextech.com
M. 815.630.7635

www.lextech.com | Apps for a Mobile Workforce
Twitter/LextechApps

Re: hiding services

Sagara Gunathunga — 2012-05-21T11:36:25

On Sun, May 20, 2012 at 2:11 PM, Kishanthan Thangarajah <
kshanth2101< at >gmail.com> wrote:


 +1 If this doesn't make any issue for existing users.

Thanks !

Re: hiding services

Kishanthan Thangarajah — 2012-05-20T08:41:16

On Mon, Apr 30, 2012 at 4:06 PM, Sagara Gunathunga <
sagara.gunathunga< at >gmail.com> wrote:


How about extending current use of "hiddenService" parameter to handle
this.? So that if the parameter is set true, then the service will not be
listed in the services list, but it will be active.

Thanks,
Kishanthan.

Re: Axis2-1.6.2 generated stubs fails to use module rampart

Kishanthan Thangarajah — 2012-05-18T18:53:23


Can you give us some more info on how you configured rampart on client
side?. Some code section from your client would be better. Just to be
sure, check whether rampart and other third party libraries are in the
client class path. Also when creating the ConfigurationContext from file
system using a repository, please make sure that you have given the correct
location and also the rampart module (rampart.mar) is placed under modules
directory.

Thanks,
Kishanthan.

Re: axis2 - file cache for attachments - file name?

Andreas Veithen — 2012-05-17T22:47:44

The DataSource stored in the DataHandler that represents the
attachment is actually a FileDataSource instance and you can get the
name of the file from there. However, the fact that Axiom leaks the
file name is actually a design flaw and this will no longer be
supported in future Axis2/Axiom versions (but there will then likely
be a well defined API to convert an attachment to a file). For more
information see [1].

Andreas

[1] http://ws.apache.org/axiom/devguide/ch03.html

On Fri, May 18, 2012 at 12:21 AM, eric johnson <ejjohnson< at >gmail.com> wrote: