You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by Kurt T Stam <ku...@gmail.com> on 2009/03/18 21:12:37 UTC
status meeting March 18, 2009
KurtStam_: hey guys
[1:58pm] jfaath: howdy
[1:58pm] tcunning: hiya
[1:58pm] KurtStam_: Did my file upload work?
[1:58pm] KurtStam_: just curious..
[1:58pm] jfaath: no
[1:58pm] jfaath: failed connection
[1:58pm] tcunning: yeah, failed for me too
[2:00pm] KurtStam_: k emailed it now too
[2:00pm] [1]Troy joined the chat room.
[2:00pm] KurtStam_: it is a screenshot of a the UDDI Browser Portlet
Proof of Concept
[2:01pm] [1]Troy is now known as TroyHaaland.
[2:01pm] tcunning: is it the one you sent around?
[2:01pm] KurtStam_: anyway, want to go around for status update?
[2:01pm] jfaath: cool
[2:01pm] KurtStam_: yeah but now actually running in a portal
[2:01pm] tcunning: cool
[2:02pm] KurtStam_: so after alfa I worked on getting openjpa to work,
which is working now
[2:02pm] KurtStam_: the build machine is still failing, but I'll get to
that..
[2:03pm] jfaath: who's been working on the portal?
[2:03pm] KurtStam_: also I cleaned up some other small issues I can't
remember now but the list of jiras got pretty short for 3.0 beta
[2:03pm] jfaath: do we have a new resource?
[2:03pm] KurtStam_: I have been working on it. I have a standing offer
from a UI guy
[2:03pm] KurtStam_: so I'm setting up the framework, so he can go to town
[2:04pm] tcunning: nice!
[2:04pm] KurtStam_: I picked GWT b/c it is simple, and b/c I don't need
persistence, just UI
[2:04pm] KurtStam_: GWT is apache2 licensed so we should be good there.
[2:05pm] jfaath: gotcha
[2:05pm] KurtStam_: I'm thinking of 3 portlets; browse, search and register
[2:05pm] KurtStam_: and I just just for it to work end2end;
[2:05pm] KurtStam_: browser -> GTW tomcat -> jUDDI tomcat WS
[2:06pm] KurtStam_: browser looking at the Pluto Portal
[2:06pm] KurtStam_: I'm thinking that portlets are nice so people can
embed it in their apps
[2:07pm] KurtStam_: also I looked at he 3 client side API that are remaining
[2:07pm] KurtStam_: turns out all of them are optional
[2:07pm] KurtStam_: but we prob want to implement the subscription
client side.
[2:07pm] jfaath: did you get a chance to read chapter 7?
[2:07pm] KurtStam_: so we can test that subscriptions work
[2:07pm] jfaath: i'd like a second opinion on my assessment
[2:08pm] KurtStam_: no sorry, not yet.
[2:08pm] KurtStam_: I'm kinda done woth my status want to jump in?
[2:08pm] jfaath: sure
[2:08pm] jfaath: I was ready to work on replication, until I read
through chapter 7
[2:09pm] jfaath: than when searching for more information on the net, i
found Anne's old post about it being an "ugly rat's nest"
[2:09pm] jfaath: and i couldn't agree more
[2:09pm] KurtStam_: yeah I remember that
[2:09pm] jfaath: trying to do load balancing and failover with XML
messaging is ugly, and that's putting it nicely
[2:10pm] jfaath: chapter 8 talks about transferring data between
registries in a different context
[2:10pm] jfaath: with root and affiliates
[2:10pm] KurtStam_: sounds like ESB type of functionality
[2:10pm] jfaath: and it focuses on the subscription functionality to
achieve this
[2:11pm] jfaath: so, i think that should be our next api focus
[2:11pm] jfaath: i'm ready to put a couple of weeks of hard labor into it
[2:11pm] KurtStam_: cool.
[2:11pm] KurtStam_: it seems to me that we need subscription more then
anything else
[2:11pm] tcunning: i am too. SCOUT-57 i should be checking in today
and then i'm done there.
[2:12pm] KurtStam_: so it'd be great to divide and conquor
[2:12pm] TroyHaaland: so we are really no further with Subscription then
we were in December?
[2:12pm] jfaath: yea, i meant to go through and JIRA it up, but have
been tied down with other things
[2:13pm] KurtStam_: Hi Troy, how are you?
[2:13pm] TroyHaaland: good, hopeful that we were going to be talking
about the Beta release
[2:14pm] jfaath: that's a good point, what are the milestones for beta?
[2:14pm] KurtStam_: yeah I added tag in jira
[2:14pm] jfaath: assuming that kurt reads chapter 7 and concludes the
same thing
[2:14pm] KurtStam_: and assigned taks
[2:14pm] TroyHaaland: was also wondering about the Alpha release and any
feedback that may have come back
[2:14pm] KurtStam_: I will read chapter 7..soon
[2:14pm] KurtStam_: but I'm thinking we can release beta without it,
[2:15pm] KurtStam_:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10401&fixfor=12313630
[2:15pm] KurtStam_: we have 9 tasks
[2:15pm] KurtStam_: but subscription needs to be broken out
[2:15pm] jfaath: yea, i'll get to that, perhaps today
[2:15pm] tcunning: want to break them out now?
[2:16pm] KurtStam_: sure
[2:16pm] KurtStam_: got some suggestions?
[2:16pm] tcunning: registration seems like a "part"
[2:16pm] tcunning: notification seems like a "part"
[2:17pm] tcunning: the subscription model itself (durations / point in
time / coverage / etc) seems like something
[2:17pm] tcunning: registration and notification probably could be
drilled down further
[2:18pm] KurtStam_: I could work on notification, so I can test the
client side subscription API
[2:19pm] jfaath: yea, i built out subscription before on the old juddi,
i just have to re-familiarize myself with the spec
[2:20pm] KurtStam_: let me add these 4 to jira now
[2:23pm] KurtStam_: 3 I can't count..
[2:23pm] KurtStam_: done
[2:23pm] jfaath: also, knowing what subscription entailed, i already did
some of the legwork with operational info
[2:24pm] jfaath: it keeps track of changes in entities
[2:24pm] KurtStam_: this is the "model"
[2:24pm] KurtStam_: ?
[2:24pm] jfaath: so, I think it's a matter of "saving" subscriptions and
returning results based on those subscriptions
[2:25pm] KurtStam_: right and we need some background processing to call
back?
[2:25pm] jfaath: operational info is a uddi structure that keeps global
information on entities
[2:26pm] tcunning: are we generating operational info now on changes?
[2:26pm] jfaath: yep, i added that in knowing we would need it
[2:26pm] tcunning: cool
[2:26pm] jfaath: i remember the big annoyance with subscription saving
was the subscription filter
[2:26pm] jfaath: which is basically a bunch of find_* xml messages
[2:27pm] jfaath: find_business, find_service, etc
[2:27pm] tcunning: right because you can save a subscription to a query
[2:27pm] jfaath: yep, so how do we store it? as a big text blob?
[2:27pm] jfaath: or individually?
[2:27pm] tcunning: i think we resolve the results of the query and
assign subscriptions to the result
[2:28pm] jfaath: i remember checking the danish guys code and i think
they store it as a blob
[2:28pm] tcunning: i didn't see anything in the spec about whether new
data (a new tmodel that fits the query for example) is re-resolved into
the results
[2:28pm] tcunning: or do we just save the query itself?
[2:29pm] jfaath: anyway, other than that, subscription is pretty
straight-forward. I'll have to re-read the spec
[2:30pm] KurtStam_: ok well maybe we can break the tasks out even more.
Like I said can take the notification
[2:31pm] KurtStam_: any other natural fits?
[2:31pm] KurtStam_: on how to divi it up?
[2:31pm] TroyHaaland: has there been any additional interest to provide
development support post the Alpha release (besides UI)?
[2:31pm] jfaath: well, i think the two operations might be
divisible...saving and returning results
[2:32pm] KurtStam_: we may get support for replication
[2:33pm] jfaath: oh yea?
[2:33pm] jfaath: from where?
[2:33pm] KurtStam_: yeah one of the Jboss clients is really waiting for
that and may be able to provide a resource
[2:33pm] TroyHaaland: is there a time frame?
[2:34pm] tcunning: we've been hearing that for a while though, not sure
i'd count on it.
[2:34pm] KurtStam_: right, so I think out plan should be to release with
subscription
[2:35pm] KurtStam_: and have replication be an added bonus
[2:35pm] tcunning: sounds good to me
[2:35pm] TroyHaaland: wouldn't replication be the only API not included
in the release?
[2:35pm] KurtStam_: y but officially it is a required API
[2:36pm] TroyHaaland: do the commercial vendors support it?
[2:36pm] KurtStam_: according to Anna no..
[2:36pm] KurtStam_: and she is an analyst
[2:36pm] KurtStam_: so she should know that stuff
[2:37pm] jfaath:
http://www.nabble.com/Registry-Replication-td9777609.html
[2:37pm] TroyHaaland: I still need to go through chapter 7 again
[2:37pm] jfaath: at 4/2007, she apparently said they don't
[2:37pm] TroyHaaland: but I wonder Kurt if an ESB could provide that
functionality
[2:38pm] KurtStam_: yeah JBossESB has it..
[2:38pm] KurtStam_: well the failover etc
[2:38pm] KurtStam_: we need to investigate how that would work.
[2:39pm] TroyHaaland: yeah, does Jboss have a sandbox that we could test on?
[2:39pm] KurtStam_: you can download a bundle
[2:39pm] KurtStam_: and run on your local box
[2:40pm] TroyHaaland: Tom, do you know if Mark, etc... is expexting
replication?
[2:40pm] TroyHaaland: *expecting
[2:40pm] tcunning: don't know. I know subscription is the most useful
one for us.
[2:41pm] tcunning: it looks like Systinet and BEA might support replication
[2:41pm] tcunning: not sure about SOA Software
[2:42pm] KurtStam_: so my proposal would be to dig into subscription,
maybe add some more subtasks, make sure the load is evenly spread
[2:42pm] jfaath: where do you see that tom?
[2:43pm] jfaath: b/c it might be that they support it using a
proprietary method, or even the subscription api
[2:43pm] tcunning: just googling replication uddi v3
[2:43pm] jfaath: as anne suggests in her post
[2:43pm] tcunning: some systinet replication API's pop up
[2:43pm] KurtStam_: and then work to 3.0 beta list. Leave replication
for 3.0 or later
[2:43pm] TroyHaaland: both of those vendors acquired the registry
[2:43pm] tcunning: i agree with Kurt
[2:44pm] TroyHaaland: I assume by now they have had time to complete
[2:45pm] tcunning: we could always write Anne and ask her if anything
has changed since her post?
[2:45pm] jfaath: replication is not insurmountable, i just think it
would take as much time to complete as all of juddi has so far
[2:45pm] TroyHaaland: I think that makes sense as well
[2:45pm] jfaath: with everyone working on it
[2:46pm] jfaath: but, i await kurt's second opinion
[2:46pm] KurtStam_: ok I will read
[2:46pm] KurtStam_: promise
[2:46pm] KurtStam_:
[2:47pm] KurtStam_: anything else?
[2:47pm] TroyHaaland: how was, if any, feedback on Alpha?
[2:47pm] KurtStam_: looks to me beta is in reach
[2:47pm] jfaath: i think we're good...i'm going to dive into
subscription spec today and see if i can come up with tasks
[2:48pm] KurtStam_: looks like poeple are going for 2.0rc6
[2:48pm] jfaath: yea, i wonder how many implemented alpha
[2:48pm] jfaath: one thing we should be concerned with is keeping the
model stable
[2:48pm] TroyHaaland: Alpha is pretty much v2 meaning supported API's
[2:48pm] jfaath: well, the apis have enhancements
[2:49pm] jfaath: specified by v3
[2:49pm] You left the chat by being disconnected from the server.
[2:49pm] You rejoined the room.
[2:49pm] TroyHaaland: right, was thinking that the current v2 base may
have checked out the Alpha
[2:50pm] jfaath: yea, the concern may be that the back-end will change
[2:51pm] jfaath: but if you go with juddi v2, you will be stuck with a
differenct db structure and an old architecture
[2:52pm] TroyHaaland: that's where the community could deliver migration
tools / plans, etc..
[2:52pm] KurtStam_ left the chat room. (Read error: 60 (Operation timed
out))
[2:52pm] jfaath: true
[2:52pm] jfaath: kurt, are you there?
[2:52pm] KurtStam__: y
[2:53pm] KurtStam__: the response was pretty good I thought on the the
serverside
[2:53pm] tcunning: just wrote anne, hopefully we'll hear back on that soon
[2:55pm] jfaath: well, i think we are good
[2:55pm] jfaath: perhaps we can wrap up by going over who will be
working on what in the coming weeks?
[2:56pm] jfaath: I'll look over the subscription api, come up with some
tasks and start working on it
[2:56pm] KurtStam__: cool
[2:56pm] jfaath: i can put in significant time in the next two weeks
[2:56pm] KurtStam__: I will start on the notification stuff
[2:56pm] KurtStam__: tom are you almost done with scout?
[2:57pm] tcunning: yes, SCOUT-57's the last one and i'll have that in today
[2:57pm] KurtStam__: so please assign some of the task to yourself
[2:58pm] tcunning: i'll start tomorrow on jUDDI but i'm waiting on
someone to test so could we put the scout release off until that's done?
[2:58pm] KurtStam__: I think you are the one waiting on the scout reease..
[2:58pm] KurtStam__: so sure fine by me
[2:58pm] jfaath: what about load testing juddi now? that would be a
useful exercise
[2:59pm] jfaath: particularly i'd like to see how queries work with
large results and the pagination
[2:59pm] tcunning: definitely sounds like a good JIRA bug
[2:59pm] jfaath: oh, i see that's a jira
[3:00pm] KurtStam__: sure are you volunteering, or just curious?
[3:00pm] TroyHaaland: is there enough test data to properly test?
[3:00pm] jfaath: 181
[3:00pm] KurtStam__: yeah I added it
[3:00pm] KurtStam__: a while back
[3:00pm] tcunning: kurt's way ahead of us
[3:01pm] You left the chat by being disconnected from the server.
[3:01pm] You rejoined the room.
[3:01pm] You left the chat by being disconnected from the server.
[3:01pm] You rejoined the room.
[3:01pm] KurtStam_____: k I'm afraid I have to move on to the next thing
[3:01pm] TroyHaaland: so.... Marcos is good with Macros?
[3:02pm] jfaath: ok
[3:02pm] KurtStam_____: I'm around, so we can talk later this week..
[3:02pm] jfaath: sounds like a wrap
[3:02pm] jfaath: ok
[3:02pm] KurtStam_____: cheers
[3:03pm] TroyHaaland: ciao
Re: status meeting March 18, 2009
Posted by Kurt T Stam <ku...@gmail.com>.
BTW these where the issues that got closed after the alpha release went out.
Task JUDDI-149 FIXED BusinessEntities require serviceProjections
collection Major Closed
Task JUDDI-136 FIXED How to deal with a table prefix (JUDDI_) when
using JPA Major Closed
Bug JUDDI-195 FIXED OpenJPA does not work in alpha
Major Closed
Bug JUDDI-194 FIXED We only want the exploded webapps/juddi
directory Major Closed
Task JUDDI-182 WON'T FIX Investigate using the maven release plugin.
Major Closed
Bug JUDDI-175 FIXED resources are not on the eclipse classpath by
default Minor Closed
--Kurt
Kurt T Stam wrote:
> KurtStam_: hey guys
> [1:58pm] jfaath: howdy
> [1:58pm] tcunning: hiya
> [1:58pm] KurtStam_: Did my file upload work?
> [1:58pm] KurtStam_: just curious..
> [1:58pm] jfaath: no
> [1:58pm] jfaath: failed connection
> [1:58pm] tcunning: yeah, failed for me too
> [2:00pm] KurtStam_: k emailed it now too
> [2:00pm] [1]Troy joined the chat room.
> [2:00pm] KurtStam_: it is a screenshot of a the UDDI Browser Portlet
> Proof of Concept
> [2:01pm] [1]Troy is now known as TroyHaaland.
> [2:01pm] tcunning: is it the one you sent around?
> [2:01pm] KurtStam_: anyway, want to go around for status update?
> [2:01pm] jfaath: cool
> [2:01pm] KurtStam_: yeah but now actually running in a portal
> [2:01pm] tcunning: cool
> [2:02pm] KurtStam_: so after alfa I worked on getting openjpa to work,
> which is working now
> [2:02pm] KurtStam_: the build machine is still failing, but I'll get
> to that..
> [2:03pm] jfaath: who's been working on the portal?
> [2:03pm] KurtStam_: also I cleaned up some other small issues I can't
> remember now but the list of jiras got pretty short for 3.0 beta
> [2:03pm] jfaath: do we have a new resource?
> [2:03pm] KurtStam_: I have been working on it. I have a standing offer
> from a UI guy
> [2:03pm] KurtStam_: so I'm setting up the framework, so he can go to town
> [2:04pm] tcunning: nice!
> [2:04pm] KurtStam_: I picked GWT b/c it is simple, and b/c I don't
> need persistence, just UI
> [2:04pm] KurtStam_: GWT is apache2 licensed so we should be good there.
> [2:05pm] jfaath: gotcha
> [2:05pm] KurtStam_: I'm thinking of 3 portlets; browse, search and
> register
> [2:05pm] KurtStam_: and I just just for it to work end2end;
> [2:05pm] KurtStam_: browser -> GTW tomcat -> jUDDI tomcat WS
> [2:06pm] KurtStam_: browser looking at the Pluto Portal
> [2:06pm] KurtStam_: I'm thinking that portlets are nice so people can
> embed it in their apps
> [2:07pm] KurtStam_: also I looked at he 3 client side API that are
> remaining
> [2:07pm] KurtStam_: turns out all of them are optional
> [2:07pm] KurtStam_: but we prob want to implement the subscription
> client side.
> [2:07pm] jfaath: did you get a chance to read chapter 7?
> [2:07pm] KurtStam_: so we can test that subscriptions work
> [2:07pm] jfaath: i'd like a second opinion on my assessment
> [2:08pm] KurtStam_: no sorry, not yet.
> [2:08pm] KurtStam_: I'm kinda done woth my status want to jump in?
> [2:08pm] jfaath: sure
> [2:08pm] jfaath: I was ready to work on replication, until I read
> through chapter 7
> [2:09pm] jfaath: than when searching for more information on the net,
> i found Anne's old post about it being an "ugly rat's nest"
> [2:09pm] jfaath: and i couldn't agree more
> [2:09pm] KurtStam_: yeah I remember that
> [2:09pm] jfaath: trying to do load balancing and failover with XML
> messaging is ugly, and that's putting it nicely
> [2:10pm] jfaath: chapter 8 talks about transferring data between
> registries in a different context
> [2:10pm] jfaath: with root and affiliates
> [2:10pm] KurtStam_: sounds like ESB type of functionality
> [2:10pm] jfaath: and it focuses on the subscription functionality to
> achieve this
> [2:11pm] jfaath: so, i think that should be our next api focus
> [2:11pm] jfaath: i'm ready to put a couple of weeks of hard labor into it
> [2:11pm] KurtStam_: cool.
> [2:11pm] KurtStam_: it seems to me that we need subscription more then
> anything else
> [2:11pm] tcunning: i am too. SCOUT-57 i should be checking in today
> and then i'm done there.
> [2:12pm] KurtStam_: so it'd be great to divide and conquor
> [2:12pm] TroyHaaland: so we are really no further with Subscription
> then we were in December?
> [2:12pm] jfaath: yea, i meant to go through and JIRA it up, but have
> been tied down with other things
> [2:13pm] KurtStam_: Hi Troy, how are you?
> [2:13pm] TroyHaaland: good, hopeful that we were going to be talking
> about the Beta release
> [2:14pm] jfaath: that's a good point, what are the milestones for beta?
> [2:14pm] KurtStam_: yeah I added tag in jira
> [2:14pm] jfaath: assuming that kurt reads chapter 7 and concludes the
> same thing
> [2:14pm] KurtStam_: and assigned taks
> [2:14pm] TroyHaaland: was also wondering about the Alpha release and
> any feedback that may have come back
> [2:14pm] KurtStam_: I will read chapter 7..soon
> [2:14pm] KurtStam_: but I'm thinking we can release beta without it,
> [2:15pm] KurtStam_:
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10401&fixfor=12313630
>
> [2:15pm] KurtStam_: we have 9 tasks
> [2:15pm] KurtStam_: but subscription needs to be broken out
> [2:15pm] jfaath: yea, i'll get to that, perhaps today
> [2:15pm] tcunning: want to break them out now?
> [2:16pm] KurtStam_: sure
> [2:16pm] KurtStam_: got some suggestions?
> [2:16pm] tcunning: registration seems like a "part"
> [2:16pm] tcunning: notification seems like a "part"
> [2:17pm] tcunning: the subscription model itself (durations / point in
> time / coverage / etc) seems like something
> [2:17pm] tcunning: registration and notification probably could be
> drilled down further
> [2:18pm] KurtStam_: I could work on notification, so I can test the
> client side subscription API
> [2:19pm] jfaath: yea, i built out subscription before on the old
> juddi, i just have to re-familiarize myself with the spec
> [2:20pm] KurtStam_: let me add these 4 to jira now
> [2:23pm] KurtStam_: 3 I can't count..
> [2:23pm] KurtStam_: done
> [2:23pm] jfaath: also, knowing what subscription entailed, i already
> did some of the legwork with operational info
> [2:24pm] jfaath: it keeps track of changes in entities
> [2:24pm] KurtStam_: this is the "model"
> [2:24pm] KurtStam_: ?
> [2:24pm] jfaath: so, I think it's a matter of "saving" subscriptions
> and returning results based on those subscriptions
> [2:25pm] KurtStam_: right and we need some background processing to
> call back?
> [2:25pm] jfaath: operational info is a uddi structure that keeps
> global information on entities
> [2:26pm] tcunning: are we generating operational info now on changes?
> [2:26pm] jfaath: yep, i added that in knowing we would need it
> [2:26pm] tcunning: cool
> [2:26pm] jfaath: i remember the big annoyance with subscription saving
> was the subscription filter
> [2:26pm] jfaath: which is basically a bunch of find_* xml messages
> [2:27pm] jfaath: find_business, find_service, etc
> [2:27pm] tcunning: right because you can save a subscription to a query
> [2:27pm] jfaath: yep, so how do we store it? as a big text blob?
> [2:27pm] jfaath: or individually?
> [2:27pm] tcunning: i think we resolve the results of the query and
> assign subscriptions to the result
> [2:28pm] jfaath: i remember checking the danish guys code and i think
> they store it as a blob
> [2:28pm] tcunning: i didn't see anything in the spec about whether new
> data (a new tmodel that fits the query for example) is re-resolved
> into the results
> [2:28pm] tcunning: or do we just save the query itself?
> [2:29pm] jfaath: anyway, other than that, subscription is pretty
> straight-forward. I'll have to re-read the spec
> [2:30pm] KurtStam_: ok well maybe we can break the tasks out even
> more. Like I said can take the notification
> [2:31pm] KurtStam_: any other natural fits?
> [2:31pm] KurtStam_: on how to divi it up?
> [2:31pm] TroyHaaland: has there been any additional interest to
> provide development support post the Alpha release (besides UI)?
> [2:31pm] jfaath: well, i think the two operations might be
> divisible...saving and returning results
> [2:32pm] KurtStam_: we may get support for replication
> [2:33pm] jfaath: oh yea?
> [2:33pm] jfaath: from where?
> [2:33pm] KurtStam_: yeah one of the Jboss clients is really waiting
> for that and may be able to provide a resource
> [2:33pm] TroyHaaland: is there a time frame?
> [2:34pm] tcunning: we've been hearing that for a while though, not
> sure i'd count on it.
> [2:34pm] KurtStam_: right, so I think out plan should be to release
> with subscription
> [2:35pm] KurtStam_: and have replication be an added bonus
> [2:35pm] tcunning: sounds good to me
> [2:35pm] TroyHaaland: wouldn't replication be the only API not
> included in the release?
> [2:35pm] KurtStam_: y but officially it is a required API
> [2:36pm] TroyHaaland: do the commercial vendors support it?
> [2:36pm] KurtStam_: according to Anna no..
> [2:36pm] KurtStam_: and she is an analyst
> [2:36pm] KurtStam_: so she should know that stuff
> [2:37pm] jfaath:
> http://www.nabble.com/Registry-Replication-td9777609.html [2:37pm]
> TroyHaaland: I still need to go through chapter 7 again
> [2:37pm] jfaath: at 4/2007, she apparently said they don't
> [2:37pm] TroyHaaland: but I wonder Kurt if an ESB could provide that
> functionality
> [2:38pm] KurtStam_: yeah JBossESB has it..
> [2:38pm] KurtStam_: well the failover etc
> [2:38pm] KurtStam_: we need to investigate how that would work.
> [2:39pm] TroyHaaland: yeah, does Jboss have a sandbox that we could
> test on?
> [2:39pm] KurtStam_: you can download a bundle
> [2:39pm] KurtStam_: and run on your local box
> [2:40pm] TroyHaaland: Tom, do you know if Mark, etc... is expexting
> replication?
> [2:40pm] TroyHaaland: *expecting
> [2:40pm] tcunning: don't know. I know subscription is the most
> useful one for us.
> [2:41pm] tcunning: it looks like Systinet and BEA might support
> replication
> [2:41pm] tcunning: not sure about SOA Software
> [2:42pm] KurtStam_: so my proposal would be to dig into subscription,
> maybe add some more subtasks, make sure the load is evenly spread
> [2:42pm] jfaath: where do you see that tom?
> [2:43pm] jfaath: b/c it might be that they support it using a
> proprietary method, or even the subscription api
> [2:43pm] tcunning: just googling replication uddi v3
> [2:43pm] jfaath: as anne suggests in her post
> [2:43pm] tcunning: some systinet replication API's pop up
> [2:43pm] KurtStam_: and then work to 3.0 beta list. Leave replication
> for 3.0 or later
> [2:43pm] TroyHaaland: both of those vendors acquired the registry
> [2:43pm] tcunning: i agree with Kurt
> [2:44pm] TroyHaaland: I assume by now they have had time to complete
> [2:45pm] tcunning: we could always write Anne and ask her if anything
> has changed since her post?
> [2:45pm] jfaath: replication is not insurmountable, i just think it
> would take as much time to complete as all of juddi has so far
> [2:45pm] TroyHaaland: I think that makes sense as well
> [2:45pm] jfaath: with everyone working on it
> [2:46pm] jfaath: but, i await kurt's second opinion
> [2:46pm] KurtStam_: ok I will read
> [2:46pm] KurtStam_: promise
> [2:46pm] KurtStam_: [2:47pm] KurtStam_:
> anything else?
> [2:47pm] TroyHaaland: how was, if any, feedback on Alpha?
> [2:47pm] KurtStam_: looks to me beta is in reach
> [2:47pm] jfaath: i think we're good...i'm going to dive into
> subscription spec today and see if i can come up with tasks
> [2:48pm] KurtStam_: looks like poeple are going for 2.0rc6
> [2:48pm] jfaath: yea, i wonder how many implemented alpha
> [2:48pm] jfaath: one thing we should be concerned with is keeping the
> model stable
> [2:48pm] TroyHaaland: Alpha is pretty much v2 meaning supported API's
> [2:48pm] jfaath: well, the apis have enhancements
> [2:49pm] jfaath: specified by v3
> [2:49pm] You left the chat by being disconnected from the server.
> [2:49pm] You rejoined the room.
> [2:49pm] TroyHaaland: right, was thinking that the current v2 base may
> have checked out the Alpha
> [2:50pm] jfaath: yea, the concern may be that the back-end will change
> [2:51pm] jfaath: but if you go with juddi v2, you will be stuck with a
> differenct db structure and an old architecture
> [2:52pm] TroyHaaland: that's where the community could deliver
> migration tools / plans, etc..
> [2:52pm] KurtStam_ left the chat room. (Read error: 60 (Operation
> timed out))
> [2:52pm] jfaath: true
> [2:52pm] jfaath: kurt, are you there?
> [2:52pm] KurtStam__: y
> [2:53pm] KurtStam__: the response was pretty good I thought on the the
> serverside
> [2:53pm] tcunning: just wrote anne, hopefully we'll hear back on that
> soon
> [2:55pm] jfaath: well, i think we are good
> [2:55pm] jfaath: perhaps we can wrap up by going over who will be
> working on what in the coming weeks?
> [2:56pm] jfaath: I'll look over the subscription api, come up with
> some tasks and start working on it
> [2:56pm] KurtStam__: cool
> [2:56pm] jfaath: i can put in significant time in the next two weeks
> [2:56pm] KurtStam__: I will start on the notification stuff
> [2:56pm] KurtStam__: tom are you almost done with scout?
> [2:57pm] tcunning: yes, SCOUT-57's the last one and i'll have that in
> today
> [2:57pm] KurtStam__: so please assign some of the task to yourself
> [2:58pm] tcunning: i'll start tomorrow on jUDDI but i'm waiting on
> someone to test so could we put the scout release off until that's done?
> [2:58pm] KurtStam__: I think you are the one waiting on the scout
> reease..
> [2:58pm] KurtStam__: so sure fine by me
> [2:58pm] jfaath: what about load testing juddi now? that would be a
> useful exercise
> [2:59pm] jfaath: particularly i'd like to see how queries work with
> large results and the pagination
> [2:59pm] tcunning: definitely sounds like a good JIRA bug
> [2:59pm] jfaath: oh, i see that's a jira
> [3:00pm] KurtStam__: sure are you volunteering, or just curious?
> [3:00pm] TroyHaaland: is there enough test data to properly test?
> [3:00pm] jfaath: 181
> [3:00pm] KurtStam__: yeah I added it
> [3:00pm] KurtStam__: a while back
> [3:00pm] tcunning: kurt's way ahead of us
> [3:01pm] You left the chat by being disconnected from the server.
> [3:01pm] You rejoined the room.
> [3:01pm] You left the chat by being disconnected from the server.
> [3:01pm] You rejoined the room.
> [3:01pm] KurtStam_____: k I'm afraid I have to move on to the next thing
> [3:01pm] TroyHaaland: so.... Marcos is good with Macros?
> [3:02pm] jfaath: ok
> [3:02pm] KurtStam_____: I'm around, so we can talk later this week..
> [3:02pm] jfaath: sounds like a wrap
> [3:02pm] jfaath: ok
> [3:02pm] KurtStam_____: cheers
> [3:03pm] TroyHaaland: ciao
>