Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5484

resteasy-springMVC example doesn't post the contacts form correctly when run in JBoss

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1 ER2
    • EAP_EWP 5.1.0
    • RESTEasy
    • None
    • Not Required

    Description

      when run in JBoss resteasy-springMVC example runs in this context url
      http://localhost:8080/resteasy-springMVC
      but the contacts form
      http://localhost:8080/resteasy-springMVC/contacts
      tries to post to
      http://localhost:8080/contacts
      which results to error code 404.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5051 zip file problem in resteasy-springMVC example

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-542 Absolute path used in contacts.jsp of resteasy-springMVC example

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-486 Improve the documents writing for example resteasy-springMVC/README.TXT

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              weli@redhat.com Weinan Li
              mlinhard Michal Linhard (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: