Re: Error merging include schema

Muralidaran, Please ask these types of questions on the axis-user list rather than the axis-dev list. I suspect your problem is caused by the fact that you have a number of schemas that do not specify targetNamespaces, and that you import these schemas without specifying a namespace. I believe th

Re: FW: Why this wsdl is not valid Wsdl

Change: to: Anne On Tue, Apr 1, 2008 at 10:16 AM, Dayalan, Ravikumar <[EMAIL PROTECTED]> wrote: > > > > > > -Original Message- > From: Dayalan, Ravikumar > Sent: Tuesday, April 01, 2008 7:45 PM > To: 'axis-dev@ws.apache.org' > Subject:Why this wsdl is

Re: MTOM Communication with .NET

All web services created using .NET have an associated WSDL. You can obtain the WSDL from the .NET service by appending "?wsdl" to the service endpoint URL. e.g., if the endpoint URL is "http://www.example.org/service.asmx";, you can get the WSDL from "http://www.example.org/service.asmx?wsdl";. A

Re: Interopertability issues with Axis2 ADB and .NET client

You'll also get better results if you adopt a WSDL-first development model. Anne On Feb 6, 2008 7:30 PM, keith chapman <[EMAIL PROTECTED]> wrote: > AFAIK some fixes went in after 1.3 (Mainly on security related stuff). > So its advisable to use the SNAPSHOT build. > > Thanks, > Keith. > > > On Fe

Re: [Axis2] Soap Encoding support with ADB

Amila, SOAP encoding is much more likely to be used in a code-first scenario, but you must make sure that it also works in a WSDL-first scenario. Regarding one of your questions, you would never see an element defined as follows: > > > > >

Re: [Axis2] Release plan and road map for Axis2 1.4 release

Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > > > On Dec 22, 2007 7:49 PM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > I'd like to see a WS-I BP 1.1 compliance option added. > > Axis2 do have most of the Basic profile features. Do we have to run any >

Re: [Axis2] Release plan and road map for Axis2 1.4 release

I'd like to see a WS-I BP 1.1 compliance option added. Anne On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Devs and Users, > > I saw a number of users asking about the next release of Axis2 , so I > think its good time to think about that. We did our last release on >

Re: Namespace problem of Array element.

r: > 1.The same WSDL why axis2 behavior differs with Axis 1.4? > 2.If it's qualified why not use " http://math.samples"; as its namespace > instead of empty? > > Regards, > Terry > > > > On Nov 27, 2007 10:23 PM, Anne Thomas Manes <[EMAIL PROT

Re: Namespace problem of Array element.

nne On Nov 27, 2007 9:10 AM, Terry Zhou <[EMAIL PROTECTED]> wrote: > Sorry, Anne, I just think this maybe an issue of Axis 1.4, developer may > know more about it. > > Thanks, > Terry > > > > On Nov 27, 2007 10:02 PM, Anne Thomas Manes < [EMAIL PROTECTED]> wr

Re: Namespace problem of Array element.

Please send questions related to using Axis and Axis2 to the axis-user list. The axis-dev list is for issues related to developing the Axis and Axis2 frameworks themselves. Anne On Nov 27, 2007 5:31 AM, Terry Zhou <[EMAIL PROTECTED]> wrote: > Hi, all > > Is there any configuration to prevent the

Re: axis 1.4 and Basic Profile

Kumar, You can implement WS-I BP 1.1 compliant service endpoints using Axis 1.4. Axis 1.4 processes SOAP messages in accordance with the profile. Anne On Nov 16, 2007 2:27 AM, Iyengar, Kumar <[EMAIL PROTECTED]> wrote: > Hi Lawrence, > > I do mean WS-I Basic Profile. If I understand correctly Bas

Re: Simple suggestion for namespaces

Would it be possible to allow the organization to configure a default namespace format? I recommend using URNs for namespaces and giving the RDDL a resolvable URL. Anne On Nov 8, 2007 7:33 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > When we create default namespaces, why don't we have an opti

Re: [Axis2] WS-policy client support

That's a proprietary policy assertion language. It's supported only by BEA products. Talk to BEA and convince them to add support for the standard OASIS WS-SecurityPolicy. Anne On 10/31/07, Feng Lu <[EMAIL PROTECTED]> wrote: > > Hello friends, > > I am wondering whether Axis2 support WS-policy cl

Re: rpc encoding in Axis2

Axis2 does not support SOAP encoding. Use Axis 1.4 instead. Anne On 10/26/07, Iyengar, Kumar <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > > We have a program that consumes external web services using Axis. I am > currently upgrading the program to use Axis2. Our program works with Web > Ser

Re: axis2 access .net web service

Please send this type of user request to axis-user, not axis-dev. Anne On 9/23/07, zhrb <[EMAIL PROTECTED]> wrote: > > Hello, > > I am now using axis2 accessing .net web service following samples of > "EchoNonBlockingDualClient".The userguide just mentions the condition of > both web service and

Re: Axis2 access .net web service

I believe you are not creating your payload properly. I'm not an expert on AXIOM, but I think it should look like this: public static OMElement getContentOMElement() { OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace omNs = fac.createOMNamespace("http://tempuri.or

Re: Axis2 access .net web service

Also -- please ask these questions on the axis-user list rather than the axis-dev list. Anne On 9/22/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Please provide the WSDL. > > Anne > > On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote: > > > > Hello, >

Re: Axis2 access .net web service

Please provide the WSDL. Anne On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote: > > Hello, > > I am now trying to using axis2 as client to access .net web service. > > .net web service as follows: > > public string HelloWorld(string name) > { >return "Hello World"+name; > } > > Axis2 client co

Re: [Fwd: Re: Java2WSDL output for no parameters or void return type?]

Deepal, Per the wrapped convention, if you have the following interface: public String foo(); java2wsdl should generate an input element called "foo": And "foo" must be defined as: See the JAX-WS spec for the specific requirements of the wrapped convention, or my blog for a quick

Re: axis[1.3] Change in Rest Support

Do you mean Axis2 1.3? Axis 1.3 doesn't support REST. In the future, please send these requests to the axis-user group rather than the axis-dev list. Anne On 9/13/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > Hi all, > > I am using axis 1.3 and i am trying to execute a simple web service using

Re: AXIS2 Skeleton and Stub Generation

Axis2 support of RPC/literal is sketchy at best, considering that you must edit the WSDL to tell Axis2 how to handle it. See http://ws.apache.org/axis2/1_3/Axis2-rpc-support.html Anne On 8/20/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > > On 8/19/07, Anne Thomas Manes &l

Re: AXIS2 Skeleton and Stub Generation

Use of types in a message part (rather than an element) indicates that you are using an RPC style service. You should be using document style with Axis2. Anne On 8/19/07, Karuppusamy, Thamayanthi (Consultant) <[EMAIL PROTECTED]> wrote: > > > Hi, > > How the stub and skeleton class are generated

Re: Bug? SimpleType enumeration output is incorrect.

That's an inappropriate restriction. XML has no such "reserved words" constraints. If Axis2 has a problem dealing with a valid local name, it's a bug. Anne On 8/16/07, WJ Krpelan <[EMAIL PROTECTED]> wrote: > Hi > Methinks you shouldn't use "type" as element name, and > neither "element" nor "attr

Re: Fwd: [AXIOM] Undeclare default namespace

By "undeclare" I believe Xinjun means that he wants to declare the default namespace as no value, e.g., xmlns="". Anne On 7/23/07, Xinjun Chen <[EMAIL PROTECTED]> wrote: Hi Chinthaka, I have an element bValue . I have another element which is created by another OMStaxBuilder. is unqualif

Re: problem with SOAPFault custom error tags.

Is this the verbatim error you receive from .NET? I ask because it is not a valid SOAP Fault. The , , and elements must be unqualified. Also, the namespace prefix for the element has not been declared. These errors are the reason why Axis cannot properly interpret the fault. Anne On 7/16/07,

Re: Jxta bridge

Check out http://soap.jxta.org/. Anne On 3/22/07, Скворцов Никита <[EMAIL PROTECTED]> wrote: Good time of day, mighty All! I am looking for a project called Jxta Bridge. It's aim was to create combination of Axis WebService framework and Jxta P2P technologies. It was announced at 2002 by Ke

Re: Problem with the namespace prefix in Axis

rite my own HTTPSender class. The entire message I response I receive in the bytes, will have to be converted to an XML and then the data extracted without the interferrence of AXIS? Thanks regards, Anup Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Prefixes are significant when the XML mes

Re: Problem with the namespace prefix in Axis

nks & regards, Anup Anne Thomas Manes <[EMAIL PROTECTED]> wrote: As long as the prefix maps to the correct namespace URI, the messages are semantically identical. Your handler should be to handle any prefix string. Anne On 2/27/07, anup bansal wrote: > Hi All, > > I am us

Re: Possible Axis 1.4 Bug

o work with Netbeans, but after that, I didn´t change the Axis related part at all! So, I take note, in conclusion, in your opinion, I should regenerate the Java Object (Sumador) from which Axis generates the Web service. Am I right? -- *De:* Anne Thomas Manes [mailto:

Re: Possible Axis 1.4 Bug

hema to the WSDL under the _"__http://stiperez:7070/axis/services/Sumador"; namespace._ What's wrong with this?? Consider that the In-Line validator of WSDL schemas doesn´t work properly!! Did you then regen the service skeleton using wsdl2java? Anne On 3/7/07, Anne Thomas Manes &

Re: Possible Axis 1.4 Bug

In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! -- *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED] *Enviado el:* miércoles, 07 de marzo de 2007 15:29 *Para:* axis-dev@ws.apache.org *Asunto:* Re: Possible Axis 1.4 Bug Please su

Re: Possible Axis 1.4 Bug

Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining

Re: [axis2] How to Configure/Enable Axis2 for REST

I haven't said anything about this before, but it's really starting to bother me. There's a real problem with the idea of specifying an "operation" with a service that supposed to be RESTful. Keep in mind that REST is an architectural style. Rule number one when following REST architectural princ

Re: qn about binding in document/literal message mode

Please file a JIRA. On 3/4/07, Prasad Sarma <[EMAIL PROTECTED]> wrote: Hi All, When I am creating wsdl from my source code , Binding is "document/literal" messaging mode ( I am not sure how to chose the mode explicitly using the code generation wizard in axis2) I could see namespace attribute

Re: WSDL2Java Code will not compile

Robert, Both your WSDL and imported schema have errors. The WSDL does not define its faults properly. The names specified in the binding must correspond to the names specified in the portType: The portType is defined as: But the binding is d

Re: Problem with the namespace prefix in Axis

As long as the prefix maps to the correct namespace URI, the messages are semantically identical. Your handler should be to handle any prefix string. Anne On 2/27/07, anup bansal <[EMAIL PROTECTED]> wrote: Hi All, I am using Axis 1.4 for accessing a third party weservice. I am able to connect

Re: Issue with rpc/literal wsdl processing

Small correction: On 2/26/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: hi. please see the issue https://issues.apache.org/jira/browse/AXIS2-2246 For rpc/literal messages, we have to generate the wrapper elements. i.e we have to generate an outer element with local part equals to operation

Re: problems axis newbie!!! - The method fromOM

I've raised this issue before, but it never seems to get resolved. Note that the generated WSDL is document style, but the definitions include a namespace attribute. This should not be the case. The namespace attribute should be generated only for RPC style. Meanwhile -- John -- can you tell us

Re: Generating wsdl for url

Either deploy the service using the RPC message receiver, or write your own WSDL and add it to the META-INF directory. Anne On 2/13/07, John McCosker <[EMAIL PROTECTED]> wrote: Hi I'm using Axis2 and I have deployed a web service. I am now trying to generate client stubs but I am getting the fo

Re: Latest Axis2 performance benchmarking.... this time against XFire!

It should be "with maybe the exception of trading floors", which means that Axis2 should deliver sufficient perfromance to support most application, except perhaps for trading applications, i.e., applications with exceptionally high performance and scalability requirements. On 1/31/07, robert laz

Re: [axis2] simplecontent that refers itself - is that valid?

