Re: Axis2 generated wsdl soap address is 0.0.0.0

[Sanka Samaranayke]

Hi Daniel, 

Can you please check whether the IP of the machine on which you experiencing the problem is being set properly? 
I think the problem must be that the IP of the network interface of that particular machine has been set to 0.0.0.0 where it is being picked by Axis2 WSDL generating mechanism when calculating service endpoint addresses.


--Sanka


Daniel Herbison wrote:
Hi All! 
I have a web service deployed on one machine under axis2 and i'm calling it

using flex and everything is working great.  However when I place the
service on another machine under axis2 i can no longer run the services from
flex but they do run fine from the browser.  Flex is complaining about the
soap:address being set to 0.0.0.0, see below.  Why is the WSDL being set to
0.0.0.0 on one machine and on the other machine it is being set to the
correct ip 

-  
- binding="axis2:IEventServiceSOAP11Binding"> 
  http://0.0.0.0:8086/axis2/services/IEventService";
/> 
   
- binding="axis2:IEventServiceSOAP12Binding"> 
  location="http://0.0.0.0:8086/axis2/services/IEventService"; /> 
   
- binding="axis2:IEventServiceHttpBinding"> 
  http://0.0.0.0:8086/axis2/services/IEventService";
/> 
   
  
  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Why Axis 1.4 over 1.2.1?

[Abhishek Shadangi]

Thanks a lot Jeff!

Thats really helps. I cannot move on to 2.x right now due to lot of
dependencies we have in our product. Thats will be a major refactoring on
our part.

Abhishek

On 10/29/07, Walker, Jeff <[EMAIL PROTECTED]> wrote:
>
>  Your going from an extremely old version of Axis to just a very old
> version. (by the way, I don't think either are supported anymore).
> Most people on this users list have moved to Axis2.x.
>
> But, to answer your question, when you downloaded Axis1.4 you will find a
> file called release-notes.html. Here it is below. Take a look.
> -jeff
>
>  Axis Change Log Axis 1.4 Changes from 1.3 finalMany bugfixes, including:
>
>- Prevented an NPE when curMsg is null
>- Fixed memory leaks
>- Fixed incorrect serialization of extended types in arrays
>- Fixed garbage collection for TypeDesc mappings
>- Fixed a problem with exception deserialization
>- Updated outdated version numbers in documentation
>- Fixed an issue that caused non-Sun JVMs to generate a
>CurrentModificationException
>- Fixed a problem with wsdl2java-generated class constructors
>
> Axis 1.3 Changes from 1.2.1 final
>
>- Support Axis inside Applets
>- Upgrade versions of dependency jars
>- Updated xmlbeans serializer/deserializer
>- Fixes for SAAJ
>- Fixes for Code Generation
>- Fixes for tools
>- Fixes for Runtime
>- Fixes for Performance
>- Fixes for various attachments problems
>- Fixes for Memory Leaks
>- Cleanup support for JavaBeans with array-type properties
>- Extract attachment streams directly from http request (w/o
>intermediate files)
>- GC Fixes for long standing servers (Geronimo)
>- Preliminary support for MTOM
>
> Axis 1.2.1 Changes from 1.2final
>
>- Cleanup array handling for rpc/lit and doc/lit
>- Enhancements to HTTPSender/CommonsHTTPSender (including better
>cookie support)
>- Generate array of wrappers for soapenc array nillable elements
>- Better handling of elementFormDefault during dynamic wsdl
>generation
>- Fix for gracefully handling IncompatibleClassChangeError in
>websphere/weblogic
>- Better SAAJ support (dirty flag was not set leading to
>serialization problems)
>- Fix out-of-memory errors for services without attachments
>returning large response messages
>- Last but not the least more test cases...
>
> Changes from 1.2rc3
>
>- Tons of changes to typemapping system to better support jax-rpc1.1and 
> .NET
>- Improved SAAJ 1.2 support
>- Much better for rpc/lit and doc/lit (especially for arrays)
>- Map schema "wrapped" arrays (with inner  elements) into
>arrays of the item type, instead of JavaBeans, by default. Introduce the
>"-w" or "--wrapArrays" option to WSDL2Java to switch back to the earlier
>behavior.
>- Fix some WS-I related bugs. Makes it easier to deploy WS-I BP
>compatible services.
>- Internationalized happyaxis jsp pages.
>- Updated to latest dependency jars. (ex wsdl4j-1.5.1.jar)
>- Improved commons httpclient support.
>- Support for sending and receiving multiple cookies
>- Lots of fixes for performance enhancements (including eliminating
>ThreadLocal's)
>- Improved JMX support - Start/Stop server/services and
>deploy/modify services
>
> Changes from 1.2beta2
>
>- When generating WSDL, don't change the scoping rules for type
>mappings. In other words, use the most specific mappings just like we do 
> for
>message processing.
>- Fix problem with version string
>- Remove JAXP interfaces (should come from jaxp.jar, not jaxrpc.jar)
>
>
> Changes from 1.1
>
>- Preliminary SAAJ 1.2 support!
>- Improved doc/literal support
>- Improved handling of array types + WSDL generation
>- More logical type mapping registration (SOAP-ENC types are in a
>separate registry which then delegates to the default one)
>- Improved schema support (we deal with lists and groups now)
>- ServiceDesc metadata is now more generic - ServiceDesc is an
>interface and JavaServiceDesc implements it to do specific Java processing.
>- Throw fault when bad values for "mustUnderstand" attribute are
>parsed
>- log4j.properties is no longer in axis.jar. This is to avoid
>conflicts with the configuration files in other bits of the application.
>- Many bugfixes. See docs/svnlog.txt
>
> Axis 1.1 Changes from 1.0 to 1.1 that may break your code
>
>- We have changed how we map http URLs to packages, such that any
>directories in the URL are used as well as the hostname. The previous
>behavior was a defect, as it would import WSDL from the same site into the
>same place. If you do not explicitly state the mappings of URIs to 
> packages,
>things may now end up in different places
>- The default socket timeout for clients is now 60 seconds, not
>infinity. You can use the setTimeout() option on any bindi

Help for WS-Addressing on RPC Client

[Regivaldo Gomes Costa]

Friends,

I need the next help: 

I have a service that has a method that effectuates a like client call and the 
presents the below mistake:

"org.apache.axis2.AxisFault: The server failed to process the WS-Addressing 
header: wsa:Action [Reason]: A header representing a Message Addressing 
Property is not valid and the message cannot be processed"

My client (also it is a axis service) code uses RPC:

private static String ReqIDs(String reqXMLStr) throws AxisFault{
String respCred = null;
try {
RPCServiceClient serviceClient = new RPCServiceClient();
Options options = new Options();
options = serviceClient.getOptions();
EndpointReference targetEPR = new 
EndpointReference("http://localhost:80/axis2/services/VMService";);
options.setTo(targetEPR);

// Access reqCredential methode for VMService Axis2 Service
QName ReqBallot = new QName("http://ses/vm/xsd";, "ReqBallotIDs");
Object[] sendParameters = new Object[] {reqXMLStr};
Class[] respType = new Class[] { String.class };
Object[] respService = serviceClient.invokeBlocking(ReqBallot, 
sendParameters, respType);
respCred = (String) respService[0]; // Credential receive
}

How I can resolve the problem?

Thank you.
 
Regivaldo Costa


  Abra sua conta no Yahoo! Mail, o único sem limite de espaço para 
armazenamento!
http://br.mail.yahoo.com/

Problem regarding serialization in axis

[Sudhir Sharma]

Hi All,

 

I am new to web services and axis. I have a java client that accesses a .NET
webservice. My problem is that I have to submit a XML file to the
webservices using serialization and deserialization. i have the equivalent
C# code for that. I think there is something in axis for that but don't know
what and where. Can anyone help me out.

Any help will be appreciated. 

 

 

Thanks & Best Regards,

Sudhir Sharma

 

Re: AXIS 2.0 OpenJMS

[Upul Godage]

http://ws.apache.org/axis2/1_3/jms-transport.html

Hope this helps.

Upul

On 10/30/07, Saket Raizada <[EMAIL PROTECTED]> wrote:
>
> I have a HTTP client for a WebService and I want to create JMS based
> clients for it.
> Does anyone have inputs on developing a JMS based program using AXIS 2.0
> and OpenJMS.
> Any pointers/tutorials etc are appreciated.
>
> regards
> -machoq
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Problems with Schemas and WSDL in Axis2 (Fixed)

[Lahiru Sandakith]

On 10/27/07, Matthew Fadoul <[EMAIL PROTECTED]> wrote:
>
>  Hello all,
>
>
>
> Thank you for the help.  A couple comments on the solution:
>
>
>
> 1) Although the wsdl2java converter placed my schema in the resources
> directory, the Axis2 Service Archiver did not add the schema into the
> archive web service file (*.aar).  I resorted to manually copying the schema
> into the AAR file (the AAR file is just a ZIP file) each time I ran the
> archiver wizard.
>

If adding  another option in the custom wsdl attachment page of the service
archiver wizard (
http://ws.apache.org/axis2/tools/1_3/eclipse/servicearchiver-plugin.html)
to add related schemas ad a list to add it to the service will solve the
problem, I ll add that feature. You can request a feature improvement in
https://issues.apache.org/jira/browse/AXIS2/component/12310180
thanks
Lahiru

2) I played around with the various schemaLocation and namespace attributes
> in my WSDL, but I don't know if this caused any problems in the end.
>  Despite its appearance, the simple namespace "HW" is a valid URI; it's just
> a relative one, not absolute.
>
>
>
> Regards,
>
>
>
> Matt
>
>
>  --
>
> *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED]
> *Sent:* Friday, October 19, 2007 4:57 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Problems with Schemas and WSDL in Axis2
>
>
>
> Can you have a look at with a nighly build.
>
> when generating the code with wsdl2java there is a folder created named as
> resources.
>
> under this folder you should have your wsdl and xsd file.
>
> wsdl file should referto the xsd file there.
>
> i.e it should have and entry like
>
> 
>
> Amila.
>
> On 10/19/07, *Matthew Fadoul* <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
>
>
> I'm having trouble using my own schemas in WSDL.  Part of it may be
> related to the Axis2 code generation.
>
>
>
> So, I've made my own "HelloWorld" example.  Here's my process:
>
>
>
> 1) Make WSDL file (attached)
>
> 2) Process with Axis2 code generation to build client/server code.  Fill
> in a little of the skeleton code.
>
> 3) Build inside Eclipse using Ant
>
> 4) Package with the Axis2 Service Archiver.
>
>
>
> I've attached my WSDL and Schema.  The schema has little more than a type
> definition based on "xs:string".
>
>
>
> I've placed my XSD file on a local server.  This is reflected in the
> attached WSDL here:
>
>
>
> < xs:import namespace="* HW*" 
> schemaLocation="*http://strawberry/schema/HelloWorldSimple.xsd
> *" />
>
>
>
> By the time the service gets placed on the Axis server, the reference to
> the schema in "HelloWorldExternalSchemaService?wsdl" becomes:
>
>
>
> < xs:import namespace="* HW*" 
> schemaLocation="*HelloWorldExternalSchemaService?xsd=
> http://strawberry/schema/HelloWorldSimple.xsd*"; />
>
>
>
> Unfortunately, Axis can't seem to resolve my schema with the "xsd"
> option.  Because of this, the schema and all of its types are unresolved.
>
>
>
> As a side note, I've also toyed with locale schema (i.e. the XSD file is
> in the same directory as the WSDL file), though I haven't had much success
> with that route either.
>
>
>
> Questions.  Are there:
>
> Any ideas or advice for integrating schemas with WSDL?
>
> Any ideas why the code generator is changing the schema location?
>
> Any glaring mistakes (e.g. namespace problems or DOC/RPC stuff) in my
> WSDL/XSD?
>
>
>
>
>
> Thank you!
>
>
>
> Matt
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>



