Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.0 CR2
    • Fix Version/s: 4.0
    • Component/s: None
    • Labels:
      None

      Description

      I think I've another classloader puzzle for ye to tease out So, we have the 2 sars now. The service gets deployed into jbossesb.sar and the dependencies into the other etc etc.

      One of the quickstarts (transform_XML2POJO) defines an action that follows a SmooksTransformer action. This 2nd action expected some POJO instances to be attached to the message (attached and populated by Smooks). The

      The classloading gets screwed because Smooks uses the jbossesb-dependencies.sar classloader (because it's in that .sar) to load the POJO bean class instances that are attached to the message. The action instance extracts the beans from the message and tries to cast them but because that action class is in the jbossesb.sar it uses the jbosses.sar classloader to load the POJO class instances, we get a ClassCastException.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kconner Kevin Conner
                Reporter:
                tfennelly Tom Fennelly
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: