Axis 2 1.1.1 download fails...

Minor technical issue - I am trying to download the official Axis2 1.1.1 release, but the web page: http://ws.apache.org/axis2/download/1_1_1/download.cgi Returns a 500 error... -justin - To unsubscribe, e-mail: [EMAIL PROTECTE

Re: SOAPAction required?

Amila Suriarachchi wrote: On 1/10/07, *Justin Schoeman* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: OK - Appending the operation name to the URL does work, but I am not sure if .Net does this (I do not have .Net, just some recorded messages). From what I

Re: SOAPAction required?

OK - Appending the operation name to the URL does work, but I am not sure if .Net does this (I do not have .Net, just some recorded messages). From what I can read on the web, routing is supposed to occur via the first tag in the SOAP body (in this case a confirmCustomerReq message). I reali

Re: SOAPAction required?

From what I can understand, the empty string is deliberate. The service is supposed to call the correct operation for the supplied message. The SOAP documentation lists SOAPAction as required, but may be "" if no additional message routing information is required. wsdl file: http://nrs.eskom.

SOAPAction required?

I am busy testing an application at the moment (against the 9 January snapshot). When I test with an AXIS2 generated client, all works fine, but when testing with a .Net client, I get an 'The endpoint reference (EPR) for the Operation not found is http://192.168.1.10:8080/axis2/services/XMLVe

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12441169 ] Justin Schoeman commented on AXIS2-586: --- The client code is on: http://www.schoeman.org.za/axis2_test_client.tbz It is hard coded to call either of the test

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12441160 ] Justin Schoeman commented on AXIS2-586: --- Just finished testing with the 4 October nightly build. Results are the same as previous tests. The ID is still

Re: AW: [Axis2] Missing xsi:type in SOAP-Message

hrough the XMLStreamReader returned by XMLBeans, the problem either has to do with the AXIOM tree or the returned stream reader implementation. On 8/4/06, Justin Schoeman <[EMAIL PROTECTED]> wrote: AXIS2-455 as well. I tried to open another one, but Jira kept on timing out. Completely forgot to repo

Re: AW: [Axis2] Missing xsi:type in SOAP-Message

even more when interoperating with dotNET with inherited types... -justin Davanum Srinivas wrote: Justin, I see only 1 issue from you which is AXIS2-586. Are there others? -- dims On 8/4/06, Justin Schoeman <[EMAIL PROTECTED]> wrote: Abandon all hope ye who enter here ;-) ... Even wh

Re: AW: [Axis2] Missing xsi:type in SOAP-Message

Abandon all hope ye who enter here ;-) ... Even when you get xsi:type working, deserialisation is also completely broken. I have opened a number of Jira's on these issues, but never had much luck. Tried to debug it myself too, but failed miserably. If you have any better luck, please let me

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12375980 ] Justin Schoeman commented on AXIS2-586: --- The following files are required (in the same directory): http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12375096 ] Justin Schoeman commented on AXIS2-586: --- Server responses are still not always correctly serialised. For example, two successive fields in the response message, both are

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12375086 ] Justin Schoeman commented on AXIS2-586: --- OK - This only seems to affect deserialisation on the server. The client works correctly. -justin > CLONE -Axis2 does

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12374971 ] Justin Schoeman commented on AXIS2-586: --- This does not seem to be entirely resolved in Axis2 0.95. Using the same configuration as before (except for Axis2 0.95 instead

[jira] Created: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

) Type: Bug Versions: 0.94 Environment: Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94 Reporter: Justin Schoeman Assigned to: Ajith Harshana Ranabahu When receiving WSA encoded messages containing abstract types, the created objects are for the implementation of the

[jira] Commented: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

[ http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12369409 ] Justin Schoeman commented on AXIS2-455: --- 1) This problem seems to be server side, although I assume it will affect both sides. The original problem I experienced was

Re: [jira] Commented: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

abahu wrote: Hi all, I'm surprised to hear that XMLbeans fails to do the right thing! May be we need to redirect the issue to some of the XMLBeans gurus ? Ajith On 3/2/06, Justin Schoeman <[EMAIL PROTECTED]> wrote: Personally, I would love it if this was fixed! But I don

Re: [jira] Commented: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

with Vistual studio .NET 2003 client Reporter: Justin Schoeman Priority: Blocker I have been getting the following error message connecting C# clients to an Axis2 service: There is an error in XML document (1, 877). ---> System.InvalidOperationException: The specified type is abstra

[jira] Commented: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

[ http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12368248 ] Justin Schoeman commented on AXIS2-455: --- Well, I don't know if it is blocker, or not, but interoperability _is_ fairly important for a webservices platform... O

[jira] Created: (AXIS2-479) Axis2 does not deserialise abstract types correctly when receiving WSA messages

: Bug Versions: 0.94 Environment: Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94 Reporter: Justin Schoeman When receiving WSA encoded messages containing abstract types, the created objects are for the implementation of the abstract class, instead of the actual type sent over the wire

[jira] Commented: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

[ http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12367257 ] Justin Schoeman commented on AXIS2-455: --- I forgot to mention, the webservice is generated with -d xmlbeans. Full generation command is: java -classpath $AXIS2_CLASSPATH

Need help fixing interoperability bug.

Hi all, I have recently started using Axis2 (0.94) for a project, and have encountered a problem when connecting to MS C# clients. I have logged the bug on JIRA (AXIS2-455). Basically, the problem is that, with abstract parameter types, the 'type' attribute should actually be 'xsi:type'.

[jira] Created: (AXIS2-455) Axis2 dotNET interoperability problem with abstract types.

: Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94 Windows XP with Vistual studio .NET 2003 client Reporter: Justin Schoeman Priority: Blocker I have been getting the following error message connecting C# clients to an Axis2 service: There is an error in XML document (1, 877