Uploaded image for project: 'DeltaSpike'
  1. DeltaSpike
  2. DELTASPIKE-335

re-visit support of EARs

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 0.4
    • None
    • None
    • None

    Description

      #1
      our current approach to get rid of basic classloader issues (esp. with EARs) is to collect information during bootstrapping and inject the extension instance to consume the result later on. that can expose the collected information of one web-app to other web-apps (of the same EAR). in codi we used the classloader as key, however, this approach also has disadvantages.
      (something like @WebApplicationName would only work in some cases.)

      #2
      there was no real agreement about https://issues.jboss.org/browse/CDI-129.
      currently we expect that @ApplicationScoped is separated per web-app.
      however, that's at least not the case with current versions of weld.
      -> (at least for current versions of weld) we have to think about an own @WebApplicationScoped

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            struberg Mark Struberg
            gpetracek Gerhard Petracek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment