Improving faultstring messages for type restrictions

Hi, I'm a relative newcomer to Axis2 and this is my first encounter with this list. I'm pretty sure this is a question you've had time-and-again, although I've had no joy in the list archives - I probably don't know the correct terminology to frame my question. I am using Axis2 to support web-ser

Re: Improving faultstring messages for type restrictions

Hi David, I think your point is valid but I'm not sure whether we can improve fault strings up to your expectation. BTW we can improve this up to some level instead of sending "unknown". Please fill a JIRA issue for this and will try to target next major release. Thanks ! On Wed, Jan 11, 2012 a

RE: Improving faultstring messages for type restrictions

Hi David,   that is something I was running into as well.   I did not have a quick solution for that and therefore did what you should not do: I hacked the generated code. I hope others have a more sophisticated and Axis2-like solution to that.   In the WSDL, I created a WrongArgumentFaultType

Re: Improving faultstring messages for type restrictions

Hi Sagara, On 11 January 2012 11:35, Sagara Gunathunga wrote: > I think your point is valid but I'm not sure whether we can improve fault > strings up to your expectation.  BTW we can improve this up to some level > instead of sending "unknown". Please fill a JIRA issue for this and will try > to

Re: Improving faultstring messages for type restrictions

Hi Sven, I considered modifying the ADBs, but we regenerate ours on each build. We're already using the basic pattern of a custom fault type for user-level validation (with localisation), but I wanted to keep this faultstring mechanism separate, for low-level API faults. I guess I could just add

Exception names in WSDL

Hi All, I am new to AXIS2 and got couple of questions as mentioned below on Fault names in AXIS2 generated WSDLS : 1. When I create a .aar file using Service Archiver plugin version 1.3.0 (generating service xml automatically) , it is adding the service name before my exception name.

How to protect against large inline base64 strings when using MTOM for attachment uploads?

Hi All, I'm using MTOM support in Axis2 to support the upload of one or more attachments per web service request, and have cacheAttachments=true in axis2.xml so that uploaded MIME attachments are spooled to disk to prevent OutOfMemoryErrors. This works great as long as the attachments are p