Please see with the below steps, if it works for you, I am also modifying
the beta2 sample readme to include the same instructions for use with other
dbs like MySQL, DB2 etc.
On 9/17/07, Amita Vadhavkar [EMAIL PROTECTED] wrote:
Hi,
I took the following steps to get the customer sample
Hi,
Is the latest build of tuscany with the Websphere fixes available in a
Maven repository?
Thanks a lot,
Radim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 9/17/07, Radim Kolarik [EMAIL PROTECTED] wrote:
Hi,
Is the latest build of tuscany with the Websphere fixes available in a
Maven repository?
Thanks a lot,
Radim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Miro,
Both sides of a relationship defined with sdoXML:oppositeProperty need to
be non-containment references. All containment references are implicitly
bidirectional (the reverse is the elements container), so you wouldn't
really want to use an IDREF element anyway - it's just duplicate
Miro,
You are right. Bidirectional references are broken in Tuscany. They seem
to have been broken when we switched over to the new (noEMF) codegen
patterns. I guess nobody uses them much and we don't have a test case. Can
you please open a JIRA bug report to track this?
I understand your
Frank,
maybe solution for the representation of composition (containment) in XSD and
SDO is not so simple.
Recall that one class in UML class diagram can be part of many compositions but
instance of that class, in the run-time, can be part of only one whole/assembly
object (well known example
Miro,
You're right. The generated method is a little more complicated than I
said. The generated getCircle() method would actually look something like
this:
Circle getCircle() { if (getContainmentProperty() !=
getProperty_Circle_points()) return null; return (Circle)getContainer(); }
And the
