Hey Jacek,
I'm certainly into trying to work this stuff out with you. Maybe between the two of us, we can create some nice docs and some helpful code. About create_stubs.(bat|sh): it generates CORBA tie and stub classes. I'm fairly certain that CORBA is really used more for interoperating with other CORBA applications, and that pure java bean classes can (should?) use RMI without CORBA -- I definitely saw many of these stub/tie classes sprinkled amongst the test classes, and I didn't see any RMI skeleton classes, so maybe they're using CORBA rather than RMI? Can someone who knows something about this clarify? I do see that the java class doing the compiling in create_stubs is org.openorb.rmi.compiler.JavaToIdl... maybe RMI and CORBA aren't really as different as I thought? Does RMI really need all the request brokering services that CORBA offers? Doesn't CORBA impose a fair amount of overhead? I suppose using CORBA makes the bean classes available from other languages, as I thought that was one of the main points of CORBA... guess I'll go search google. ;) --Peter On Tuesday, August 13, 2002, at 04:20 AM, LASKOWSKI,JACEK (HP- Poland,ex1) wrote: > Peter, > > Certainly, there's no much help in the docs as to how to deploy entity > beans > with all the stuff like preparing mapping files, etc. The number of > documentation pages are also not very appealing - and it needs to be > changed > very soon *if* we want to encourage users to use the product nor > looking for > help searching the source code. > > So, nice to see you and me (two novice users) are keen to change it - > one is > about to write an application, and another (it's me) is about to write > some > documentation on CMP/BMP entity beans and the process of deploying it. > Excellent. > > Although the docs are loosly coupled (as the code should be, but docs > should > rather not :-)) I think I know the answer for your question - the > answer is > create_stubs.[bat|sh] script. I don't know yet how to use it, but the > very > first glance at the script has revealed it might be what you're after. > > Before I write anything I need to understand slightly the *MP entity > deployment in OpenEJB. The process (likewise to the same process in > other > EJB containers) might be divided on the following steps: > > 1/ Create an entity bean > 2/ Generate necessary stubs/skeletons which are container-specific > 3/ Database configuration in the container (so it's available during the > mapping) > 4/ Map the fields to the database > 5/ Deploy it to the container > 6/ Test it out > > The 1/ is done. Now, I'm at 3/ skipping 2/ (hoping you will sort it > out :-)) > and trying to figure out the structure and meaning of the configuration > file > (conf/openejb.conf). As the openejb.conf file is XML file, the > structure of > the file would be described in XML Schema where the comments would also > fit > in. That's on my this week's TODO list. > > The database I'll be using is PostgreSQL 7.2.1 on cygwin 1.3.12-2. > > -Jacek > >> -----Original Message----- >> From: Peter Molettiere [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, August 13, 2002 11:17 AM >> To: [EMAIL PROTECTED] >> Subject: [OpenEJB-user] castor, cmp, and open-ejb >> >> >> >> So, I'm getting deeper into open-ejb, and finding that it seems to be >> very tightly coupled with castor. In fact, it seems that the cmp >> implementation is actually part of castor. As it turns out, there's a >> note in the castor documentation saying "Enterprise JavaBeans CMP -- >> TBD". Are there docs explaining the interface between open-ejb and >> castor? Hopefully something a little higher level than the javadocs? >> >> From what I can gather, in order to implement CMP beans, you >> need to do >> the following: >> >> * setup the castor database config file for the database connection >> * write the castor mapping.xml file to map tables to beans >> * write your *Bean, *Home, and *Object classes and interfaces >> * write the ejb-jar.xml file >> * package the bean classes and ejb-jar.xml file into a >> bean.jar file >> * deploy the bean.jar file into the open-ejb server >> * write/compile/execute your client code. >> >> Does this seem correct? Am I missing anything? How about >> generating the >> RMI stubs and skeletons for distributed access? >> >> Any help appreciated. >> >> I'm trying to wrap this whole process in an application which >> takes an >> xml file describing the database config and schema, and generates >> appropriate open-ejb config files, bean .java sources, and >> ant build.xml >> file to implement cmp entity beans for the whole db schema. Yes my >> mother always told me to keep my mouth closed while chewing. :) >> >> --Peter >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: Dice - The leading online job board >> for high-tech professionals. Search and apply for tech jobs today! >> http://seeker.dice.com/seeker.epl?rel_code=31 >> _______________________________________________ >> http://OpenEJB.sf.net >> OpenEJB-user mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/openejb-user >> ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ http://OpenEJB.sf.net OpenEJB-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openejb-user
