Re: Meaning of each generated file by JacORB IDL compiler
Nick Cross <[email protected]> Thu, 4 Feb 2016 08:59:02 +0000
| Newsgroups | gmane.comp.corba.jacorb.devel |
|---|---|
| Message-ID | <[email protected]> |
On 01/02/16 14:30, Kujtim Hyseni wrote: > Hi Phil and thanks for answering! > > I really need to know short description of function of each file (in > single line) and whether it is used only by client, server or both of > them. Can you provide such an info :) since I really don't have so > much time to get that info? I understand the process as a whole but > need some precise info to put in a document regarding the files > generated by JacORB. There is a nice documentation in ORBit (C > implementation of CORBA) regarding my question, but don't know > whether you have seen that! What documentation in ORBit are you referring to ? What information above and beyond the specifications the Phil linked to are you looking for ? Regards Nick > > Thank you in forward! > > Kujtim > > ________________________________________ From: Phil Mesnier > <[email protected]> Sent: Monday, February 1, 2016 12:29 PM To: > Discussions concerning CORBA development with JacORB Cc: Kujtim > Hyseni Subject: Re: [jacorb-developer] Meaning of each generated file > by JacORB IDL compiler > > Hi Kujtim, > > I've seen you on this list for years, I'm surprised this question is > just coming up now. I suggest try some google based research, also > visit the OMG documentation base, starting with > http://www.omg.org/spec/I2JAV/ where you will find PDFs containing > all you need to answer your question thoroughly. > > Here's a little overview: The files you mention contain the Java > source which is necessary for you to create applications that either > implement the objects for the TempSensor and Termostat interfaces, or > to use those implementations from client applications using those > interfaces. Just as Java code gets rendered as bytecode in *.class > files so that the JVM can process them, Your IDL is rendered into > Java, creating the files you cite. > > Is this what you are looking for or am I misunderstanding your > question? > > Best regards, -Phil > >> On Feb 1, 2016, at 3:01 AM, Kujtim Hyseni >> <[email protected]> wrote: >> >> Hi, >> >> >> I have the following IDL declared as input: >> >> >> exception DeviceNotFound {short deviceID;}; >> >> interface TempSensor { readonly attribute long minTempRead; >> readonly attribute long maxTempRead; long readTemp(in short devID) >> raises(DeviceNotFound); }; >> >> interface Termostat { readonly attribute long minTempAllowed; >> readonly attribute long maxTempAllowed; exception TempNotAllowed >> {short deviceID;}; void setTemperature(in short devID) raises >> (DeviceNotFound, TempNotAllowed); }; >> >> >> and at the folder ..\build\generated I see the following files: >> >> >> TermostatPackage\TempNotAllowed.java >> >> TermostatPackage\TempNotAllowedHelper.java >> >> TermostatPackage\TempNotAllowedHolder.java >> >> >> _TempSensorStub.java >> >> TempSensor.java >> >> TempSensorHelper.java >> >> TempSensorHolder.java >> >> TempSensorOperations.java >> >> TempSensorPOA.java >> >> TempSensorPOATie.java >> >> >> (also files generated for DeviceNotFound exception and Termostat >> interface, but the role is the same as for TempNotAllowed and >> TempSensor respectively). >> >> >> Can someone explain the role of each of the generated files? >> >> >> Regards, >> >> Kujtim _______________________________________________ >> jacorb-developer maillist - >> [email protected] >> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer > >> > -- Phil Mesnier Principal Engineer & Partner > > OCI | WE ARE SOFTWARE ENGINEERS. tel +1.314.579.0066 x225 > ociweb.com > > > > > > _______________________________________________ jacorb-developer > maillist - [email protected] > https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer > _______________________________________________ jacorb-developer maillist - [email protected] https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer