Mule

Make sure the Transport archetype works with the new message API

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0-M2
  • Fix Version/s: 2.0.0-RC1
  • Component/s: Build: Maven
  • Labels:
    None
  • User impact:
    High
  • Similar Issues:
    MULE-2451 mule-transport-archetype has invalid method signature for overriding AbstractPollingMessageReceiver
    MULE-4618 archetypes not working
    MULE-2288 Maven archetype is not working for creating new connectors.
    MULE-4017 Make the Maven archetypes provide more value to the end users
    MULE-3330 mule-transport-archetype is not up to date with the latest API
    MULE-4066 Error output when running new maven transport archetype
    MULE-2556 The new Message API changes cause the Script Example test case to behave differently
    MULE-1104 Create a new Transport Archetype
    MULE-5162 Dynamic endpoints don't work for VM and JMS transport
    MULE-2810 Archetype needs updating for 2.0-RC1

Description

I know ofr a fact that the streaming option in the transport archetype is no longer needed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment - 17/Nov/07 04:35 PM

fixed. We really need to figure out a way to run the archetype and compile the result as part of the Maven test phase

Show
Ross Mason added a comment - 17/Nov/07 04:35 PM fixed. We really need to figure out a way to run the archetype and compile the result as part of the Maven test phase

People

Vote (0)
Watch (0)

Dates

  • Created:
    12/Nov/07 11:35 PM
    Updated:
    17/Nov/07 04:35 PM
    Resolved:
    17/Nov/07 04:35 PM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.