Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E6AB82C.1060500@verizon.net>
Date: Sat, 08 Mar 2003 19:42:36 -0800
From: Christopher Oliver <res1cf5x@verizon.net>
Reply-To: coliver@apache.org
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US;
 rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: Pier Fumagalli <pier@betaversion.org>
CC: cocoon-dev@xml.apache.org
Subject: Re: Great shot (IDL and stuff)...
References: <BA8C4774.152EA%pier@betaversion.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Pier,

If you want the IDL for Java classes you could try using the rmic 
compiler that comes with the jdk. Just do

        rmic -idl java.io.OutputStream

for example.

Otherwise, I don't think you need a JavaObject, etc. You can just do

module java {
    module lang {
         interface Object {
         };
    };
};


Regards,

Chris

Pier Fumagalli wrote:
> That is what I wanted... I didn't know that OpenORB (which is moving to
> Apache once Intalio gets around on its ass and signs the transfer letter)
> had a IdlDoc tool...
> 
> That _is_ going to make my life _so_easy_ you won't believe it...
> 
> BTW, can we split the big "Cocoon.idl" into separate files? What do you
> think? Also, the module name should be "cocoon_flow", so that we can use the
> "cocoon" module for other bindings in the future...
> 
>     Pier
> 
>