-- 
Thanks
Lahiru Sandakith

http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC  1AB1 FE5E 7464 1F01 9A0F

[ANN] Apache Rampart training

[Ruchith Fernando]

HI Folks,

I will be in San Jose on the 1st November and will be conducting a
training session on Apache Rampart[1]. Anyone interested? Register
here [2].

Also I'll be in Indianapolis for a week (10-17 Nov) if anybody's
interested we should be able to provide similar training there as
well. Those interested please contact me.

Thanks,
Ruchith

1. http://wso2.com/services/training/intro-apache-rampart/
2. http://wso2.com/services/training/

-- 
http://blog.ruchith.org
http://wso2.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Application Communication

[Hoda, Nadeem [USA]]

 
All, 
 
I apologize if there is a very easy answer for this, but what are some
of the recommended ways to communicate to an existing POJO or Spring
based system, i.e., since Axis2.war is self contained, how do you
communicate, in the easiest way, to the business layer of an enterprise
system, e.g: 
 
In the same app server: 
 
MyEnterpriseApp.ear
Axis2.war, which contains MyEnterpriseAppWebServices.aar
 
How does MyEnterpriseAppWebServices.aar communicate with
MyEnterpriseApp.ear?
 
Thanks, 
 
Nadeem

Re: wsdl2java complexType element

[Anne Thomas Manes]

You need to namespace-qualify the type references in these two element
declarations:

   

   

i.e., define a namespace declaration for your targetNamespace and use
that namespace to qualify these types.

Anne

On 10/25/07, axelspin <[EMAIL PROTECTED]> wrote:
>
> I have this kind of schema
>
> 
>
> 
>
>  nillable="true" 
> type="xs:string"
> minOccurs="0" maxOccurs="1" />
>  nillable="true" 
> type="xs:dateTime"
> minOccurs="0" maxOccurs="1" />
>  nillable="true" 
> type="xs:dateTime"
> minOccurs="0" maxOccurs="1" />
>  type="xs:string" 
> minOccurs="0" maxOccurs="1" />
>
>
> 
> 
>
> 
> 
>  base="ns:RDFResourceRequest">
> 
>  name="type"
> 
> nillable="true" type="xs:string"
> minOccurs="0" 
> maxOccurs="1" />
>  name="upperLat"
> 
> nillable="true" type="xs:string"
> minOccurs="0" 
> maxOccurs="1" />
>  name="upperLon"
> 
> nillable="true" type="xs:string"
> minOccurs="0" 
> maxOccurs="1" />
>  name="lowerLat"
> 
> nillable="true" type="xs:string"
> minOccurs="0" 
> maxOccurs="1" />
>  name="lowerLon"
> 
> nillable="true" type="xs:string"
> minOccurs="0" 
> maxOccurs="1" />
> 
> 
> 
> 
>
>
>
>
>
> 
> 
>  base="RDFResourceRequest">
> 
>  
> name="superclass_uri" nillable="true"
> 
> type="xs:string" minOccurs="0"
> maxOccurs="1" 
> />
>
> 
> 
> 
> 
>
>  type="fullInstancesRequest" />
>
>
>  type="fullClassesRequest"/>
>
>
> wsdl2java fails telling me that:
> No type was mapped to the name instance with namespace urn:neries:orfeus:ws
>
> if I add the right prefix in the type attrubutes. es
>   type="ns:fullClassesRequest"/>
>
> I get
> string value 'ns:fullClassesRequest' does not match pattern for xs:NCName
>
> Some hints? can I define complexTypes stand alone elements?
> --
> View this message in context: 
> http://www.nabble.com/wsdl2java-complexType-element-tf4690839.html#a13406683
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: FW: Axis2 WSDL2Java error during service skeliton/stub generation

[Anne Thomas Manes]

You have a type defined in the schema:



As the message says, it has no type defined. You need to specify its
schema type.

Anne

On 10/26/07, Kiran Kumar Sriram <[EMAIL PROTECTED]> wrote:
>
>
> Here is the WSDL file attached with this mail.
>
>
>
>  
>  From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: Axis2 WSDL2Java error during service skeliton/stub generation
> Date: Fri, 26 Oct 2007 10:34:30 -0400
>
>
>  Hello All
>
> I am getting this error when i try to generate Service Skeleton code from a
> WSDL file. This is a new service and we are trying to go in WSDL first
> approach. We need wsdl to be in Document/literal Wrapped style in order to
> be interoperable with .Net framework. .Net generated client stubs with out
> any problem but Axis2 WSDL2Java is giving this exception during service
> skeleton and client generation times. This is pretty simple WSDL file with
> just two methods in it. We are trying to generate skeleton and clients in
> UNWrapped mode.
>
> C:\Code\Axis14ClientTest\Axis14ClientTest1>java.exe
> -Djava.ext.dirs=C:\Softwares
> \axis2-1.3-bin\axis2-1.3\lib; org.apache.axis2.wsdl.WSDL2Java -s -ss -uw -sd
> -d
> adb -uri PCMConnection.wsdl
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.description.
> WSDL11ToAllAxisServicesBuilder).
> log4j:WARN Please initialize the log4j system properly.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException
> : org.apache.axis2.wsdl.codegen.CodeGenerationException:
> Can not determine the s
> chema type for the set_PortalVariableResponse
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
> ationEngine.java:265)
> at
> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at
> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by:
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Can
> not determ
> ine the schema type for the set_PortalVariableResponse
> at
> org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtension.walk
>
>
> I have attached WSDL file with this mail. Just to let you know .Net is fine
> with this WSDL but not Axis2 WSDL2Java tool.
>
> Any help is greatly appreciated.
>
> Thank you,
>
> Kiran
>
>
>  
>  Peek-a-boo FREE Tricks & Treats for You! Get 'em!
> 
> Climb to the top of the charts!  Play Star Shuffle:  the word scramble
> challenge with star power. Play Now!
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Need help coding web service client with axis, please!!

[Anne Thomas Manes]

You must set the SOAPAction value:

call.setSoapAction("http://tempuri.org/ValoresActuais_GetTemperatura";);

Anne

On 10/26/07, Paulo Cristo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> My name is Paulo, and i'm from Portugal.
> I need to make a client to a web service, but i'm still fresh with SOAP/WSDL
> and Axis.
> I would appreciate any hel on this.
>
> I'm trying to access the services under
> http://meteo.estg.ipleiria.pt/webservice/service1.asmx
>
>
>
> The following is a sample SOAP 1.2 request and response example available on
> that page REQUEST
>
> POST /webservice/service1.asmx HTTP/1.1
> Host: meteo.estg.ipleiria.pt
> Content-Type: application/soap+xml; charset=utf-8
> Content-Length:
> length
>
> 
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> " xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:soap12="http://www.w3.org/2003/05/soap-envelope
> ">
>  
>  http://tempuri.org/"; />
>  
> 
>  RESPONSE
>
> HTTP/1.1 200 OK
> Content-Type: application/soap+xml; charset=utf-8
> Content-Length: length
>
> 
>
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema
> " xmlns:soap12="http://www.w3.org/2003/05/soap-envelope";>
>  
>  http://tempuri.org/";>
> float
>  
>  
>
> 
>
>
>
> ---
>
> And here The following is a sample SOAP 1.1 request and response on the same
> page
> REQUEST
>  POST /webservice/service1.asmx HTTP/1.1
>
> Host: meteo.estg.ipleiria.pt
> Content-Type: text/xml; charset=utf-8
> Content-Length: length
> SOAPAction: "
> http://tempuri.org/ValoresActuais_GetTemperatura";
>
> 
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> " xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/
> ">
>  
>  http://tempuri.org/"; />
>  
> 
>
> RESPONSE
>
>  HTTP/1.1 200 OK
> Content-Type: text/xml; charset=utf-8
> Content-Length: length
>
> 
> http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="
> http://schemas.xmlsoap.org/soap/envelope/";>
>  
>  http://tempuri.org/";>
> float
>  
>  
>
> 
>
>
> And here's the code i'm using to request that service
>
> public String consume() {
> try {
>String endpoint = "
> http://meteo.estg.ipleiria.pt/webservice/service1.asmx";;
>
>Service  service = new Service();
>Call call = (Call) service.createCall();
>
>call.setTargetEndpointAddress( new java.net.URL (endpoint) );
>call.setOperationName(new QName("http://tempuri.org/";,
> "ValoresActuais_GetTemperatura"));
>
>
>System.out.print(call.getOperationName ());
>System.out.print(call.getSOAPActionURI());
>
>   String ret = (String) call.invoke(new Object[] { "" }  );
>
>System.out.print(ret);
>
>   } catch (Exception e) {
> System.err.println(e.toString());
> return e.toString();
>   }
>
> }
>
> And i'm always getting the following error:
>
> Server did not recognize the value of HTTP Header SOAPAction: .
>
> So, what i 'm i doing wrong?
> Can someone help me on this, please?
>
> Thanks
>
> Paulo
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] wsdl not understood

[Anne Thomas Manes]

I've seen a similar bug reported before. Axis2 neglected to import the
"http://employees.niws.alphasolutions.dk/xsd"; namespace into the
second schema. Try the latest nightly build. If it still isn't fixed,
file a JIRA for it.

As a work-around, edit the WSDL and add this line to the second schema
right after the  declaration:

http://employees.niws.alphasolutions.dk/xsd"/>

Anne

On 10/29/07, Peter A. Kirk <[EMAIL PROTECTED]> wrote:
> Hi
>
> When I try to make a "web reference" (in Visual Studio .net) to my
> webservice installed under Axis2, I get these two messages:
>
> 1. Schema validation warning: Schema item 'element' named
> 'simpleDataResponse' from namespace
> 'http://employees.niws.alphasolutions.dk' is invalid. Namespace
> 'http://employees.niws.alphasolutions.dk/xsd' is not available to be
> referenced in this schema.
>
> 2. Schema could not be validated. Class generation may fail or may
> produce incorrect results.
>
> I have no wsdl (it is auto-generated by Axis2), so what could the
> problem be? The following is the auto-generated wsdl (I get from
> http://localhost:8080/axis2/services/Employees_WS?wsdl). Visual Studio
> uses this wsdl to make a "web reference" but it does not seem to
> understand it.
>
> Any advice please?
>
>
>
> 
> http://schemas.xmlsoap.org/wsdl/";
> xmlns:ns1="http://employees.niws.alphasolutions.dk";
> xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
> xmlns:ns0="http://employees.niws.alphasolutions.dk/xsd";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
> targetNamespace="http://employees.niws.alphasolutions.dk";>
> Employees_WS
> 
>  xmlns:ax21="http://employees.niws.alphasolutions.dk/xsd";
> attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://employees.niws.alphasolutions.dk/xsd";>
> 
> 
>  nillable="true" type="xs:string"/>
>  nillable="true" type="xs:string"/>
> 
>  nillable="true" type="xs:string"/>
> 
> 
> 
> http://employees.niws.alphasolutions.dk";
> attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://employees.niws.alphasolutions.dk";>
> 
> 
> 
>  nillable="true" type="ns0:Employees_WS_ReturnData"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  wsaw:Action="urn:simpleData"/>
>  wsaw:Action="urn:simpleDataResponse"/>
> 
> 
>  type="ns1:Employees_WSPortType">
> http://schemas.xmlsoap.org/soap/http";
> style="document"/>
> 
>  style="document"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  type="ns1:Employees_WSPortType">
> http://schemas.xmlsoap.org/soap/http";
> style="document"/>
> 
>  style="document"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  type="ns1:Employees_WSPortType">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  binding="ns1:Employees_WSSOAP11Binding">
>  location="http://localhost:8080/axis2/services/Employees_WS"/>
> 
>  binding="ns1:Employees_WSSOAP12Binding">
>  location="http://localhost:8080/axis2/services/Employees_WS"/>
> 
>  binding="ns1:Employees_WSHttpBinding">
>  location="http://localhost:8080/axis2/services/Employees_WS"/>
> 
> 
> 
>
>
>
> Thanks,
> Peter
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cannot compile wsdl file

[Anne Thomas Manes]

You have a few things wrong with your WSDL:

First: You must import import the
http://mtomserver.sourceforge.net/wsdl/soapserver.xsd namespace into
the http://mtomserver.sourceforge.net/wsdl/soapserver.wsdl schema.

Second: You want to define your binary fields as base64Binary fields,
not as xop:Include fields. (The SOAP message will be encoded to
replace the binary fields with xop:Include elements, but you shouldn't
define it that way.) You must define the field as if it were going to
be encoded within the SOAP element, e.g.,



And since you are using MTOM, you should not define the "attachments"
parts in your WSDL messages, nor should you define the
MIME:MultipartRelated bindings. MTOM will automatically encode the
binary elements as MIME attachments if you engage the optimization
feature.

See the XOP [1] and the media type [2] specs for more information:

[1] http://www.w3.org/TR/xop10/
[2] http://www.w3.org/TR/xml-media-types/

Anne


On 10/29/07, Schmilinsky, Remsy <[EMAIL PROTECTED]> wrote:
>
>
>
> Can you please help me compile with wsdl2java the attached wsdl ?
>
> I get lots of errors.
>
> thanks
>
>  <>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AXIS 2.0 OpenJMS

[Saket Raizada]

I have a HTTP client for a WebService and I want to create JMS based
clients for it.
Does anyone have inputs on developing a JMS based program using AXIS 2.0
and OpenJMS.
Any pointers/tutorials etc are appreciated.

regards
-machoq


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Can I enforce MTOM message encoding programatically?

[Thilina Gunarathne]

Hi,
>>msgContextL.getConfigurationContext().setProperty(Constants.Configuration.ENABLE_MTOM,
> > Constants.VALUE_TRUE);
> This creates a correct MTOM message, however, finally the service
> encounters an exception (something about Mime and writing) and is no
> longer usable from then on.
What is the exception you are getting...

Try the following...
MessageContext inMessageContext = MessageContext.getCurrentMessageContext();
   OperationContext operationContext = inMessageContext.getOperationContext();
   MessageContext outMessageContext = operationContext

.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
thanks,
Thilina
>
> I also tried:
>
> > MessageContextmsgContextL=
> > MessageContext.getCurrentMessageContext();
> >
> > msgContextL.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
> > Constants.VALUE_TRUE);
> This does not work at all, I still get Base64 encoded text messages.
>
> I would much appreciate if someone could tell me the correct way of
> enforcing MTOM encoding programatically
>
> Thanks,
> -Rainer
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Ali, Haneef]

Look at the comment by Dims. He have given a link  to the svn commit.
That link says which file/function is fixed. 

Thanks,
Haneef 

-Original Message-
From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 11:57 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

And also in the JIRA it says that AXIS2-3143 is still open and is not
assigned to anyone.

-Original Message-
From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 11:56 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

Hi Ali,

I'm using Axis2 1.3 and having this problem in that.

Thanks
Raghu

-Original Message-
From: Ali, Haneef [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 11:53 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

Hi,
 
This should have been fixed in Axis2 1.3. Please check the following
issue and the comments. 

https://issues.apache.org/jira/browse/AXIS2-3143
http://marc.info/?l=axis-cvs&m=118499936203494&w=2

Thanks,
Haneef


From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 9:21 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).



Hi Amila,

 

I can't change the soap:address in wsdl file because the address is
different in each environment (localhost, QA, Production etc).

 

Do you mean to edit the soap:address manually in every environment
before deploying?  I guess that's not a good option.

 

Thanks

Raghu



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 4:53 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

 

 

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  < soap:address location=
http://10.5.2.182:80/webservices/services/MyWSService
  /> 



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

< soap:address location=
http://ws.qa.company.com/webservices/services/MyWSService
 /> 



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.


why don't you change the soap:address in wsdl file to the correct one?

Amila. 

 

Thanks in Advance.

Raghu

 




-- 
Amila Suriarachchi,
WSO2 Inc. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cannot compile wsdl file

[Schmilinsky, Remsy]

Can you please help me compile with wsdl2java the attached wsdl ?

I get lots of errors.

thanks

 <> 


mtomserver.wsdl
Description: mtomserver.wsdl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Raghu Upadhyayula]

And also in the JIRA it says that AXIS2-3143 is still open and is not
assigned to anyone.

-Original Message-
From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 11:56 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

Hi Ali,

I'm using Axis2 1.3 and having this problem in that.

Thanks
Raghu

-Original Message-
From: Ali, Haneef [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 11:53 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

Hi,
 
This should have been fixed in Axis2 1.3. Please check the following
issue and the comments. 

https://issues.apache.org/jira/browse/AXIS2-3143
http://marc.info/?l=axis-cvs&m=118499936203494&w=2

Thanks,
Haneef


From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 9:21 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).



Hi Amila,

 

I can't change the soap:address in wsdl file because the address is
different in each environment (localhost, QA, Production etc).

 

Do you mean to edit the soap:address manually in every environment
before deploying?  I guess that's not a good option.

 

Thanks

Raghu



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 4:53 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

 

 

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  < soap:address location=
http://10.5.2.182:80/webservices/services/MyWSService
  /> 



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

< soap:address location=
http://ws.qa.company.com/webservices/services/MyWSService
 /> 



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.


why don't you change the soap:address in wsdl file to the correct one?

Amila. 

 

Thanks in Advance.

Raghu

 




-- 
Amila Suriarachchi,
WSO2 Inc. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Raghu Upadhyayula]

Hi Ali,

I'm using Axis2 1.3 and having this problem in that.

Thanks
Raghu

-Original Message-
From: Ali, Haneef [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 11:53 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

Hi,
 
This should have been fixed in Axis2 1.3. Please check the following
issue and the comments. 

https://issues.apache.org/jira/browse/AXIS2-3143
http://marc.info/?l=axis-cvs&m=118499936203494&w=2

Thanks,
Haneef


From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 9:21 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).



Hi Amila,

 

I can't change the soap:address in wsdl file because the address is
different in each environment (localhost, QA, Production etc).

 

Do you mean to edit the soap:address manually in every environment
before deploying?  I guess that's not a good option.

 

Thanks

Raghu



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 4:53 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

 

 

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  < soap:address location=
http://10.5.2.182:80/webservices/services/MyWSService
  /> 



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

< soap:address location=
http://ws.qa.company.com/webservices/services/MyWSService
 /> 



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.


why don't you change the soap:address in wsdl file to the correct one?

Amila. 

 

Thanks in Advance.

Raghu

 




-- 
Amila Suriarachchi,
WSO2 Inc. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Ali, Haneef]

Hi,
 
This should have been fixed in Axis2 1.3. Please check the following
issue and the comments. 

https://issues.apache.org/jira/browse/AXIS2-3143
http://marc.info/?l=axis-cvs&m=118499936203494&w=2

Thanks,
Haneef


From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 9:21 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).



Hi Amila,

 

I can't change the soap:address in wsdl file because the address is
different in each environment (localhost, QA, Production etc).

 

Do you mean to edit the soap:address manually in every environment
before deploying?  I guess that's not a good option.

 

Thanks

Raghu



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 4:53 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

 

 

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  < soap:address location=
http://10.5.2.182:80/webservices/services/MyWSService
  /> 



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

< soap:address location=
http://ws.qa.company.com/webservices/services/MyWSService
 /> 



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.


why don't you change the soap:address in wsdl file to the correct one?

Amila. 

 

Thanks in Advance.

Raghu

 




-- 
Amila Suriarachchi,
WSO2 Inc. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis 1.4 and gSoap interoperability problems

[Dave Levitt]

Looks like this was not a library isssue. The vendor's documentation
[_including_ the wsdl file published on the server] had the wrong
namespace.

Now that that's resolved, the next hurdle is finding out that the
other test service ['process'] is currently configured to refuse
connections that are not originating from their local network.

