Mule

Transport archetype is out of date with current 2.0 API

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0
  • Fix Version/s: 2.0.2
  • Component/s: Tools
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    MULE-3330 mule-transport-archetype is not up to date with the latest API
    MULE-2684 Make sure the Transport archetype works with the new message API
    MULE-2810 Archetype needs updating for 2.0-RC1
    MULE-5172 mule-catalog-archetype has no tests, generates broken code
    MULE-4859 Update transport archetype to create a custom MuleMessageFactory
    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-2933 Transport Archetype should not produce MessageAdapter class by default
    MULE-3409 A few issues with the transport archetype
    MULE-5688 Out-of-box project archetype fails with unexpected NullPayload

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dirk Olmes added a comment - 14/Apr/08 09:28 AM

Another comment from the same thread:

It would also be nice if the generated test cases reflected the answers given to the questions asked by the archetype. For
example, tests are created for the receiver also when answering 'n' to the question about supporting inbound requests. Similarly, a MuleEndpointURI class is used for the EndpointURI in the xxxEndPointTestCase, also when specifying a socket endpoint (where a SocketEndpointURIBuilder should be used instead).

Show
Dirk Olmes added a comment - 14/Apr/08 09:28 AM Another comment from the same thread:
It would also be nice if the generated test cases reflected the answers given to the questions asked by the archetype. For example, tests are created for the receiver also when answering 'n' to the question about supporting inbound requests. Similarly, a MuleEndpointURI class is used for the EndpointURI in the xxxEndPointTestCase, also when specifying a socket endpoint (where a SocketEndpointURIBuilder should be used instead).
Hide
Permalink
Daniel Feist added a comment - 17/Apr/08 02:47 PM

Made some updates in this changeset some more might be needed though. Ideally we should expend archetype test case if it is not catching this simple complication errors.

http://fisheye.codehaus.org/changelog/mule/?cs=11571

Show
Daniel Feist added a comment - 17/Apr/08 02:47 PM Made some updates in this changeset some more might be needed though. Ideally we should expend archetype test case if it is not catching this simple complication errors. http://fisheye.codehaus.org/changelog/mule/?cs=11571
Hide
Permalink
Dirk Olmes added a comment - 29/Apr/08 07:04 AM

I think Dan has fixed the issues with the archetype so far.

I left this issue open to increase the coverage of the archetype test, i.e. when generating a sample project from the archetype, make sure the maximum number of features are turned on. This may as well be solved in 2.0.2.

Show
Dirk Olmes added a comment - 29/Apr/08 07:04 AM I think Dan has fixed the issues with the archetype so far. I left this issue open to increase the coverage of the archetype test, i.e. when generating a sample project from the archetype, make sure the maximum number of features are turned on. This may as well be solved in 2.0.2.
Hide
Permalink
Dirk Olmes added a comment - 07/May/08 02:45 AM

The issue itself should be resolved now with the changesets referenced above.

Keeping this issue open, though, until the CI server is fixed.

Show
Dirk Olmes added a comment - 07/May/08 02:45 AM The issue itself should be resolved now with the changesets referenced above. Keeping this issue open, though, until the CI server is fixed.
Hide
Permalink
Dirk Olmes added a comment - 12/May/08 07:43 PM

CI server running test successfully.

Show
Dirk Olmes added a comment - 12/May/08 07:43 PM CI server running test successfully.

People

Vote (0)
Watch (0)

Dates

  • Created:
    11/Apr/08 07:20 PM
    Updated:
    12/May/08 07:43 PM
    Resolved:
    12/May/08 07:43 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.