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-3198

Unable to use java.io.File payload with file transport

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

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0
  • Fix Version/s: 2.0.1
  • Component/s: Transport: File
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

When using streaming FileMessageAdaptor with a FileInputStream payload is used by default.

When not using streaming FileContentsMessageAdaptor is used with a byte[] payload is used by default.

Since work on the file transport to make streaming work correctly it is no longer possible to pass a java.io.File payload.

We either need to:
i) Create a 3rd message adaptor for this case (which I suppose would only be used when overriding defaults)
ii) Make the FileMessageAdaptor a bit more intelligent so if it is created with a File getPayload() returns a file, and it is was created with a FileInputStream it returns a FileInputStream when getPayload() is called.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Java Source File
    FileObjectMessageAdapter.java
    09/Apr/08 07:50 AM
    2 kB
    Markus Demolsky
  2. Java Source File
    FileObjectMessageAdapterTestCase.java
    09/Apr/08 07:50 AM
    2 kB
    Markus Demolsky

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MULE-3199 Connectors should have default streaming message adaptor specified in service descriptor

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

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
2d 3h 8m 1 Daniel Feist 10/Apr/08 01:24 PM

People

  • Assignee:
    Daniel Feist
    Reporter:
    Daniel Feist
Vote (0)
Watch (1)

Dates

  • Created:
    08/Apr/08 10:15 AM
    Updated:
    10/Apr/08 01:24 PM
    Resolved:
    10/Apr/08 01:24 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.