On 10/26/07, Dave Levitt <[EMAIL PROTECTED]> wrote:
> Since the libraries at each end are fixed, I was wondering about
> modifying the wsdl2java generated code in the 'ServiceStub' class [the
> createCall() method and / or the settings and parameters before the
> call.invoke() method is performed.
>
> I would not like to change the library on the client side, as it is
> working fine for RPC style calls to several other services [including
> a .NET service].
>
> On 10/26/07, Cort, Tom <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I experienced a similar problem. The code generators for gsoap and axis
> > generated incompatible implementations, even when I gave each of them
> > the exact same WSDL file. During my debugging I did some packet
> > sniffing. It appeared that they could not agree on where the xmlns
> > attribute should go. I ended up trying csoap (
> > http://csoap.sourceforge.net/ ). It worked with axis, but I strongly
> > warn against using it. I've discovered nearly 30 buffer overflows and at
> > least 1 memory leak in csoap. The project hasn't had much activity
> > lately and the csoap author didn't respond to the patch I sent him. I've
> > since created a new project cshampoo ( http://cshampoo.sourceforge.net )
> > to clean up csoap. I should be releasing the first beta in the next week
> > or two.
> >
> > -Tom
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Simulated func name problem using SOAPUI

[ab]

I posted an issue(http://marc.info/?l=axis-user&m=119316258912686&w=2) a few 
days ago about an incorrect Operation name being returned in the SOAP Response 
under load. 

UPDATE: I was able to simulate the issue using SOAP UI as the client and with 
quite few threads (5 or so) accessing 2 different functions in the Webservice 
(deployed 
on JBoss too). I looked at the Request/Response using the SOAP Monitor and 
found 
that the function names were mismatched randomly. The response data itself was 
all 
correct except for the function names.

I'm really curious to know if anyone else experienced/resolved this since I was 
able 
to replicate it so easily. Am I missing something?

I'm concerned what implications this may have for Axis clients under load? Is 
there 
any check by clients to validate the function names in  the SOAP response to 
match 
that in SOAP Request?



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

RE: Why Axis 1.4 over 1.2.1?

[Walker, Jeff]

Your going from an extremely old version of Axis to just a very old
version. (by the way, I don't think either are supported anymore).
Most people on this users list have moved to Axis2.x.
 
But, to answer your question, when you downloaded Axis1.4 you will find
a file called release-notes.html. Here it is below. Take a look.
-jeff
 

Axis Change Log


Axis 1.4


Changes from 1.3 final

Many bugfixes, including: 

*   Prevented an NPE when curMsg is null 
*   Fixed memory leaks 
*   Fixed incorrect serialization of extended types in arrays 
*   Fixed garbage collection for TypeDesc mappings 
*   Fixed a problem with exception deserialization 
*   Updated outdated version numbers in documentation 
*   Fixed an issue that caused non-Sun JVMs to generate a
CurrentModificationException 
*   Fixed a problem with wsdl2java-generated class constructors 


Axis 1.3


Changes from 1.2.1 final


*   Support Axis inside Applets 
*   Upgrade versions of dependency jars 
*   Updated xmlbeans serializer/deserializer 
*   Fixes for SAAJ 
*   Fixes for Code Generation 
*   Fixes for tools 
*   Fixes for Runtime 
*   Fixes for Performance 
*   Fixes for various attachments problems 
*   Fixes for Memory Leaks 
*   Cleanup support for JavaBeans with array-type properties 
*   Extract attachment streams directly from http request (w/o
intermediate files) 
*   GC Fixes for long standing servers (Geronimo) 
*   Preliminary support for MTOM 


Axis 1.2.1


Changes from 1.2final


*   Cleanup array handling for rpc/lit and doc/lit 
*   Enhancements to HTTPSender/CommonsHTTPSender (including better
cookie support) 
*   Generate array of wrappers for soapenc array nillable elements 
*   Better handling of elementFormDefault during dynamic wsdl
generation 
*   Fix for gracefully handling IncompatibleClassChangeError in
websphere/weblogic 
*   Better SAAJ support (dirty flag was not set leading to
serialization problems) 
*   Fix out-of-memory errors for services without attachments
returning large response messages 
*   Last but not the least more test cases... 


Changes from 1.2rc3


*   Tons of changes to typemapping system to better support
jax-rpc1.1 and .NET 
*   Improved SAAJ 1.2 support 
*   Much better for rpc/lit and doc/lit (especially for arrays) 
*   Map schema "wrapped" arrays (with inner  elements) into
arrays of the item type, instead of JavaBeans, by default. Introduce the
"-w" or "--wrapArrays" option to WSDL2Java to switch back to the earlier
behavior. 
*   Fix some WS-I related bugs. Makes it easier to deploy WS-I BP
compatible services. 
*   Internationalized happyaxis jsp pages. 
*   Updated to latest dependency jars. (ex wsdl4j-1.5.1.jar) 
*   Improved commons httpclient support. 
*   Support for sending and receiving multiple cookies 
*   Lots of fixes for performance enhancements (including
eliminating ThreadLocal's) 
*   Improved JMX support - Start/Stop server/services and
deploy/modify services 


Changes from 1.2beta2


*   When generating WSDL, don't change the scoping rules for type
mappings. In other words, use the most specific mappings just like we do
for message processing. 
*   Fix problem with version string 
*   Remove JAXP interfaces (should come from jaxp.jar, not
jaxrpc.jar) 


Changes from 1.1


*   Preliminary SAAJ 1.2 support! 
*   Improved doc/literal support 
*   Improved handling of array types + WSDL generation 
*   More logical type mapping registration (SOAP-ENC types are in a
separate registry which then delegates to the default one) 
*   Improved schema support (we deal with lists and groups now) 
*   ServiceDesc metadata is now more generic - ServiceDesc is an
interface and JavaServiceDesc implements it to do specific Java
processing. 
*   Throw fault when bad values for "mustUnderstand" attribute are
parsed 
*   log4j.properties is no longer in axis.jar. This is to avoid
conflicts with the configuration files in other bits of the application.

*   Many bugfixes. See docs/svnlog.txt
  


Axis 1.1


Changes from 1.0 to 1.1 that may break your code


*   We have changed how we map http URLs to packages, such that any
directories in the URL are used as well as the hostname. The previous
behavior was a defect, as it would import WSDL from the same site into
the same place. If you do not explicitly state the mappings of URIs to
packages, things may now end up in different places 
*   The default socket timeout for clients is now 60 seconds, not
infinity. You can use the setTimeout() option on any binding (cast it to
an org.apache.axis.client.Stub first) to change this. 
*   The API for writing custom schema from a Serializer
(writeSchema()) has changed! We now return an Element which should be
suitable for either dropping under an  or 
declaration as an anonymous t

Re: Why Axis 1.4 over 1.2.1?

[Abhishek Shadangi]

I would like re-iterate. Please suggest if anybody has any idea!

Any help is highly appreciated.

Thanks
Abhishek.

On 10/25/07, Abhishek Shadangi <[EMAIL PROTECTED]> wrote:
>
> Hi Guys,
>
> I recently joined this community, and I wish you guys can help me find
> answers!
>
> 1. What are the improvements/features/functionalities added to Axis 1.4(since
> 1.2.1)?
> 2. If I am already using Axis 1.2.1 extensively, how would it affect me if
> I upgrade to 1.4?
> 3. What are the advantages with 1.4 over 1.2.1?
> 4. Last but not the least, where can I find the release notes or any
> documentation?
>
> Any help would be highly appreciated.
>
> Thanks
> Abhishek




-- 
Abhishek Shadangi
001-703-973-9466
3007 Hickory Grove Ct.
Firfax VA, 22031

RE: [Axis2] How to specify wsdl operation so that wsdl2java generates method throwing java.lang.RemoteException

[Pantvaidya, Vishwajit]

I am generating the interface (-ssi option) and none of the methods generated 
there with Axis2 1.3 are defined as throwing RemoteException (as was the case 
in Axis1). My web service implementation methods which are coded to match the 
Axis1 generated interface throw RemoteException. So now after wsdl2java with 
Axis2, I have compile time issues as the method signature does not match.


From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 5:28 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] How to specify wsdl operation so that wsdl2java generates 
method throwing java.lang.RemoteException

generated stub method already throws this exception isn't?

eg.
public  java.lang.String Echo(

java.lang.String echoIn7)


throws java.rmi.RemoteException

{

Amila.
On 10/26/07, Pantvaidya, Vishwajit < [EMAIL PROTECTED]> wrote:

I am migrating to Axis2 1.3 from Axis1. I have existing code that relies on the 
webservice methods throwing java.lang.RemoteException. Is it possible to 
specify an operation in the wsdl, such that, wsdl2java generates methods that 
throw RemoteException? I know that is not the best way to do it - but just for 
compatibility with existing code.



Thanks,



Vish.



--
Amila Suriarachchi,
WSO2 Inc.

log4j issue

[thomas mccarthy]

Hi, I am trying to use log4j in my application running
on axis2 and am encountering some issues. I initialize log4j using the
following:
    public void init(ServiceContext serviceContext) 
    {
        // establish log4j
       
DOMConfigurator.configure("/usr/local/apache-tomcat-6.0.10/webapps/axis2/WEB-INF/services/CMSApi-log4j.xml");
    }
which works fine for a while, but at some point it stops working
without error. I was thinking it might be conflicting with the axis
log4j.properties file or something. Has anyone seen a similar problem
or have any ideas what the issue or solution could be?




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 generated wsdl soap address is 0.0.0.0

[Daniel Herbison]

Hi All! 
I have a web service deployed on one machine under axis2 and i'm calling it
using flex and everything is working great.  However when I place the
service on another machine under axis2 i can no longer run the services from
flex but they do run fine from the browser.  Flex is complaining about the
soap:address being set to 0.0.0.0, see below.  Why is the WSDL being set to
0.0.0.0 on one machine and on the other machine it is being set to the
correct ip 

-  
-  
  http://0.0.0.0:8086/axis2/services/IEventService";
/> 
   
-  
  http://0.0.0.0:8086/axis2/services/IEventService"; /> 
   
-  
  http://0.0.0.0:8086/axis2/services/IEventService";
/> 
   
  
-- 
View this message in context: 
http://www.nabble.com/Axis2-generated-wsdl-soap-address-is-0.0.0.0-tf4713352.html#a13472967
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Case of method names generated by wsdl2java

[Pantvaidya, Vishwajit]

From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 5:00 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Case of method names generated by wsdl2java


On 10/25/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:



I noticed following differences in wsdl2java behavior in axis2 1.3 as against 
axis1 1.4:



 1.  Axis2 retains case of the operations for method names. Axis 1 would start 
the method name in lowercase and keep other letters from operation name in same 
case. I liked this - is there any way to achieve the same with axis2?

i'll check this.


 1.  Axis 1 would correctly translate empty operation message outputs as void 
methods (these are cases where the schema types defined for these message parts 
do not contain any elements) - Axis2 does not do that. While this is not a bug 
deal - any suggestion on how to achieve same behavior with axis2 are welcome.

I have fixed this will commit soon.

Amila.

[Pantvaidya, Vishwajit] Thanks Amila, Please let me know which nightly build I 
need to take to try this fix out.

Thanks,



Vish.





--
Amila Suriarachchi,
WSO2 Inc.

RE: [Axis2] 1.3 wsdl2java generates code with missing methods

[Pantvaidya, Vishwajit]

Thanks Amila. Can you let me know which nightly build I should take to try out 
the fix?



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 4:57 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] 1.3 wsdl2java generates code with missing methods

I have fixed this issue locally. will commit soon.

Amila.
On 10/25/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]  > wrote:

A quick clarification - the MessageReceiverInOut class generated by wsdl2java 
contains references to the missing methods. As this is an autogenerated class, 
I do not want to edit it myself to remove these problems.



Any insights?





From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2007 5:25 PM
To: axis-user@ws.apache.org
Subject: Axis2 1.3 wsdl2java generates code with missing methods



I am using wsdl2java to generate java code from a wsdl using wsdl2java options 
"-o -ss -sd -ssi -f -uw -uri -ns2p". The result includes a MessageReceiverInOut 
class that is missing a method resulting in a compiletime error "method 
wrapIsUploadAllowed(OperationStatusType) is undefined for the type 
...MessageReceiverInOut".



I observed that this seems to happen when wsdl parts in different messages 
refer to the same complex type. In such cases, the wrap methods in the 
MessageReceiver class for the first operation is created while that for the 
other one is not created. E.g. in this case the method 
wrapUpload(OperationStatusType) gets created while 
wrapIsUploadAllowed(OperationStatusType) is missing.



Wsdl snippet is included below.



Is this a bug?










































>


























... 

























...

















...

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





































...



--
Amila Suriarachchi,
WSO2 Inc.

Empty element

[Sunesh Kumra]

Hi,
I'm using axis2-1.3 and am facing a strange problem that the encoded
SOAP request has an empty  element, which causes the WS to
throw an exception. Has anyone experienced this kind of an issue ?
I've generated and deployed the WS and then developed a client using
both the ADB as well as XMLBeans (both the client versions has the same
behaviour). I have captured the SOAP messages using a TCP Monitor.
Excerpt of the requests:

 
http://localhost:8090/ReserveAmountChargingService/services/Rese
rveAmountCharging
 
urn:uuid:1A3E13D08490819A341193676851007
 ""
  
Excerpt from the response:

 
http://www.w3.org/2005/08/addressing/fault
 
urn:uuid:41BBE642BADD2EDC831193677481559
 

   ""

 
  
  
 
wsa:ActionNotSupported
The [action] cannot be processed at the
receiver.

 
  

Cheers,
Sunesh


Ericsson Services Limited 
Registered Office: Unit 4, Midleton Gate, Guildford Business Park, Guildford, 
Surrey, GU2 8SG 
Registered Number in England and Wales: 3709800 
This communication is confidential and intended solely for the addressee(s). 
Any unauthorised review, use, disclosure or distribution is prohibited. If you 
believe this message has been sent to you in error, please notify the sender by 
replying to this transmission and delete the message without disclosing it. 
Thank you. 
Ericsson Services Limited does not enter into contracts or contractual 
obligations via electronic mail, unless otherwise agreed in writing between the 
parties concerned.
E-mail including attachments is susceptible to data corruption, interruption, 
unauthorised amendment, tampering and viruses, and we only send and receive 
e-mails on the basis that we are not liable for any such corruption, 
interception, amendment, tampering or viruses or any consequences thereof. 


__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

RE: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Raghu Upadhyayula]

Hi Amila,

 

I can't change the soap:address in wsdl file because the address is
different in each environment (localhost, QA, Production etc).

 

Do you mean to edit the soap:address manually in every environment
before deploying?  I guess that's not a good option.

 

Thanks

Raghu



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 29, 2007 4:53 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Problem with soap:address location in the WSDL (IP
Address is not a public IP that is accessible from Internet).

 

 

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  < soap:address location=
http://10.5.2.182:80/webservices/services/MyWSService
  /> 



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

< soap:address location=
http://ws.qa.company.com/webservices/services/MyWSService
 /> 



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.


why don't you change the soap:address in wsdl file to the correct one?

Amila. 

 

Thanks in Advance.

Raghu

 




-- 
Amila Suriarachchi,
WSO2 Inc. 

Re: XMLBeans MTOM Client

[robert lazarski]

xmlbeans in axis2 currently has no support for mtom - AFAIK only adb
does. There's a long standing jira open for this, but so far no one
has done the work or had the interest. You'd probably have to supply
patches in order for it to make xmlbeans with mtom a reality.

Robert

On 10/29/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
> Hi.
>
> How about this command:
>
> wsdl2java -uri MTOMSample.wsdl -p mtom.client -d xmlbeans -s -o build/client
>
> MTOMSample.wsdl defines a service that use MTOM.
>
> Is it possible? (MTOM client using XMLBeans data binding).
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

XMLBeans MTOM Client

[Antonio Manuel Muñiz Martín]

Hi.

How about this command:

wsdl2java -uri MTOMSample.wsdl -p mtom.client -d xmlbeans -s -o build/client

MTOMSample.wsdl defines a service that use MTOM.

Is it possible? (MTOM client using XMLBeans data binding).

response prefix omitted

[axelspin]

Hi,

I am developing ws with axis2 (1.2,1.3 behave the same) and AXIOM with raw
XML in out and I need to include in a SOAP envelope of a document/literal
style WS a response that is an RDF document.

in my operation method, if I print out the OMElement, just before leaving
the payload to axis2 I get the right document with the right prefix in front
of the RDF root tag.

http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:dc="http://purl.org/dc/elements/1.1/";
xmlns:wgs="http://www.w3.org/2003/01/geo/wgs84_pos#";
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#";
xmlns:xsd="http://www.w3.org/2001/XMLSchema#";>
  ...


Afterwards, when I get the SOAP message the prefix disappears! while all the
namespaces are still there.

below there is the  the xsd I use in my wsdl to declare the RDF element

http://www.w3.org/2001/XMLSchema";>
http://www.w3.org/1999/02/22-rdf-syntax-ns";
schemaLocation="resources?xsd=rdf-dummy.xsd"/> 

[request elements omitted...]



 



and the Response Message declaration takes this shape:






am I doing something wrong?
how can I tell to axis2 not to erase the prefixes of my response root tag?


thanks
-- 
View this message in context: 
http://www.nabble.com/response-prefix-omitted-tf4712371.html#a13469794
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] wsdl not understood

[Peter A. Kirk]

Hi

When I try to make a "web reference" (in Visual Studio .net) to my
webservice installed under Axis2, I get these two messages:

1. Schema validation warning: Schema item 'element' named
'simpleDataResponse' from namespace
'http://employees.niws.alphasolutions.dk' is invalid. Namespace
'http://employees.niws.alphasolutions.dk/xsd' is not available to be
referenced in this schema.

2. Schema could not be validated. Class generation may fail or may
produce incorrect results.

I have no wsdl (it is auto-generated by Axis2), so what could the
problem be? The following is the auto-generated wsdl (I get from
http://localhost:8080/axis2/services/Employees_WS?wsdl). Visual Studio
uses this wsdl to make a "web reference" but it does not seem to
understand it.

Any advice please?




http://schemas.xmlsoap.org/wsdl/";
xmlns:ns1="http://employees.niws.alphasolutions.dk";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:ns0="http://employees.niws.alphasolutions.dk/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
targetNamespace="http://employees.niws.alphasolutions.dk";>
Employees_WS

http://employees.niws.alphasolutions.dk/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://employees.niws.alphasolutions.dk/xsd";>









http://employees.niws.alphasolutions.dk";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://employees.niws.alphasolutions.dk";>




















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











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
























http://localhost:8080/axis2/services/Employees_WS"/>


http://localhost:8080/axis2/services/Employees_WS"/>


http://localhost:8080/axis2/services/Employees_WS"/>






Thanks,
Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] MTOM Interoperability

[Hoda, Nadeem [USA]]

 
Has anyone had success implementing MTOM with Axis2 and created clients
from other web service frameworks/toolkits?
 
I just tried deploying the MTOM sample that comes with Axis2 and created
a .NET client (web reference.) 
 
.NET doesn't even succeed in creating a client.
 
I would like to use MTOM with Axis2, but seems to be more complicated
than expected.
 
Any pointers, guidance would be appreciated? 
 
Any details instructions/how-tos/simple guide beyond the Axis2 MTOM
how-to (http://ws.apache.org/axis2/1_0/mtom-guide.html).
 
Thanks, 
 
Nadeem
 
.NET Errors:
 
Error 1 Custom tool error: Unable to import WebService/Schema. Schema
with targetNamespace='http://www.w3.org/2005/05/xmlmime' has invalid
syntax. The 'name' attribute cannot be present. Line 4, position 6. The
'name' attribute cannot be present.
Error 2 Custom tool error: Unable to import WebService/Schema. Schema
with targetNamespace='http://www.w3.org/2005/05/xmlmime' has invalid
syntax. The 'name' attribute cannot be present. Line 4, position 6. The
'name' attribute cannot be present.

[Axis2] Can I enforce MTOM message encoding programatically?

[Rainer Menzner]

Hi,

I'm trying to encode binary data to be delivered from an Axis2 web 
service based the capabilities that a client explicitly specifies. This 
requires that MTOM is programatically enabled or disabled when creating 
the responsne message. Hence I cannot use the services.xml.


I tried the following in the service implementation:

MessageContextmsgContextL= 
MessageContext.getCurrentMessageContext();
   
 msgContextL.getConfigurationContext().setProperty(Constants.Configuration.ENABLE_MTOM, 
Constants.VALUE_TRUE);
This creates a correct MTOM message, however, finally the service 
encounters an exception (something about Mime and writing) and is no 
longer usable from then on.


I also tried:

MessageContextmsgContextL= 
MessageContext.getCurrentMessageContext();

msgContextL.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM, 
Constants.VALUE_TRUE);

This does not work at all, I still get Base64 encoded text messages.

I would much appreciate if someone could tell me the correct way of 
enforcing MTOM encoding programatically


Thanks,
-Rainer


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Mac os x Leopard Java has the RegexpBug

[Massimiliano Masi]

Hi all,

Just FYI: I have a mac os x leopard and I have (I think !!!) this problem:

https://issues.apache.org/jira/browse/AXIS2-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

I have java version "1.5.0_13"

This is the exception:

at  
org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
 [java] Caused by: java.util.regex.PatternSyntaxException:  
Dangling meta character '*' near index 0

 [java] *.local
 [java] ^
 [java] at java.util.regex.Pattern.error(Pattern.java:1650)
 [java] at java.util.regex.Pattern.sequence(Pattern.java:1787)
 [java] at java.util.regex.Pattern.expr(Pattern.java:1687)
 [java] at java.util.regex.Pattern.compile(Pattern.java:1397)
 [java] at java.util.regex.Pattern.(Pattern.java:1124)
 [java] at java.util.regex.Pattern.compile(Pattern.java:817)
 [java] at java.util.regex.Pattern.matches(Pattern.java:919)
 [java] at java.lang.String.matches(String.java:1921)
 [java] 	at  
org.apache.axis2.transport.http.ProxyConfiguration.validateNonProxyHosts(ProxyConfiguration.java:261)
 [java] 	at  
org.apache.axis2.transport.http.ProxyConfiguration.isProxyEnabled(ProxyConfiguration.java:223)






This message was sent using IMP, the Internet Messaging Program.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: wsdl2java mixed=true support?

[ROBINSON JULIEN]

Thanks Amila for your answer. I must say I don't really see the point of
mixed in web services anyway, so I'm glad that it's simply ignored. :-)

Julien

Amila wrote:
> ADB does not support this attribute. Try with xml beans (i.e 
> -d xmlbenas)
> 
> Amila.
> 
> Julien wrote (and edited):
> 
>   mixed="true"
>   
>   My question is: is this parameter supported?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Handling webservice unavailability

[k2g]

What is the generic solution if a service becomes unavailable. Since
axisfault extends remoteexception i believe catching the same should tell us
that service isnt available. In addition to axisfault ... should timeout be
implemented so that after several tries ... if the response doesnt come back
it means service isnt available.

Service unavaibility can be due to many reasons like server downtime,
network latency and so on.

-- 
--
Krishna

Re: wsdl2java mixed=true support?

[Amila Suriarachchi]

ADB does not support this attribute. Try with xml beans (i.e -d xmlbenas)

Amila.

On 10/26/07, ROBINSON JULIEN <[EMAIL PROTECTED]> wrote:
>
>
> Hi all,
>
> I've got a legacy WSDL that contains a complexType with the parameter
> mixed="true"
>
> I've tried generating Java using Axis2, and the generated Java is the
> same with and without this parameter.
>
> My question is: is this parameter supported?
> What should be generated?
>
> Thanks for any info!
> Julien
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [AXIS2] SOAP Header problem

[Amila Suriarachchi]

I have fixed this locally will commit soon.

On 10/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi again,
>
> I have verified it to be a question solely about the attribute in the
> SOAP Header block.
> I have generated and executed a SOAP request through AXIS2. I have
> copied the generated SOAP message and executed it again (SoapUI) this
> time with the only difference that I manually inserted the missing
> attribute.
> And this works.
>
> So - how do I force AXIS2 to accept the attribute I set on an Java
> object representing the SOAP header block?
>
> BR
> Morten
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 25. oktober 2007 13:38
> To: axis-user@ws.apache.org
> Subject: RE: [AXIS2] SOAP Header problem
>
> Thanks for the answer.
>
> In my case I have no problem in reaching the correct service deployed.
> The problem is, that the server-side will validate the incomming XML
> document (SOAP message) and this validation fails because my generated
> SOAP Header Block is not correct according to the XSD defining the
> Header Block.
>
> So I do not think the soapAction is a problem in this case.
>
> I somehow need to force AXIS2 to use my attribute settings (Java part)
> for generating the correct SOAP Header Block.
>
> BR
> Morten
>
>
> -Original Message-
> From: Jon Hanshew [mailto:[EMAIL PROTECTED]
> Sent: 24. oktober 2007 20:45
> To: axis-user@ws.apache.org
> Subject: Re: [AXIS2] SOAP Header problem
>
>
> The first thing that I see is that "soapAction" is null ("").
>
> It needs to match your service call.  The Axis2 stub code generated by
> wsdl2java does a "setAction" call that uses the wsdl value of soapAction
> to identify the function to call on the service.
>
> Hope this helps.
>
>
> morten.frank wrote:
> >
> > Hi,
> >
> > I am currently evaluating different WS technologies to be used in a
> > client side Java environment.
> >
> > The deal is, that we have a number of WSDL docs and they refer several
>
> > XSD schemas for describing service input/output and data types etc.
> >
> > My problem is, that somehow I can't get AXIS2 to generate the correct
> > SOAP header block according to our WSDL and XSD definitions.
> >
> > Example:
> >
> > A WSDL document defines the binding:
> >> type="tns:HelloWorldService">
> >> transport="http://schemas.xmlsoap.org/soap/http"/>
> >   
> >   
> >   
> >   
> >> message="common:MetadataMessage" part="metadata" use="literal"/>
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >
> > The thing to note is the  > part="metadata" use="literal"/> part.
> >
> > The Common.wsdl is imported in the above WSDL and is defined as:
> >   > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > xmlns:tns="http://common.ntpsoa.nordea.com/common/wsdl/v1";
> > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:md="http://metadata.ntpsoa.nordea.com/object";
> > xmlns:err="http://error.ntpsoa.nordea.com/object/v1"; name="CommonWSDL"
> > targetNamespace="http://common.ntpsoa.nordea.com/common/wsdl/v1";>
> >   
> >   
> >> namespace="http://metadata.ntpsoa.nordea.com/object";
> > schemaLocation="../xsd/Metadata.xsd"/>
> >> namespace="http://error.ntpsoa.nordea.com/object/v1";
> > schemaLocation="../xsd/Error.xsd"/>
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> > 
> >
> > In the Metadata.xsd the following part is defined:
> >  > use="required">
> >
> >
> > I have run the WSDL file through the wsdl2java to generate the client
> > stub.
> > I have tried with ADT and XMLBeans as binding mechanism, both give the
>
> > same result: In both cases I get an Java class representing the
> > Metadata. In both cases I am able to set the Java attributes for the
> > elements and attributes of the underlying XML document, including the
> > "schemaVersion".
> >
> > Using XMLBeans I have tried to dump the headerblock generated by
> > XMLBeans. The result is:
> >  > xmlns:obj="http://metadata.ntpsoa.nordea.com/object";>
> >   N231820
> >   SE
> >   String
> >   String
> >
> > 2007-10-22T15:29:55.625+02:00 > am
> > p>
> >   String
> >   false
> > 
> >
> > Note, that "schemaVersion" is set correctly at this point.
> >
> > But in both cases, the actual SOAP message looks like:
> >
> >   > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> >   
> >> xmlns="http://metadata.ntpsoa.nordea.com/object";
> > soapenv:mustUnderstand="0">
> >   N231820
> >   SE
> >  

Re: [Axis2] XmlSchema choice element not supported, other problems

[Amila Suriarachchi]

as ajith told  -uw works only with the sequece. i.e only for doc/lit wrapped
style wsdls.

On 10/26/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
>
> Thanks Ajith. By the way - a surprising revelation was that, after
> enclosing the choice and inner sequence elements in complextypes, there is
> no code now generated for those data elements inside them.


could you paste your element here?

Amila.





- Vish.
>
> >-Original Message-
> >From: Ajith Ranabahu [mailto:[EMAIL PROTECTED]
> >Sent: Wednesday, October 24, 2007 8:53 PM
> >To: axis-user@ws.apache.org
> >Subject: Re: [Axis2] XmlSchema choice element not supported, other
> problems
> >
> >Hi,
> >it is not a matter whether Schema can support it. All the schema
> >constructs you mentioned are legal. However the Axis2 codegen supports
> >only sequence based unwrapping. What was meant by saying choice is
> >supported is the ability to generate code for it in beans - not for
> >unwrapping (Actually if you think of unwrapping a choice, it would be
> >quite ambiguous. A choice element signifies an alternative and how
> >would you select the parameters for it ?).
> > If you don't want unwrapping ADB will create a bean for you that has
> >all the choice items put at alternatives. i.e you will be given
> >setters/getters for all items but only the last item set will take
> >effect.
> >
> >
> >Ajith
> >On 10/24/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>
> >>
> >> Success at last! - it worked when I enclosed the choice element and the
> >> embedded sequence element within a complexType.
> >>
> >> But still this is strange because:
> >>
> >> -  as far as I can see, XmlSchema does not require this
> >>
> >> -  the same wsdl used to work in axis1
> >>
> >>
> >>
> >> Attaching the wsdl that works.
> >>
> >> I have not yet checked if the code generated is backwardly compatible
> >with
> >> the one generated by axis1. I suspect it may not be.
> >>
> >>
> >>
> >>
> >>
> >>
> >>  
> >>
> >>
> >> From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]
> >>  Sent: Wednesday, October 24, 2007 7:36 PM
> >>
> >>  To: axis-user@ws.apache.org
> >>  Subject: RE: [Axis2] XmlSchema choice element not supported, other
> >problems
> >>
> >>
> >>
> >>
> >> I did a little more try and error and found that it does not seem to
> like
> >2
> >> things:
> >>
> >> - the choice element
> >>
> >> - a sequence element within another sequence element
> >>
> >>
> >>
> >> Any of these things if present give that error. Attaching the wsdl with
> >the
> >> choice and sequence-within-sequence elements commented out from the
> >complex
> >> type UserType. This wsdl works. Uncomment one/both these cases and it
> >fails.
> >>
> >>
> >>
> >> Should I file a bug?
> >>
> >>
> >>
> >>
> >>
> >>
> >>  
> >>
> >>
> >> From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]
> >>  Sent: Wednesday, October 24, 2007 5:35 PM
> >>  To: axis-user@ws.apache.org
> >>  Subject: RE: [Axis2] XmlSchema choice element not supported, other
> >problems
> >>
> >>
> >>
> >> Thanks Raghu.
> >>
> >> I am using Axis2 1.3. So according to the wso2 link below - the choice
> >> element should not be an issue. But for me it does not work with "-uw"
> >> option - it gives the exception I mentioned below. Any ideas why this
> is
> >> happening?
> >>
> >>
> >>
> >>
> >>
> >>
> >>  
> >>
> >>
> >> From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED]
> >>  Sent: Wednesday, October 24, 2007 5:27 PM
> >>  To: axis-user@ws.apache.org
> >>  Subject: RE: [Axis2] XmlSchema choice element not supported, other
> >problems
> >>
> >>
> >>
> >> Hi Vish,
> >>
> >>
> >>
> >> Both the links shown below are referring to different
> >versions
> >> of Axis2
> >>
> >>
> >>
> >>
> >> http://ws.apache.org/axis2/0_93/adb/adb-howto.html says not
> >> supported - From the URL it looks like this link is for version 0.93 of
> >> Axis2
> >>
> >> http://wso2.org/library/2670 says supported - In the
> article,
> >it
> >> says that it is for version 1.3 of Axis2
> >>
> >>
> >>
> >> So I guess that depends on what version you are using.
> >>
> >>
> >>
> >> Thanks
> >>
> >> Raghu
> >>
> >>  
> >>
> >>
> >> From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]
> >>  Sent: Wednesday, October 24, 2007 5:22 PM
> >>  To: axis-user@ws.apache.org
> >>  Subject: [Axis2] XmlSchema choice element not supported, other
> problems
> >>
> >>
> >>
> >> I have found the cause of my wsdl2java problems when I use the default
> >ADB
> >> binding with the options "-o -ss -sd -ssi -f -uw -uri -ns2p" - one of
> the
> >> complex types defined in my wsdl has an xmlschema choice element. That
> >with
> >> the "-uw" option gives
> >> "org.apache.axis2.wsdl.codegen.CodeGenerationException:
> >> Unsupported Schema format for unwrapping! found unknown type but
> expected
> >> Element at

