Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2143

Hotdeployed components can't be configured through components.xml

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0.CR2
    • Fix Version/s: The future
    • Component/s: Hot Deploy
    • Labels:
      None

      Description

      he hot deployment scanner is isolated, using a URLClassloader that is not available once that method comes to a close. The only way to make this work would be to keep that classloader alive during the rest of the startup process. I can direct you to the line of code that you need to look at if you are curious about it.

      Check out lines 540 and 541 or org.jboss.seam.init.Initialiation. The scanForHotDeployableComponents uses the following logic to create a component scanner:

      URL[] urls =

      { url }

      ;
      classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader());
      paths = new File[]

      { directory }

      ;

      Once it processes the classes, that classloader is discarded and obviously, since it is a URLclassloader, the classes aren't going to be found later on.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  pmuir Pete Muir
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: