First of all, thank you for your quick response. "bschmoll1" wrote : | I don't know how you're packaging the HL7 schemas, but you could try reducing the number of schemas down to the message type your actually interested in, which appears to be the PRPA_IN201101UV01, plus base schema's. | Yes, PRPA_IN201101UV01 is the schema that contains the message definition, but it has dependences on the other schemas, so I cannot reduce the number with getting a deployment exception because the deployer cannot locate referenced resources. I'm packaging them as resources in the jar file, so they are available when the deployment is done.
"bschmoll1" wrote : It looks to me like there are a number of message types that are being parsed that don't seem relevant to the WSDL, MCCI_MT000100UV01.xsd, COCT_MT040203UV01.xsd. I assume each of these also have references to the datatypes.xsd, voc.xsd and the other base schema's, which is why there are numerous references to them. I would hope that those definitions would be cached and not be loaded into memory multiple times, but given the OutOfMemoryException that may be what is occuring. | I guess the cache is not working and the stack is loading the same schemas a lot of times. If it is a problem of memory, it is a high issue, as this example implements a really simple use case out of the more than 1000 available. JBossWS should be able to deal with the total amount of data loaded from shemas (less than 2 Mb), which I don't know end up in more than 1 Gb when exploded into memory. Again, thank you very much. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193807#4193807 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193807 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
