Re: [Axis2] Correct location for third party lib(s)

[Deepal Jayasinghe]

yes , with third party lib can locate inside .Saar file and with them
that will be like as follows
  
few.Saar
   MATA-INF
 services.ml
  Borg
apache
 .
 lib
   my lib1.jar
   my lib2.jar

(http://www.developer.com/open/article.php/3557741)
 

Michael Robinson wrote:

> What is the correct location for third party libraries within an Axis
> 2 service? Should these be packaged within the .aar file?
>
>  
>
> I seem to remember reading this information somewhere in the
> documentation but was unable to find it today. If it does in fact
> exist could someone please point me in the correct direction?
>
> 
>
> *
> This e-mail and any files transmitted with it are intended solely
> for the use of the entity or individual(s) to whom they are
> addressed and not for reliance upon by unintended recipients. If
> you are not the intended recipient or the person responsible for
> delivering the e-mail to the intended recipient be advised that you
> have received this e-mail in error and that any use, dissemination,
> forwarding, printing, or copying of this e-mail and any files
> transmitted are strictly prohibited. If you have received this
> e-mail in error please delete the entire email and immediately
> notify us by email to the sender or by telephone to the AOC main
> office number, (404) 656-5171. Thank you.
> *
>

-- 
Thanks,
Deepal

~Future is Open~ 

Re: [Axis2] 0.95 complex types with proprietary MessageReceiver

[Ajith Ranabahu]

Hi,
Please see my answers inline

On 3/31/06, Sebastian J. Schultheiss <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> we would like to write a service that accepts and returns xs:complex-types. We
> tried to do so by hand, going from the Java class to an axis-generated WSDL, 
> but
> we always ended up with xs:any-types. So we now tried to define a WSDL and go
> from there, by using the WSDL2Java command line tool.
>
> Our input WSDL is attached as SVMHCServiceComplex.wsdl. We left the generated
> classes alone except for the PortSkeleton, where we implemented this simple
> business logic in the method indicated by the Todo comment:
>
> public axis2.apache.org.xsd.PredictEpitopesResponseDocument 
> predictEpitopes(
> axis2.apache.org.xsd.PredictEpitopesRequestDocument param0)
> throws Exception {
> try{
> PredictEpitopesResponseDocument ret =
> PredictEpitopesResponseDocument.Factory.newInstance();
> ret.getPredictEpitopesResponse().setBoolres(true);
> ret.getPredictEpitopesResponse().setFloatres((float)23.42);
> ret.getPredictEpitopesResponse().setStringres(allele + "\t" + 
> sequence);
> return ret;
> } catch(Exception e){
> //TODO fill this with the necessary business logic
> throw new java.lang.UnsupportedOperationException();
> }
> }

upto this point what you've done is correct.

> We also wrote a services.xml, wich is attached. Is there a way to 
> auto-generate
> a services.xml? Is ours correct?

Yes. use the -sd option with the codegenerator. Your services.xml
seems to be correct anyway
>
> When deployed as an AAR, Axis2 generates a WSDL that seems to be invalid, it 
> is
> attached as SVMHCServiceComplex_auto.wsdl.

We actually discovered this problem recently and unfortunately it is
not documented anywhere. The Axis2 WSDL generator generates the WSDL
without taking any notice of a generated message receiver and that
screws up the thing when there is a generated message receiver
What you can do is to include the WSDL file inside the META-INF folder
of the aar file. Then axis2 will pickup the correct WSDL

>We tried to use our generic Client
> which creates an OMElement that corresponds to the request specifications from
> our original WSDL.
>
> The communication however doesn't work, it gives us this as a response:
>
> org.apache.axis2.AxisFault: Transport error 500 . Error Message is
> Apache Tomcat/5.5.15 - Error report
> description The server encountered an internal error () that
> prevented it from fulfilling this request.exception
> javax.servlet.ServletException: Servlet execution threw an exception
> root cause java.lang.NoClassDefFoundError
> axis2.apache.org.xsd.PredictEpitopesRequestDocument$Factory.parse(PredictEpitopesRequestDocument.java:150)
> svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.fromOM(SVMHCServicePortMessageReceiverInOut.java:142)
> svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.invokeBusinessLogic(SVMHCServicePortMessageReceiverInOut.java:51)
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:408)
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:288)
> 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
>
> Can you give us some hints as how to create a service that accepts
> xs:complex-types? Is it ok to just overwrite the auto-generated WSDL with our
> original? Is it ok for the auto-generated one to look like this?
>
> Thanks a lot for your time,
>
> -- Sebi
>
>
>


--
Ajith Ranabahu

Re: ADB and Cardinality

[Ajith Ranabahu]

Hi Arnaud,
Seems like a bug in the code generator! I guess you should be reporting a Jira
(Appreciate if you can attach your schema also)

Ajith

