axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Commented: (AXIS2-4363) Classcast exception when enabling MTOM with ADB
Date Tue, 02 Jun 2009 21:27:07 GMT


Andreas Veithen commented on AXIS2-4363:

The problem is caused by the fact that some parts of Axis2 code directly use
This needs to be changed so that the code refers to the corresponding interface(s), i.e. OMXMLStreamReader
and OMAttachmentAccessor. There are actually several reasons for this:

1. If the log level is set to DEBUG, OMElementImpl#getXMLStreamReader wraps the OMStAXWrapper
in a OMXMLStreamReaderValidator. This causes the issue described above.
2. is part of axiom-impl (the LLOM implementation
of Axiom), but Axis2 should ideally only refer to axiom-api.
3. It's against the programming-to-interface paradigm.
4. In Axiom trunk, OMStAXWrapper has been merged with the corresponding class from the DOOM
implementation and now lives in axiom-api (as
still exists, but only for compatibility reasons. It would be great if we could eliminate
it on the longer term.

Files in Axis2 that refer to

modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate.xsl -> this means
that wsdl2java generates code that refers to

> Classcast exception when enabling MTOM with ADB 
> ------------------------------------------------
>                 Key: AXIS2-4363
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: ADB databinding
>            Reporter: Julien Henry
>            Assignee: Andreas Veithen
> When enabling MTOM and generating client stub with ADB, I get the following error when
using my WS to download attachments:
> {code}
> java.lang.ClassCastException:
> cannot be cast to
>   at$XXXBundleType$Factory.parse(
>   at$DownloadXXXResponse$Factory.parse(
>   at
> {code}
> This error only occurs when log level for org.apache.axiom is DEBUG so a workaround is
to set log level > DEBUG.
> The bug is also present with staged 1.5 version.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message