ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "Axis2/HackathonDec2005/chatlog" by DeepalJAID
Date Fri, 09 Dec 2005 20:10:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by DeepalJAID:

New page:
== Chat log ==

 [10:27]	Ajith: . Have a interface for the repsitory

 [10:27]	Ajith: so that a repo does not depend on the FS

 [10:27]	Ajith: FS -> File System

 [10:39]	dims pokes the team

 [10:40]	dims: are u guys awake? :)

 [10:40]	Chinthaka: yes

 [10:40]	Ajith: yep

 [10:40]	Ajith: Glen's on a call

 [10:40]	Chinthaka: another call :)

 [10:40]	dims: busy guy

 [10:41]	dims: :)

 [10:43]	dims: and where is the boss?

 [10:44]	Chinthaka: boss ?

 [10:45]	Deepal: who is the boss :) ?

 [10:45]	dims mutters...sanjiva?

 [10:46]	Ajith: Boss is on the way I guess

 [10:46]	Chinthaka: BTW, we started to think abt a file system abstraction, which we wanted
to do some time back too

 [10:46]	dims: ok

 [10:46]	Chinthaka: that is a big ISSUE and will take some time .. So we will leave it behind,
after the discussion

 [10:47]	dims: yep

 [10:47]	Chinthaka: we are fixing whatever spelling mistakes, as and when we find them

 [10:47]	dims: lots of things to do before we take that one on.

 [10:47]	dims: +1

 [10:48]	Chinthaka: BTW, when are you coming here ? Tomoro afternoon ?

 [10:48]	Chinthaka: time ?

 [10:49]	dims: yes

 [10:49]	dims: around 1:00 PM

 [10:51]	dims: i'll take the shuttle and get to the hotel and try to find u guys

 [10:51]	dims: when is paul reaching?

 [10:56]	Chinthaka: I think Paul and Sanjiva are coming together by 2.00 p.m.

 [11:00]	Chinthaka: I think we are converging for a design on AxisConfig abstraction here

 [11:01]	Chinthaka: so that, we do not depend on file system or anything

 [11:01]	Chinthaka: Glen : Would you like to explain that here, please .. :) And we can move
on with debugging ...

 [11:16]	FR^2 has joined

 [11:29]	Chinthaka has disconnected: Read error: 113 (No route to host)

 [11:30]	Chinthaka has joined

 [11:31]	Deepal: I think we need to discuss how to miggrete from Axis 1.x

 [11:32]	Deepal: we need to provide backword compatibility 

 [11:32]	Chinthaka: hey guys

 [11:32]	Chinthaka: sorry I went up for a Coke

 [11:32]	Chinthaka: Paul ??

 [11:32]	Chinthaka: where are you ?

 [11:36]	gdaniels has disconnected: Read error: 110 (Connection timed out)

 [11:39]	Glen-away has joined

 [11:39]	Glen-away is now known as gdaniels

 [11:39]	gdaniels: OK, my summary...

 [11:40]	gdaniels: We've agreed that we want a "discovery-like" way of getting AxisConfigurations

 [11:41]	gdaniels: We want a ConfigurationFactory (or whatever we call it) that needs a couple
of kinds of information - 1) the class name of the actual factory (i.e. FileConfigurationFactory,
DBConfigurationFactory), and 2) a bag of properties which will be used by the instance factory
to do work (i.e. filename, etc)

 [11:42]	gdaniels: That thing will give us an AxisConfiguration.  It will be able to default
by using system properties, home directory configuration files, etc... (i.e. AXIS_CONFIG=org.apache.axis2.config.FileConfigurationFactory)

 [11:43]	gdaniels: So there are now two ways we can look at AxisConfiguration (WAKE UP EVERYONE

 [11:43]	gdaniels: 1) AxisConfiguration is read-only.  It gets its data from the filesystem
or DB or memory, but if you want to *write* to it, you need another object (maybe the instance
of the configuration factory)

 [11:44]	gdaniels: 2) AxisConfiguration is read-write, and has "deployService()" type methods
on it.  These would do the right thing in terms of writing to the filesystem/DB/backing-store.

 [11:44]	gdaniels: Assuming I got that right, we're wondering what people think.

 [11:45]	gdaniels: so... is anyone there aside from us warm sunny San Diego folks?

 [11:45]	dims: +1

 [11:45]	gdaniels: So dims, do you like (1) or (2), or do you need more info to clarify?

 [11:46]	Chinthaka: warm ? I prefer it over the snowy Boston ;)

 [11:46]	dims: So we could have a spring based AxisConfiguration

 [11:46]	gdaniels: yes

 [11:46]	gdaniels: the real question is do we want AxisConfiguration to be read/write, or
just read

 [11:46]	dims: let's start with 1

 [11:47]	dims:  read-only

 [11:47]	Chinthaka: +1 for read only

 [11:47]	gdaniels: Chinthaka and Glen like (2)

 [11:47]	gdaniels: oops, maybe I was wrong :)

 [11:47]	Chinthaka: at least for now ...

 [11:47]	dims: write is specific to the configuration provider

 [11:47]	gdaniels: but we do need a generic interface for writing

 [11:48]	Chinthaka: I'm talking abt the current plan and then to support read only later

 [11:48]	dims: let's start with read only and then revisit if we can live w/o a write

 [11:48]	Ajith: I like 1 since for me AxisConfig is only a infostore for ne

 [11:48]	Ajith: me

 [11:48]	dims: BUT the problem is for example synapse wants to add dyanmic services on the

 [11:49]	gdaniels: my preference is to make AxisConfiguration read/write, which makes building
in-memory versions,etc, very easy

 [11:49]	gdaniels: dims: +1

 [11:49]	Ajith: so basically even if you have several implementations the diff would only
be in the read write code

 [11:49]	dims: argh!

 [11:49]	gdaniels: then the individual instances can implement write operations in their own
way, even if they want to throw UnsupportedOperation

 [11:49]	Deepal: my idea is there shoud be write capability some where

 [11:49]	Deepal: it might be in AxisOCnfig or Context

 [11:49]	gdaniels: Deepal: I sure hope so :)

 [11:49]	Ajith: so we can push the read write code to a seperate builder/creator componet

 [11:50]	dims: another trouble is how to notify the engine that the AxisConfig got updated

 [11:50]	dims: (someone drops a aar in the FS)

 [11:50]	Ajith: BTW my guess is 90% case we will read from the config rather than writing
from it

 [11:50]	dblevins has joined

 [11:50]	Chinthaka: sorry, confused you people a bit. I also like to have the second option
(I'm with Glen). But as far as the impl is concern, we can differ the way we should do it
still leaving some flexibility

 [11:51]	gdaniels: That's up to the individual implementation, dims - and you shouldn't need
to "notify" it.... it just updates itself. :)

 [11:51]	dims: ok, let's go for #2 then.

 [11:51]	Ajith: ?

 [11:51]	gdaniels: i.e. when the AxisConfiguration changes, that's all you need.  Oh, it needs
to recalc the handler chains, though.

 [11:51]	dims: hoi dblevins

 [11:51]	dims: exactly

 [11:51]	Chinthaka: so, majority set for #2 ?

 [11:51]	dblevins: dims: hi!

 [11:51]	dims: with a notifier thing.

 [11:52]	gdaniels: well, first let's make sure everyone understands everything.  If there
are more questions, let's discuss first.

 [11:52]	gdaniels: then VOTE

 [11:52]	gdaniels: is everyone OK on the differences/options?

 [11:52]	Chinthaka: ok ...

 [11:52]	dims: ok

 [11:52]	Chinthaka: but I think we can't make a decision now ..

 [11:53]	Chinthaka: better to put this in to the list

 [11:53]	gdaniels: you think we should VOTE on the list, Chinthaka?

 [11:53]	dims: we make a proposal to the list 

 [11:53]	dims: we all should agree first :)

 [11:53]	gdaniels: ok

 [11:53]	gdaniels: let's do both

 [11:53]	Chinthaka: are we agreed ? :)

 [11:53]	gdaniels: quick vote between us here and then we'll inform the list what we talked

 [11:53]	Chinthaka: me yes :)

 [11:53]	dims: Let's do #2 (with minimal write?)

 [11:54]	gdaniels: I think #2 as well

 [11:55]	dims says it's getting real bad here outside my window

 [11:56]	gdaniels: egads - I was just talking to Philippe about that... he was saying it's
just ridiculous snow

 [11:57]	dims: decision made?

 [11:57]	gdaniels: ok yes

View raw message