http://schemas.xmlsoap.org/soap/envelope/";>
SOAP-ENV:Server
502 Bad Gateway
Invalid response from upstream server
localhost:8000
Probably un-related, but that actually isn't a valid fault structure,
the detail can only contain na
first place thought that it
was
> valid and tried to deal with it, and I've now encountered two
completely
> independent products that produce faults like this (Mindreef SoapScope
> and gSoap). Maybe it was permitted in an earlier incarnation?
>
> -Original Message-
>
Title: [axis2] unable to run client
Following along a similar set of steps to those outlined in the databinding client part of the docs, i ran WSDL2Code on the wsdl with the option to use xmlbeans. In my client, i new up an instance of the generated stub, SoapStub stub = new SoapStub(); leave
Title: verbosity of client code
Are there any plans to reduce the verbosity of the code that needs to be written by the client? a 2 liner in Axis 1.x (create the stub, call login), now takes 7 lines of code. Do you really think this is an improvement ?
SoapStub stub = new SoapStub();
Login l
he ".axis2/modules" directory in your home directory.
>
>Now everything should work. We are working on an updated release; sorry for
>the pain!
>
>Ajith
>
>On 1/12/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>>
>> Following along a similar set of steps t
://www.nrs.eskom.co.za/xmlvend/base/2.0/schema', at
>
> Following a discussion on the Axis2 user list (titled "Consuming Axis2
webservice with c# client?", starting on 17/02/06), it was discovered
that this was due to an incorrect namespace in the Axis2 message.
> The followi
Title: RE: [jira] Commented: (AXIS2-455) Axis2 dotNET interoperabilityproblem with abstract types.
given that the problem occurs when the WS-A code gets turned on, my first instinct would be its a problem in that.
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED
There was a service running at that endpoint (for the
soapbuilders interop testing) it has however been down for quite a while now,
previous attempts to prod people to get the endpoint active again have always
failed.
Perhaps the axis2 folks will put up an interop endpoint
?
Cheers
Simon
I doubt that'll help, because that type is not the outer wrapper.
-Original Message-
From: Tom Jordahl (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 21, 2006 1:21 PM
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS-2442) java file genrated using
WSDL2JAVA fail to compi
Title: RE: java file generated using WSDL2JAVA fail to compile with 'too many parameters' error
He can't because its not his service (its mine) shouldn't axis be smart enough to not generate a constructor for all the parameters once there's too many ?
Cheers
Simon
-Original Message
M
To: axis-dev@ws.apache.org
Subject: Re: java file generated using WSDL2JAVA fail to compile with 'too many parameters' error
Please log a bug then :)
On 3/25/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>
>
> He can't because its not his service (its mine) shouldn&#x
I'll try it out, are there nightly builds available ?
Thanks
Simon
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 11:32 AM
To: axis-dev@ws.apache.org
Subject: Re: [jira] Resolved: (AXIS2-515) WSDL2Java generates
uncompilablecode.
Please don't do this, if the schema says
then
a
Means something completely different to
a
Cheers
Simon
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 02, 2006 11:05 AM
To: axis-dev@ws.apache.org
Subject: Re: [jira] Commented: (AXIS
On Tue, 04 Apr 2006 07:02:40 +0600, in soap you wrote:
>On Mon, 2006-04-03 at 13:10 -0700, Simon Fell wrote:
>> Please don't do this, if the schema says
>>
>>
>>
>>
>>
>>
>> then
>>
>> a
>>
>>
>>
>
29 Mar 2006 16:23:52 -0500, in soap you wrote:
>http://cvs.apache.org/dist/axis2/nightly/
>
>On 3/29/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>> I'll try it out, are there nightly builds available ?
>>
>> Thanks
>> Simon
>>
>> -Orig
ding a client, not a server, the -ss -sd -g options are no
good to me.
Cheers
Simon
On Wed, 29 Mar 2006 16:23:52 -0500, in soap you wrote:
>http://cvs.apache.org/dist/axis2/nightly/
>
>On 3/29/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>> I'll try it out, are there
ope/";>/>xmlns:ns2="urn:enterprise.soap.sforce.com">xmlns="urn:enterprise.soap.sforce.com">pwd
>0
>
>
>As i'm bulding a client, not a server, the -ss -sd -g options are no
>good to me.
>
>Cheers
>Simon
>
>On Wed, 29 Mar 2006 16:
using the apr 6 snapshot, i generated a client stub using xmlbeans, by
running
wsdl2java -s -d xmlbeans -uri enterprise.wsdl
I have some client code that uses the stub
SoapStub s = new
SoapStub("http://www.salesforce.com/services/Soap/c/7.0";);
Login l = Login.Factory.newInstance
On Wed, 19 Apr 2006 22:16:26 +0600, in soap you wrote:
>On Wed, 2006-04-19 at 14:47 +, Ajith Harshana Ranabahu (JIRA) wrote:
>> [ http://issues.apache.org/jira/browse/AXIS2-587?page=all ]
>>
>> Ajith Harshana Ranabahu resolved AXIS2-587:
>> --
Project: Apache Axis 2.0 (Axis2)
>> Type: Bug
>
>> Components: databinding
>> Environment: Axis2.0 RC4, JDK 1.5.06, WinXP
>> Reporter: Simon Fell
>> Priority: Blocker
>> Attachments: WhiteSpaceAndExtensionTypes.zip
>>
>> A valid resp
[jira] Commented: (AXIS2-632) get errors trying to parse
validresponse
On Sat, 2006-04-29 at 00:06 -0700, Simon Fell wrote:
> the few verbs lots of nouns approach is a very successful design
> model, to do it in web services with a static schema requires the
> schema/runtime stack to sup
ssues.apache.org/jira/browse/AXIS-1912
> > Project: Axis
> > Type: Bug
> > Components: Basic Architecture
> > Versions: 1.2RC3
> > Environment: JDK1.5.01, WinXP
> > Reporter: Simon Fell
> > Attachments: enterprise_sfell2.wsdl, partne
.NET does this also, but it gets it wrong in a couple of scenarios I've
run into (around arrays of arrays), just something to be careful of.
Cheers
Simon
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 11, 2005 6:31 AM
> To: axis-dev@ws.apache.o
AXIS-1912
>> URL: http://issues.apache.org/jira/browse/AXIS-1912
>> Project: Axis
>> Type: Bug
>> Components: Basic Architecture
>> Versions: 1.2RC3
>> Environment: JDK1.5.01, WinXP
>> Reporter: Simon Fell
>> Attachment
I'd be really really happy if the axis2 package/class names didn't clash
with the axis1.x names, so that I can run both axis1 & axis2 in the same
jvm instance.
Cheers
Simon
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 11, 2005 8:53 AM
To: axis-
Is switching to org.apache.axis2.* really that bad ?
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 11, 2005 4:22 PM
To: axis-dev@ws.apache.org
Subject: RE: [Axis2] Moving SOAP classes to its own package
Hi Simon,
> I'd be really really happy
My point is that the character reference 0x03 is not valid XML,
regardless of whether its a raw byte or &3; both are illegal xml. The
only encoding you can do to transport that string is to base64 encode
it.
Cheers
Simon
On Tue, 31 May 2005 23:48:52 +0200 (CEST), in soap you wrote:
> [
> h
+1, and make sure you log a bug for WSE3.0 CTP on ladybug
http://lab.msdn.microsoft.com/productfeedback/
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Monday, July 18, 2005 8:09 AM
To: Thilina Gunarathne
Cc: axis-dev@ws.apache.org
Subject: Re: [Axis2] MIME
The Whitemesa usage looks correct to me, the content-Id should not
include the cid: schema identifier.
Cheers
Simon
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 19, 2005 8:27 AM
To: Sanjiva Weerawarana
Cc: axis-dev@ws.apache.org; Thilina Gunarat
-2136
> Project: Apache Axis
>Type: New Feature
> Components: Basic Architecture
>Versions: 1.2.1
>Reporter: Simon Fell
>Priority: Minor
>
>
>provide support for handling gziped compressed requests & responses in the
>http client.
NB, i pl
PROTECTED]
Sent: Tuesday, July 26, 2005 7:51 PM
To: Simon Fell
Subject: [jira] Commented: (AXIS-2136) support request & response gzip
compression on HTTP transport
[
http://issues.apache.org/jira/browse/AXIS-2136?page=comments#action_1231
6832 ]
Davanum Srinivas commented on AXIS-
Title: Gzip patch
I added a new patch to the issue in jira, but I didn't see any jira email go out.
http://issues.apache.org/jira/browse/AXIS-2136
And my comment to go with the patch
"Here you go. I'd be much happier if the default was to accept gzipped responses, its negotiated between
Cool. I'm still working on the same support for HttpSender as well.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, July 29, 2005 12:55 PM
To: axis-dev@ws.apache.org
Subject: Re: Gzip patch
Done. Checked in as-is :)
thanks,
dims
On 7/29/05,
on http://ws.apache.org/axis2/ the download now, and download it links
for the 0.92 release take you to
http://ws.apache.org/axis2/releases.html which only has 0.9 & 0.91.
Cheers
Simon
also the release notes in the binary distribution say its v0.91.
Cheers
Simon
On Thu, 29 Sep 2005 23:01:07 -0400, in soap you wrote:
>we need to fix it...here's the correct url:
>http://ws.apache.org/axis2/download.cgi
>
>thanks,
>dims
>
>On 9/29/05, Simon Fell <[E
Other fun facts & figures, the axis binary download weights in at
33Mb, compared to 24Mb for the entire .NET 1.1 runtime installer.
Cheers
Simon
On Fri, 30 Sep 2005 07:18:50 +0200 (CEST), in soap you wrote:
> [ http://issues.apache.org/jira/browse/AXIS2-249?page=all ]
>
>Simon
t: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Versions: 0.92
> Environment: WinXP, JDK 5.0
> Reporter: Simon Fell
> Attachments: enterprise.wsdl
>
> The code generated from the WSDL seems to be extremely excessive both
in terms of numb
The HTTP transport should support everything in the Axis 1.1 transport,
including proxies, gzip, ntlm auth etc.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, September 30, 2005 7:24 AM
To: axis-dev@ws.apache.org; robert burrell donkin
Subject: Re: [Axis
I hope everyone spots the smilly in my blog post.
But first impressions count for a lot, and frankly my first impression
of Axis2 wasn't good.
A) the download links for 0.92 on the main axis2 site took you to a page
which didn't mention 0.92
B) the release notes in 0.92 say it's 0.91
C) was shock
org
Cc:
Subject: RE: [jira] Commented: (AXIS2-249) Exessive number & size of filesgenerated from WSDL
On Fri, 2005-09-30 at 09:45 -0700, Simon Fell wrote:
> Yes, there's a lot of schema, this is a real world service that handles
> millions of requests a day, not some hello wor
!!
/me takes responsibility :)
Fixed A,B,D. C is in progress.
-- dims
On 9/30/05, Simon Fell <[EMAIL PROTECTED]> wrote:
> I hope everyone spots the smilly in my blog post.
>
> But first impressions count for a lot, and frankly my first impression
> of Axis2 wasn't good.
&g
rward, I'm new to Maven and the Axis2 build setup.
Tx
Simon
-Original Message-----
From: Simon Fell
Sent: Monday, October 03, 2005 9:41 AM
To: axis-dev@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: [Axis2] WS-SNAFU - That hurts!!
Quick turn around, thanks!
Are there nightly build somewh
Title: [axis2] client code
I couldn't spot an obvious tutorial or sample for a doc/literal client generated from WSDL, so this is what i ended up with, but it seems very verbose, is there some trick I'm missing ? (there's 23 lines of code to make 2 WS call, the second call requiring a single
Title: [axis2] turning off WS-A
I'm calling a service that doesn't require WS-Addressing, using an Axis2.0 client generated from the WSDL is there anyway to tell Axis2 to not generate the WS-Addressing headers ?
Thanks
Simon
r operation basis ?
>
>Simon Fell wrote:
>
>> I'm calling a service that doesn't require WS-Addressing, using an
>> Axis2.0 client generated from the WSDL is there anyway to tell Axis2
>> to not generate the WS-Addressing headers ?
>>
>> Thanks
>> Simon
>>
Then its not taking effect. Are you sure its in the right location ?
If you monitor the HTTP traffic with, I think you'll find that the
server is returning the 400 error with no body, which is what it does
when the request gets too large.
Cheers
Simon
-Original Message-
From: Seung Hyun
On Thu, 07 Aug 2003 15:43:13 -0700, in soap you wrote:
>
>When getting a DIME service to work w/ WSE1.0, I discovered that WSE was
>send a MustUnderstand header with WS-routing info. Axis, not
>understanding such headers, threw an exception.
>
>Unfortunately, the exception got thrown after the p
1452
> > URL: http://issues.apache.org/jira/browse/AXIS-1452
> > Project: Axis
> > Type: Bug
> > Components: WSDL processing
> > Versions: beta-2
> > Environment: XP, JDK 1.4.2_03
> > Reporter: Simon Fell
> > P
ssage-
From: Venkat Reddy (JIRA) [mailto:axis-dev@ws.apache.org]
Sent: Wed 2/16/2005 10:31 PM
To: Simon Fell
Cc:
Subject: [jira] Commented: (AXIS-1818) MessageElement [] for doesn't include all elements
[ http://issues.apache.org/jira/browse/AXIS-1818?page=comments#ac
Remember that only the HTTP binding specifies the SOAPAction header. Not
all bindings are going to have a SOAPAction that's external to the
envelope.
> -Original Message-
> From: Chathura Herath [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 17, 2005 7:31 PM
> To: axis-dev@ws.apache.o
wsdl
Versions: 0.94
Environment: WinXP, JDK 1.5
Reporter: Simon Fell
Priority: Minor
running WSDL2Code from a command prompt window, if it can't find the AXIS_HOME
setting, then it'll close the window.
--
This message is automatically generated by JIRA.
-
If you th
: JDK 1.5, Win XP
Reporter: Simon Fell
running wsdl2code -uri enterprise.wsdl
stops with this exception
RuntimeException: Schema for namespace 'urn:enterprise.soap.sforce.com' already
contains type 'string
at
org.apache.axis2.wsdl.codegen.CodeGeneration
[ http://issues.apache.org/jira/browse/AXIS2-382?page=all ]
Simon Fell updated AXIS2-382:
-
Attachment: enterprise.wsdl
> WSDL2Code stops with confusing exception message
>
>
> Ke
Reporter: Simon Fell
WSDL contains soapAction="", so it should generate a SOAPAction: "" header, but
doesn't.
POST /services/Soap/c/7.0 HTTP/1.1
User-Agent: Axis/2.0
SOAPAction:
Connection: Keep-Alive
Host: www.salesforce.com
Transfer-Encoding: chunked
Content-Type
[ http://issues.apache.org/jira/browse/AXIS2-385?page=all ]
Simon Fell updated AXIS2-385:
-
Attachment: enterprise.wsdl
This is the WSDL, I"m using the xmlbeans stuff in case that makes a difference.
I've logged this before on an earlier release
Environment: WinXP / JDK 1.5
Reporter: Simon Fell
Priority: Minor
If you use the default HTTP transport, it does send a HTTP User-Agent that
identifies it as Axis, but if you switch to the CommonsHTTPSender transport, it
gets the default commons HTTP user agent. It would be useful to have
1.5.06
Reporter: Simon Fell
Priority: Blocker
Attachments: enterprise.wsdl
ran WSDL2Java -s -uri enterprise.wsdl.
a) it generates a single file that is 5Mb in size and 121914 lines long (i
acedently hit format in eclipse and had to kill eclipse after 5 minutes of it
trying to format the
[ http://issues.apache.org/jira/browse/AXIS2-515?page=all ]
Simon Fell updated AXIS2-515:
-
Attachment: enterprise.wsdl
please sign up for a free salesforce.com developer account, and do some real
world testing of your releases.
http://www.salesforce.com
[
http://issues.apache.org/jira/browse/AXIS2-515?page=comments#action_12371864 ]
Simon Fell commented on AXIS2-515:
--
here's a quick sample i wrote for an earlier version of axis 2
http://www.pocketsoap.com/weblog/2005/10/1563.html
goto
[
http://issues.apache.org/jira/browse/AXIS2-515?page=comments#action_12371866 ]
Simon Fell commented on AXIS2-515:
--
And i attached the WSDL earlier (also to previous bugs with WSDL2Java on this
wsdl)
> WSDL2Java generates uncompilable c
: Bug
Components: wsdl
Environment: Axis 1.0 RC1, JDK 1.5.06 WinXP
Reporter: Simon Fell
Priority: Blocker
Attachments: enterprise.wsdl
I ran WDSL2Java -s -uri enterprise.wsdl (i'll attach the wsdl)
The generated stub doesn't compile, it contains duplicate inner classes for all
th
[ http://issues.apache.org/jira/browse/AXIS2-587?page=all ]
Simon Fell updated AXIS2-587:
-
Attachment: enterprise.wsdl
> WSDL2Java generates duplicate fault classes, can't compile genera
[
http://issues.apache.org/jira/browse/AXIS2-587?page=comments#action_12375017 ]
Simon Fell commented on AXIS2-587:
--
That should be Axis 2.0 RC1
> WSDL2Java generates duplicate fault classes, can't compile genera
, WinXP
Reporter: Simon Fell
Priority: Blocker
A valid response from the query call (wsdl is the enterprise wsdl that's now
part of the tests) fails to be de-serialized with an error.
Exception in thread "main" java.lang.RuntimeException:
java.lang.RuntimeException: Unexpected
[
http://issues.apache.org/jira/browse/AXIS2-632?page=comments#action_12377040 ]
Simon Fell commented on AXIS2-632:
--
Seems like a doc/literal case that the 4 year old Axis 1.1 supports really
should work in Axis 2, isn't this suposed to be a step fo
, JDK 1.5.06
Reporter: Simon Fell
Priority: Critical
Attachments: partner.wsdl
WSDL2Java -s -u -uri partner.wsdl
compiled the generated code, called the query method which takes a session
Header, like this
SforceServiceStub stub = new SforceServiceStub
[ http://issues.apache.org/jira/browse/AXIS2-694?page=all ]
Simon Fell updated AXIS2-694:
-
Attachment: partner.wsdl
> Soap:Body is serialized inside of a soap:Header element
> ---
>
>
generated build.xml fails to build
--
Key: AXIS2-695
URL: http://issues.apache.org/jira/browse/AXIS2-695
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Versions: 1.0
Environment: WinXP, JDK 1.5.06
Reporter: Simon Fell
nding
Versions: 1.0
Environment: WinXP, JDK 1.5.06
Reporter: Simon Fell
using the WSDL from AXIS2-694
ran WSDL2Java -s -u -uri partner.wsdl
the WSDL includes an xsd:any on the definition of SObject, which doesn't appear
to have made it into the SObject class, this may be re
Environment: JDK1.5.01, WinXP
Reporter: Simon Fell
Attachments: enterprise_sfell2.wsdl, partner.wsdl, xsd_any_response.txt
If a service makes heavy use of elements, these all get meapped to
MessageElement [], this seems to use way more memory than if the xsd:any isn't
there and all the ele
[ http://issues.apache.org/jira/browse/AXIS-1912?page=history ]
Simon Fell updated AXIS-1912:
-
Attachment: xsd_any_response.txt
This is the response message
> MessageElement requires inordanate ammounts of mem
[ http://issues.apache.org/jira/browse/AXIS-1912?page=history ]
Simon Fell updated AXIS-1912:
-
Attachment: partner.wsdl
this is the WSDL that uses
> MessageElement requires inordanate ammounts of mem
[ http://issues.apache.org/jira/browse/AXIS-1912?page=history ]
Simon Fell updated AXIS-1912:
-
Attachment: enterprise_sfell2.wsdl
this is the stongly typed WSDL that doesn't use
> MessageElement requires inordanate ammounts o
Environment: WinXP, JDK1.5.01
Reporter: Simon Fell
Priority: Blocker
I generated client stubs from the attached WSDL, and made a call to the
retrieve method, which corectly generates this request
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001
[ http://issues.apache.org/jira/browse/AXIS-1919?page=history ]
Simon Fell updated AXIS-1919:
-
Attachment: enterprise_sfell2.wsdl
> Deserialization of derived types gets messed up
> ---
>
> Ke
[
http://issues.apache.org/jira/browse/AXIS-1735?page=comments#action_63677 ]
Simon Fell commented on AXIS-1735:
--
One thing to be aware of with this is that many tools, most noteably .NET can't
handle messages with mixed encodings, the entire me
[
http://issues.apache.org/jira/browse/AXIS-2025?page=comments#action_66649 ]
Simon Fell commented on AXIS-2025:
--
character 0x03 is not valid in XML, regardless of how you try and encode it.
> Illegal XML characters in String arguments and ret
ture
Versions: 1.2.1
Reporter: Simon Fell
Priority: Minor
provide support for handling gziped compressed requests & responses in the http
client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
[
http://issues.apache.org/jira/browse/AXIS2-80?page=comments#action_12316780 ]
Simon Fell commented on AXIS2-80:
-
For SOAP 1.1 at least, the specs are clear that the charset indicated in the
content-type header overrides any charset you might sniff from
[ http://issues.apache.org/jira/browse/AXIS-2136?page=all ]
Simon Fell updated AXIS-2136:
-
Attachment: gzip.diff.zip
Here's a patch to enable gzip for CommonsHTTPSender.
Am still working on the equivilent changes to HTTPSender. (which seems
: WinXP, JDK 5.0
Reporter: Simon Fell
Attachments: partner.wsdl
running WSDL2Code on a WSDL that has operations with headers generates code
that doesn't compile, in addition, headers get repeated multiple times in the
method signatures, e.g.
p
[ http://issues.apache.org/jira/browse/AXIS2-248?page=all ]
Simon Fell updated AXIS2-248:
-
Attachment: partner.wsdl
> WSDL with headers generates uncompilable code
> -
>
> Key: AXIS2-248
&g
[ http://issues.apache.org/jira/browse/AXIS2-249?page=all ]
Simon Fell updated AXIS2-249:
-
Attachment: enterprise.wsdl
> Exessive number & size of files generated from WSDL
> ---
>
>
0.92
Environment: WinXP, JDK 5.0
Reporter: Simon Fell
Attachments: enterprise.wsdl
The code generated from the WSDL seems to be extremely excessive both in terms
of numbers & size, are you code gen'ing the entire runtime engine??
for the same WSDL, .NET 1.1 generates 1 file that
, code from SVN as of 10/3/2005
Reporter: Simon Fell
Priority: Minor
using WSDL2Code where the WSDL operation has the soapAction defined as
should result in a generated SOAPAction header of
SOAPAction: ""
but it generates
SOAPAction:
--
This message is automatically generat
have nightly builds
---
Key: AXIS2-259
URL: http://issues.apache.org/jira/browse/AXIS2-259
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
Environment: WinXP, JDK 5.0
Reporter: Simon Fell
There don't appear to b
10/3/2005
Reporter: Simon Fell
If the WSDL defines a soap header for the operation then a parameter is
included in the stub for this header, in reality not all headers are required
and you should be able to pass null, currently if you do that, you get an NPE,
to avoid the NPE you have to c
/3/2005
Reporter: Simon Fell
the generated message for the query call in the WSDL generates 2 sets of
WS-Addressing headers (will attach WSDL & client code)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
[ http://issues.apache.org/jira/browse/AXIS2-261?page=all ]
Simon Fell updated AXIS2-261:
-
Attachment: partner.wsdl
generated the client proxies with WDSL2Code -uri partner.wsdl
> duplicate WS-Addressing headers are s
[ http://issues.apache.org/jira/browse/AXIS2-261?page=all ]
Simon Fell updated AXIS2-261:
-
Attachment: testPartnerClient.java
> duplicate WS-Addressing headers are sent
>
>
> Key: AXIS2-261
&g
[
http://issues.apache.org/jira/browse/AXIS2-261?page=comments#action_12331236 ]
Simon Fell commented on AXIS2-261:
--
The generated request is, I've reformatted the xml, so its easier to read
POST /services/Soap/u/6.0 HTTP/1.1
User-Agent: Axi
[
http://issues.apache.org/jira/browse/AXIS2-261?page=comments#action_12331237 ]
Simon Fell commented on AXIS2-261:
--
Also, you should declare the WSA namespace in the envelope (or header) element
to save repeating its declaration so many times
Reporter: Simon Fell
In the generated client code, there's no getters or setters that represent an
xsd:any in the schema, you're left to grunge around with xmlCursors yourself,
this is a PIA because the xmlCursor is not aware of where the xsd:any is
declared in the sequence, so suddenly
, JDK 5.0, code from SVN 10/3/2005
Reporter: Simon Fell
while parsing a response slightly smaller than 4Mb in size, Axis2 had to grow
the heap to ~60Mb to handle it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators
[ http://issues.apache.org/jira/browse/AXIS2-266?page=all ]
Simon Fell updated AXIS2-266:
-
Attachment: enterprise.wsdl
> can't serialize a request that contains a derived type
> --
>
>
WinXP, JDK 5.0, code from SVN 10/3/2005
Reporter: Simon Fell
Attachments: enterprise.wsdl
The WSDL (attached) defines a base type, sObject, and a type that extends it,
Account. it also defines an operation called create which take 0..n sObject's.
Trying to call this operation using the
[
http://issues.apache.org/jira/browse/AXIS-2265?page=comments#action_12332618 ]
Simon Fell commented on AXIS-2265:
--
Is the server running .NET ? by default a .NET server won't accept a request
larger than 4Mb, so Axis is correctly reporting wha
[ http://issues.apache.org/jira/browse/AXIS-1799?page=history ]
Simon Fell updated AXIS-1799:
-
Attachment: partner.wsdl
> WSDL2Java generates name clashes now didn't in 1.1 or
: 1.2
Environment: XP / JDK 1.4.2_03
Reporter: Simon Fell
Priority: Critical
Attachments: partner.wsdl
Somewhere between 1.2 RC1 and the 02/02/2005 CVS drop, I now get this error
from the attached WSDL
org.apache.axis.wsdl.toJava.DuplicateFileException: Duplicate file name:
com\s
.2RC2
Environment: XP / JDK 1.4.x /
Reporter: Simon Fell
This actually with the 1.2 RC3
If the WSDL contains a element, this is mapped to a MessageElement [], in
Axis 1.1 calling getValue on one of these MessageElement's would return the
contents of the element post XML processing, in Axis
1 - 100 of 107 matches
Mail list logo