On 3/31/06, Arnaud Blandin <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to use ADB in order to reduce the footprint of the generated
> code in AXIS2 and I am facing a problem with cardinalities:
> Roughly speaking, my WSDL defines a schema structure like:
>
>  maxOccurs="unbounded"/>
>  maxOccurs="unbounded"/>
>  maxOccurs="unbounded"/>
>
> The first problem (minor) comes from the generated code that doesn't
> compile:
>
> java.lang.String[] textArray = stateMachine1.getTextArray();
> object.setTo((java.lang.String[])
>
> org.apache.axis2.databinding.utils.ConverterUtil.convertToArray(
>  java.lang.String.class,stateMachine1.getTextArray()));
> // Move to a start element
> event = reader.getEventType();
> while (event!= javax.xml.stream.XMLStreamReader.START_ELEMENT) {
> event = reader.next();
> }
>
> org.apache.axis2.databinding.utils.SimpleArrayReaderStateMachine
> stateMachine2 = new
> org.apache.axis2.databinding.utils.SimpleArrayReaderStateMachine();
> stateMachine2.setElementNameToTest(new
> javax.xml.namespace.QName("http://www.example.com","B";));
> stateMachine2.read(reader);
> java.lang.String[] textArray = stateMachine2.getTextArray();
>
> ---> textArray is declared a second time and it is not used in the
> class.
>
> My second problem lies when I want to process like:
> foo
> bar
> bar
>
> The engine sends an IllegalState as it somehow assumes that a B will be
> there.
>
> Can you please let me know if I am missing something or if I encovered a
> bug?
> I am using AXIS2 0.95 release.
>
> Thanks,
>
> Arnaud
>


--
Ajith Ranabahu

Re: [Axis2] [AXIOM] Whre is the SVN?

[Ruchith Fernando]

Use:

https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/

Thanks,
Ruchith

On 4/1/06, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> The "Source Code" link on http://ws.apache.org/commons/axiom/index.html
> does not work :-(
>
> How can I get the latest svn co?
>
> Thanks,
> Samisa...
>

[Axis2] [AXIOM] Whre is the SVN?

[Samisa Abeysinghe]

The "Source Code" link on http://ws.apache.org/commons/axiom/index.html 
does not work :-(


How can I get the latest svn co?

Thanks,
Samisa...

unable to get soap header in Axis2

[Gopal Patwa]

Hi,

I have custom wsdl with just an echo service which contain soap header
as input for action but when I view my wsdl from browser it does not
show up the soap header part??

Any help ??, let me if anything wrong in wsdl it self

Thanks
Gopal

my wsdl file


http://org.apache.axis2/" xmlns:tns="http://org.apache.axis2/"

    xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" 
    xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
    
    
    
   
targetNamespace="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://www.w3.org/2001/XMLSchema">
   
http://schemas.xmlsoap.org/ws/2004/08/addressing"
   
schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing" />
    
    
    http://www.w3.org/2001/XMLSchema"

  
targetNamespace="http://org.apache.axis2/xsd">
  

   

   

   

    
  

   

   

   

    
   

   

    
    
    
    
    
    
    
    
  
  
    
  
  
  
    
  
  
    
  
  
    
    
    
    
    
    
    
    
    
    
    
  
    
  
    
    
  
    
  
    
    
    http://schemas.xmlsoap.org/soap/http" />
    
   

    
    
   


part="MessageID"

use="literal"/>
   


part="ReplyTo"

use="literal"/>
    
    
    
    
    
    http://schemas.xmlsoap.org/soap/http" />
    
   

    
    
   


part="RelatesTo"

use="literal"/>
    
    
    
    
    
    
   
http://localhost:8080/axis2/services/keystone"/>
    
  

  
    
 http://set.by.caller"/>    
     
  

problems for Axis 1.3

[Jordan Lee]

Hi,

We're having problems with the  tag using Axis 1.3.









Basically, we wanted to implmeent non-exclusive or. So  either value 1 and 
value 2 are present, or one of either, but not neither.

If we only set value2, then Axis complains about value 1 not being present. 

Has anyone ever seen something like this before?

thanks,
Jordan.

RE: Which Axis for WebLogic 9.1?

[Hendrik Schreiber]

Supposedly WebLogic 9.0/9.1 fully support J2EE 1.4. 

> -Original Message-
> From: Hendrik Schreiber [mailto:[EMAIL PROTECTED] 
> Sent: Friday, March 31, 2006 4:23 PM
> To: axis-user@ws.apache.org
> Cc: David Ingbretsen
> Subject: RE: Which Axis for WebLogic 9.1?
> 
> Lars,
> 
> Yeah - the problem is definitely similar, which is why I'd 
> like to find 'matching' versions. I.e. which version of Axis 
> does play well with WebLogic 9.1 - if there is one at all 
> that does that.
> 
> We compared filesizes etc and concluded that the 
> webservices.jar that ships with 9.1 is a different one than 
> the one shipping with 8.1. So the problem is similar, but not 
> the same.
> 
> -hendrik
> 
> > -Original Message-
> > From: Lars Torunski [mailto:[EMAIL PROTECTED]
> > Sent: Friday, March 31, 2006 4:19 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: Which Axis for WebLogic 9.1?
> > 
> > Maybe you have a similar problem compared to
> > http://ws.apache.org/axis/java/install.html#WebLogic8.1
> > 
> > WebLogic 8.1 ships with webservices.jar that conflicts with Axis' 
> > saaj.jar and prevents Axis 1.2 from working right out of 
> the box. This 
> > conflict exists because WebLogic uses an older definition of
> > javax.xml.soap.* package from Java Web Services Developer 
> Pack Version 
> > 1.0 ,
> > whereas Axis uses a newer revision from J2EE 1.4.
> > 
> > Hendrik Schreiber wrote:
> > >
> > > Hey,
> > >
> > > We are currently upgrading from WebLogic 8.1 to 9.1 and 
> one of the 
> > > things that stopped working is Axis 1.1.
> > >
> > > We are seeing the following NullPointerException in the 
> Call class:
> > >
> > > java.lang.NullPointerException
> > > at org.apache.axis.client.Call.invoke(Call.java:1768)
> > > at
> > > 
> > 
> com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReport
> > > Client.java:738)
> > >
> > > at
> > > 
> > 
> com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient
> > > .java:255)
> > >
> > > <...>
> > >
> > > Apparently this is linked to WebLogic prefering its own
> > saaj classes. 
> > > In fact when we prepend the saaj jar that comes with Axis
> > 1.1 to the
> > > WebLogic classpath, things work out. However, that is 
> unfortunately 
> > > not an option for us.
> > >
> > > So what I was wondering is the following:
> > >
> > > - Has anyone figured out what's the best way to get Axis 
> (preferably
> > > 1.1) to run with WebLogic 9.1?
> > > - Is there a version of Axis that works smoothly with 
> WebLogic 9.1?
> > > - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3?
> > >
> > > Thanks for your help!
> > >
> > > -hendrik
> > >
> > 
> > 
> > 
> 

RE: Which Axis for WebLogic 9.1?

[Hendrik Schreiber]

Lars,

Yeah - the problem is definitely similar, which is why I'd like to find
'matching' versions. I.e. which version of Axis does play well with
WebLogic 9.1 - if there is one at all that does that.

We compared filesizes etc and concluded that the webservices.jar that
ships with 9.1 is a different one than the one shipping with 8.1. So the
problem is similar, but not the same.

-hendrik

> -Original Message-
> From: Lars Torunski [mailto:[EMAIL PROTECTED] 
> Sent: Friday, March 31, 2006 4:19 PM
> To: axis-user@ws.apache.org
> Subject: Re: Which Axis for WebLogic 9.1?
> 
> Maybe you have a similar problem compared to
> http://ws.apache.org/axis/java/install.html#WebLogic8.1
> 
> WebLogic 8.1 ships with webservices.jar that conflicts with Axis' 
> saaj.jar and prevents Axis 1.2 from working right out of the 
> box. This conflict exists because WebLogic uses an older definition of
> javax.xml.soap.* package from Java Web Services Developer 
> Pack Version 1.0 
> ,
> whereas Axis uses a newer revision from J2EE 1.4.
> 
> Hendrik Schreiber wrote:
> >
> > Hey,
> >
> > We are currently upgrading from WebLogic 8.1 to 9.1 and one of the 
> > things that stopped working is Axis 1.1.
> >
> > We are seeing the following NullPointerException in the Call class:
> >
> > java.lang.NullPointerException
> > at org.apache.axis.client.Call.invoke(Call.java:1768)
> > at
> > 
> com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReport
> > Client.java:738)
> >
> > at
> > 
> com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient
> > .java:255)
> >
> > <...>
> >
> > Apparently this is linked to WebLogic prefering its own 
> saaj classes. 
> > In fact when we prepend the saaj jar that comes with Axis 
> 1.1 to the 
> > WebLogic classpath, things work out. However, that is unfortunately 
> > not an option for us.
> >
> > So what I was wondering is the following:
> >
> > - Has anyone figured out what's the best way to get Axis (preferably
> > 1.1) to run with WebLogic 9.1?
> > - Is there a version of Axis that works smoothly with WebLogic 9.1?
> > - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3?
> >
> > Thanks for your help!
> >
> > -hendrik
> >
> 
> 
> 

Re: Which Axis for WebLogic 9.1?

[Lars Torunski]

Maybe you have a similar problem compared to 
http://ws.apache.org/axis/java/install.html#WebLogic8.1


WebLogic 8.1 ships with webservices.jar that conflicts with Axis' 
saaj.jar and prevents Axis 1.2 from working right out of the box. This 
conflict exists because WebLogic uses an older definition of 
javax.xml.soap.* package from Java Web Services Developer Pack Version 
1.0 , 
whereas Axis uses a newer revision from J2EE 1.4.


Hendrik Schreiber wrote:


Hey,

We are currently upgrading from WebLogic 8.1 to 9.1 and one of the 
things that stopped working is Axis 1.1.


We are seeing the following NullPointerException in the Call class:

java.lang.NullPointerException
at org.apache.axis.client.Call.invoke(Call.java:1768)
at 
com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReportClient.java:738) 

at 
com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient.java:255) 


<...>

Apparently this is linked to WebLogic prefering its own saaj classes. 
In fact when we prepend the saaj jar that comes with Axis 1.1 to the 
WebLogic classpath, things work out. However, that is unfortunately 
not an option for us.


So what I was wondering is the following:

- Has anyone figured out what's the best way to get Axis (preferably 
1.1) to run with WebLogic 9.1?

- Is there a version of Axis that works smoothly with WebLogic 9.1?
- Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3?

Thanks for your help!

-hendrik

Which Axis for WebLogic 9.1?

[Hendrik Schreiber]

Title: Which Axis for WebLogic 9.1?






Hey,


We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1.


We are seeing the following NullPointerException in the Call class:


java.lang.NullPointerException

    at org.apache.axis.client.Call.invoke(Call.java:1768)

    at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReportClient.java:738)

    at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient.java:255)

<...>


Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us.

So what I was wondering is the following:


- Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1?

- Is there a version of Axis that works smoothly with WebLogic 9.1?

- Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3?


Thanks for your help!


-hendrik

[Axis2] Correct location for third party lib(s)

[Michael Robinson]

What is the correct location for third party libraries
within an Axis 2 service? Should these be packaged within the .aar file? 

 

I seem to remember reading this information somewhere in the
documentation but was unable to find it today. If it does in fact exist could
someone please point me in the correct direction? 










This e-mail and any files transmitted with it are intended solely
for the use of the entity or individual(s) to whom they are
addressed and not for reliance upon by unintended recipients.  If
you are not the intended recipient or the person responsible for
delivering the e-mail to the intended recipient be advised that you
have received this e-mail in error and that any use, dissemination,
forwarding, printing, or copying of this e-mail and any files
transmitted are strictly prohibited. If you have received this
e-mail in error please delete the entire email and immediately
notify us by email to the sender or by telephone to the AOC main
office number, (404) 656-5171. Thank you.

[ANN]Apache Axis2C 0.9 released

[Sahan Gamage]

Hi All,

We are proud to announce the release of Apache Axis2C version 0.90.
You can download this release from
http://ws.apache.org/axis2/c/download.cgi

Key Features

   1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages.
This has complete XML infoset support.
   2. Support for One-Way Messaging (In-Only) and Request Response
Messaging (In-Out)
   3. Module Architecture, mechanism to extend the SOAP Processing Model
   4. Content hierarchy
   5. Directory based deployment model
   6. Raw XML providers
   7. WS-Addressing, both the submission (2004/08) and final (2005/08) versions
   8. Transports supports: HTTP
  * Both simple axis server and Apache2 httpd module

Experimental Features

   1. WSDL Object Model support New
  * Dynamic invocation

Other notes

   1. Interoperability tested with Axis2/Java for XML in/out client and services
   2. Addressing interoperability on client side

Major changes since last release

   1. Minimal memory leaks
   2. Apache2 module working in Windows
   3. More samples and tests
   4. WSDL Object Model built based on the proposed WSDL 2.0 Component model.
   5. Dynamic Invocation
   6. Numerous bug fixes since last release

What is stii to do
   1.  Module version support
   2. Archive based deployment Model
   3. Improved and user friendly Client API
   4. Support for MTOM/ MIME/ SwA
   5. Sessions scoping for Application, SOAP, Transport and Request levels
   6. Service Groups
   7. Different character encoding support
   8.  WSDL Code Generation Tool for Stub and skeletons (based on Java tool)
   9. Security module
   10. REST (REpresentational State Transfer) Support
   11. Server side Web Service Policy support
   12. Axis2 Web Application (Web App)

We welcome your early feedback on this implementation.
Thanks for your interest in Axis2C

-- Apache Axis2C Team --

ADB and Cardinality

[Arnaud Blandin]

 
Hi,

I am trying to use ADB in order to reduce the footprint of the generated
code in AXIS2 and I am facing a problem with cardinalities:
Roughly speaking, my WSDL defines a schema structure like:





The first problem (minor) comes from the generated code that doesn't
compile:

java.lang.String[] textArray = stateMachine1.getTextArray();
object.setTo((java.lang.String[])
 
org.apache.axis2.databinding.utils.ConverterUtil.convertToArray(
 java.lang.String.class,stateMachine1.getTextArray()));
// Move to a start element
event = reader.getEventType();
while (event!= javax.xml.stream.XMLStreamReader.START_ELEMENT) {
event = reader.next();
}

org.apache.axis2.databinding.utils.SimpleArrayReaderStateMachine
stateMachine2 = new
org.apache.axis2.databinding.utils.SimpleArrayReaderStateMachine();
stateMachine2.setElementNameToTest(new
javax.xml.namespace.QName("http://www.example.com","B";));
stateMachine2.read(reader);
java.lang.String[] textArray = stateMachine2.getTextArray();

---> textArray is declared a second time and it is not used in the
class.

My second problem lies when I want to process like:
foo
bar
bar

The engine sends an IllegalState as it somehow assumes that a B will be
there.

Can you please let me know if I am missing something or if I encovered a
bug?
I am using AXIS2 0.95 release.

Thanks,

Arnaud

server not recognizing ws-security information

[Dalys Sebastian]

I had been trying to make wss4j work with Axis-0.95 for a week, but with no 
success. I
have been successfully running version of wss4j with Axis-0.93 though.

My server runs on Tomcat and has a secure service running. I have axis2.xml 
under
WEB-INF/conf and my services.xml of the secure service has been configured with 
the
InflowSecurity and OutflowSecurity parameters. (I had to specify actionMapping 
element as
well for every operation in my secureservice although this was not mentioned in 
security
sample that was provided with Axis-0.95, wonder why? I was getting 'operation 
not found'
without adding this element.)

My problem is, When I send a message from the client to the server, my server 
considers
it as a normal web service message and is not recognizing any of the security 
headers.
Nor is it getting the data enclosed in the client's message body. And it 
returns with a
normal web service response with no security headers.

At the client, I get the following exception: 
WSDoAllReceiver: Request do not contain security header

I thought it could be a certificate verification error by the server, but what 
confuses
me is that these certificates are all valid and successfully working with
Axis-0.93+wss4j.

I am attaching a copy of the request-response interaction which I obtained from 
tcpmon.

I appreciate any help on this.
Thanks,
Dalys
 

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
==
Listen Port: 8084
Target Host: localhost
Target Port: 8085
 Request 
POST /BWP/services/SecureBWPWebServices HTTP/1.1
User-Agent: Axis/2.0
SOAPAction: urn:getConfigFiles
Host: localhost:8084
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8

16b6
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"; 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
 soapenv:mustUnderstand="1">http://www.w3.org/2001/04/xmlenc#"; Id="EncKeyId-18623335">
http://www.w3.org/2001/04/xmlenc#rsa-1_5"; />
http://www.w3.org/2000/09/xmldsig#";>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier";
 
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";>H2Nh6UEp+NfVnuL6eDdoehHSis4=