Re: [Axis2] How to specify wsdl operation so that wsdl2java generates method throwing java.lang.RemoteException

[Amila Suriarachchi]

generated stub method already throws this exception isn't?

eg.
public  java.lang.String Echo(

java.lang.String echoIn7)


throws java.rmi.RemoteException

{

Amila.

On 10/26/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
>
>  I am migrating to Axis2 1.3 from Axis1. I have existing code that relies
> on the webservice methods throwing java.lang.RemoteException. Is it
> possible to specify an operation in the wsdl, such that, wsdl2java generates
> methods that throw RemoteException? I know that is not the best way to do it
> – but just for compatibility with existing code.
>
>
>
> Thanks,
>
>
>
> Vish.
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: What's the goal of the changeImportAndIncludeLocations in AxisService ?

[Amila Suriarachchi]

when generating the code wsdl2java it renames the schema and wsdl import
locations.
it copies all the xsd files and wsdl files to the resources folder.

so at the resources folder the schema location would look like this.


but one you depoly the service it should look like this.


the above mentioned method will do this change. So the solution for your
problem is
not to change the generated schema locations.

Amila.




On 10/25/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>
> Hi Amila,
>
> Will you be able to have a look at this issue ?
>
>
> Thanks
> Deepal
>
> Vincent Brabant wrote:
> > Hello the list.
> > We are using Axis2 1.3 and the wsdl2java under JDK 1.4
> > Near everything is working like a charm except the following.
> >
> > We put in the services.xml the parameter useOriginalwsdl to true.
> > It means that NORMALLY, the original wsdl should be returned like it,
> without
> > any modification.
> >
> > But it's not the case. The "original wsdl" is modified.
> > It's modified by the fact the changeImportAndIncludeLocations of the
> > AxisService class is called.
> >
> > the question is why that method is called ? What's the goal of such a
> method ?
> >
> > Now, in place of having something like that
> > http://myrepository/mySchema.xsd"; />
> > I have now
> > http://myrepository/mySchema.xsd"; />
> >
> > Any reason why ?
> >
> > Because, in our case, a client that want to call my wsdl can't use the
> returned
> > wsdl. Because schemaLocation means nothing for the client.
> >
> > P.S. such modification has been done in SVN the 3rd july 2007 (SVN
> Commit
> > 552837) by amilas.
> >
> > Vincent Brabant
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
> 
> "The highest tower is built one brick at a time"
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] out of memory

