Hi Adriano,
Let me show what I got so far: Below is the debug dump and the relevant portion
of the logic will be in ResultSetProcessor and ResultSetRow. Based on
it, it is seen
that the parent/s attributes and data is not added. Please let me know
if you are
looking for something more/different.
[
https://issues.apache.org/jira/browse/TUSCANY-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Maynard updated TUSCANY-1147:
--
Attachment: Tuscany-1147.patch
OK, here's version 3. This one has the same code to fi
Hi All,
UpdateGenerator.getUpdateCommand()
- Here the logic to form update statement is such that for forming WHERE
CLAUSE,
it first iterates over PKs and then the columns which are undergoing
changes.
In case where, update is occurring on a table row which does not have a PK,
the statement
getti
Hi All,
In addition to the problem mentioned in below link,
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg16304.html
Found one more issue when tried to have a PK on the same table
OrderDetails{ORDER_ID, PRODUCT_ID, PRICE} , PK - ORDER_ID
And update is attempted to update ORDER_ID to
I'll jump in here, as I was the one pushing this proposal for M2.
I think it's useful to have some samples building using Ant to show
how someone who isn't a maven user can build Tuscany applications
(rather than Tuscany itself). In this sense, the Ant scripts serve
as a template for people to c
[
https://issues.apache.org/jira/browse/TUSCANY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486662
]
Frank Budinsky commented on TUSCANY-1197:
-
Thanks Yang, I missed that.
I found the getSequenceFeature() m
[snip]
[EMAIL PROTECTED] wrote:
Author: rfeng
Date: Tue Apr 3 20:19:08 2007
New Revision: 525379
URL: http://svn.apache.org/viewvc?view=rev&rev=525379
Log:
Add isConversational to the Interface
I think it's ok for now if you want to have this conversational boolean
flag on Interface, but
Hi Amita,
The table must have a primary key defined. We should be throwing an
exception when an update attempt like this takes place. If you want to
open a JIRA and fix this, that would be great. Thanks.
Brent
On 4/4/07, Amita Vadhavkar <[EMAIL PROTECTED]> wrote:
Hi All,
UpdateGenerator.getU
Amita,
I think we intended to not allow any updates to the primary key
field. If we do want to allow this, I would suggest that the fix is to
have the UpdateGenerator use the old value of the PK field for the
where clause rather than the current value. That way you would get
something like "upda
Hi,
I came to this from the Java C&I spec which defines some conversation
characteristics. Is @Conversational used to define the intent? If so, it's a
bit wierd that the Java C&I steps into the intent area only with this
annotation.
Thanks,
Raymond
- Original Message -
From: "Jean-
[
https://issues.apache.org/jira/browse/TUSCANY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Maynard closed TUSCANY-1201.
-
Resolution: Invalid
> AccessViolation in DataObjectImpl::logDeletion()
> --
AccessViolation in DataObjectImpl::logDeletion()
Key: TUSCANY-1201
URL: https://issues.apache.org/jira/browse/TUSCANY-1201
Project: Tuscany
Issue Type: Bug
Components: C++ SDO
Af
AccessViolation in DataObjectImpl::logDeletion()
Key: TUSCANY-1202
URL: https://issues.apache.org/jira/browse/TUSCANY-1202
Project: Tuscany
Issue Type: Bug
Components: C++ SDO
Af
Raymond Feng wrote:
Hi,
I came to this from the Java C&I spec which defines some conversation
characteristics. Is @Conversational used to define the intent?
Yes, that's my understanding.
If so, it's a bit wierd that the Java C&I steps into the intent area
only with this annotation.
The Ja
Thanks Amita, I also debugged the code and took this conclusion. And I
wasn't sure if it's supposed to work this way.
Is there anybody that could confirm that it should work this way?
Adriano Crestani
On 4/4/07, Amita Vadhavkar <[EMAIL PROTECTED]> wrote:
Hi Adriano,
Let me show what I got so
Thought I'm mention:
I'm in the process of adding support for generating exceptions from faults
in the Axis2 W2J. This addresses one or more JIRAs that have been opened.
My code basically works but I need to merge with the latest code and
clean up a bit. I don't want to stop anyone from do
Hi,
Our Wiki website is incomplete and some of the links point readers to
incorrect information or empty links.
I'm interested in getting the website into a consumable form and look
forward to any help that I can get for this.
Here is how I'll approach this:
- Compare the content to the old webs
Hi,
I'm porting a subset of the SPIs in the "kernel/spi" module to use the
interface-based assembly model. These SPIs will be consumed by the core.
Other interfaces/classes in the "kernel/spi" module will be moved/ported
into corresponding submodules as we go with the modulization work.
I'll
I think allowing changes to PK columns would be a mistake.
Brent Daniel wrote:
Amita,
I think we intended to not allow any updates to the primary key
field. If we do want to allow this, I would suggest that the fix is to
have the UpdateGenerator use the old value of the PK field for the
where
Venkata Krishnan wrote:
Hi,
Yes, what Luciano is suggesting here makes sense to me as well.
Thanks
- Venkat
On 4/4/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
Sebastien wrote:
> I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
alpha1 is
>probably better. I'll start with a
Hello Adriano,
This use of convention is actually for the "write" side of things. A PK
is needed to generate correct update commands based on the SDO Change
Summary. In the absence of a defined PK, the DAS will assume any column
named ID is the PK and use that in the generated statement.
A
The RDB DAS will only populate a graph with data returned from the used
query. If you want a graph that contains data from related tables then
the query provided must return that data (typically a join). The
relationship tests in the test suite demonstrate this.
--Kevin
Adriano Crestani wrot
Module modules/impl-java-xml currently depends on the SCA Java C&I
annotations. I would like to remove that dependency on the annotations
as it does not seem necessary now the annotation processor does not need
to be an SCA component anymore. If there's no objection I will clean
that up later t
Simon Nash wrote:
I'll jump in here, as I was the one pushing this proposal for M2.
I think it's useful to have some samples building using Ant to show
how someone who isn't a maven user can build Tuscany applications
(rather than Tuscany itself). In this sense, the Ant scripts serve
as a templa
Hi,
The annotation dependency will be required for the processors that deal with
the annotations, for example, ReferenceProcessor will need to access
@Reference. Where should we place the these processors? I thought
impl-java-impl is the module reponsible to parse annotations.
Thanks,
Raymon
Luciano Resende wrote:
I have committed some new contribution services interfaces under
revision #
525071 that would better align the contribution service module with the
SCDL4J proposals. Note that some of these interfaces, that would be
used for
artifact resolving, will need to be implemente
Raymond Feng wrote:
Hi,
The annotation dependency will be required for the processors that
deal with the annotations, for example, ReferenceProcessor will need
to access @Reference. Where should we place the these processors? I
thought impl-java-impl is the module reponsible to parse annotati
I am interested in the transition from the the 0.95 locateService API to
the 1.0 APIs. Has there been any work done in this area? In
particular, I am interested in the look up of the context associated
with a service since CurrentCompositeContext is removed from 1.0 and
ComponentContext is re
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple phases
as you described.
As for your specific questions, let me try to clarify :
- The assembly module deals with 3 types of files, .component
[snip]
Luciano Resende wrote:
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple
phases
as you described.
As for your specific questions, let me try to clarify :
- The assembly module deals
Jean-Sebastien Delfino wrote:
[snip]
Luciano Resende wrote:
Hi Sebastien
Your understanding is very right, with the new artifactProcessor
interfaces, we should be able to separate the load phases in multiple
phases
as you described.
As for your specific questions, let me try to clarify :
Jean-Sebastien Delfino wrote:
Venkata Krishnan wrote:
Hi,
Yes, what Luciano is suggesting here makes sense to me as well.
Thanks
- Venkat
On 4/4/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
Sebastien wrote:
> I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
alpha1 is
>pro
Since it's going to take a little bit of time to be able to bring up end
to end scenarios with our new modularized kernel, I think it would be
useful to be able to run simple SCA applications using a thin layer on
top of Spring like the one I had prototyped in my sanbdox in modules [1]
and [2]
Thanks Kelvin ; )(again)
Adriano Crestani
On 4/4/07, Kevin Williams <[EMAIL PROTECTED]> wrote:
Hello Adriano,
This use of convention is actually for the "write" side of things. A PK
is needed to generate correct update commands based on the SDO Change
Summary. In the absence of a defined PK
[EMAIL PROTECTED] wrote:
Author: rfeng
Date: Wed Apr 4 22:47:55 2007
New Revision: 525710
URL: http://svn.apache.org/viewvc?view=rev&rev=525710
Log:
Port the core SPIs to use the new assembly model
I integrated your new core-spi and host-spi in the build under
tuscany/java/sca/modules.
35 matches
Mail list logo