glassfish
  1. glassfish
  2. GLASSFISH-18073

Named query validation happens too late

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.2_dev, 4.0_dev
    • Fix Version/s: 3.1.2_dev, 4.0_dev
    • Component/s: entity-persistence
    • Labels:
      None

      Description

      Currently Named query validation happens at first EM creation. This results in two issues.
      1. Archives with invalid named queries are deployed successfully and we get a runtime exception while using them
      2. If Java2db is turned on, the exception for named query validation gets the container into an inconsistent state.

      This issue has been reported in various user forums and we have also observed Arun struggling with it while developing JavaOne demo.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Mitesh Meswani
            Reporter:
            Mitesh Meswani
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: