Re: SDO Samples

[Fuhwei Lwo <fu...@bricemedia.com>]

Frank,
    
  As a user learning SDO by examples, I prefer one file per one example  so I don't need to be forced to understand example files directory  structure and dependency.
  
  Regards,
  
  Fuhwei Lwo
  
Frank Budinsky <fr...@ca.ibm.com> wrote:  Robbie,

Looks pretty good to me. I wonder if someone from the SCA team can comment 
on consistency of approach with other Tuscany and Apache samples. What do 
others think about using things like SdoSampleConstants. What about the 
shouldUseDataGraph() call to query the user to choose from two ways to run 
it?

For this:

            // TODO: do you need to do this ?
            employees.add(newEmployee);

The answer is no. You would only need to add the newEmployee if you 
created it by calling DataFactory.create(). Since you created it by 
calling create() on the parent object, it's already attached, so this call 
to add will be a NOOP.

Frank.

Robbie J Minshall  wrote on 06/29/2006 02:48:15 PM:

> 
> I am working on some samples for the SDO specification.  Any 
> thoughts or comments on the following would be appreciated. 
> 
> The first point of contact with SDO may or may not be the 
> specification or an introductory paper, regardless it of the first 
> point of contact I would hope that the samples are complete and 
> usable enough that they can be used in close conjunction with the 
> spec, sdo papers, or on their own.  With this in mind it is very 
> very important that the documentation generated ( I think the the 
> project site is a good candidate here ) include a very consumable 
> tutorial as well as a good outline of the sample packaging and usage
> so that the user can either use the samples on their own or in 
> reference to the paper or specification in their hand. 
> 
> Currently the draft samples have a package that includes the code 
> snipets throughout the specification so that the user can read each 
> section and run or modify the very simple code snipet as it appears 
> in the 2. 0 specification (these are essentially primatives).  The 
> next package includes working samples from the Examples Section of 
> the 2.0 Specification.  The code in these sections is as close to 
> the code in the specific Example as possible with differences 
> highlighted ( the sample you reviewed is one example of this ).  The
> third package includes working samples from other sources, such as 
> papers, with the intention that a user could read the paper and then
> modify and execute the working sample appropiately. 
> 
> The current draft samples can simply be executed as a standAlone 
> Java application from the command line or from within eclipse. 
> 
> The following is a sample of the style the Full Examples are 
> written.  I am going to concentrate comments on this single example,
> then complete the others in the same mann.  If people have comments 
> or suggestions please let me know : 
> 
> 
> 
> thanks, 
> Robbie Minshall. [attachment "sample.zip" deleted by Frank 
> Budinsky/Toronto/IBM] 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org