Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 39315 invoked from network); 8 Sep 2003 12:42:24 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Sep 2003 12:42:24 -0000 Received: (qmail 96717 invoked by uid 500); 8 Sep 2003 12:42:07 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 96589 invoked by uid 500); 8 Sep 2003 12:42:06 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 96570 invoked from network); 8 Sep 2003 12:42:06 -0000 Received: from unknown (HELO www.princetongames.org) (66.250.40.202) by daedalus.apache.org with SMTP; 8 Sep 2003 12:42:06 -0000 Received: from localhost (ammulder@localhost) by www.princetongames.org (8.11.6/8.11.6) with ESMTP id h88C4RZ31216 for ; Mon, 8 Sep 2003 08:04:27 -0400 X-Authentication-Warning: www.princetongames.org: ammulder owned process doing -bs Date: Mon, 8 Sep 2003 08:04:27 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@www.princetongames.org To: geronimo-dev@incubator.apache.org Subject: [JMX] Streaming data to an MBean Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The JSR-88 implementation needs to send the finished module to the server to deploy, which can generally happen over the network. The only way I know of to invoke a server component this way is to defined an MBean method that takes a byte array. But I'd really rather avoid loading the whole module in memory (I've seen 10MB EARs before, usually full of static content and third-party libraries, and I'm sure that's not the biggest). Is there any way to stream the data to a JMX MBean, and let it spool it to disk as it arrives? Or should we consider having something like an always-on servlet that accepts application uploads from the JSR-88 deployer, puts them somewhere sensible on disk, and returns a URL on the server filesystem which then the JSR-88 deployer can pass with the DDs to a normal deploy call on a deployer MBean? Thanks, Aaron