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

(unknown)

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

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

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

[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

connecting AXIS 2 HANDLER with JDOM parser-Dissertation

josephina — 2012-05-17T22:47:16

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

axis2 - file cache for attachments - file name?

eric johnson — 2012-05-17T22:21:21

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

Bug #AXIS2-4445; Workaround?

Oliver Heard — 2012-05-11T09:59:54

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

Axis2-1.6.2 generated stubs fails to use module rampart

Asen — 2012-05-10T16:34:30

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 is not
specified it seems that fails to find the deployed modules in
WEB-INF/modules
In other words I am receiving a AxisConfiguration without any modules.

What I am doing wrong here?
I had not have the issue with Axis-1.5 since there it was using a
Listener instead of MessageContext.getCurrentMessageContext()

My axis2.xml is the same as it comes from the distribution, but with
added two more globally engaged modules.

<module ref="addressing"/>
    <module ref="soapmonitor" />
    <module ref="rampart"/>

private void configureServiceClient(ConfigurationContext
configContext, AxisService axisService)
            throws AxisFault {
        if (configContext == null) {
            if (MessageContext.getCurrentMessageContext() == null) {
                configContext = ConfigurationContextFactory.
                        createConfigurationContextFromFileSystem(null, null);
                createConfigCtx = true;
            } else {
                configContext =
MessageContext.getCurrentMessageContext().getConfigurationContext();
            }
        }
        this.configContext = configContext;
        hashCode = (int)anonServiceCounter.incrementAndGet();

        // Initialize transports
        ListenerManager transportManager = configContext.getListenerManager();
        if (transportManager == null) {
            transportManager = new ListenerManager();
            transportManager.init(this.configContext);
        }

        // save the axisConfig and service
        axisConfig = configContext.getAxisConfiguration();

        if (axisService == null) {
            axisService = createAnonymousService();
        }

Any news regarding the AXIS2-5290 issue ?

COURTAULT Francois — 2012-05-10T09:43:08

Hello,

Could somebody provide me please some feedbacks regarding the AXIS2-5290<https://issues.apache.org/jira/browse/AXIS2-5290> issue ?

Best Regards.

Axis2 1.5.3 - WSDL2Java client stub - dealing with fault data outside of Detail element

2012-05-10T07:43:55

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:

<s:Body>
  <s:Fault>
 <s:Code>
<s:Value>s:Sender</s:Value>
 </s:Code>
 <s:Reason>
<s:Text xml:lang="en-AU">The RegistrationEndDateTime has an invalid
datetime format. Check that it does not specify timezone information or
have more than seconds precision.</s:Text>
 </s:Reason>
 <s:Detail>
<InvalidDateTimeFormatFaultDetail xmlns="http://schemas.xyz/faults"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
   <ErrorNumber>50016</ErrorNumber>

<ErrorReferenceId>7f2f1085-9c7e-44a8-b1b7-2a995d0a4e0f</ErrorReferenceId>
   <RequestProcessedByEnvironment>Discovery</RequestProcessedByEnvironment>
   <ElementName>RegistrationEndDateTime</ElementName>
</InvalidDateTimeFormatFaultDetail>
 </s:Detail>
  </s:Fault>
</s:Body>

The InvalidDateTimeFormatFaultDetail is what is defined in the WSDL/XSD.
 Axis2 only generates this detail bit as the exception - the rest is
abandoned.  I therefore don't have access to the other soap fault fields,
such as Code and Reason.

I had a look at the stub, and can see where it catches an AxisFault, pulls
out its Detail element, matches it up with one of the defined exceptions
from the WSDL, and populates and throws an instance of the WSDL exception
with the details from the Detail element.

Is there any way to work-around this so I can get access to the Reason
data?

One thing I did try was generating the stub with a different exception base
class (using -ebc) of org.apache.axis2.AxisFault. This actually ends up
providing the info I need, mainly because in the stub it gets an
instantiation exception when trying to instantiate the WSDL exception and
cast it to java.lang.Exception.  The stub then throws the original
AxisFault.  This provides me all the data I want, but it seems kind of
wrong to do it this way (i.e. getting the data through the fact the stub
can't process the exception properly :-) ).  Thoughts anyone?

Thanks heaps
Matt

[axis1 servers vs axis2 client] no such operation exception received until WSDL is seen

JOSE L MARTINEZ-AVIAL — 2012-05-09T03:16:40

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:

    <service name="ValuationsXMLGenerator" provider="java:RPC"
style="document" use="literal">
        <parameter name="wsdlTargetNamespace" value="urn:xml.generator.ws"/>
        <parameter name="schemaUnqualified" value="urn:xml.generator.ws"/>

        <parameter name="className"
value="com.bpi.stmts.generacion.WSGenerator"/>
        <parameter name="extraClasses"
value="com.bpi.stmts.generacion.vo.XMLRequestBase"/>
        <parameter name="allowedMethods" value="generateCurrentXML"/>


        <operation name="generateCurrentXML" qname="generateCurrentXML"
returnQName="CurrentXMLResponse" returnType="rtns:XMLResponse"
xmlns:rtns="urn:xml.generator.ws" soapAction="generateCurrentXML">
            <parameter qname="CurrentXMLRequest" xmlns:pns="urn:
xml.generator.ws" type="tns:CurrentXMLRequest" xmlns:tns="urn:
xml.generator.ws"/>
        </operation>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:XMLRequestBase"
        type="java:com.bpi.stmts.generacion.vo.XMLRequestBase"/>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:XMLResponse"
        type="java:com.bpi.stmts.generacion.vo.XMLResponse"/>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:CurrentXMLRequest"
        type="java:com.bpi.stmts.generacion.vo.CurrentXMLRequest"/>

    </service>

The Axis2 client is created using the WSDL generated by Axis1 online. The
issue we have found is that when the server is restarted, the service
answers to any request to execute the method generateCurrentXML with a No
Such Operation exception, as follows:

<soapenv:Fault>
<faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Client</faultcode>
<faultstring>No such operation 'CurrentXMLRequest'</faultstring>
<detail>
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/
">myserver</ns2:hostname>
</detail>
</soapenv:Fault>

This happens until someone queries the URL
http://myserver/myapp/services/ValuationsXMLGenerator?wsdl. Then all the
request go through, and they are answered correctly. Has anyone see this
behavior before? if so, is there any way to fix it?

thanks

Axis1.6 -- making Https calls

Nandeesh Kaggere — 2012-05-07T20:01:38

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

[ANN] Release of Axis2 1.6.2, Sandesha2 1.6.2 and Rampart 1.6.2

Sagara Gunathunga — 2012-05-04T04:44:42

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.org/axis2/java/core/download.cgi
http://axis.apache.org/axis2/java/rampart/download/1.6.2/download.cgi
http://axis.apache.org/axis2/java/sandesha/download.cgi

As always, we welcome any and all feedback at:

java-dev< at >axis.apache.org - for developer-related questions/concerns
java-user< at >axis.apache.org - for general questions, usage, etc.


NOTE  - Axis2 1.6.2 compatible with Axis2 Transports 1.0.0 version.


Thanks for your interest in Apache Axis2!

[Rampart] 1.6.2

James Annesley — 2012-04-30T14:48:28

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

Role of wss10 and wss11 assertions

Philippe A. — 2012-04-27T14:53:37

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,

Release date Axis2 1.7 ?

Ningashetty, Kumar * — 2012-04-26T17:01:21

Hello
    When would be the expected release of Axis2 1.7 ?

Regards

MTOM attachment handling question

Philippe A. — 2012-04-26T15:49:22

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?

Axis2 - JSON mapped - namespace (mismatch)

2012-04-26T12:59:04

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 prefix from the element name.
        See org.apache.axis2.json.AbstractJSONOMBuilder line 116 to 143

When I use a full stop "." I get an error, that the method is not found 
(Axis is looking for the howl thing, prefix and element name)
When I use a colon ":" I get the an error in the data binding (this is ok, 
 because of the mismatching namespace issue and when i get the prefixed 
matched to the correct namespaces this should be solved.)

Before I try to work around the mismatching namespace issue I really would 
like to know, 
how this is supposed to work with prefix, how prefix and element-name are 
separated, what prefixes are used for and what axis does with them.

Thanks for your help and best regards
Matthias