[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [alf-dev] RE: RE: Availability of complete POC sample code
|
Deepa,
Thanks for the feedback. I'll take a look. Most of the testing I have
done personally on this sample has been running inside eclipse.
Possibly there is an assumption that you have built and deployed
everything inside eclipse successfully before running the standalone
build.xml but I'll have a look before speculating further.
Tim
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Deepa Rai
Sent: Wednesday, August 02, 2006 2:23 PM
To: alf-dev@xxxxxxxxxxx
Subject: [alf-dev] RE: RE: Availability of complete POC sample code
Hi Tim,
Thanks for the explanation. I ran into lot of build problems. I think
none of the build.xml files contain compile target so the jar and war
files that got created after clean were wrong. I had to manually add
compile target in order to have correct jar, war files of different
project.
The other thing I had to do was deploy each web service to Axis
manually. It was not mentioned in your instructions document. I was
getting deployment errors for service flows until I deployed all
required web services to Axis.
I don't run anything (tomcat, active bpel etc.) within eclipse.
That's it for now.
Thanks,
Deepa
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of alf-dev-request@xxxxxxxxxxx
Sent: Tuesday, August 01, 2006 9:27 PM
To: alf-dev@xxxxxxxxxxx
Subject: alf-dev Digest, Vol 14, Issue 2
Send alf-dev mailing list submissions to
alf-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/alf-dev
or, via email, send a message with subject or body 'help' to
alf-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
alf-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than
"Re: Contents of alf-dev digest..."
Today's Topics:
1. RE: Build Vocab Meeting moved to Wed 1PM PDT (Doug Fierro)
2. Build Vocab Meeting Wed 8/2 @ 1:30 PDT (Steve Taylor)
3. RE: Availability of complete POC sample code (Deepa Rai)
4. RE: RE: Availability of complete POC sample code (Tim Buss)
5. RE: ALF Source Code Mangement
VocabularyMeeting+1-303-928-3232 id 6053141# Wednesday 10:00AM
PDT - meeting minutes (Tim Buss)
----------------------------------------------------------------------
Message: 1
Date: Tue, 1 Aug 2006 11:41:15 -0500
From: Doug Fierro <dfierro@xxxxxxxxxx>
Subject: RE: [alf-dev] Build Vocab Meeting moved to Wed 1PM PDT
To: alf-dev@xxxxxxxxxxx
Message-ID:
<OF0B14DB0D.185C87C2-ON872571BD.005B6FF7-862571BD.005BAA9B@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
>Hi Steve
>
>I'd like 1:30 PDT on Wednesday better.
>
>Tim
Wednesday afternoon would work better for me too; flexible on the start
time.
Doug Fierro
Director of Product Management
IBM Rational Build Forge
dfierro@xxxxxxxxxx
512 225 0436
http://www.buildforge.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/alf-dev/attachments/20060801/07649273/attac
hmen
t.html
------------------------------
Message: 2
Date: Tue, 1 Aug 2006 11:08:01 -0600
From: Steve Taylor <steve@xxxxxxxxxxxx>
Subject: [alf-dev] Build Vocab Meeting Wed 8/2 @ 1:30 PDT
To: alf-dev@xxxxxxxxxxx
Message-ID: <p06230912c0f53a900b2c@[192.168.3.30]>
Content-Type: text/plain; charset="us-ascii"
The next conf call, is Wed 8/2 - 1:30 PM PDT.
Phone Number: 1-913-227-1219
Pass Code: 908088
Topic: What does Build mean in terms of a Use Case?
Thanks, Steve
--
Catalyst Systems Corporation
Ph: 800-359-8049 x114
505-424-6439
Fax: 505-424-6438
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/alf-dev/attachments/20060801/64f2948a/attac
hmen
t.html
------------------------------
Message: 3
Date: Tue, 1 Aug 2006 14:09:06 -0400
From: "Deepa Rai" <drai@xxxxxxxxxxx>
Subject: [alf-dev] RE: Availability of complete POC sample code
To: <alf-dev@xxxxxxxxxxx>
Message-ID: <1154455913_4035@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Thanks Tim!!
I did setup the POC sample and could run it without any problems....
instructions were very helpful. The only thing that didn't work for me
was build.xml file that is used to deploy all the web services war files
and event manager in stand alone Tomcat. I made few corrections and was
able to deploy my stuff.
So far so good.... my next step is to understand the sample.
Thanks,
Deepa
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of alf-dev-request@xxxxxxxxxxx
Sent: Tuesday, August 01, 2006 12:00 PM
To: alf-dev@xxxxxxxxxxx
Subject: alf-dev Digest, Vol 14, Issue 1
Send alf-dev mailing list submissions to
alf-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/alf-dev
or, via email, send a message with subject or body 'help' to
alf-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
alf-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than
"Re: Contents of alf-dev digest..."
Today's Topics:
1. Build Vocab Meeting moved to Wed 1PM PDT (Steve Taylor)
2. RE: Build Vocab Meeting moved to Wed 1PM PDT (Tim Buss)
3. Availability of complete POC sample code (Deepa Rai)
4. RE: Availability of complete POC sample code (Tim Buss)
----------------------------------------------------------------------
Message: 1
Date: Mon, 31 Jul 2006 13:01:01 -0600
From: Steve Taylor <steve@xxxxxxxxxxxx>
Subject: [alf-dev] Build Vocab Meeting moved to Wed 1PM PDT
To: alf-dev@xxxxxxxxxxx
Message-ID: <p0623090dc0f40259de09@[192.168.3.30]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hi Everyone,
Sorry for the missed conference calls for the Build Vocabulary.
Mondays are not working
out for me. Can we move the meeting to Wednesdays at 1PM PDT?
Thanks, Steve
--
Catalyst Systems Corporation
Ph: 800-359-8049 x114
505-424-6439
Fax: 505-424-6438
------------------------------
Message: 2
Date: Mon, 31 Jul 2006 12:07:54 -0700
From: "Tim Buss" <TBuss@xxxxxxxxxx>
Subject: RE: [alf-dev] Build Vocab Meeting moved to Wed 1PM PDT
To: "ALF Developer Mailing List" <alf-dev@xxxxxxxxxxx>
Message-ID:
<55646D9DC2748E4CACDD632FF2E53982028A585C@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi Steve
I'd like 1:30 PDT on Wednesday better.
Tim
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Steve Taylor
Sent: Monday, July 31, 2006 12:01 PM
To: alf-dev@xxxxxxxxxxx
Subject: [alf-dev] Build Vocab Meeting moved to Wed 1PM PDT
Hi Everyone,
Sorry for the missed conference calls for the Build Vocabulary.
Mondays are not working
out for me. Can we move the meeting to Wednesdays at 1PM PDT?
Thanks, Steve
--
Catalyst Systems Corporation
Ph: 800-359-8049 x114
505-424-6439
Fax: 505-424-6438
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
------------------------------
Message: 3
Date: Mon, 31 Jul 2006 17:16:35 -0400
From: "Deepa Rai" <drai@xxxxxxxxxxx>
Subject: [alf-dev] Availability of complete POC sample code
To: <alf-dev@xxxxxxxxxxx>
Message-ID: <1154380761_3410@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi,
Thanks for your responses to my earlier post.
Tim, when do you think complete POC sample would be available to the
public along with required jars and instruction docs?
It would be great if you can give us a rough idea so we can proceed with
our efforts accordingly.
Many thanks,
Deepa
------------------------------
Message: 4
Date: Mon, 31 Jul 2006 14:36:06 -0700
From: "Tim Buss" <TBuss@xxxxxxxxxx>
Subject: RE: [alf-dev] Availability of complete POC sample code
To: "ALF Developer Mailing List" <alf-dev@xxxxxxxxxxx>
Message-ID:
<55646D9DC2748E4CACDD632FF2E53982028A5B25@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi Deepa,
Just checking in few loose ends today. I should have the instructions
ready a bit later today.
All the jars can be downloaded from elsewhere and that's the plan for
right now. I am pretty sure I can check some of them in and will do so
once I have clarification on what but it's probably not worth waiting
for that since it will be an incomplete set.
Tim
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Deepa Rai
Sent: Monday, July 31, 2006 2:17 PM
To: alf-dev@xxxxxxxxxxx
Subject: [alf-dev] Availability of complete POC sample code
Hi,
Thanks for your responses to my earlier post.
Tim, when do you think complete POC sample would be available to the
public along with required jars and instruction docs?
It would be great if you can give us a rough idea so we can proceed with
our efforts accordingly.
Many thanks,
Deepa
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
------------------------------
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
End of alf-dev Digest, Vol 14, Issue 1
**************************************
------------------------------
Message: 4
Date: Tue, 1 Aug 2006 13:50:27 -0700
From: "Tim Buss" <TBuss@xxxxxxxxxx>
Subject: RE: [alf-dev] RE: Availability of complete POC sample code
To: "ALF Developer Mailing List" <alf-dev@xxxxxxxxxxx>
Message-ID:
<55646D9DC2748E4CACDD632FF2E53982028A65D2@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi Deepa,
Thanks for the good news. Let me know what problems you ran into with
the build.xml.
The sample is basically a stubbed version of the first part of the POC
scenario. By "stubbed I mean there is no real functionality behind the
services. In the POC scenario, TeamTrack initiates the request, the
source is got and build and Tean track is updated. The optional Scan
and Test service flow part of the POC are not included in the sample
currently for various reasons althoug the TT service flow will raise the
event to run them
A couple of things that may not be obvious are the service flows and the
event manager client.
The service flows are in the form of ActiveBPEL BPR files. These are
like .jar files. You can open them with a .zip utility. They contain
the BPEL file, the WSDL files and/or the PartnerLink .WSDLs that
reference them and some activeBPEL specific XML deployment files that
tie things together. The BPEL was actually developed using the Oracle
BPEL designer but can with some minor changes be edited using the Active
BPEL desinger. I hope to document that and provide Active BPEL eclipse
projects sometime soon.
The event manager client is a library that raise an alf event. It can
use a file to fill the event and this feature is used in the sample. It
also allow the caller to override the values of fields when the even is
requested. It also has a feature to allow the event to be raised on a
separate thread so that the service stub can simulate an asynchronous
operation in a synchronous request. For example the request to "build"
returns immediately with a response indicating that it got the request.
However the "build" takes time and when it is done will raise an event.
The client will become a core piece of ALF but the current
implementation needs some refinement and a few fixes.
This is a POC sample so nothing in it represents final work or
interfaces.
Tim
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Deepa Rai
Sent: Tuesday, August 01, 2006 11:09 AM
To: alf-dev@xxxxxxxxxxx
Subject: [alf-dev] RE: Availability of complete POC sample code
Thanks Tim!!
I did setup the POC sample and could run it without any problems....
instructions were very helpful. The only thing that didn't work for me
was build.xml file that is used to deploy all the web services war files
and event manager in stand alone Tomcat. I made few corrections and was
able to deploy my stuff.
So far so good.... my next step is to understand the sample.
Thanks,
Deepa
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
------------------------------
Message: 5
Date: Tue, 1 Aug 2006 18:26:42 -0700
From: "Tim Buss" <TBuss@xxxxxxxxxx>
Subject: RE: [alf-dev] ALF Source Code Mangement
VocabularyMeeting+1-303-928-3232 id 6053141# Wednesday 10:00AM
PDT -
meeting minutes
To: "ALF Developer Mailing List" <alf-dev@xxxxxxxxxxx>
Message-ID:
<55646D9DC2748E4CACDD632FF2E53982028FF368@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Meeting minutes for the ALF Source Code Management Vocabulary Meeting on
Wednesday July 28th at 10:00AM PDT
Agenda
0. Last meetings's minutes (below)
1. Status on tasks (see list in minutes below)
2. Data model and Schema (see attached)
3. Events
4. Any other business
Attendees
Richard Title
Mark Phippard
Eric Minick
Tim Buss
0. Last weeks minutes were accepted. No additional comments were noted
except I had the date wrong.
1. Tasks
Completed
T20 Add the notion of User to the concepts User is an important concept
to SCM since a primary function is to attribute changes to particular
authors
Eric added some "user stuff"
Todo
T15.
Expand "primitive" use cases to include more detail (eg datatypes,
method signatures) Richard made some updates. Adam committed to update
the items he signed up for and resend the email soliciting for
volunteers to address the remaining items
T17.
Create a schema from the data model.
Tim has create a set of type defintions from the main data model.
Workspace still needs to be addressed. Revision Specification need more
discussion (see T21)
T19
Wikki pictures. There are some placeholders for pictures in the Wikki.
These need to be populated. In particular it would be good to get the
updated data model into the Wikki
T21. Refine the idea of "Revision Specification". Define the common use
cases.
There are several ways this could be expressed. For example:
A) as an opaque string to ALF
B) as a formal set of "objects" that can be related in some formal way
C) as an ALF defined "language string
D) some combination of above.
It seems that there are some common use cases (eg get "latest" from
branch) that should be defined explicitly by ALF but there are many
other cases. It seems unwise for ALF to attempt to define a fully
generalized approach. For this cases ALF should just allow the
underlying tool to extend the ALF services or provide tool specific
services. We need to decide what cases make sense for ALF to formally
define.
This should be an agenda item for next week.
T22. Create WSDL for operations and events
2. Data model and Schema
The schema was given a quick review.
It was noted that two spellings of Label were used.
Some of last meetings discussion may not be reflected in the
schema and that should be reviewed.
It was noted that timestamp is currently a string and since time
is important to SCM it was thought better if the schema datetime type
was used.
3. Events
We walked through the various proposed operations and discussed the
events that might result. My notes are not good on this CreateWorkspace
no event needed?
ModifyWorkspace
no event needed?
RemoveWorkspace
no event needed?
AddAssets
Seems similar to CreateNewVersions
a NewElementVersion event seems useful. An issue would be if
there 100s at once as a project gets checked it.
RemoveAssets
ElementRemoved seems reasonable. Probably not a core ALF
scenario IntentToModify
Not clear what the ALF scneario would be. An issue would be if
there are 100s of locks at once if a project gets locked. May need an
event it it could be slow.
CreateNewVersions
(see AddAssets)
CreateStream
NewStream event seems reasonable. Probably not a core ALF
scenario. May need an event if it could be slow.
CreateBaseline
NewBaseline event seems reasonable. Might be connected with a
build. May need an event if it could be slow.
UpdateWorkset
WorksetUpdated (Workspace surely?) Probably the trigger to
start the build CompareElementVersions
CompareComplete event seems reasonable. Might be connected with
a build. May need an event if it could be slow.
Merge
Merge does not seem like a good candidate for ALF since it can
fail in ways that cannot be detected. If it is useful then it may need
an event if it could be slow.
Promote
ElementVersionPromoted seem a bit to granular.
ElementVersionsPromoted seems more useful
3. Any other business
A point was raise that perhaps raising an ALF Event for every
asynchronous action completion may be too heavyweight. An alternative
using a dynamic callback service passed with the operation was
suggested. This would probably tale the form of an ALF event in
defintion but would connect back to the calling instance of the service
flow directly. The removes the need to create new service flow
instance and simplifies data correlation in some cases.
Tim Buss - Serena.
-----Original Message-----
From: Tim Buss
Sent: Wednesday, July 12, 2006 4:19 PM
To: 'ALF Developer Mailing List'
Subject: RE: [alf-dev] ALF Source Code Mangement
VocabularyMeeting+1-303-928-3232 id 6053141# Wednesday 10:00AM PDT -
meeting minutes
Meeting minutes for the ALF Source Code Management Vocabulary Meeting on
Wednesday July 12th at 10:00AM PDT
Agenda
0. Last meetings's minutes (below)
1. Status on tasks (see list in minutes below)
2. Data model and Schema
3. Any other business
Attendees
Richard Title
Adam Simantel
Brian Carroll
Tim Buss
Eric Minick
0. Last weeks minutes were accepted. No additional comments were noted.
1. Tasks
Completed
T11. Integration based use cases
We decided that this was being discussed extensively as part of the
build use case and that we can piggy back off that discussion. This
will become important once we have the proposed schema/WSDL since we
will need to apply the use case filter to determine if we have a
reasonable definition (ie useful but not overreaching)
T16.
Update Data model based on ALF meeting feedback.
Brian sent out the updates.
Todo
T15.
Expand "primitive" use cases to include more detail (eg datatypes,
method signatures) Richard made some updates. Adam committed to update
the items he signed up for and resend the email soliciting for
volunteers to address the remaining items
T17.
Create a schema from the data model.
Tim has create a set of type defintions from the main data model.
Workspace still needs to be addressed. Revision Specification need more
discussion (see T21)
T19
Wikki pictures. There are some placeholders for pictures in the Wikki.
These need to be populated. In particular it would be good to get the
updated data model into the Wikki
T20 Add the notion of User to the concepts User is an important concept
to SCM since a primary function is to attribute changes to particular
authors
Eric agreed to take this on.
T21. Refine the idea of "Revision Specification". Define the common use
cases.
There are several ways this could be expressed. For example:
A) as an opaque string to ALF
B) as a formal set of "objects" that can be related in some formal way
C) as an ALF defined "language string
D) some combination of above.
It seems that there are some common use cases (eg get "latest" from
branch) that should be defined explicitly by ALF but there are many
other cases. It seems unwise for ALF to attempt to define a fully
generalized approach. For this cases ALF should just allow the
underlying tool to extend the ALF services or provide tool specific
services. We need to decide what cases make sense for ALF to formally
define.
This should be an agenda item for next week.
T22. Create WSDL for operations and events
2. Data model and Schema
We discusse the simplified data model. A few changes were suggested
It seems natural that the SCM system would be identified by the service
endpoint and may not need to be explictly described as part of the data
model. In other words the service endpoint should provide sufficient
context for the operations ALF cares about. It was noted that SCM
provides a context relationship to all of the entities and that this was
probably best descibed through operation defintion rathter thand the
data model
Label seems to be in the correct place. The relationship between
ElementVersion and Label might be better annotated with "refers to" or
not annotated than with "has" since, in the abstract at least, Labels
are not owned by the Element Version.
Lock seem to be in the right place on Element Version since typically
you lock the tip of a branch which would be an Element Version.
Not one argued strongly to keep the idea of Revision Identifier so it
remains gone.
It was suggested that it may be useful for an Element Version to provide
ancestor and successor IDs so that its position in an element tree could
be determined. This is relatively cheap to do although the use case for
ALF is not immediately clear. On the data model this can be described
with a relationship line.
StreamParent should be represented as a relationship line. Probably
should be Branch ancestor and Branch successor to be complete.
ChangeSet and Baseline remain as sibling Version Collections with
different meanings. It was agree that any relationship between this was
better expressed through SCM operations or would be held externally in
Build and Issue tracking tools. The need for a relationship store as a
common service in ALF was mentioned. This has been proposed elsewhere.
We did not have time to walk through the schema so that was left for
howework
Action items -
Tim will prepare the workspace description for the next meeting. T17 We
need to come up this the set of operation and the events they cause.
T15 could provide an initial set
3. Any other business
Agenda items for the next meeting
"Revision Specification" (see T21)
Datamodel/schema workspace
Operations/Events in preparetion for WSDL
Tim Buss - Serena.
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
------------------------------
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
End of alf-dev Digest, Vol 14, Issue 2
**************************************
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