[Amila Suriarachchi]

isn't there any problem when you generate the code for each wsdl seperately?

can you investigate this and see what objects creates more and what objects
create this problem?

Amila.

On 10/25/07, Peter A. Kirk <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I am trying to track down a "java.lang.OutOfMemoryError: Java heap
> space" exception in my application.
>
> I am not sure exactly where the problem lies, but possibly something to
> do with CodeGenerationEngine.
>
> My program generates web-services on the fly, and I use Axis2 to help me
> along. The out of memory problem occurs if I am generating lots of
> web-services in a loop.
>
> For example, if I write a large loop like the following, I get an error.
> (Note this is a boiled down version of my actual code which does a lot
> more stuff - and usually I get the exception after 20 iterations or so).
>
> Am I doing something wrong here, or is there a limitation with the
> CodeGenerationEngine?
>
>
> String[] parms = new String[] {"-o", "c:/temp", "-sd", "-ss", "-S", ".",
> "-R", ".", "--noMessageReceiver", "--noBuildXML", "--noWSDL", "-uri",
> "c:/temp/exmployee.wsdl" };
>
> CommandLineOptionParser parser = new CommandLineOptionParser(parms);
>
> try
> {
> for (int i=0;i<400;i++)
> {
> CodeGenerationEngine engine = new CodeGenerationEngine(parser);
> engine.generate();
> }
> }
> catch (Exception e)
> {
> System.out.println("Error " + e.getMessage());
> }
>
> Thanks,
> Peter
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Case of method names generated by wsdl2java

[Amila Suriarachchi]

On 10/25/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
>
>
>
> I noticed following differences in wsdl2java behavior in axis2 1.3 as
> against axis1 1.4:
>
>
>
>1. Axis2 retains case of the operations for method names. Axis 1
>would start the method name in lowercase and keep other letters from
>operation name in same case. I liked this – is there any way to achieve the
>same with axis2?
>
>
i'll check this.


>1. Axis 1 would correctly translate empty operation message outputs
>as void methods (these are cases where the schema types defined for these
>message parts do not contain any elements) – Axis2 does not do that. While
>this is not a bug deal - any suggestion on how to achieve same behavior 
> with
>axis2 are welcome.
>
>
I have fixed this will commit soon.

Amila.

Thanks,
>
>
>
> Vish.
>
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] 1.3 wsdl2java generates code with missing methods

[Amila Suriarachchi]

I have fixed this issue locally. will commit soon.

Amila.

On 10/25/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
>
>  A quick clarification – the MessageReceiverInOut class generated by
> wsdl2java contains references to the missing methods. As this is an
> autogenerated class, I do not want to edit it myself to remove these
> problems.
>
>
>
> Any insights?
>
>
>   --
>
> *From:* Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, October 23, 2007 5:25 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Axis2 1.3 wsdl2java generates code with missing methods
>
>
>
> I am using wsdl2java to generate java code from a wsdl using wsdl2java
> options "-o -ss -sd -ssi -f -uw -uri -ns2p". The result includes a
> MessageReceiverInOut class that is missing a method resulting in a
> compiletime error "method wrapIsUploadAllowed(OperationStatusType) is
> undefined for the type …MessageReceiverInOut".
>
>
>
> I observed that this seems to happen when wsdl parts in different messages
> refer to the same complex type. In such cases, the wrap methods in the
> MessageReceiver class for the first operation is created while that for the
> other one is not created. E.g. in this case the method 
> wrapUpload(OperationStatusType)
> gets created while wrapIsUploadAllowed(OperationStatusType) is missing.
>
>
>
> Wsdl snippet is included below.
>
>
>
> Is this a bug?
>
>
>
>
>
>  name="OperationStatusType">
>
> 
>
>  name="successFlag" type="s:boolean"/>
>
>  name="messageLevel" type="s:string"/>
>
>  name="messageCode" type="s:string"/>
>
>  name="message" type="s:string"/>
>
> 
>
> 
>
>  name="OperationStatusElement" type="tns:OperationStatusType"/>
>
>
>
>  name="UploadRequestElement">
>
> 
>
> 
>
>
> 
>
>
> 
>
>
> 
>
> 
>
> >
>
> 
>
>
>
>  name="IsUploadAllowedRequestElement">
>
> 
>
> 
>
>
> 
>
>
> 
>
>
> 
>
> 
>
> 
>
> 
>
> … 
>
>  element="tns:UploadRequestElement">
>
> 
>
> 
>
>  element="tns:OperationStatusElement">
>
> 
>
>
>
> 
>
>  element="tns:IsUploadAllowedRequestElement">
>
> 
>
> 
>
>  element="tns:OperationStatusElement">
>
> 
>
> …
>
> 
>
>  message="tns:UploadRequest">
>
>  message="tns:UploadResponse">
>
> 
>
> 
>
>  message="tns:IsUploadAllowedRequest">
>
>  message="tns:IsUploadAllowedResponse">
>
> 
>
> …
>
> http://schemas.xmlsoap.org/soap/http"; style="document"/>
>
> 
>
>  style="document"/>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>  style="document"/>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> …
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Amila Suriarachchi]

On 10/24/07, Raghu Upadhyayula <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
>
>
> I have a problem with the soap:address location generated when
> I browse the WSDL in the browser.
>
>
>
> I'm using Axis2 1.3.
>
>
>
> I'm looking at the WSDL in the browser using
> http://ws.qa.company.com/webservices/services/MyWSService?wsdl
>
>
>
> I get the WSDL and the soap:address location in the WSDL looks
> like   http://10.5.2.182:80/webservices/services/MyWSService
> * />
>
>
>
> But then problem is with the IP Address coming in the
> soap:address location 10.5.2.182 is not a public IP that is accessible
> from Internet.
>
>
>
> What changes should I do to change the soap:address location
> to look like
>
>  http://ws.qa.company.com/webservices/services/MyWSService
> * />
>
>
>
> Another thing, I found is that this is working fine if I use *
> ?wsdl2* in the URL above.
>
>
>
> *Note:*
>
> In my *services.xml* I have *useOriginalWSDL* property set to
> *true* and *modifyUserWSDLPortAddress* was also set to *true*.
>
>
>
> I've tried changing *modifyUserWSDLPortAddress* to *false*,
> but what happened in that case was the soap:address location was not
> modified at all.
>
>
>
> The soap:address location case as
> http://localhost:80/webservices/services/MyWSServicebecause
>  the original WSDL had this address in the soap:address location,
> since the localhost was coming as it, I've change the *
> modifyUserWSDLPortAddress* property back to true.
>

why don't you change the soap:address in wsdl file to the correct one?

Amila.

Thanks in Advance.
>
> Raghu
>
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: nested complex types

[Amila Suriarachchi]

may be a problem with the adb schema compiler.
can you send your wsdl and the schema files?

Amila.

