Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-697

Exception "Could not deploy to container" should report the real exception why the managed server is failing

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Done
    • None
    • None
    • None
    • None

    Description

      Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container".

      The real exception should be reported, for example "port in use".

      Furthermore, the message is unclear: how far does this "Could not deploy to container" message stretch? If we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported with this exception or not?

      Attachments

        Issue Links

          Activity

            People

              ozizka_jira Ondrej Zizka (Inactive)
              gdesmet@redhat.com Geoffrey De Smet
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: