[snip]

JS, Raymond,

I have attached a picture depicting the components the Shopping Store Composite will have. I hope this represents the same picture you had in mind.

Looks pretty good, I have a few suggestions below.

Otherwise, please let me know.

As you can see there, some questions arose:

1 - The composite will offer its service via WS or we will invoke it locally (the local one will be easier to implement J)

<rfeng>I think it could be both: we add binding.ws and binding.sca for the service.</rfeng>

I think we need two composite services, one for the catalog and the other for the shopping cart, as SCA cannot promote two component-services as one composite-service.

The services could be provided with a selection of bindings:
- binding.ws
- binding.jsonrpc and to make it easy to invoke from an Ajax client
- binding.atom will work well with Ajax clients too
- binding.sca will help integrate with other SCA composites in an SCA domain


2 - The Shopping Cart Service will be implemented as a POJO or as a Session Bean? -> I have it currently implemented as a POJO but turning it into a session bean will not be difficult (fingers crossed)

<rfeng>I would say POJO for now as we don't have implementation.jee yet. We could add a reference to an external EJB using binding.ejb if it's needed.</rfeng>

+1 for a Java component implementation for now

+1 for putting together a JEE variation of the shopping cart later, when we have support for <implementation.jee>


3 -The Persistence Service will be implemented as a POJO or as an Entity Bean?
4 - Shall we use DAS to persist the data?

<rfeng>We could use implementation.data or implementation.das to persist the data. Luciano, which one supports write?</rfeng>

How about starting really simple with a Java component implementation that just uses JDBC to talk to the database like what Douglas has started to contribute recently (see http://issues.apache.org/jira/browse/TUSCANY-1844)?

I have put his implementation of the getting-started store sample that integrates a database under demos/tutorial/store-database, thinking that it could be useful in the context of the tutorial.


Let's try to come up with a final version of it so we can start taking ownership of the different components in order to start coding.

Two more thoughts:

- add a local Catalog component that has the catalog store in a local database.

- run the different components on different SCA nodes.


Hope to hear from you soon.

Regards,

Mario E. Antollini
Intel Software
ASDC
+54 351 414 5594
[EMAIL PROTECTED]

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to