On 16/07/07, haleh mahbod [EMAIL PROTECTED] wrote:
Hi Kelvin,
1. As Ant pointed out, Release note needs to be updated to capture the
very
important announcement that was made for SDO Tuscany and that is
completion
of SDO spec 2.1.
sure
2. Tuscany 1143 was identified as an unresolved defect for Beta. Should this
be addressed in 1.0 or can it be moved to post 1.0?
I think it's an important one for 1.0 as our runtime metadata organisation
is rather messy without this and I think it will probably bite us if we
don't.
3. some of the links on this page do not work: C:\sdoRel1\tuscany-
sdo-1.0-incubating\docs\javadoc\sdo-samples\index.html
thanks, I'll check it out.
4. Is commentary_for_x the level of trace? If yes, would it make sense to
change the name to trace_detailed, trace_medium, trace_low?
Two comments here. I'm not sure how esoteric the term trace here is. It's
very familiar to me, but for someone who has never encountered the term it
may not instantly convey the message, whereas I think what I have used
does. The second is that it doesn't really do the full job that you might
expect of trace. There's no entry/exit messages, no call stack depth
representation, and it doesn't tell you anything about what's going on
inside SDO; so someone who does understand the term trace might have
different expectations. The commentary output conveys the temporal sequence
of SDO API calls that must be made in a flattened fashion.
5. C:\sdoRel1\tuscany-
sdo-1.0-incubating\docs\javadoc\sdo-samples\index.html.. javadoc for Class
SampleBase. Are these SPIs that one would use to develop samples? If yes,
the text reads as if this and the sampleInfra are not interesting to
users.
I'll take a peek at the pom and try to figure out how to exclude these
6. Samples Overview:
a) In the overview parag you have a link to Tuscany main site for the
section you say contribute pack to the project. It would be better if this
linked to getInvolved page.
thx
b) You could remove the first sentence since it does not really make sense.
How about .. Apache Tuscany SDO Samples are provided here to help users
learn SDO.'index by SDO subproject ' lists the different samples available
to you. These samples provide a starting point for learning SDO and can be
extended and enhanced to experiment with other available SDO features.
Please help us enhance these samples by sending your feedback to Tuscany
mailing list or join us and contribute to this project get involved
link.
i'll review and incorporate
7. Running samples: can you modify the test to make it clear that
BINARY-BASE is a variable that needs to be set in the script? For
example...
In order to run the samples, locate runSamples script file for the
environment you work on under samples directory. Modify the file to point
BINARY-BASE to the directory on your file system where lib and samples
reside. You are then ready to run the samples.
yes, I have a to do to make an improvement here (incidentally, I
haven't run the runsamples.sh script since I don't yet have a linux
environment since my hard drive failure, if someone could verify this it
would be great)
btw. I did this and I get an error. It complaints that it cannot find
executeSamples class file.
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesREM under the License.
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesset BINARY_BASE=
c:\sdoRel1\tuscan
y-sdo-1.0-incubating
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesset RELEASE=-1.0-incubating
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesset LIB=
c:\sdoRel1\tuscany-sdo-1.
0-incubating\lib
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesset CLASSPATH=
c:\sdoRel1\tuscany-
sdo-1.0-incubating\lib\sample-sdo--1.0-incubating.jar;
c:\sdoRel1\tuscany-sdo-1.
0-incubating\lib\sdo-api-r2.1--1.0-incubating.jar; c:\sdoRel1\tuscany-
sdo-1.0-in
cubating\lib\tuscany-sdo-lib--1.0-incubating.jar; c:\sdoRel1\tuscany-
sdo-1.0-inc
ubating\lib\tuscany-sdo-impl--1.0-incubating.jar; c:\sdoRel1\tuscany-
sdo-1.0-inc
ubating\lib\tuscany-sdo-tools--1.0-incubating.jar; c:\sdoRel1\tuscany-
sdo-1.0-in
cubating\lib\codegen-ecore-2.2.3.jar; c:\sdoRel1\tuscany-
sdo-1.0-incubating\lib\
codegen-2.2.3.jar; c:\sdoRel1\tuscany-
sdo-1.0-incubating\lib\ecore-2.2.3.jar;
c:
\sdoRel1\tuscany-sdo-1.0-incubating\lib\ecore-change-2.2.3.jar;
c:\sdoRel1\tusca
ny-sdo-1.0-incubating\lib\ecore-xmi-2.2.3.jar; c:\sdoRel1\tuscany-
sdo-1.0-incuba
ting\lib\common-2.2.3.jar; c:\sdoRel1\tuscany-
sdo-1.0-incubating\lib\xsd-2.2.3.j
ar; c:\sdoRel1\tuscany-sdo-1.0-incubating\lib\stax-api-1.0.1.jar
C:\sdoRel1\tuscany-sdo-1.0-incubating\samplesjava
target.org.apache.tuscany.sam
ples.sdo.ExecuteSamples
Exception in thread main java.lang.NoClassDefFoundError:
target/org/apache/tus
cany/samples/sdo/ExecuteSamples
yes, that would be as expected without having edited binary_base. I'm
going to adopt ant's suggestion and set it to .. by default (or whatever
works if you are in the local directory)