Not valid. On 1/31/07, Eric Deshayes <[EMAIL PROTECTED]> wrote: Hi, I am not sure of the validity of that xsd type. Thanks for answering me... Eric - To unsubscribe, e-mail: [EMAIL PRO

Re: not able to retrieve attribute (elements work fine)

without anything special being done to cause it. - Dennis Anne Thomas Manes wrote: > attributeFormDefault only applies to local attributes (those defined > within a complexType). But this attribute is defined as a global > attribute (a direct child of the ). All entities (elements, >

Re: not able to retrieve attribute (elements work fine)

cify attributeFormDefault="qualified", so why are you saying the attribute needs to be namespace qualified? - Dennis Anne Thomas Manes wrote: > The attribute is defined as a global attribute in the jxdm.xsd, > therefore it must be namespace qualified. The error is in the m

Re: not able to retrieve attribute (elements work fine)

of bug fixes in that, and it's possible this problem has been corrected. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Anne Thomas Manes wrote: &

Re: not able to retrieve attribute (elements work fine)

Danny, According to your schema, the attribute should be namespace qualified. Hence the message you get back from the service should look like this: http://jxdm.ws.doc.state.sc.us"; xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> Rebecca Mace Smith The reason why your request for

Re: FW: Needs help in writing WSDL

ec 27, 2006 12:03:27 PM org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver resolveEntity [wsdl2java] INFO: Resolving schema with publicId [http://www.it.ojp.gov/jxdm/ncic_2000/1.0.2] and systemId [jxdm/ncic_2000/1.0.2/ncic_2000.xsd] [wsdl2java] Dec 27, 2006 12:03:27 PM org.apache.axis2.xmlbeans.C

Re: Questions about "Unsupported content Simple Type Union"

It sounds like the schema defines the type more than once. On 11/2/06, Jose Manuel Valladares Pernas <[EMAIL PROTECTED]> wrote: When I use xmlbeans I get an exception because of "Duplicate global type": Duplicate global type: [EMAIL PROTECTED]://www.opentravel.org/OTA/2003/05 (Original global t

Re: axis2 1.1

RC1 was released on Oct 9: Download locations : * binary and source distributions - http://people.apache.org/~thilina/axis2/1.1-RC1/ * jars http://people.apache.org/~thilina/maven/org.apache.axis2/jars/ * mars (addressing and SOAP monitor) http://people.apache.org/~thilina/maven/org.apache.axis

Re: Bean Serialization

Willem, You should send this type of user question to the axis-user list rather than to the axis-dev list. As a starting point, I recommend you read these documents: http://ws.apache.org/axis/java/client-side-axis.html http://ws.apache.org/axis/java/user-guide.html You should also find these ar

Re: issue-clarification 'incorrect local element definition with elementFormDefault=qualified' or not ?

There are a great many bugs in Axis 1.2RC. On 10/19/06, Andreas Schöller <[EMAIL PROTECTED]> wrote: Am 19.10.2006 um 18:51 schrieb Anne Thomas Manes: > Please try it with Axis 1.4. Hello Anne Thomas Manes, thanks for your advice, and i'd really like to do so, but i simply

Re: issue-clarification 'incorrect local element definition with elementFormDefault=qualified' or not ?

Please try it with Axis 1.4. On 10/18/06, Andreas Schöller <[EMAIL PROTECTED]> wrote: Hello axis developers, while trying to access a axis-driven webservice using the ZSI-modul from python i ran into some problems. I reported back to the python- developing team as i believed the cause of troubl

Re: WS-callback support in axis

WS-Callback has not been accepted by the industry. (Only BEA implements it.) It has been superceded by WS-Addressing. Anne On 10/15/06, Rodrigue Butaye <[EMAIL PROTECTED]> wrote: Hello, Is there in Axis a support for the ws-callback protocol as defined by BEA(http://dev2dev.bea.com/webservices

Re: Error occurred while testing the CodeGen Tool

See http://ws.apache.org/axis2/1_0/jibx/jibx-codegen-integration.html and http://jibx.sourceforge.net/tutorial/binding-tutorial.html. The binding file specifies how to map Java object to XML. Anne On 9/26/06, Evanthika Amarasiri <[EMAIL PROTECTED]> wrote: Hi, I was testing the Code Gener

Re: Axis2 1.0 beta?

It's not a "beta" release, but it also isn't a stable, production-quality release. Given the number of bugs, it should not have been released as a 1.0 version. You should wait for 1.1. Anne On 9/22/06, Donald Miller <[EMAIL PROTECTED]> wrote: Thank you for replying so fast! I appreciate it gr

Re: Can I expose services of a new technology as web services?

What's the nature of your "particular technology"? If you can invoke the technology using Java, then you should be able to use Axis to enable it as a web service. Anne On 9/12/06, Domenico Caputi <[EMAIL PROTECTED]> wrote: WJ Krpelan wrote: > Axis is open source, just do it! > Cheers > Wolfgang

Re: maxOccurs Interop Problem

This is a bug in Axis -- please file a bug report in JIRA. On 9/7/06, Amol Ambekar <[EMAIL PROTECTED]> wrote: am using axis 1.4 I have a complex type element called ArrayOfString WSDL Snippet The

Re: [VOTE] Axis2 next release (Axis2 1.1)

If you call it 1.5, then you need to be absolutely certain that it is a solid, reliable, robust release. It doesn't matter how much new stuff has been added -- the major issue with 1.0 was quality. I recommend calling it 1.1. You have to prove yourselves before agrandizing yourselves. Anne On 9/

Re: No deserializer error

You must define a deserializer for your User type. Anne On 8/29/06, Rodrigo Faria <[EMAIL PROTECTED]> wrote: I am facing a "No deserializer" error coming from Apache Axis code. This is the installed version: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.5.3 Created-By: 1.4.1_01-b01 (Sun Micr

Re: [Axis2] Learning Axis & Hair Los

Here's a tutorial on AXIOM: http://ws.apache.org/axis2/1_0/OMTutorial.html (The developers are busy fixing bugs -- unfortunately, the documentation will come later. But please continue to provide constructive criticism. Perhaps you could compile a list of things you found unintelligible and creat

Re: WSDL2Java works for an invalid WSDL

Please note that the first WSDL was not valid. You MUST NOT specify the namespace attribute in the elements when using document style. Anne On 8/8/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: Keith, Can you please file a JIRA with this. Thanks, Chinthaka keith chapman wrote: > Hi, > > I tr

Re: [Axis2]Fwd: Question regarding wsdl level imports in Axis 2 ...

I believe your problem is caused by the section and the in the service WSDL. A WSDL can have only one section. Anne On 8/7/06, Srinath Perera <[EMAIL PROTECTED]> wrote: -- Forwarded message -- From: Vishal Deshpande <[EMAIL PROTECTED]> Date: Aug 7, 2006 3:27 PM Subject: Quest

Re: SwA Axis2 implementation swaRef document literal

s I am not using MTOM in the correct way because the image is being sent base64 encoded and I guess that should be sent in mime type!!! Any suggestion??? Thanks in advanced -Mensaje original----- De: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Enviado el: viernes, 28 de julio de 2006 18:59 Para

Fwd: SwA Axis2 implementation swaRef document literal

htLtpdtLTa9tLt hLsQuyMf0../k4krqa//0g== So I guess I am not using MTOM in the correct way because the image is being sent base64 encoded and I guess that should be sent in mime type!!! Any suggestion??? Thanks in advanced -Mensaje original----- De: Anne Thomas Manes

Re: SwA Axis2 implementation swaRef document literal

ods that receive OMElement object as parameters. But I NEED that the stub has methods that receive DataBinding objects (for example EnqueueImage see WSDL below) as parameters. Any suggestion? Thanks Regards -Mensaje original- De: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Enviado el: vi

Re: SwA Axis2 implementation swaRef document literal

As long as you're using Axis2, I suggest using MTOM rather than SwA. Anne On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote: Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have the addAttachment method, so I don´t know how to send the image and I cannot

Re: axis-mailing-list

See http://ws.apache.org/axis/mail.html. Send a mail to [EMAIL PROTECTED] from the email account that you originally subscribed with. You must then confirm your unsubscription request by replying to the confirmation mail you get. Anne On 7/26/06, Christian Sell <[EMAIL PROTECTED]> wrote: H

Re: AXIS2::Serialization of conplex type throws NPE

One more note: I think you need to use a later build. When using Document style, the definition in the WSDL binding must not specify a namespace attribute. I believe this problem is fixed in the latest build. Anne On 7/12/06, Pradeepta Bhattacharya <[EMAIL PROTECTED]> wrote: Do you mean tha

Re: Null Pointer Exception: BijectiveNSMap.java

I suggest you submit this question to the folks that supplied you with this package: com.ctc.wstx.util.BijectiveNsMap.findPrefixByUri Anne On 7/2/06, Giridhar Manepalli <[EMAIL PROTECTED]> wrote: Hello, I am facing the same problem as this one http://mail-archives.apache.org/mod_mbox

Re: Client using Axis2

Rebuild the service using document/literal. Then you can use Axis2 as an asynchronous client. Given the simplicity of the interface, there's no reason to use rpc/encoded.AnneOn 6/29/06, Marta García Rueda <[EMAIL PROTECTED]> wrote: Thank you very much for your response.I thought use Axis2 because

Re: [Axis2] Unwrapping support - how to maintain the part name reference ?

You would need to use the message name as the namespaceURI to ensure uniqueness. (Notice that your example uses "part1" for both input and output messages for the same operation.)Anne On 6/28/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi all,Dennis has been a bit silent on the mailing list these

Re: Migration Axis 1 to Axis 2

uration?mmm, I just made performace analysis with Jmeter on this services developed in axis 1.2, I wish to develop same service in axis 2.0 to compare performance with axis 2.Someone help me :( :)Thanks-- Initial Header ---From  : "Anne Thomas Manes" [EMAIL PROT

Re: Migration Axis 1 to Axis 2

Fabio,There are errors in your WSDL. You must fix them before you can get Axis2 to work.You've defined the service as document style, but your message parts reference types rather than elements. (A document style service MUST reference elements; and RPC style service MUST reference types.) Either c

Re: [Axis2] Implementing unwrapped (was Re: [Axis2] Planning for Axis2 next rev - 1.1 (?))

Dennis,The terminology is confusing. When using Document style, the message body on the wire must always contain at most one element. When using "non-wrapped" document style, the databinding maps that body element to a value object. When using "wrapped" style, that body element (which has the same

Re: [axis2] - wsdl2java - exception

Please post the WSDL. On 6/23/06, Gmail <[EMAIL PROTECTED]> wrote: I'm new to axis2. I have wsdl from which in axis 1.* I have succesfullygenerated java code, but in axis2 I got following exception:Exception in thread "main"org.apache.axis2.wsdl.codegen.CodeGenerationException :org.apache.axis2.wsd

Re: AXIS1x bug: 2+ operations with same input/output

ng?Why is not soapaction used?Is it the same for Axis2?Greetings.Julio César.>From: "Anne Thomas Manes" < [EMAIL PROTECTED]>>Reply-To: axis-dev@ws.apache.org>To: axis-dev@ws.apache.org>Subject: Re: AXIS1x bug: 2+ operations with same input/output >Date: Sun, 4 Jun 2006

Re: Axis Error - Server

Please post the WSDL.On 6/2/06, Nicolas Guaneme <[EMAIL PROTECTED]> wrote: Hello all,I have a bug with a web service I have 3 method for show I have a problem with a method excatly I run the client an the tcp-mon showthe message that send the client and response the server. this ist

Re: AXIS1x bug: 2+ operations with same input/output

It's not a bug. Each operation must have a unique signature (defined as the qname of the child element of the element).AnneOn 6/3/06, Julio César Pérez Arques <[EMAIL PROTECTED]> wrote: Hello boyz.I am developing a axis ws that has 2 operations with same input/output. Iuse axis 1.4 and wsdl2java.

Re: Error Axis

Please supply the WSDL and the input message.AnneOn 5/23/06, Nicolas Guaneme <[EMAIL PROTECTED] > wrote:Hello , I hava a WS and show me this exception in the TCP-Mon   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd=" http://www.w3.org/2001/XMLSchema"xmlns:xsi="http://www.w3.org/

Re: Help Me!!

What do you mean you can't create a client stub? Whay happens when you try?And what do you mean you never return the soap headers? You have no headers defined in your messages?I did notice that you have what appears to be a typo in the name of the return element -- it's called "tns:getBabkListRespo

Re: ServiceMix

ServiceMix is a CodeHaus project, not an Apache project. You need to ask them what their plans are. See http://servicemix.org/. AnneOn 5/10/06, Arjuna Chala <[EMAIL PROTECTED]> wrote: Is there a plan to build Axis2 support into Apache ServiceMix?

Re: FW: [Axis 1.3] wsdl with import vs. without import

You need to define a targetNamespace for your schema.AnneOn 4/7/06, Dovholuk, Clint <[EMAIL PROTECTED] > wrote: Can anybody point me at my problem with ""?  I added this to my server-config.wsdd... but it didn't 'help' any.. From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]] Sent: Thursda

Re: [Axis2] Schema with no targetNamespace rejected

Here's the email thread:http://marc.theaimsgroup.com/?l=axis-user&m=114348410608730&w=2And here's the standard OTA schema which has no targetNamespace: http://www.opentravel.org/2005B/OTA_SimpleTypes.xsd(You'd think a standards group would have the sense to define a namespace!)Anne On 3/29/06, Denn

Re: [Axis2] Schema with no targetNamespace rejected

I recently responded to a question from someone using the OTA schema which does not declare a targetNamespace (bad form on their part, but such is the case).AnneOn 3/28/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote: Sanjiva Weerawarana wrote:>On Tue, 2006-03-28 at 19:33 +1200, Dennis Sosnoski wrot

Re: [Axis2] Schema with no targetNamespace rejected

I agree with Dennis on this. WSDL 1.1 doesn't *require* that a schema have a targetNamespace. The BP does, but that's a best practice, not a spec requirement. WSDL 2.0 requires that schemas have a targetNamespace, but that doesn't change WSDL 1.1.The better solution is to throw a warning if the ta

Re: java file generated using WSDL2JAVA fail to compile with 'too many parameters' error

The Opportunity complex type has too many child elements to map to a Java object. You'll have to figure out a way to break it into multiple types, or you need to use the messaging API and map it to a DOM.Anne On 3/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:Hi,I have generated java files us

Re: Accessing attachment in message-style or document/literal servic e

Naeem,Please ask user questions on the user discussion list. The dev list is for the folks developing the Axis code base. I don't believe that you can access attachments using the messaging API. I suggest that you switch to the RPC provider. (It supports document/literal.) AnneOn 2/27/06, Naeem Mal

Re: rpc/encoded support?

Axis 2 does not yet support rpc/encoded.On 2/3/06, local-underground <[EMAIL PROTECTED]> wrote: Does Axis2 0.94 support rpc/encoded WSDL2Java code generation?  Also, are there known issues calling a rpc/encoded Web Service?The Web Service I am calling below is rpc/encoded.--- local-underground <[EM

Re: [Axis2] Re: Compliance with Java Web Services APIs

Axis2 supports WS-Addressing. Axis1 supports WS-Addressing via See http://ws.apache.org/addressing/. AnneOn 2/2/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote: Hi,   I am wondering what sort of compliance we have wrt to the Java Web Services API's described in http://java.sun.com/webservices/inde

Re: WSDL 2.0 is a non-goal for Axis2 1.0?

According to the WSDL 2.0 Working Group, they don't expect to produce a Proposed Recommendation until the second half of 2006. We'll be lucky to see WSDL 2.0 finalized before the end of the year. I agree with Dims. WSDL 2.0 should be a non-goal for Axis 2 1.0. AnneOn 1/10/06, Ajith Ranabahu <[EM

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

          Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement(

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

t;[EMAIL PROTECTED]> wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement()

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

orrect?             Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 4:36 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You mu

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

You must use to bring in a schema with the same namespace and to bring in a schema with a different namespace. So you must change this:  

Re: Question concerning criteria of wsdl document for "wrapped" styl e

Dies, You might find my bog entry on the wrapped convention helpful: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html (Check the comments for a couple of corrections to the example WSDL.) Note: If your message definition also contains header parts, Axis 1.2 will not rec

Re: [axis2] WSDL2Code throws NPE on complex type

I agree that the NPE isn't particularly informative, but you do have a number of errors in your WSDL. I suggest you get a WSDL editor with a validation function. The Cape Clear SOA Editor is free and works pretty well. First error: You have two elements defined in your schema named "elementReturn

Re: [Axis2] SOAPMessageContext

+1 to separating the programming model from the implementation model. AnneOn 11/13/05, Paul Fremantle <[EMAIL PROTECTED]> wrote: So I think the approach will work, but we are introducing a performance overhead straight away. I know its just a method call. I would like to try the approach proposed,

Re: Body elements get copied into Headers !

Code? WSDL? WSDD? On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: We are getting pretty strange problem when trying to generate or publish a soap message. All the paremeters which should have been part of the SOPA BODY element are copying into the SOAP headers.The actually body tag is emp

Re: [Axis2] Road Map for next release

I caution you regarding the "XMethods core services". As far as I'm aware, XMethods hasn't vetted any of the services listed on the site, and many contain invalid WSDL. I recommend that you stick with commercial WSDLs (Google, Amazon, Yahoo, EBay, Salesforce.com, UDDI, etc.) as well as whatever int

Re: .net java InvalidCastException

We need more information ... Either provide the entire WSDL, or provide all pertinent parts that apply to the operation (all types and messages plus the portType and binding) AnneOn 10/26/05, Kuldeep Malhotra <[EMAIL PROTECTED]> wrote: Hi i am using apache axis to write web services b

  1   2   >