On 10/24/07, csanders <[EMAIL PROTECTED]> wrote:
>
> Ok thanks for your response.
>
> On Wed, 2007-10-24 at 15:41 +0100, Gudla, Natraj (GE Money, consultant)
> wrote:
> > I have used wsdl2java with axis2 1.2. It might be worth having a close
> look at your wsdl verifying your element and type references.
> >
> > I am really busy with my work otherwise i would have looked at your
> wsdl.
> >
> > -Original Message-
> > From: csanders [mailto:[EMAIL PROTECTED]
> > Sent: 24 October 2007 15:29
> > To: axis-user@ws.apache.org
> > Subject: RE: nested complex types
> >
> >
> > Both of those changes made wsdl2java segfault with antlr errors.  Did
> > you do this using axis2 or axis1 ?
> >
> > It seems their must be something simple I'm doing wrong, it can't be
> > this hard to get it to generate code that works.
> >
> >
> > On Wed, 2007-10-24 at 08:42 +0100, Gudla, Natraj (GE Money, consultant)
> > wrote:
> > > Hi,
> > >
> > > It depends on where and how you are refer to "CompanyBasicInfo". From
> your code i understand this is an element in the first place having a
> complex type. So in your wsdl this should be included as a ref=""  name="" ref="CompanyBasicInfo">. You might must be having your current as
> .
> > >
> > > When i faced this, i solved it as the above. CompanyBasicInfo is an
> element and you refer it as a type in wsdl, hence the error "Type is
> missing". Either change your schema to make CompanyBasicInfo as an
> independant type OR change your wsdl to create a reference.
> > >
> > > hope this helps.
> > >
> > > Cheers
> > > Natraj.
> > >
> > > -Original Message-
> > > From: csanders [mailto:[EMAIL PROTECTED]
> > > Sent: 23 October 2007 21:14
> > > To: axis-user@ws.apache.org
> > > Subject: nested complex types
> > >
> > >
> > > Hi all :).
> > >
> > > I'm having some trouble getting nested complex types to work
> correctly.
> > > I'm noticing that for members of the generated class, instead of using
> > > the generated Wrapper class ( which it does generate ) , it uses
> > > OMElement.
> > >
> > > When I run wsdl2java I get several warnings about missing types, for
> > > example :
> > >
> > > [WARN] Type {urn:beagle}CompanyBasicInfo missing!
> > >
> > > I noticed that the items that don't give me warnings are declared like
> > > this:
> > >
> > >   
> > >
> > >   > > maxOccurs="1"/>
> > >   > > maxOccurs="1"/>
> > >
> > >   
> > >
> > > and all the ones that it complains are missing are declared like:
> > >
> > >   
> > >
> > > 
> > >   maxOccurs="1"/>
> > >   > >   > > maxOccurs="1"/>
> > >
> > > ...
> > >
> > > 
> > >
> > >   
> > >
> > > The wsdl file I'm using was created by gSOAP, and I'm using Axis2-1.3,
> > > and java1.6 on ubuntu amd64.
> > >
> > > Thanks!
> > > Charlie
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

SOAP request size

[Daniel JavaDev]

Hi all,

I'm finding it difficult to calculate the total size of my SOAP requests to
a remote web service.
This is important because the web service in question refuses requests that
go over a certain limit, and such limit takes into account the whole HTTP
request size (including HTTP headers, etc).

There doesn't seem to be any API call that returns the content-length of my
request.

Can anyone provide any hints with regards to this?

Cheers

Dan

Re: [Axis2]will Axis2 1.3 client work well with JAX-RPC service ?

[Amila Suriarachchi]

On 10/24/07, Ashok Kumar Rajendran <[EMAIL PROTECTED]> wrote:
>
> Thanks Amila ,
>
> I checked the wsdl Its   Document literal service., So i can use Axis2 . I
> am able to generate my stubs code using ADB as data binding.
>
> So is that means every thing is ok to start implementation part  ?
>
> Will Axis2  supports Proxy authentication to connect to a web service ?
>

yes,
http://wso2.org/library/230#PROXY


Regards,
> Ashok
>
>
> On 10/24/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On 10/24/07, Ashok Kumar Rajendran < [EMAIL PROTECTED]> wrote:
> > >
> > > Hi all ,
> > >
> > >   I am a novice user of Axis2 . I  have a few questions  .We have a
> > > web service which is implemented using JAXRPC . we need to write a client
> > > application for it .
> > >
> >
> > does this have use rpc/encoded style. if so you can not use Axis2. other
> > wise you can.
> >
> >
> >  Will a web service cilent (with ADB as data binding )written using
> > > Axis2 1.3  works well with this JAX-RPC service ?
> > >
> >
> > depends on the complexity of your schema. if it contains only the adb
> > supported elements then you can use ADB. othewise use Xml beans. This best
> > way to know this is to generate code and see.
> >
> >
> >  or we have to switch back to Axis 1.4 ?
> > >
> > > can we have different XML binding method in client and server side ?
> > > say ADB in client and XML-Beans or JAXB in server side ?
> > >
> >
> > of course. even you can have different language implementations.
> > actually this is the main idea of the web services. What matters is the soap
> > message passes through the wire.
> >
> > Amila.
> >
> >
> >  I will really appreciate your help.
> > >
> > > Thanks,
> > > Ashok
> > >
> > >
> > >
> >
> >
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
>
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

RE: ArrayOfString gives a java.lang.ClassCastException

[Archibald Moepi]

Hi,
I've discovered that when I call the method it reaches the .Net
webservice and throws the exception when it's returning the results. I
found this other exception in the logs, 
 
StandardManager[/axis] Session event listener threw exception
java.lang.IllegalStateException: getAttribute: Session already
invalidated
 at
org.apache.catalina.session.StandardSession.getAttribute(StandardSession
.java:953)
 at
org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardS
essionFacade.java:171)
 at
org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(Ax
isHTTPSessionListener.java:43)
 at
org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(
AxisHTTPSessionListener.java:72)
 at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:
658)
 at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:
607)
 at
org.apache.catalina.session.StandardManager.processExpires(StandardManag
er.java:793)
 at
org.apache.catalina.session.StandardManager.run(StandardManager.java:870
)
 at java.lang.Thread.run(Thread.java:534)
 
can these 2 exceptions be related?
 
I'm running:
java=1.4.2_04-b05
axis1.2
Tomcat 4.1.30



From: Archibald Moepi [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 25, 2007 5:00 PM
To: axis-user@ws.apache.org
Subject: ArrayOfString gives a java.lang.ClassCastException


Hi,
 
I've got a .Net webservice and calling it using a java axis client. I've
got a method that takes an int as a parameter and returns a String array
and when I generated the classes using wsdl2java it created a class
called ArrayOfString. When I call this  method it executes fine for the
first couple of times and then it starts giving a
java.lang.ClassCastException, but when I restart Tomcat it works fine
again for the first couple of times then it starts breaking again.
What exactly is wrong?
Here is the exception:
 
AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.lang.IllegalArgumentException:
[EMAIL PROTECTED]
 faultActor: 
 faultNode: 
 faultDetail: 
 
{http://xml.apache.org/axis/}stackTrace:java.lang.IllegalArgumentExcepti
on: [EMAIL PROTECTED]
 at
org.apache.axis.encoding.ser.BeanPropertyTarget.set(BeanPropertyTarget.j
ava:142)
 at
org.apache.axis.encoding.DeserializerImpl.valueComplete(DeserializerImpl
.java:249)
 at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja
va:509)
 at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1083)
 at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
171)
 at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
 at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:238)
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)
 at org.apache.axis.client.Call.invoke(Call.java:2402)
 at org.apache.axis.client.Call.invoke(Call.java:2301)
 at org.apache.axis.client.Call.invoke(Call.java:1758)
 at org.tempuri.ServiceSoapStub.getFields(ServiceSoapStub.java:729)
 at
za.co.test.common.service.ServiceFacade.loadFields(ServiceFacade.java:13
1)
 at za.co.test.ca.MyServlet.processRequest(MyServlet.java:47)
 at za.co.test.ca.MyServlet.doGet(MyServlet.java:109)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:256)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241
4)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:171)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:163)
 at
org.apache.catalina.core.StandardPipeline$Stan

Re: Unrecognized elment in response xml (axis 2)

[harsha kilangodi]

Hi Deepal
  thanks for the information. The issues are already created in JIRA the issue 
numbers  are TUSCANY-1788
AXIS2C-97 
AXIS2-3281 
  Some of the issues related to xsi: name space are already fixed . Could you 
give me the url to download latest jars.
   
  I couldn't find the stax parser in resin/lib. I have downloaded the stax 
parser but I dont know how to set it in resin.conf.   I have tried xlan and 
xercess paresers but the problem is not solved with that. Please help me. 
   
  Thanks
  Harsha
  

Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
  hi harsha,
I know the issues and I have encountered the problem a several times ,
it was mainly due to namespaece context handling in underline xml
parser. Can you please find the stax parser you can find in resin. In
the meantime please create a JIRA

Thanks
Deepal
> Hi
> I am trying to port web services deployed on resin-2.1.20 (axis2)
> to resin-3.1.3 server. The response xml file contains some
> unrecognizable element which gives parse exception. The exception is
> given below
>
> Reference to undeclared namespace prefix: 'xsi'. Error processing
> resource 'file:///C:/Documents and Settings/harsharaja/De...
>
> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>..
>
>
> We get some element in the response like
>
> > xmlns:ax21="http://beans.ws30.xora.com/xsd";>
>
> but URI is not coming in the xml header. We face problem when the data
> type is String and the value is null.
>
> I am using axis2-1.3 , Resin-3.1.3 server, JDK 1.5 and using SOAP-UI
> tool for testing. I have attached the wsdl (TimeTrackServices301.xml) and
> the response xml (Response.xml). Try to open Response.xml in Internet
> Explorer you will get the above error message. Please help me to solve
> this problem.
>
> With regards
> Harsha
>
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> 
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: AXIS2 and .NET Interop

[Maxim Geraskyn]

Paul,

> I'm surprised .NET can't handle HTTP chunking... its a common approach.
>
> Paul

I'm not so experienced in web technologies, but this is the first time
I see SOAP client uses "chunked". Normally "content-length" header is
used by default ( AXIS 1.*, SoapUI, .NET )

Maxim

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: axis2 1.3 wsa:To header usage

[David Illsley]

Sure,
The WS-A WG didn't really define much on the mlti-hop scenario so the
specifications don't help much here. It is worth pointing out that in
the interops we did, it became apparent that SOAP Binding 3.5 [1] was
interpreted by different people in different ways, and that the
'safest' route is to put the transport address you're sending the
message to in the wsa:To.

All that said, if you want to raise a JIRA about the fact that the
Axis2 WS-A Handlers don't process soap role/actor attributes, (I think
a different scenario than you're talking about) I'd be willing to take
a look.
Cheers,
David

[1] http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/#soaphdrvtransport

On 26/10/2007, Brian De Pradine <[EMAIL PROTECTED]> wrote:
>
> Hello Erwin,
>
> The thing about intermediaries is that they are usually there to hide the
> address of the of the ultimate receiver ( imagine a gateway server or proxy
> for instance ). In that case flowing the address of the ultimate receiver
> across the intermediary would tend to make having the intermediary a bit
> pointless.
>
> Anyone else care to chime in?
>
>  Cheers
>
>  Brian DePradine
>  Web Services Development
>  IBM Hursley
>  External  +44 (0) 1962 816319 Internal 246319
>
>  If you can't find the time to do it right the first time, where will you
> find the time to do it again?
>
>
> "Erwin Reinhoud" <[EMAIL PROTECTED]> wrote on 25/10/2007 15:54:10:
>
>
>  > Hello all,
>  >
>  > Don't know if this is the correct location to post this, so please
>  > let me know if not.
>  >
>  > I create a client and want to make a call with WS-Addressing
>  > headers. What i noticed is that often there is a strong relation
>  > between the wsa:To value and the actual http uri being used to send
>  > the message to the next hop. I thought the wsa:To could contain the
>  > (logical) value of the end destination. So if there are two
>  > intermediairies than the wsa:To can stay the same over all hops.
>  > Currently this does not seem to be. Is my perception of the wsa:To wrong?
>  >
>  > ServiceClient client = new ServiceClient(context,null);
>  > Options ops = new Options();
>  > Endpointreference to = new Endpointreference("finalDest");
>  > ops.setTo(to);
>  > Endpointreference epr = new Endpointreference("http:
>  > //localhost/axis2/services/myservice");
>  > client.setoptions(ops);
>  > client.setTargetEpr(epr);
>  >
>  > The ops.setTo value will be used to dispatch the message.
>  >
>  >
>  > Kind regards,
>  > Erwin
>  >
>  >
>  >
>  >
> -
>  > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
>  > For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>
>
>
>  
>
>
>
>
> Unless stated otherwise above:
>  IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
>  Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
>
>
>
>
>
>
>


-- 
David Illsley - IBM Web Services Development

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]