TmLioiACvLKcBbOsPUVGFB/XMXKcWh7SjErULxfzS87Qj3c+8Oi4LpA6Gr9Q/MbTg6Te1HlmAltNKtu7VRC87zu/v6qqbNl6E5HU+q4Y33kh9xhozGeIwfMls2G73gj6WGl3rc21ttbf98aHmz291Mgs6V7PfaCK1Ey5uCJ3kEFfWsugZF3ZzvlwBJE58rFz7reK1GQ6SJUTt5ufRxcVdrMzYhyh71dv1cB/VtQonC2v2/rJkvTjffJlEgxMe4oVW3OSwsiz9wcXA9J/6dZzK1N0Qcjkkamai9afOuCx48rgDJf7+8vzo94OOHCJoye/vJb+8dEnSpT6pvEcn9Vyng==
http://www.w3.org/2000/09/xmldsig#"; Id="Signature-12241337">

http://www.w3.org/2001/10/xml-exc-c14n#"; 
/>
http://www.w3.org/2000/09/xmldsig#rsa-sha1"; />


http://www.w3.org/2001/10/xml-exc-c14n#"; />

http://www.w3.org/2000/09/xmldsig#sha1"; />
899QSGf4UAC0Y3A8XDDYj2mtJLY=



http://www.w3.org/2001/10/xml-exc-c14n#"; />

http://www.w3.org/2000/09/xmldsig#sha1"; />
TtUfg4/yNLS+5WaH9DDVfudC9sU=



http://www.w3.org/2001/10/xml-exc-c14n#"; />

http://www.w3.org/2000/09/xmldsig#sha1"; />
yNcto56xPordAVxf/S9O3s17CFk=



http://www.w3.org/2001/10/xml-exc-c14n#"; />

http://www.w3.org/2000/09/xmldsig#sha1"; />
zJbXo6uqCB4+J7+YXfQp68XMGto=



enrXfwhD1MS81wHeRNhI4FQk7y8hDnkSB5mFkYp4KslZPr+Py6/elxDpgG6dEuaCNDGDVJZ3TLta
HH7b8zLmFyTk+AaoQ4CxHZqR3VlWA08UIkDY+wwBb9aD+2u/mAcML9n4n6i1JVbMsPIUpWVsmRlJ
I9C0iksnsiAx+53ObnRmU4VQO3x2ZiNlcSnK/jOv+YsV4n177fPwfYyMbZRfmyJAkzGIZKCY008Q
tT2bskd8iSEJThtj7YF71ByqFgLOu42pr/PUcJPNLH9UgeRoby3m0Jn9V3LbG8+D7uAEUcERMNm7
PWZqVcvN2QQxo7VspOVh4CRnLg/4mUiZi4qV1w==


http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 wsu:Id="STRId-21509627">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier";
 
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";>athIQAw7HxbADXZGoX3TeY7V7a8=

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 
wsu:Id="Timestamp-6775863">2006-03-31T16:31:56.515Z2006-03-31T16:36:56.515Zhttp://www.w3.org/2005/08/addressing"; 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 
wsu:Id="id-30216319">http://localhost:8084/BWP/services/SecureBWPWebServiceshttp://www.w3.org/2005/08/addressing"; 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 
wsu:Id="id-16625677">http://www.w3.org/2005/08/addressing/anonymoushttp://www.w3.org/2005/08/addressing"; 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 wsu:Id="id-2831">urn:uuid:CFBBBDC75E4EA
 588F011438227153441http://www.w3.org/2005/08/addressing";>urn:getConfig

[Axis2] 0.95 complex types with proprietary MessageReceiver

[Sebastian J. Schultheiss]

Hi there,

we would like to write a service that accepts and returns xs:complex-types. We
tried to do so by hand, going from the Java class to an axis-generated WSDL, but
we always ended up with xs:any-types. So we now tried to define a WSDL and go
from there, by using the WSDL2Java command line tool.

Our input WSDL is attached as SVMHCServiceComplex.wsdl. We left the generated
classes alone except for the PortSkeleton, where we implemented this simple
business logic in the method indicated by the Todo comment:

public axis2.apache.org.xsd.PredictEpitopesResponseDocument predictEpitopes(
axis2.apache.org.xsd.PredictEpitopesRequestDocument param0)
throws Exception {
try{
PredictEpitopesResponseDocument ret =
PredictEpitopesResponseDocument.Factory.newInstance();
ret.getPredictEpitopesResponse().setBoolres(true);
ret.getPredictEpitopesResponse().setFloatres((float)23.42);
ret.getPredictEpitopesResponse().setStringres(allele + "\t" + 
sequence);
return ret;
} catch(Exception e){
//TODO fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
}

We also wrote a services.xml, wich is attached. Is there a way to auto-generate
a services.xml? Is ours correct?

When deployed as an AAR, Axis2 generates a WSDL that seems to be invalid, it is
attached as SVMHCServiceComplex_auto.wsdl. We tried to use our generic Client
which creates an OMElement that corresponds to the request specifications from
our original WSDL.

The communication however doesn't work, it gives us this as a response:

org.apache.axis2.AxisFault: Transport error 500 . Error Message is
Apache Tomcat/5.5.15 - Error report
description The server encountered an internal error () that
prevented it from fulfilling this request.exception
javax.servlet.ServletException: Servlet execution threw an exception
root cause java.lang.NoClassDefFoundError
axis2.apache.org.xsd.PredictEpitopesRequestDocument$Factory.parse(PredictEpitopesRequestDocument.java:150)
svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.fromOM(SVMHCServicePortMessageReceiverInOut.java:142)
svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.invokeBusinessLogic(SVMHCServicePortMessageReceiverInOut.java:51)
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:408)
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:288)
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


Can you give us some hints as how to create a service that accepts
xs:complex-types? Is it ok to just overwrite the auto-generated WSDL with our
original? Is it ok for the auto-generated one to look like this?

Thanks a lot for your time,

