Hi, Are we planning on any ORB samples for this release? Can we get any demo that has been used by iona's orbacus? Or do we just write a simple hello world client & server demo?
Also, I don't see any EJB/RMI binding being worked on... Did I miss something? All the RMI changes have been so far only in the core layer. Do we plan to create an EJB binding or not? I would interested in contributing to that.... Thanks Balaji -----Original Message----- From: Mosur Ravi, Balaji Sent: Monday, June 19, 2006 9:27 AM To: yoko-dev@incubator.apache.org Subject: RE: Defining Samples for M1 Release... I concur... I was also thinking of single demo with all the variants explained through that demo... - Balaji -----Original Message----- From: Conway, Alan Sent: Monday, June 19, 2006 9:18 AM To: yoko-dev@incubator.apache.org Subject: RE: Defining Samples for M1 Release... Can I put out a heartfelt plea NOT to continue the usual IONA tradition of having 5,000 variations on the 10-line "hello world" client-server sample? Something that's worked well in training courses & publications in the past is the "demo *system*". You introduce people up front to a simple system (e.g. the climate control system from Adavanced CORBA, stock trading system, whatever) that is simple enough to define in a couple pages of IDL, or a couple megabytes of WSDL ;) but interesting enough to allow demonstration of client/server/transactions/events whatever. You put those interfaces in a *central* place and you start writing your sample clients, servers etc. The point being you write them all to a common set of interfaces so you only write ONE CORBA server, and you can call it with your ONE yoko client, or your ONE straight CORBA client. Then you configure the router for SOAP-to-CORBA you use your ONE soap client and re-use the CORBA OR yoko servers we wrote earlier etc. The point being not to have a gazillion copies of the "hello world" interface and a gazillion almost identical re-implementations of the "hello-world" client and server. You only need new code to illustrate new features. Lots of demos can re-use existing code with with different configuration, or run existing clients against new servers etc. If some demo can't be expressed in the existing system, update the central interfaces so it can rather than introducing a heap of almost identical "hello world++" interfaces and demos. Software reuse - it can work for demos also! Cheers, Alan. On Fri, 2006-06-16 at 09:04 -0400, Mosur Ravi, Balaji wrote: > Hi adi, > > I was thinking of putting the demos inside the ws part... > > How about these names for the demos: > > Samples\ws\client (means just web service enabling a client) > Samples\ws\server (webservice enabling a server) > Samples\ws\clientserver (both client & server)... > > I am open to any other suggestions... > > - Balaji > > -----Original Message----- > From: Sakala, Adinarayana > Sent: Friday, June 16, 2006 12:55 AM > To: yoko-dev@incubator.apache.org > Subject: Defining Samples for M1 Release... > > When discussing M1 layout we came up with three set of samples that we > thought will be good. > i.e, > samples\ > \(ejb|rmi) > \orb > \ws > > Do we want any other category of samples? > > For "ws" part, i see balaji created three JIRA items for three demos > YOKO-58, YOKO-59, YOKO-60 > Is the intention that these will be three separate demos under \ws > directory? > something like, > samples\ws\ > \yokoclient_corbaserver > \yokoclient_yokoserver > \corbaclient_yokoserver > i definetely dont like the directory names, i just spelled out what you > mentioned in the jira. Hopefully > there are better names :) > > Do somebody want to outline what would be a good sample(s) for "orb" and > "ejb/rmi" categories? > If anybody want to contribute to these samples thats even better :) > > thanks, > Adi > > > >
