JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-5095

DefaultMessageCollection getPayloadAsBytes() and getPayloadAsString(enc) throw UnsupportedOperationException

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 3.0.0
  • Fix Version/s: 3.0.1, 3.1.0
  • Component/s: Core: API
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

The issue of having these 2 methods throw an UOE is that they are called by Mule itself, like in DefaultMuleEvent.getMessageAsString(enc).

I don't think it is a correct behavior for Mule to trip on its own UOEs.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Transition Time In Source Status Execution Times Last Executer Last Execution Date
Open Open Closed Closed
52d 6h 47m 1 Matt Brandabur 08/Nov/10 06:41 PM

People

  • Assignee:
    Matt Brandabur
    Reporter:
    David Dossot
Vote (0)
Watch (0)

Dates

  • Created:
    17/Sep/10 12:54 PM
    Updated:
    08/Nov/10 06:41 PM
    Resolved:
    08/Nov/10 06:41 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.