We're doing a feasibility study on GLUE 4.1.2 running in a JBoss 3.2.3 container, and are having some trouble when both the GLUE client and endpoint are in the same JVM.
Out test setup consists of a simple GLUE service running in one web application and a simple GLUE client running in another web application, both in the same JBoss instance. Basic SOAP request/reply envelopes go through just fine, but MIME/DIME attachments cause UnMarshall/NullPointer exceptions.
Running the test service and client applications in two different JBoss instances work flawlessly.
This seems to have something to do with GLUE detecting that the client and endpoint are in the same JVM, and switching to RMI instead of HTTP for transport.
Are there any RMI settings in JBoss that could affect this process?
OK. Two fixes. One, deploy GLUE client and service in two different EAR files, each specifying their own classloader as defined by the "Scoping" documentation.
Two, wait until WebMethods releases GLUE 5.0 and deploy in one EAR file.