Here is a first version of the implementation proposed:
https://issues.apache.org/jira/browse/TUSCANY-2297
I've added the Collection interface support to the implementation-data-xml,
where the logic of the put, post, get, and delete methods are, basically,
the same of the update, insert, get, and
I agree with you. Changing the return type of put and delete methods
wouldn't be useful for all kinds of situations.
To this first version I will let the implementation-data-xml support both
interfaces DATA and Collection.
On Thu, Apr 24, 2008 at 1:48 PM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
On Thu, Apr 24, 2008 at 8:30 AM, Douglas Leite <[EMAIL PROTECTED]> wrote:
> I have started to integrate the Collection interface with
> implentation-data-xml. Although the methods present in the DATA interface
> (get, insert, update, delete) can be replaced by the Collection interface's
> method
I have started to integrate the Collection interface with
implentation-data-xml. Although the methods present in the DATA interface
(get, insert, update, delete) can be replaced by the Collection interface's
methods (get, post, put, delete), there are some differences. The update and
delete DATA me
I'd suggest the following as the next steps around implementation-data-xml
- Add support for data collection interface from implementation-data
- At this point, integration with binding-atom-abdera should be
working, it would be great to integrate this with our store tutorial,
either by enhancing
In my last contribution, I have proposed a first version of Update and
Insert methods for impl.data.xml component.
One of the insert method limitations is that the table must only have
columns which types are char or varchar. However, I want to improve this,
allowing any sql primitive type.
The fac
