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

pageflow-2.1.xsd resolved from internet rather than from classpath

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • EAP_EWP 5.1.1
    • EAP 5.0.0
    • Seam, Testsuite
    • None
    • Hide
      The JpdlParser in JBPM included some hard-coded file names of XSDs, which referred to internet locations and ignored XSDs in the classpath. This caused failures when those internet locations were unavailable. The hard-coded paths have been removed and the classpath is now searched for the XSDs.
      Show
      The JpdlParser in JBPM included some hard-coded file names of XSDs, which referred to internet locations and ignored XSDs in the classpath. This caused failures when those internet locations were unavailable. The hard-coded paths have been removed and the classpath is now searched for the XSDs.
    • Documented as Resolved Issue

    Description

      As you can see in https://jira.jboss.org/jira/browse/SOA-936?focusedCommentId=12507924#action_12507924 we noticed a problem where seam tests are trying to resolve http://jboss.com/products/seam/pageflow-2.1.xsd and times out because that is at the moment not available.

      Namely the tests are:
      org.jboss.test.deployers.seam.test.SeamDvdExampleUnitTestCase
      org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase

      Reading http://seamframework.org/Community/HeadsUpOnPossibleDeploymentErrorHTMLVersion it makes sense to have schema files in the test suite classpath. It is really a time waster to have test suites depend on internet resources that will always die when you need them. And IMHO testability or products is what really can allow us scale.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBPM-1710 Provide local reference for Seam pageflows to pageflow-2.0.xsd

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPM-2774 parsing of pageflow causes to require internet connection

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPM-1707 pageflow parsing is slow

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-5740 Upgrade JBPM 3 to 3.2.10 from SOAP 5.1.0

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              mnovotny@redhat.com Marek Novotny
              akostadi1@redhat.com Aleksandar Kostadinov
              Misty Stanley-Jones Misty Stanley-Jones (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: