SV: Axis2/c source in VS

Here are the *.vcproj and axis2c.sln Let me know if there is anything else you need. /Indra -Ursprungligt meddelande- Från: Supun Kamburugamuva [mailto:[EMAIL PROTECTED] Skickat: to 2008-09-18 16:22 Till: Apache AXIS C Developers List Ämne: Re: Axis2/c source in VS Yes, That would be

[jira] Created: (AXIS2-4038) Getting Error 500--Internal Server Error org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 start byte 0x93 (at char #2885, byte #-1)

Getting Error 500--Internal Server Error org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 start byte 0x93 (at char #2885, byte #-1)

[jira] Updated: (AXIS2-4038) Getting Error 500--Internal Server Error org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 start byte 0x93 (at char #2885, byte #-1)

[ https://issues.apache.org/jira/browse/AXIS2-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiranmoy Chakraborty updated AXIS2-4038: Attachment: ManageClientDeviceRegister.20080902.wsdl build.xml The

Re: Problem in rendering CDATA tag.

Hi, I managed to isolate the problem. The problem vanishes when Rampart module is not engaged in axis2.xml. I can get the ![CDATA[ ]] intact. However, when I engage the rampart module, the CDATA tag is removed. I have used Rampart 1.4 , example 04. The steps to reproduce is shown below. 1.

Problem printing a WSDL (when we have useOriginalwsdl = true and wsdlImportLocationAdjusted = true)

Hi all, I am using latest Axis2 1.4.1. In my axis2.xml I have set useOriginalwsdl = true. The AAR I am deploying has a WSDL that in turn imports another WSDL. This is specified in the following way: import namespace= http://multiarray.interoperability.wsstack.softwareag.com/ext/;

[jira] Commented: (AXIS2-2148) AxisFault: Mapping qname not fond for the package:...

[ https://issues.apache.org/jira/browse/AXIS2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632685#action_12632685 ] keyevent commented on AXIS2-2148: - I am having the same issue with axis2 1.4.1, it is quite

[jira] Created: (AXIS-2759) org.xml.sax.SAXException: Invalid element

org.xml.sax.SAXException: Invalid element -- Key: AXIS-2759 URL: https://issues.apache.org/jira/browse/AXIS-2759 Project: Axis Issue Type: Bug Components: Serialization/Deserialization,

[jira] Created: (AXIS2-4039) JAXWS: Store the exception thrown from a web method implementation in a property so that it can be queried by an outbound jaxws handler

JAXWS: Store the exception thrown from a web method implementation in a property so that it can be queried by an outbound jaxws handler --- Key:

[jira] Resolved: (AXIS2-4039) JAXWS: Store the exception thrown from a web method implementation in a property so that it can be queried by an outbound jaxws handler

[ https://issues.apache.org/jira/browse/AXIS2-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4039. --- Resolution: Fixed JAXWS: Store the exception thrown from a web method implementation in a

Re: [AXIS2] Should JSON messages be considered as REST?

+1 .. but I'm a bit confused. I assume by "REST" you meant that the response has media type text/xml instead of application/soap+xml, right? If we think about it that way, can we get rid of the "isDoingREST" flag?? (I've hated that from day 1 and haven't had a chance to really dig thru it

Re: [AXIS2] Should JSON messages be considered as REST?

Let me describe the problem in more detail. As of now Axis2 enables you to plug in various message types by registering them in the axis2.xml. Some of these message types will be SOAP based (like text/xml and application/soap+xml) while others are not. And in the latter case when a exception