More comments inline...
On Jul 2, 2006, at 2:02 PM, Simon Nash wrote:
My comments are inline below.
Simon
Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
Start a community discussion on the end to end scenarios that
we want to
support in M2.
On 7/3/06, Jim Marino [EMAIL PROTECTED] wrote:
...and involve a lot less upfront planning?
In other words, people work on what interests them and the community
cuts a release when it decides a useful level of new functionality
has been reached.
Can you provide pointers to any other Apache
On Jul 3, 2006, at 11:31 PM, ant elder wrote:
On 7/3/06, Jim Marino [EMAIL PROTECTED] wrote:
...and involve a lot less upfront planning?
In other words, people work on what interests them and the community
cuts a release when it decides a useful level of new functionality
has been reached.
Jim,
Comments inline below.
Simon
Jim Marino wrote:
On Jul 3, 2006, at 2:57 PM, Simon Nash wrote:
Jim Marino wrote:
cut/
From the scenarios we should derive technical
specifications, designs that implement those specifications, and
tests that validate that the implementations match
I think releasing every 4-6 weeks is probably a bit too often.
Most users won't want to upgrade so frequently, especially at
this stage of an incubator project when new releases may be a bit
unstable. Another factor is the overhead involved in cutting a
release. On balance I'd suggest releasing
Hi Clemens,
I changed the subject since your question may have more general
interest than the thread on scenarios...
An entry point (now renamed service) would be discoverable through
a management API. There has been some talk about providing a Tuscany
management API so if you are
Jim Marino wrote:
cut/
From the scenarios we should derive technical
specifications, designs that implement those specifications, and
tests that validate that the implementations match the specifications.
This seems a bit heavy-weight for an open source project. Are you
suggesting we
On Jul 3, 2006, at 2:57 PM, Simon Nash wrote:
Jim Marino wrote:
cut/
From the scenarios we should derive technical
specifications, designs that implement those specifications, and
tests that validate that the implementations match the
specifications.
This seems a bit heavy-weight for an
On Jul 3, 2006, at 3:08 PM, Simon Nash wrote:
Jim Marino wrote:
cut/
Some of the initial scenarios may end up in M2 and
I'm a bit worried that this will discourage people from working
on something important to them because it is not slated for a
predetermined milestone. For example, if
My comments are inline below.
Simon
Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
Start a community discussion on the end to end scenarios that we
want to
support in M2.
I'm thinking about concrete end to end scenarios that define the end
Comments linline ...
Jim Marino wrote:
On Jul 2, 2006, at 2:02 PM, Simon Nash wrote:
My comments are inline below.
Simon
Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
Start a community discussion on the end to end scenarios that we
want
On Jul 2, 2006, at 2:51 PM, Clemens Utschig - Utschig (Oracle) wrote:
Comments linline ...
Jim Marino wrote:
On Jul 2, 2006, at 2:02 PM, Simon Nash wrote:
My comments are inline below.
Simon
Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
On 7/2/06, Simon Nash [EMAIL PROTECTED] wrote:
I think the purpose of scenarios is not to serve as tests, but to
define required functionality in terms that are meaningful from
a user perspective.
Agreed at the high level. At a low-level I don't see that there would
be much difference between
I completly miss an end-to-end scenario .. like accessing a service
through tuscany ... say from a website (preferrably JSF)..
helloworld via tuscany ... am I missing something?
Jim Marino wrote:
On Jul 2, 2006, at 2:51 PM, Clemens Utschig - Utschig (Oracle) wrote:
Comments linline ...
On 7/2/06, Clemens Utschig - Utschig (Oracle)
[EMAIL PROTECTED] wrote:
I completly miss an end-to-end scenario .. like accessing a service
through tuscany ... say from a website (preferrably JSF)..
helloworld via tuscany ... am I missing something?
We have a bunch of helloworld-esque samples
yup,
this is the reason why I ask :-) can someone add that (me?)
/clemens
Jeremy Boynes wrote:
On 7/2/06, Clemens Utschig - Utschig (Oracle)
[EMAIL PROTECTED] wrote:
I completly miss an end-to-end scenario .. like accessing a service
through tuscany ... say from a website (preferrably JSF)..
More comments inline...
On Jul 2, 2006, at 2:02 PM, Simon Nash wrote:
My comments are inline below.
Simon
Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
Start a community discussion on the end to end scenarios that
we want to
support in M2.
Sure, you can add the scenario - you just need to create a wiki
account if you don't already have one. If you are interested in
helping to create a JSF integration, that would be fantastic.
Jim
On Jul 2, 2006, at 3:43 PM, Clemens Utschig - Utschig (Oracle) wrote:
yup,
this is the reason
at least I added a tag to the wiki page on it :-)
more to follow ..
Jim Marino wrote:
It would be good if I replied before sending :-) Sure, you can add
the scenario - you just need to create a wiki account if you don't
already have one. If you are interested in helping to create a JSF
Jim
how would I discover an exposed entry point? end of day - it's a wsdl
... (looking into the API, some kind of entrypoint explorer
functionality would be cool ...)
/clemens
Jim Marino wrote:
Cool! When you have questions, ask away.
Jim
On Jul 2, 2006, at 4:09 PM, Clemens Utschig -
On Jul 1, 2006, at 12:07 AM, Jeremy Boynes wrote:
Jean-Sebastien Delfino wrote:
1. Use scenarios to drive the M2 work
Start a community discussion on the end to end scenarios that we
want to
support in M2.
I'm thinking about concrete end to end scenarios that define the
end user
21 matches
Mail list logo