-- Sebi
http://org.apache.axis2/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:tns="http://org.apache.axis2/";
targetNamespace="http://org.apache.axis2/";>

http://www.w3.org/2001/XMLSchema";
xmlns:ns1="http://org.apache.axis2/xsd"; 
targetNamespace="http://org.apache.axis2/xsd";
elementFormDefault="unqualified" attributeFormDefault="unqualified">
































http://schemas.xmlsoap.org/soap/http"; 
style="document"/>



http://www.org.apache.axis2"/>


http://www.org.apache.axis2"/>





http://localhost/axis2/services/SVMHCService:localhost/axis2/services/SVMHCService";
/>



http://org.apache.axis2/xsd"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:tns="http://org.apache.axis2/"; 
targetNamespace="http://org.apache.axis2/";>http://www.w3.org/2001/XMLSchema"; 
xmlns:ns1="http://org.apache.axis2/xsd"; 
targetNamespace="http://org.apache.axis2/xsd"; elementFormDefault="unqualified" 
attributeFormDefault="unqualified">


































http://schemas.xmlsoap.org/soap/http"; style="document"

Re: [Axis2 0.95] NullpointerException invoking .NET webService

[Anne Thomas Manes]

Note that the response message uses SOAP encoding, and Axis 2 doesn't support SOAP encoding.AnneOn 3/31/06, Ajith Ranabahu <
[EMAIL PROTECTED]> wrote:Hmm..Seems the woodstox parser caused an error due to some encoding issue!
Could be the ISO encoding (ISO-8859-1) !On 3/31/06, Arnaud MERGEY <[EMAIL PROTECTED]> wrote:> Hi,> I'm writting a dynamic webservice invoker with Axis2. I'm testing .NET
> interroperability and Axis2 give me a nullpointerexception with a sample> .NET webservice parsing the response.> This is stack trace:> The 2 first lines show message is sent to the ..NET server and
> invokation response is received (I'have tried this web service with> SOAPUI and I'heve same response than second line), so> NullpointerException is throw when Axis2 parse the response.> This web service works perfectly with a dynamic axis based client. I'd
> prefered to base my implementation on Axis2 than Axis> An Idea ?> Thanks,> Arnaud>>> httpclient.wire.content - DEBUG - >> "> encoding='UTF-8'?>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">> />> xmlns="
http://lottoexchange.net/LottoDrawings">2006-11-05Alaska2005-11-05Test"
> httpclient.wire.content - DEBUG - << "> encoding="ISO-8859-1"?>> SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:xsd="
http://www.w3.org/2001/XMLSchema"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:SOAP-ENC="
http://schemas.xmlsoap.org/soap/encoding/"> xmlns:si="http://soapinterop.org/xsd">> xsi:type="xsd:string">

Re: [Axis2] Encoding Style

[Anne Thomas Manes]

Axis 2 does not [yet] support rpc/encoded.AnneOn 3/31/06, Arnaud MERGEY <[EMAIL PROTECTED]> wrote:
Eran Chinthaka a écrit :Hi,It wasn't my question I didn't need to change charset, I need to have
encodingStyle attribute for interoperability with GLU RPC web servicesArnaud> Arnaud MERGEY wrote:>>> Is it possible to use some Axis2 option to have encoding style attribute ?
> options.setProperty(MessageContext.CHARACTER_SET_ENCODING,> );>> -- Chinthaka>  Hi,>> I'have same problem,>
>>> I'have compared Axis 1.3 and Axis2 0.95 soap request generation (dynamic> invocation) Axis 1.3 (OK):>> > 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:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"> xmlns:ns1="x">DEFAIRE> href="" id="id0"
> soapenc:root="0"> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> xsi:type="xsd:int"> xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/">7 Axis2 (KO : org.apache.axis2.AxisFault
: this is a soap-encoded endpoint)>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">> />> xmlns="http://www.webmethods.com/wsdl/AnagramImpl/">DEFAIRE7
 Is it possible to use some Axis2 option to have encoding style attribute ? Arnaud>> Dharminder Singh>> Wed, 26 Feb 2003 12:26:41 -0800
>>> Hi all,>>> I have a question about the encoding style attribute. I'm using axis as> a client to a glue server and I'm setting the encoding style attribute on>> both the rpc element aswell as the body element in the request soap
> message. It seems that glue expects the encoding style attribute to be>> on the envelope or body elements. If the encoding style attribute is not> on this level glue throws a "this is a soap encoded endpoint" exception.
>>> I looked at the axis code specifically SOAPEnvelope.java and> SOAPBody.java and I see that attributes on the body element are never> serialized. Is this correct or am I doing >something wrong?
>>> I appreciate any help.>>> Thanks>> Dharminder Singh>

setTargetService() to external service

[Larry Tan]

Hi,
When i perform messageContext.setTargetService(), can i do it such that 
the
target service is another service in another Axis engine? E.g. external URL,
or another container etc.
Many thanks

Regards,
Larry Tan


-- 
The University of Stirling is a university established in Scotland by
charter at Stirling, FK9 4LA.  Privileged/Confidential Information may
be contained in this message.  If you are not the addressee indicated
in this message (or responsible for delivery of the message to such
person), you may not disclose, copy or deliver this message to anyone
and any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.  In such case, you should destroy this
message and kindly notify the sender by reply email.  Please advise
immediately if you or your employer do not consent to Internet email
for messages of this kind.

Re: [Axis2] Encoding Style

[Arnaud MERGEY]

Eran Chinthaka a écrit :

Hi,
It wasn't my question I didn't need to change charset, I need to have 
encodingStyle attribute for interoperability with GLU RPC web services


