This can be fixed by simply removing the OMText.isComplete() method.. I have done the change in my local codebase and it works.. But cannot commit due to shaky connection.
If anybody is in urgent need of this, go ahead and change it... If not I'll commit it by tommorow with a test case...
Thanks,
~Thilina
On 5/21/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
It's the least I expected... I fixed this bug for Axis2 .9 and now I found that somebody has reverted the fix....My bad... I should have add a test case :(....
~Thilina
On 5/20/06, Timo Ahokas (JIRA) <[EMAIL PROTECTED] > wrote:[ http://issues.apache.org/jira/browse/AXIS2-753?page=comments#action_12412575 ]
Timo Ahokas commented on AXIS2-753:
-----------------------------------
Seems to only occur when ENABLE_MTOM is also set to true (only setting the SOAP 1.2 version doesn't cause this error).
> Setting SOAP Version URI to type 1.2 creates invalid Content-Type that fails during parsing
> -------------------------------------------------------------------------------------------
>
> Key: AXIS2-753
> URL: http://issues.apache.org/jira/browse/AXIS2-753
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Versions: 1.0
> Environment: Windows XP, Tomcat 5.5, Eclipse + Sysdeo plugin
> Reporter: Timo Ahokas
> Attachments: TestCode2.zip
>
> When setting SOAP version is set to 1.2 on the client (via options.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI)), the action parameter is empty and is encoded in the following way:
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_26C55753A5E981E64A11479668765601;
> type="application/xop+xml";
> start="< 0.urn:uuid:[EMAIL PROTECTED]>";
> start-info="application/soap+xml"; charset=UTF-8;action=""
> This action part is invalid due to the multiple quotes and the server fails to parse it in
> javax.mail.internet.ParameterList constructor, resulting in a "SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope" which masks the OMException with a
> "Invalid Content Type Field in the Mime Message" message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
