Hello Kevin , Luciano,
Thanks a lot for all your suggestions and looking forward to have a IRC chat
with you.
I am proposing 9th Nov 5.30 a.m. IST (8th Nov 4.00 p.m. PST) for approx. 1
hr.
Please join the chat and we all can discuss -
1) what we are trying to provide - service, container
2) what
Hi Amita,
This sounds good. Thanks for getting up so early!
--
Kevin
Amita Vadhavkar wrote:
Hello Kevin , Luciano,
Thanks a lot for all your suggestions and looking forward to have a
IRC chat
with you.
I am proposing 9th Nov 5.30 a.m. IST (8th Nov 4.00 p.m. PST) for
approx. 1
hr.
Please
Hi Kevin,
Thanks a lot for the comments. I have posted the code and doc on JIRA-904
for the container work. Also, am most likely missing something in the
database
connection portion. Would like to discuss with you.
Will you please provide feedback on JIRA-904 attachments?
I am checking with
Hello Amita,
This looks promising. I notice your test case uses explicit updates and
inserts. While this is supported by the DAS it is not the preferred
usage which is to allow the RDB DAS to generate the CUD statements from
the SDO change history. Could you modify the example to read a
Hi Luciano,
I have attached code jar and doc today to
https://issues.apache.org/jira/browse/TUSCANY-898
Here I am trying to follow the approach of implementing SCA container for DAS.
Will you please go through the same and let me know if there is some
overlap in what you are developing with
Hi Amita,
This is looking good. Some comments inline:
Amita Vadhavkar wrote:
Hi,
I am trying to create a container for DAS-SCA too (not just for stored
procedure) and will be able to send a working code in ML over the
weekend.
Below is summary of what I got so far from the previous mail
Hi,
I am trying to create a container for DAS-SCA too (not just for stored
procedure) and will be able to send a working code in ML over the weekend.
Below is summary of what I got so far from the previous mail discussions and
some questions.
The integration between DAS and SCA can happen at
On Oct 24, 2006, at 2:11 PM, Kevin Williams wrote:
Jim Marino wrote:
When I first read the thread on this, I thought the DAS service
would be a component extension type (e.g. analogous to a
implementation.java or implementation.ejb) and not a component
implementation type, which
Hi,
I would also like to understand this a little better ... here I am thinking
aloud and hope the others will help in getting my persceptions right...
I guess firstly it is a question of how or where we want to position 'DAS
Integration' in SCA. Is is something we want to integrate as the
On Oct 25, 2006, at 3:54 AM, Venkata Krishnan wrote:
Hi,
I would also like to understand this a little better ... here I am
thinking
aloud and hope the others will help in getting my persceptions
right...
I guess firstly it is a question of how or where we want to
position 'DAS
Comments in-line...
On 10/25/06, Jim Marino [EMAIL PROTECTED] wrote:
On Oct 25, 2006, at 3:54 AM, Venkata Krishnan wrote:
Hi,
I would also like to understand this a little better ... here I am
thinking
aloud and hope the others will help in getting my persceptions
right...
I guess
Jim Marino wrote:
On Oct 24, 2006, at 2:11 PM, Kevin Williams wrote:
Jim Marino wrote:
When I first read the thread on this, I thought the DAS service
would be a component extension type (e.g. analogous to a
implementation.java or implementation.ejb) and not a component
Luciano Resende wrote:
Comments in-line...
On 10/25/06, Jim Marino [EMAIL PROTECTED] wrote:
On Oct 25, 2006, at 3:54 AM, Venkata Krishnan wrote:
Hi,
I would also like to understand this a little better ... here I am
thinking
aloud and hope the others will help in getting my
When I first read the thread on this, I thought the DAS service would
be a component extension type (e.g. analogous to a
implementation.java or implementation.ejb) and not a component
implementation type, which would allow for dynamic and eventually
declarative configuration styles. Either
Jim Marino wrote:
When I first read the thread on this, I thought the DAS service would
be a component extension type (e.g. analogous to a
implementation.java or implementation.ejb) and not a component
implementation type, which would allow for dynamic and eventually
declarative
Hi Amita
I think we were both going on the same way, with the DAS Service sample,
altough i had the interface more like this, to be more flexible :
public interface DASService {
public DAS configureService(String configFile);
public DataObject executeCommand(String commandName);
I like the idea of a DASService sample. We might think to integrate
this as part of BBank too!
--
Kevin
Luciano Resende wrote:
Hi Amita
I think we were both going on the same way, with the DAS Service sample,
altough i had the interface more like this, to be more flexible :
public
I'll take a look at this on Monday, and provide some feedback...
I had started a simmilar thing as well... with the same idea of having this
as a sample...
- Luciano
On 10/21/06, Amita Vadhavkar [EMAIL PROTECTED] wrote:
Hi ,
I am also following up another thread
Luciano Resende wrote:
Kevin, from what I understood from your suggestion, it was looking to me
more like exposing DAS as a service :
public interface RDBDASService
DataObject execute(String commandName);
DataObject executeSQL(String abitrarySQL);
void
I would suggest that we start right away with a RDBDAS-based solution.
I also think that the best place to start would be with an interface
that is weakly typed. That is, a service interface in terms of
dynamic SDO's. If we go this route we can avoid the generation (by hand
or otherwise) of
I think this would be useful but it seems more like a traditional
persistence API than what Luciano was suggesting. With this one a
user needs to know about DataObject's, commands, SQL strings etc.
just like they would if they were using raw JDBC or JPA.
On the other hand, Luciano's
The real difference between the two approaches is that one is Typed or
static and the other is dynamic. I think both are needed but was
suggesting that we start with dynamic since it is the most flexible and
seems to be a reasonable stepping stone towards a static capability.
With either,
22 matches
Mail list logo