Arnaud

Arnaud MERGEY wrote:
  
 


Is it possible to use some Axis2 option to have encoding style attribute ?




options.setProperty(MessageContext.CHARACTER_SET_ENCODING,
);

-- Chinthaka
 Hi,

I'have same problem,



I'have compared Axis 1.3 and Axis2 0.95 soap request generation (dynamic 
invocation)




Axis 1.3 (OK):

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:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="x">DEFAIREhref="#id0"/>soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xsi:type="xsd:int" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>7




Axis2 (KO : org.apache.axis2.AxisFault: this is a soap-encoded endpoint)

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>xmlns="http://www.webmethods.com/wsdl/AnagramImpl/";>DEFAIRE7




Is it possible to use some Axis2 option to have encoding style attribute ?



Arnaud



  

Dharminder Singh
Wed, 26 Feb 2003 12:26:41 -0800



Hi all,


I have a question about the encoding style attribute. I'm using axis as 

a client to a glue server and I'm setting the encoding style attribute on
both the rpc element aswell as the body element in the request soap 

message. It seems that glue expects the encoding style attribute to be
on the envelope or body elements. If the encoding style attribute is not 

on this level glue throws a "this is a soap encoded endpoint" exception.

I looked at the axis code specifically SOAPEnvelope.java and 
SOAPBody.java and I see that attributes on the body element are never 
serialized. Is this correct or am I doing >something wrong?



I appreciate any help.



Thanks


Dharminder Singh
  

Re: [Axis2] Encoding Style

[Eran Chinthaka]

Arnaud MERGEY wrote:
>  
> 
> Is it possible to use some Axis2 option to have encoding style attribute ?


options.setProperty(MessageContext.CHARACTER_SET_ENCODING,
);

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

[Axis2 0.95] get WSDL Message Parts

[Arnaud MERGEY]

Hi,

With Axis2 WSDL parsing model (org.apache.wsdl classes), I can parse the 
wsdl file and get wsdl infos. But I can't find how to get message parts
(WSDL4J code: 
wsdlVersionWrapper.getDefinition().getPortType(portTypeQName).getOperation(operationName, 
null, null).getInput().getMessage().getParts())
Is it possible with org.apache.wsdl classes, I'd prefer don't mix WDSL4J 
and org.apache.wsdl classes.


Thanks,
Arnaud

Re: How to reproduce "WSDL2Java okay"+"uncompilable code generated"

[Ali Sadik Kumlali]

