The WSDL namespace URI indicates the WSDL version.
Anne
On 1/19/09, Shah Asrani wrote:
> Hi,
> Is the any way in Axis2 to find out the version of WSDL file
> programmatically, I need to find ouf if a given WSDL file is version
> 1.1 or 2.0?
>
> Best Regards
>
You should use the "WSDL first" method to build these services. Define
a common schema that defines the "A" type, and then import that schema
into your WSDLs.
Anne
On Tue, Sep 9, 2008 at 2:56 PM, Jonge, Merijn de
<[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> I'm using axis2-1.4.1 and Eclipse/WTP a
general purpose test tool it works fine with message using
> soap and creates the same error with the soapenv alias.
>
> I agree with you that these messages are semantically same.
>
> Thanks
>
>
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAI
Marc,
You must register a type mapping for the SiteDTO type. (I suggest
using a BeanMapping.)
Anne
On Thu, Sep 11, 2008 at 5:26 PM, <[EMAIL PROTECTED]> wrote:
> Thanks for your help!
>
>
>
> Marc
>
>
>
>
>
> From: Martin Gainty [mailto:[EMAIL PROTECTED]
> Sent:
The type declaration is valid.
indicates that the element may contain one of the elements
listed in the choice group. The minOccurs="0" attribute indicates that
the element is optional. It is not intended to be an array; therefore,
it would be inappropriate to say maxOccurs="unbounded".
Anne
O
The two messages are semantically the same. The .NET service should
have no trouble deserializing it.
What is the message you are receiving?
Anne
On Wed, Sep 10, 2008 at 3:59 PM, Soyer, Muhammed A. <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is it possible to control the serialization of the request mes
The latest version of ADB no longer imposes the limitations described
in the documentation. It offers pretty comprehensive support for XML
Schema now.
Anne
On Tue, Sep 2, 2008 at 2:53 PM, Peter Conrey <[EMAIL PROTECTED]> wrote:
> I have been developing web services and web service clients in a la
Axis 1.3 has known problems with arrays.
I suggest you upgrade to Axis 1.4, although it has other issues with arrays.
Anne
On Thu, Sep 4, 2008 at 10:31 AM, Roy Barman, Shashwata
<[EMAIL PROTECTED]> wrote:
> Problem Summary-
>
>
>
> There is a WS-I compliant valid WSDL ( attached). When consumed v
Shripad,
The error indicates that the server does not know how to process the
"anyType" type. How does the WSDL describe the ns8:PushRsp element?
Why does your message override the element type by specifying
xsi:type="xsd:anyType"?
I doubt that the problem is related to ws-addressing.
Anne
On
operfusion.co.uk/show/4694/3/
Anne
On Thu, Aug 28, 2008 at 7:37 AM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> SOAP encoding processors look for a local name "multiRef", so if you
> used "bananas" instead, the SOAP processor might not be able to
> proce
l to change the accessor name to, say,
> "bananas" and generate
>
>
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="xsd:int"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
> 2
The use of multiple references is defined in "The rules for
serialization" in Section 5.1 [1] of the SOAP 1.1 spec:
The rules for serialization are as follows:
1. All values are represented as element content. A multi-reference
value MUST be represented as the content of an independent element
Add elementFormDefault="qualified" to the declaration in your WSDL.
In your message you specify a default namespace in the
element, so that namespace then applies to all child
elements in the message instance. If you do not specify
elementFormDefault, then your child elements are defined as
unqu
You didn't define a typemapping for ArrayOf_xsd_string.
Anne
On Tue, Aug 26, 2008 at 5:26 AM, O. Bigalk <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am developing a web service with a method that takes a complex type as
> parameter.
> The method takes three parameters the first is an String the secon
This is a 404 Not Found message.
You must have specified a wrong URL.
Anne
On Tue, Aug 26, 2008 at 8:35 AM, sarika pramod <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am getting this error when i am deploying the AXIS webservice in JBOSS
>
> C:\FCIPlannerServer-1.0\WEB-INF\classes\com\fci\server\ws
Expose another service using Axis.
On Tue, Jul 22, 2008 at 8:44 AM, Pugalia, Jai P (JP) <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have implemented a web service using Axis2. As Axis2 supports only
> document/literal, the WSDL style for this web service is document/literal.
>
> The client for the web
Do you have a fault message defined in the portType? If so, then you
must also define the fault in the binding.
It would help to see the entire WSDL.
Anne
On Mon, Jul 14, 2008 at 12:17 PM, Juan Gabriel Arias
<[EMAIL PROTECTED]> wrote:
> Hi all,
> i'm facing this issue. I try to generate the java
Add a namespace declaration to the WSDD. That way the namespace will not change.
See http://www.oio.de/axis-wsdd/namespace.htm.
Anne
On Tue, Jul 15, 2008 at 4:45 AM, Roy van Rijn <[EMAIL PROTECTED]> wrote:
> Ah, I've just found out what the problem is.
>
> When we deploy the application, the firs
You need to modify your WSDL so that its bindings specify
use="literal" rather than use="encoded". You also need to redefine
your arrays and any other types or elements that use types from the
SOAP encoding namespace.
Anne
On Mon, Jun 30, 2008 at 2:16 AM, Sander de Boer <[EMAIL PROTECTED]> wrote:
Your schema indicates that the Result element should not be namespace
qualified. If you want the Result element to be namespace qualified,
you must declare it as a global element, or you must override the
default setting within the element declaration by adding the attribute
form="qualified", e.g.,
> -Message d'origine-
> De : Jacky Rymasz-Maillot
> Envoyé : mardi 17 juin 2008 09:45
> À : axis-user@ws.apache.org
> Objet : RE: Send direct XML rather than using Java classes
>
> Thanks alot.
> It works fine ;)
>
> Jack
>
> -Message d'orig
out the namespaces to process
>> correctly.
>>
>> SOAPUI generates the namespace prefixes on the child elements only for V3.
>> For V2, the namespace prefixes are not generated.
>>
>> Thanks,
>> Muralidaran Chakravarthy
>>
>>
>> Anne Thomas M
Pierre,
In XML Schema, an element declaration describes an element that will
appear in an XML document. A type declaration (complexType or
simpleType) describes a type (i.e., the structure of an element and
the type of data that the element contains). It's comparable to the
relationship between an
What problem are you having?
Note that your WSDL does not contain a binding or service description.
Anne
On Thu, Jun 19, 2008 at 11:36 AM, Mathias P.W Nilsson
<[EMAIL PROTECTED]> wrote:
>
> Think I'm going mad. I still havn't solved this.
>
> WSDL
>
>
> http://ws.hairless.edgesoft.se";
> xmlns:a
PUI generates the namespace prefixes on the child elements only for V3.
> For V2, the namespace prefixes are not generated.
>
> Thanks,
> Muralidaran Chakravarthy
>
>
> Anne Thomas Manes wrote:
>>
>> Muralidaran,
>>
>> I'm at a loss to explain why y
Use the SAAJ API. See
http://users.skynet.be/pascalbotte/rcx-ws-doc/saajpost.htm for
samples.
Anne
On Mon, Jun 16, 2008 at 11:04 AM, Jacky Rymasz-Maillot
<[EMAIL PROTECTED]> wrote:
> I am using actually Axis 1.4.
> Is it still possible? If so, where can I find an example?
> Thank you for all your
There no option for asking the tools to generate attributes rather
than elements. For the most part, it's considered a bad practice. Bear
in mind that attributes must be simple types.
Anne
On Mon, Jun 16, 2008 at 8:08 AM, Zaq Rizer <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 16, 2008 at 6:54 AM, kei
You will need to customize the WSDL generated by NetBeans.
Currently your types section maps each Java object attribute to an XSD
element. You need to redefine them as XSD attributes.
Anne
On Tue, Jun 10, 2008 at 11:33 AM, Alessio Brescia
<[EMAIL PROTECTED]> wrote:
> Hi everyone!
>
> I've got a l
See http://wso2.org/library/176
Anne
On Thu, Jun 12, 2008 at 12:12 PM, jaybytez <[EMAIL PROTECTED]> wrote:
>
> I just have a quick question on a piece of Axis2 that I am not understanding.
> If I have a WSDL with multiple operations and I create an instance of
> ServiceClient using the default co
Specify the -n switch and provide a namespace of your choice.
See http://ws.apache.org/axis/java/user-guide.html#Java2WSDLBuildingWSDLFromJava
Anne
On Thu, Jun 12, 2008 at 12:30 PM, Josh <[EMAIL PROTECTED]> wrote:
> When using Axis 1.4's Java2WSDL, my ip address appears in the impl, intf and
> ta
As the error message indicates, you need to add a SOAPAction header to
the HTTP message. In your client code:
MimeHeaders hd = smsg.getMimeHeaders();
hd.addHeader("SOAPAction", "urn:yoursoapaction");
See http://users.skynet.be/pascalbotte/rcx-ws-doc/saajpost.htm for a
sample SAAJ
Axis2 does not support SOAP Encoding. Try Axis instead.
Or use a flatter object model. Keep in mind that SOAP is not a
distributed object middleware system. XML is good for exchanging
hierarchical data structures. It's not so good at exchanging rich
object graphs.
Anne
On Thu, Jun 12, 2008 at 2:
Try naming your derived simpleType:
This will force Axis to generate a type for you, and then you cast the
short to this type.
Anne
On Thu, Jun 12, 2008 at 5:42 PM, Roger P
<[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 8:48 PM, David Ojeda <[EMA
Muralidaran,
I'm at a loss to explain why you are receiving the BP2404 validation
error. As far as I can see, your WSDL contains a valid SOAP binding.
Which validation tool are you using? Perhaps it is looking for the
literal string "soapbind:binding" rather than the semantic equivalent
-- in your
Actually, this won't work.
You want to define "foo" as a simpleType that restricts xs:string, e.g.,
Anne
On Sat, Jun 14, 2008 at 5:03 PM, Jake Goulding <[EMAIL PROTECTED]> wrote:
> Ack, please disregard - turns out I had a simple copy and paste error:
>
>
>
> should have been
>
>
>
You declared "foo" as an element, not as a type. Hence you have not
defined a type called "foo".
Anne
On Sat, Jun 14, 2008 at 3:49 PM, Jake Goulding <[EMAIL PROTECTED]> wrote:
> Hey all:
>
> I am having some trouble importing a WSDL that contains two top-level
> schemas. The WSDL itself is attach
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
That's a bug in Axis 1.2. Please upgrade to Axis 1.4.
On Wed, May 28, 2008 at 4:52 AM, Karthik R <[EMAIL PROTECTED]> wrote:
> Hello Friends,
>
>
> Hello Friends,
>
> While Accessing a webservice using axis 1.2, we are sending the input as
> arrayofComplex Data Type.
>
> ComplexData Type - a Class
I'm confused. You have a WSDL document, correct? Did you run it
through WSDL2Java? That should generate a skeleton and a WSDD. You
still have to write some code to plug into the skeleton.
Alternatively, you can start with a class and deploy it using the JWS
option (assuming you have no complex typ
See this great WSDD reference:
http://www.oio.de/axis-wsdd/
http://www.oio.de/axis-wsdd/namespace.htm
http://www.oio.de/axis-wsdd/operation.htm
The element specifies the targetNamespace for the WSDL,
which typically propagates through to the elements and types of the
runtime messages unless you o
ocessing(OMElement sCIncidentProcessing0) method that Axis
> generated stubs provide.
>
> When I invoke the web service using the Eclipse generated client stubs
> instead of Axis (with the input string like "Input 2" above, I get no
> exceptions and I get correct result
The message you want to send is not a valid SOAP message. You may have
at most one child element in the SOAP Body. You should define a
wrapper element for your two elements.
Anne
On Tue, May 20, 2008 at 9:23 AM, Kurt Kavanaugh <[EMAIL PROTECTED]> wrote:
>
>
> Any thoughts? I am worried about exte
Why does the service exchange strings rather than typed XML? If it's a
web service, it should define its interface using a
language-independent API, such as WSDL or a schema. Did the service
provider at least provide you with a description of the expected
string format? The first place I'd look is
The specific error is caused by a reference to an undefined type:
soapenc:Array. You can resolve it by importing the soapenc namespace.
Except that Axis2 doesn't support RPC/encoded. Try Axis instead.
Anne
On Tue, May 20, 2008 at 3:02 PM, Steve Brough <[EMAIL PROTECTED]> wrote:
> I hope you can h
Axis 1.4 + WSS4J is compatible with WSE 3.0.
Anne
On Fri, May 16, 2008 at 3:32 AM, José Ferreiro <[EMAIL PROTECTED]> wrote:
> Hello Anthony,
>
> Apache has two projects on web services [http://ws.apache.org/].
> 1 - Axis 1.x [2]
> 2 - and Axis2 which is a redesign of Axis 1.x [3].
>
> I fully agr
You should be able to use any SOAP client library to invoke your Axis2 service.
What language would you like to use?
.NET: add a WebReference to your client class and point to the service WSDL
JavaScript: try the WSO2 Mashup tool
Java: pick your poison:
- JAX-WS reference implementation (from Glas
The .NET service uses wrapped document/literal, and Axis generates
rpc/encoded by default.
You need to configure the service to use style=wrapped and use=document.
You might find it easier if you use wsdl2java to generate a client
stub for you because it will generate all the proper settings for y
Use Axis (as opposed to Axis2). See http://ws.apache.org/axis/.
Anne
On Wed, Apr 23, 2008 at 3:31 AM, Christophe Hamerling
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I need to call a RPC/Encoded WS. Unfortunatly, this style has been
> deprecated and it is not possible to build Stub from WSDL with c
Axis generates RPC/encoded by default unless you tell it otherwise. It
doesn't check the WSDL at runtime, so it relies on you to specify the
proper settings.
If you use wsdl2java, the generated client stub will have all the
proper settings, but because you are using the Call interface, you
must pr
Attributes are generally okay.
Choice, list, union, abstract types, and substitution groups can cause
interoperability problems.
Anne
On Thu, May 1, 2008 at 3:47 PM, John Eapen <[EMAIL PROTECTED]> wrote:
>
> Hello -
>
> Are there any do and don't with regards to interoperability when it comes to
On Thu, May 1, 2008 at 6:21 PM, A Sunley <[EMAIL PROTECTED]> wrote:
>
> Greetings,
>
> We are attempting to generate some skeleton code from a wsdl using
> wsdl2java. Our schema contains some custom objects which have nested arrays.
>
> F
The beauty of SOAP is that it hides your implementation from the
application on the other side of the wire. You can handle your binary
file your way (e.g., with a DataHandler), and the application on the
other side of the wire can handle it its way. The only thing that
matters is what goes on the w
The best way to manage what is included or excluded from your WSDL is
to edit the WSDL so that it exposes just what you want, then redeploy
the service using the useOriginalWsdl setting.
Anne
On Fri, Apr 25, 2008 at 10:20 AM, Glen Verran <[EMAIL PROTECTED]> wrote:
> Hi there,
> I am still having
You must upgrade to at least Axis 1.3 (1.4 is preferable) if you want
to use "wrapped" style.
Anne
On Fri, Apr 25, 2008 at 11:08 AM, SDev <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm using Axis 1.2.1. I've auto generated a web service which created a wsdl
> that was clattered with references to
You didn't include the schema, but I suspect you need to add the following
attribute to your element:
elementFormDefault="qualified"
Anne
On Wed, Apr 16, 2008 at 1:01 PM, Thomas Vaughan <
[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> I think I've narrowed down the cause of a problem I'm hav
Axis2 does not support SOAP encoding.
On Tue, Apr 8, 2008 at 11:39 AM, Detelin Yordanov
<[EMAIL PROTECTED]> wrote:
> Hello guys,
> Does Axis2 1.4 support rpc/encoded WSDLs?
> I am able to deploy a service aar with a custom rpc/encoded WSDL but I could
> not invoke it successfully, so I decided t
the objects.
>
> -Ryan
>
>
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 08, 2008 8:33 AM
> To: axis-user@ws.apache.org
> Subject: Re: xml:id does not want to work
>
> You need to also declare the "xml"
> occurrence, no element in the message.
> Thanks, Anne.
>
>
>
> On 4/9/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > If you specify minOccurs="1", then you can't return an empty array.
> > You must have at least one item in the array.
>
which I
> suspect it means the corresponding element occuring at least once, but it
> didn't seem to work. Or, have I missed something?
>
>
>
> On 4/9/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > If an element has been d
Please provide the specific error(s).
Anne
On Mon, Apr 7, 2008 at 1:17 PM, Jack Sprat <[EMAIL PROTECTED]> wrote:
> I have a WSDL that passes WS-I basic profile validation when run from the
> latest version of soapUI. I have a partner using .Net to consume the
> service that gets an error when tr
You need to also declare the "xml" namespace prefix:
xmlns:xml="http://www.w3.org/XML/1998/namespace";
Anne
On Mon, Apr 7, 2008 at 1:44 PM, McCullough, Ryan
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> In my wsdl, I am importing an xsd schema file. That xsd file has an import:
>
>
>
>
>
If an element has been defined as minOccurs="0", and you have no
occurrences, then there should be no elements in the message. Is that
what you mean by "drops the array"? If you define an element to wrap
the array, then that element should still be there, but Axis2
typically doesn't define an eleme
Perhaps your senior architect is confusing "operation" with
"interface". WSDL 2.0 limits a service (i.e., the thing described by
the WSDL) to a single interface. An interface can expose multiple
operations, though. The WSDL 2.0 "interface" is equivalent to a WSDL
1.1 "portType". I disagree with the
XMLBeans should be able to handle any valid schema. The structure you
specify doesn't seem particularly unusual. I suggest using XMLBeans
for your data binding framework. SOAP sends and receives XML
regardless of how you process it on your end.
Anne
On Mon, Apr 7, 2008 at 7:31 AM, Asensio, Rodrig
-- Forwarded message --
From: Hari C <[EMAIL PROTECTED]>
Date: Sun, Apr 6, 2008 at 5:26 PM
Subject: Help Please
To: [EMAIL PROTECTED]
Our project is having an existing webservice running in axis1.1.1.We were
trying to create a new service in axis 1.3. and wanted to package the AA
e written in flash actionscript, and
> webservice is very limited on this platform, and the addressing namespace
> does not seem to be declared.
>
> Is there any simplier solution?
> Has anybody ever used Flash with axis2 and a session management ?
>
>
> Thanks for your
Here's another good WSDD reference:
http://www.oio.de/axis-wsdd/
Anne
On Wed, Apr 2, 2008 at 10:44 AM, Tomás Tormo <[EMAIL PROTECTED]> wrote:
> Hi
>
>Does anybody know any good link wich has a good explanation about wsdd
> writting method?
> By the way... can you read me? It's just because i
The input message does not conform to the schema defined by the
service. We need to see the WSDL to diagnose it further. But-- the
input message uses SOAP Encoding, and Axis2 does not support SOAP
Encoding.
Anne
On Mon, Mar 31, 2008 at 8:32 PM, Tony Liu <[EMAIL PROTECTED]> wrote:
> Hello,
> I dep
symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665)
> >>> at
> >>> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
> >>> at
> >>>
> >>>
> org.apach
xmlns:ns="urn:TestSearchEngine"
> qname="ns:requestDetail"
> type="java:webservices.wsdoclittest.annethomas.RequestDetail"
> serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> dese
gt;
>
>
> type="tns:TestSearchEngineInterface">
> transport="http://schemas.xmlsoap.org/soap/http"; />
>
>
>
gt; Please provide java2wsdl and wsdl2java Tool and Command for Documnet
> litetal web services with Axis.
> any reference, any tutorial, ??
>
>
> Anne, Thank you very much for your reply.
>
>
>
>
> Regards
> Santosh
>
>
>
>
>
> Anne Th
> 2008-09-09
> London
>
>
> Santosh
> 25
> London
>
>
>
>
>
> =x
>
>
If you want to keep the WSDL the same, then I suggest you use the
WSDL-first approach rather than the POJO approach. Take the WSDL from
your Axis 1.4 service and use WSDL2Java to generate a new service
skeleton.
Anne
On Fri, Mar 28, 2008 at 5:47 AM, Thomas Burdairon
<[EMAIL PROTECTED]> wrote:
> G
Thilina,
The WS-I Attachments Profile [1] defines the standard WSDL description for SwA.
[1] http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html
Anne
On Fri, Mar 28, 2008 at 10:39 AM, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> Hi,
> You cannot generate WSDL with the knowledge of SwA
Specify -y wrapped rather than -y document. That will produce a
"wrapped" document/literal service, and it will automatically generate
the beanmappings for you.
Anne
On Fri, Mar 28, 2008 at 11:24 AM, sh_santosh <[EMAIL PROTECTED]> wrote:
>
>
>
> can anybody provide working command like this for
For best results, your POJO should avoid using Java Collections.
Anne
On Fri, Mar 28, 2008 at 6:59 PM, Nate Roe <[EMAIL PROTECTED]> wrote:
>
> I wonder this in part because of the issue that I reported
> (https://issues.apache.org/jira/browse/AXIS2-3655, where a service returning
> a List fail
It's pretty simple -- don't include a DTD in your SOAP message.
Anne
On Mon, Mar 24, 2008 at 11:11 PM, Appasamy Thirugnana
<[EMAIL PROTECTED]> wrote:
>
>
> Pl help me out to find when this error will occur adn whats the
> solution, In axis2/Java i am getting this error
>
>
> 2008-03-25 12:20:2
;
>
> Thank you,
> Nate
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
>
>
> Sent: Monday, March 24, 2008 6:26 PM
> To: axis-user@ws.apache.org
> Subject: Re: What might cause "Unexpected subelement return"?
>
>
The message you are sending doesn't match the expected input specified
by the WSDL.
The service is expecting something lie this:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:enc="http://schem
Please post the message you are sending.
Anne
On Wed, Mar 26, 2008 at 4:50 AM, Simon Steinacker
<[EMAIL PROTECTED]> wrote:
> The WSDL of the service is located here:
> http://131.107.254.90:8080/XdsService/XDSRegistry?wsdl
>
> Thanks a lot,
> Simon
>
>
> Martin Gainty wrote:
> > anfuegen WSD
{
> > list.add(createPerson(Integer.toString(i)));
> > }
> >
> > return list;
> > }
> >
> > Should I file a JIRA for this problem in general, or the "anyType"
> pro
return list;
> }
>
> Should I file a JIRA for this problem in general, or the "anyType" problem
> specifically?
>
> I will try using a modified WSDL to generate the client stub and see how
> that goes.
>
> Thank you,
> Nate
>
>
>
> binding="axis2:doCalculateSOAP12Binding">
> location="http://localhost:8080/axis2/services/doCalculate"/>
>
> binding="axis2:doCalculateHttpBinding">
> location="http://localhost:8080/axis2/services/doCalcu
Nate,
The message indicates that the unexpected subelement is called "return".
Look at your WSDL to determine what the expected message structure
should be, and compare it to the actual message returned.
Anne
On Fri, Mar 21, 2008 at 5:04 PM, Nate Roe <[EMAIL PROTECTED]> wrote:
>
> I have tested
Please post the WSDL.
Anne
On Thu, Mar 20, 2008 at 4:28 AM, Richard Fagot <[EMAIL PROTECTED]> wrote:
> Nobody knows why Axis 2 client can not correctly interpret complex
> type returned by an axis 1 server ?
>
>
>
>
> 2008/3/17, Richard Fagot <[EMAIL PROTECTED]>:
> > I would like to add sent s
Are you asking how to use the REST interface and submit your
parameters using url encoding?
That's only possible when using simple types.
Anne
On Thu, Mar 13, 2008 at 7:50 PM, Michael Potter <[EMAIL PROTECTED]> wrote:
> Martin,
>
> I don't think I have any problem with the transport.
>
> I am
Browsers have a tendency to strip out the namespace declarations. You
have to view the source.
Anne
On Fri, Mar 14, 2008 at 5:44 AM, Seetha Rama Krishna
<[EMAIL PROTECTED]> wrote:
> Hi,
> I deployed example3 in tomcat and the wsdl file which is displaye on
> browser i saved it as OrderProcess
The WSDL2Java generated stub uses the Axis API, so the two methods
result in the same performance. The advantage of using the generated
stub is that you write less code, and it automatically sets the
correct settings for the call based on the info in the WSDL.
Anne
On Thu, Mar 13, 2008 at 3:03 PM
Is there an element preceding the import?
Anne
On Wed, Mar 12, 2008 at 3:35 AM, asd <[EMAIL PROTECTED]> wrote:
> hi,all.
> are there anyone who had some experience in activebpel?
> i had occured a problem when using ActiveBpel ,because i don`t getted
> a membership of ActivePoints forum,so,i
A byte array is not a simple type. Can you use a different type?
On Wed, Mar 12, 2008 at 6:05 AM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
> Hi Anne,
>
> thanks for your reply, i managed to generate a document/literal WSDL file
> (with java2wsdl), to use in the J2ME Wireless Toolkit Stub genera
Using the "style" parameter. See
http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and
http://ws.apache.org/axis/java/reference.html#Java2WSDLReference.
Anne
On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
> Hi Anne,
>
> thanks for your reply. How exactly would i
So it would be nice to not force people use keywords in their
> XML... Granted its difficult to forsee what all keywords are in all
> programming languages, but "return" seems like a sure bet. :) Is there a
> way to customize this?
>
>
>
> Thanks,
>
> Chris
The Axis2 java2wsdl tool generates doc/literal -- but my guess is that
it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2,
etc. I suggest you use the Axis java2wsdl tool and specify "wrapped"
style. The resulting WSDL should be acceptable to J2ME. You can then
use that WSDL as input
"Wrapped" style produces a document/literal service which provides the
best interoperability with .NET.
It's the way to go.
Anne
On Mon, Mar 3, 2008 at 10:52 AM, Luca Rasconi <[EMAIL PROTECTED]> wrote:
> Hi all, my goal is to create an interoperable ws (java server and dot
> net client) so I wou
WS-Security -- implemented via Apache Rampart.
On Tue, Mar 4, 2008 at 12:38 PM, chitgoks <[EMAIL PROTECTED]> wrote:
> hi
> what are your techniques to making your web service server secure? ive read
> ssl aint enuff. i have exposed methods for authentication and i used an app
> called http analyze
Use the Document object rather than the Element object in your interface.
Anne
On Thu, Mar 6, 2008 at 9:32 AM, Duseja, Sushil
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am using Axis 1.4 and I am having a problem accessing an echo service
> (doc/literal).
>
> Here's the code:-
>
>
>
> MyService
>
>
>
That's a limitation that Sun's JAX-WS implementation has imposed. It's
based on a constraint defined in the WS-I Basic Profile which requires
unique wire signatures based on the QName of the child element of the
SOAP Body. Axis2 does not impose that limitation because it supports
additional dispatc
Convert your Hashmap to an array.
Anne
On Fri, Mar 7, 2008 at 2:42 AM, <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi Group,
>
>
>
> I have raised this question to the forum before but did not get concrete
> replies.
>
>
>
> I am trying to return a user-defined java Object from a web-service method
> w
File a bug report with Adobe. A SOAP stack should not barf on a valid
NCName like "return".
Anne
On Sat, Mar 8, 2008 at 11:53 PM, Chris Hyzer <[EMAIL PROTECTED]> wrote:
>
> Hey,
> Im using Axis2 (latest) and all defaults for inputs to Java2WSDL. I have a
> simple service, and each operation has
1 - 100 of 2007 matches
Mail list logo
