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

    • Release Notes Text:
      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.
    • Release Notes Docs Status:
      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.

        Gliffy Diagrams

          Attachments

            Issue Links

            is blocked by

            Feature Request - A new feature of the product, which has yet to be developed. JBPM-1710 Provide local reference for Seam pageflows to pageflow-2.0.xsd

            • Major - A request that should be considered seriously but is not a show stopper.
            • Resolved

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

            • Major - A request that should be considered seriously but is not a show stopper.
            • Resolved

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

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

            Task - A task that needs to be done. JBPAPP-5740 Upgrade JBPM 3 to 3.2.10 from SOAP 5.1.0

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. SOA-935 Access restrictions inconsistent between legacy SOA-P consoles and JON enterprise console

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  akostadinov Aleksandar Kostadinov
                  Writer:
                  Misty Stanley-Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: