Thanks for your help, Andreas. JIRA issue created: AXIS2-4468
Michael
On Tue, Aug 18, 2009 at 10:17 PM, Andreas Veithen wrote:
> Michael,
>
> The following log message is interesting:
>
> org.apache.axiom.om.impl.MTOMXMLStreamWriter - Returning access to
> the original output stream: java.io.
Michael,
The following log message is interesting:
org.apache.axiom.om.impl.MTOMXMLStreamWriter - Returning access to
the original output stream: java.io.bufferedoutputstr...@14181418
It means that the xmlbeans databinding bypasses the normal StAX
XMLStreamWriter and writes part of the output d
Michael,
Can you test this with 1.5 and if the problem persists, create a
minimal AAR that reproduces the problem (so that we can debug it)?
Andreas
On Fri, Aug 14, 2009 at 12:27, Michael Fryars wrote:
> Axis2 v1.4.1, running in a WAR in a tomcat 6 container.
>
> On Fri, Aug 14, 2009 at 12:20 PM
Axis2 v1.4.1, running in a WAR in a tomcat 6 container.
On Fri, Aug 14, 2009 at 12:20 PM, Andreas Veithen wrote:
> Which version of Axis2 do you use?
>
> Andreas
>
> On Fri, Aug 14, 2009 at 11:39, Michael Fryars wrote:
> > Hello,
> > I'm seeking some advice/help with a character encoding problem
Which version of Axis2 do you use?
Andreas
On Fri, Aug 14, 2009 at 11:39, Michael Fryars wrote:
> Hello,
> I'm seeking some advice/help with a character encoding problem with an axis2
> service (i.e. server side).
>
> When my service receives a (WS/SOAP) request with:
> Content-Type: text/x
Hello,
I'm seeking some advice/help with a character encoding problem with an axis2
service (i.e. server side).
When my service receives a (WS/SOAP) request with:
Content-Type: text/xml; charset=UTF-8
in the HTTP header, everything works fine, any unusual charcters in the
response are correc