Hi,Eclipse Web Tools Platform (WTP)  comes with XSD and WSDL editors which are able to validate.For more information please visit http://www.eclipse.org/webtools/Regards,Ali Sadik KumlaliAnne Thomas Manes <[EMAIL PROTECTED]> wrote: There are other problems with this WSDL besides the wrong qnames in your message parts. (Note that they aren't unqualified because there is a default namespace (the wsdl namespace); but these elements are in the xsd1 namespace.)  When using RPC style, your message parts must reference types, not elements. To fix the WSDL, either change the style to "document" (and remove the namespace attributes from the  definitions) or change the message parts to reference types rather than elements. I disagree with you that wsdl2java should have a
 built-in WSDL validator and should be able to catch all WSDL errors. As a best practice, you should validate your WSDL before running wsdl2java. Many WSDL editors provide WSDL validators. I'm not aware of an open source WSDL validator, though. (Perhaps someone would like to volunteer to build one?) I do think that wsdl2java should generate an error when it encounters an unresolvable reference, though.  e.g.,"http://schemas.xmlsoap.org/wsdl/}echoStringParam is referenced but not defined"Anne On 3/30/06, Morten Mortensen <[EMAIL PROTECTED]> wrote: I can now directly provoke, what I said yesterday: WSDL2Java
 runningsmoothly, but the generated coded in an uncompilable state!To reproduce, take the "Axis2SampleDocLit.wsdl" from the 0.95distribution, make the error like I did in my own WSDL by removing the qualification from the message-elements like this (see the attachedfile; slightly modified variant of the original sample):Change e.g. -  <- remove "xsd1"- into - <- no "xsd1" Now the WSDL2Java runs without any errors, but the compilation failssince the code shown in my original message below
 is produced.I think, that there ought to be a negative test-case for WSDL2Java with this type of WSDL!It is very good, that given correct WSDL, then all is fine - but in reallife, we fiddle with WSDL for a long time, maybe do not get it right forthe first number of times and then it is important to have tools like WSDL2Java do some aggressive verification of the WSDL...Having to track down the cause of generated, uncompilable code is tootough.Developers - are you listening?Regards,Morten Sabroe Mortensen -Oprindelig meddelelse-Fra: Morten MortensenSendt: 29. marts 2006 17:38Til: axis-user@ws.apache.orgEmne: Mode "Document/literal" vs. "Document/literal wrapped" Hi allWith the 0.95 version, how come I can use WSDL2Java to generate*un-compilable* code?Apparently, when I write WSDL as "Document/literal wrapped",
 thegenerated "XXXReceiverInOut" has bad "toOM()", "fromOM()" and "toEnvelope()" (for an example, see the below "toOM()"-implementation;the parameter does not have the right type!).Why does this happen? What to do?Regards,Morten Sabroe Mortensen ---   ...private  org.apache.ws.commons.om.OMElementtoOM(org.apache.ws.commons.om.OMElement param){if (param instanceoforg.apache.axis2.databinding.ADBBean ){org.apache.ws.commons.om.impl.builder.StAXOMBuilder builder = neworg.apache.ws.commons.om.impl.builder.StAXOMBuilder(org.apache.ws.commons.om.OMAbstractFactory.getOMFactory(),param.getPullParser(
 org.apache.ws.commons.om.OMElement.MY_QNAME));org.apache.ws.commons.om.OMElementdocumentElement = builder.getDocumentElement();((org.apache.ws.commons.om.impl.OMNodeEx )documentElement).setParent(null); // remove the parent linkreturn
 documentElement;}else{   //todo finish this onece the bean serializer has the necessary methodsreturn null;}}   ...--- 
		New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

Re: [Axis2 0.95] NullpointerException invoking .NET webService

[Ajith Ranabahu]

Hmm..
Seems the woodstox parser caused an error due to some encoding issue!
Could be the ISO encoding (ISO-8859-1) !

On 3/31/06, Arnaud MERGEY <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm writting a dynamic webservice invoker with Axis2. I'm testing .NET
> interroperability and Axis2 give me a nullpointerexception with a sample
> .NET webservice parsing the response.
> This is stack trace:
> The 2 first lines show message is sent to the ..NET server and
> invokation response is received (I'have tried this web service with
> SOAPUI and I'heve same response than second line), so
> NullpointerException is throw when Axis2 parse the response.
> This web service works perfectly with a dynamic axis based client. I'd
> prefered to base my implementation on Axis2 than Axis
> An Idea ?
> Thanks,
> Arnaud
>
>
> httpclient.wire.content - DEBUG - >> " encoding='UTF-8'?> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> /> xmlns="http://lottoexchange.net/LottoDrawings";>2006-11-05Alaska2005-11-05Test"
> httpclient.wire.content - DEBUG - << " encoding="ISO-8859-1"?> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:si="http://soapinterop.org/xsd";> xsi:type="xsd:string">

Distinguish axis engine(s) in Tomcat

[Larry Tan]

Hi,
I'm new to Axis. I'll like to find out if i have 2 servlets (both 
extending
AxisServlet) deployed under same webapp, will there be 2 separate engines or
both of them sharing 1 Axis engine? Is there anyway of distinguishing them?
Another question: If i have a subclass of AxisServlet in a webapp and
AxisServlet in another webapp, it'll be 2 Axis Engine i suppose? Is there
anyway of letting them share 1 engine across different webapp?
The reason i asked is because I'm trying to get ActiveBPEL to work with
WSRF (deployed in Tomcat).

Thanks,
Larry Tan


-- 
The University of Stirling is a university established in Scotland by
charter at Stirling, FK9 4LA.  Privileged/Confidential Information may
be contained in this message.  If you are not the addressee indicated
in this message (or responsible for delivery of the message to such
person), you may not disclose, copy or deliver this message to anyone
and any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.  In such case, you should destroy this
message and kindly notify the sender by reply email.  Please advise
immediately if you or your employer do not consent to Internet email
for messages of this kind.

Encoding Style

[Arnaud MERGEY]

 Hi,
I'have same problem,

I'have compared Axis 1.3 and Axis2 0.95 soap request generation (dynamic 
invocation)


Axis 1.3 (OK):
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:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="x">DEFAIREhref="#id0"/>soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xsi:type="xsd:int" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>7


Axis2 (KO : org.apache.axis2.AxisFault: this is a soap-encoded endpoint)
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>xmlns="http://www.webmethods.com/wsdl/AnagramImpl/";>DEFAIRE7


Is it possible to use some Axis2 option to have encoding style attribute ?

Arnaud


Dharminder Singh
Wed, 26 Feb 2003 12:26:41 -0800



Hi all,


I have a question about the encoding style attribute. I'm using axis as 

a client to a glue server and I'm setting the encoding style attribute on
both the rpc element aswell as the body element in the request soap 

message. It seems that glue expects the encoding style attribute to be
on the envelope or body elements. If the encoding style attribute is not 

on this level glue throws a "this is a soap encoded endpoint" exception.

I looked at the axis code specifically SOAPEnvelope.java and 
SOAPBody.java and I see that attributes on the body element are never 
serialized. Is this correct or am I doing >something wrong?



I appreciate any help.



Thanks



Dharminder Singh

[Axis2 0.95] NullpointerException invoking .NET webService

[Arnaud MERGEY]

Hi,
I'm writting a dynamic webservice invoker with Axis2. I'm testing .NET 
interroperability and Axis2 give me a nullpointerexception with a sample 
.NET webservice parsing the response.

This is stack trace:
The 2 first lines show message is sent to the ..NET server and 
invokation response is received (I'have tried this web service with 
SOAPUI and I'heve same response than second line), so 
NullpointerException is throw when Axis2 parse the response.
This web service works perfectly with a dynamic axis based client. I'd 
prefered to base my implementation on Axis2 than Axis

An Idea ?
Thanks,
Arnaud


httpclient.wire.content - DEBUG - >> "encoding='UTF-8'?>xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>xmlns="http://lottoexchange.net/LottoDrawings";>2006-11-05Alaska2005-11-05Test"
httpclient.wire.content - DEBUG - << "encoding="ISO-8859-1"?>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";  
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";  
xmlns:xsd="http://www.w3.org/2001/XMLSchema";  
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";  
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";  
xmlns:si="http://soapinterop.org/xsd";>xsi:type="xsd:string">

in axis2?

[SOA Work]

One last question for axis2 and I got all the information I need ;-) 
Thank you all for the very important and interesting information you gave me 
the last weeks.

Is the  tag supported in axis2? Axis was the only framework I 
knew which supported the metadata information to be generated into the 
resulting wsdl. 
Is there a way to specifiy the information (f.e. by adding documentation tags 
to the entries in service.xml)?

thx a lot
Dominik
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192