hi,
it was very good chat we made lot of plans and tasks
(and now we need to make sure all tasks will be worked on ...):
we have made folowing decisions
* timeline for releases and content of first release (see below
RELEASE_PLAN)
* decided to use changes file (in doc) to keep track of important
changes between release, including:
major bug fixes (point to bugzilla), new functionality: update
change log with some explanation etc
* release plan and tasks will be kept in doc/RELEASE_PLAN.txt:
please edit file to indicate which task is taken and its status and
put any other tasks you wor on there!!!!
chat log is below.
thanks,
alek
ps. WSIF is part of IBM WAS 5 to read more about it and
http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=NetworkDeployment
in particular there is good WSIF documentation
http://publib7b.boulder.ibm.com/wasinfo1/en/info/ae/ae/twsf_ep.html
Note: pre1_2_0-patches branch is for some people in IBM we wanted to
support from a nightly build level
Current content of doc/RELEASE_PLAN.txt:
RELEASE PLAN for Apache WSIF 2.0 :
* alpha/baseline relelase (friday):
do not use this verin unless you are willing to report to us what is
missing :-)
just make it to have a reference point: test the process
* beta (next Friday)
work on documentation and doing necessary changes to get samples to run
document build process (maybe also tests)
* RC1 on Dec 18th (or more RCs if necessary) that is converted to final
relelase
* release often after 2.0 (including bug fixes and doc changes)
baseline would be 2.0.x then if we really have something significant
change the 0
TASKS:
* [Jeremy Sat 11a GMT (6am EST)] fixing problem with text files marked
by Eclipse as binary in CVS
* [owen] look on Forrest and having separate pages for WSIF inside Axis
* [nirmal + alek] samples and modularization
* [alek] split README.html into smaller pices and make it addressing two
communities: WSIF users and WSIF developers; README.html right now is
kind of mixed up
* [alek] simplify wsif.css
* [alek] check in JAR files that we know WSIF works OK with LICENSE and
README(and can be checked in)
* [jeremy] automatic generation of javadoc API
* get the link to the API javadoc off the home page working
* write/test sample that uses xmethods WSDL (DynamicInvoker + stub)
* make sure that all dependencies are documented
* test process to build binary and source distributions
* document how to run samples (step by step)
* document how to run tests (step by step)
* document how to build (step by step)
* work on developer guide that explains what different methods on
WSIFOperation are doing with exampels (such as
executeRequestResponseAsync ...)
* check (and edit if necessary) Javadoc on the API (org.apache.wsif)
* check (and edit if necessary) Javadoc on util and base (WSIFUtils and
org.apache.wsif.base)
TASKS (lower priority)
* check (and edit if necessary) Javadoc for AXIS provider
* check (and edit if necessary) Javadoc for Apache SOAP provider
* check (and edit if necessary) Javadoc for JMS/SOAP provider
* figure out how to make JMS sample to use as simple as possible maybe
with some locally started JMS serivce ...
* document how to run sample interacting using JMS
* figure out how to make JCA sample to use as simple as possible maybe
with some local JCA connetor...
* document how to run samle interacting using JCA
* document how to run samle interacting using EJB
* sample showing customisation of WSIF: how to write simple code to pick
your preferred port at runtime
LATER
* [nirmal, alek, Jeremy ???] for sampels it would be good to have
something pernament for EJB/JMS
using Open Source EJBs/JMS (such as JBoss), etc. can we do that? is
that feasible?
* [alek ...] LATER: modularisation
[09:59] <hughesj> hey guys
[09:59] <antElder> hi
[10:00] *** whitlock (~[EMAIL PROTECTED]) has joined
channel #wsif
[10:01] *** owenb (~[EMAIL PROTECTED]) has joined channel #wsif
[10:03] <hughesj> Not sure what's happened to Nirmal ... I'd like to
wait a few more minutes for him
[10:03] <antElder> ok alek was on earlier and said he'd be back at 10 so
wait for him also
[10:05] <alek_s> ok i am just back
[10:05] *** nirmal (~[EMAIL PROTECTED]) has joined
channel #wsif
[10:06] <nirmal> hello all
[10:06] <alek_s> hi nirmal
[10:06] <hughesj> hi
[10:06] <hughesj> ok shall we commence?
[10:06] <nirmal> ok
[10:06] <owenb> ok
[10:07] <alek_s> ok
[10:07] <hughesj> Are we agreed, the objective of this chat is to
determine what needs to be done for the first Apache release of WSIF
[10:07] <antElder> yes
[10:07] <owenb> yes
[10:07] <antElder> My opinon is that the priority is to get a release
out with what we have already. Just doing that now or soon is more
important than sorting out functionality and doc. But, I think it would
look a bit funny and not have much credability to go straight to a final
release without either a beta or RC. So I think we should have both a
beta1 and RC1 which gives us a little time to add stuff.
[10:08] <nirmal> I agree we don't need any more functionality, but we
need better user guides - this is the first release and we should make
it as easy as possible to set up and use
[10:09] <nirmal> so the priority would be for documentation, samples,
user guides
[10:09] <alek_s> samples (and unit tests) should work and be well tested
[10:09] <hughesj> we need a sample that just connects to a service (from
xmethods say)
[10:09] <antElder> should we decide on a timeframe 1st or just talk
about what is in the release?
[10:10] <dims> How about being able to build and use WSIF with just one
provider say Axis? Is this already in?
[10:10] <alek_s> let first decide what are releases (alpha, beta, rc,
final)?
[10:10] <hughesj> I would vote for beta, then RC1 followed quickly by final
[10:10] <antElder> no its not dims, its not so easy, may have to wait
till next release
[10:10] <dims> :(
[10:11] <antElder> you can use wsif with just the jars for the provider
you want
[10:11] <hughesj> plus I feel the benefit of WSIF would not be realised
in that release if only Axis was supported
[10:11] <nirmal> yes, with just one provider people won't see the value
[10:11] <alek_s> hi dims: i thinkyou are right that this is what is
expected of wsif
[10:11] <dims> last i checked i needed JMS for being able to use Axis
[10:11] <nirmal> so I think we need to make it easy to use - use public
services as samples as Jeremy suggested, so users don't have to deploy
things
[10:11] <hughesj> you should only need JMS to compile Axis provider
[10:12] <hughesj> not run it
[10:12] <dims> understood. thanks.
[10:12] <alek_s> aactually isnt just JMS API?
[10:12] <hughesj> yes
[10:13] <hughesj> we should modularise Axis provider to be two providers
perhaps (later release)
[10:13] <nirmal> Re. using public services for samples: we know we can
do this for SOAP, but what about other protocols - could we host a
public EJB and preconfigure the setup in the sample's WSDL?
[10:13] *** Signoff: hughesj (Read error: EOF from client)
[10:14] <alek_s> i think modularizatin is *very* important nboth during
compilation and deployment ...
[10:15] <nirmal> yes alek, important item for next release
[10:15] <antElder> jeremy is just trying to reconnect
[10:15] <owenb> I agree that modularization is a good thing, but I think
that it is more important for users to simply start trying out WSIF. If
that means building the lot, then so be it
[10:16] <nirmal> For now we have to live with providing step-by-step
instructions to make it easy to build...
[10:16] <alek_s> ... and we need to test those instructions not only by
ourselves :-)
[10:17] <nirmal> right, we can cajole folks on axis-dev to try it out
[10:18] <nirmal> re. hosting EJBs/JMS services, etc. can we do that? I'm
not a J2EE expert in any way, is that feasible?
[10:19] <alek_s> by hosting i thnk you also mean to monitor it so it is
actually working (and not taking too many resources)
[10:19] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[10:19] <hughesj> I'm back
[10:19] <antElder> Can I mention the timeframe again? There's buckets of
stuff we could do, i'd like a release this year, which is really less
than 2 weeks. Some of this doc would take a while to get right
[10:20] <nirmal> ok, let's get a list of outstanding items, then figure
out time needs?
[10:20] <alek_s> o what about this: we make an alpha release tomorrow
just to see what are problems in source and binary distribution (and we
have something to comapre agains)?
[10:20] <nirmal> hmmm...can we even build a dist with the current build
file?
[10:21] <hughesj> then that's probably the first task
[10:21] <hughesj> test the process
[10:21] <alek_s> on my list: documentatin including setup (CLASSPATH),
running samples, building WSIF inclusding setup
[10:21] <dims> +1 Release Early, Release Often.
[10:21] <hughesj> :)
[10:21] <antElder> the nightly build gets done so it must work?
[10:21] <hughesj> who uses the nightly build images?
[10:21] <alek_s> yes but is anybody using nightly build?
[10:21] <antElder> me
[10:22] <antElder> everyone?
[10:22] <antElder> what else would they use?
[10:22] <nirmal> +1 to alpha release tomorrow
[10:22] <hughesj> +1 for that
[10:22] <alek_s> +1 (so just we have something)
[10:23] <antElder> I don't know it makes it sound a bit flaky calling it
an alpha
[10:23] <alek_s> could somebody tell me what is pre1_2_0-patches branch?
[10:23] <antElder> couldn't we have a beta1?
[10:23] <alek_s> i tried using it last few days and i have run into
number of problems ...
[10:24] <nirmal> ant: then people might actually expect to set it up and
run it fairly easily
[10:24] <hughesj> hmmm ... then documentation included in RC1, minor
essential bug fixes in final
[10:24] <alek_s> so i think alpha is good meaning *untested*
[10:24] <hughesj> ok
[10:24] <antElder> its not really un tested people do use wsif
[10:24] <nirmal> I'd also like a beta with new samples (between the
alpha and RC)
[10:25] <hughesj> the pre1_2_0-patches branch is for some people in IBM
we wanted to support from a nightly build level
[10:25] <hughesj> any bug fixes we're doing for them are going into the
trunk as well
[10:25] <alek_s> i would like to propose to keep list of changes in HTML
file
[10:26] <hughesj> but they didn't want all the new changes we're doing
in the trunk
[10:26] <nirmal> +1 for change list (use alpha as baseline)
[10:26] <alek_s> looking on CVS commits log messages does not give any
overall picture of what are changes for ...
[10:26] <hughesj> it's a bit difficult to list a set of changes ...
changes since when?
[10:27] <hughesj> changes from alpha to beta I agree
[10:27] <hughesj> but to list the changes since we dropped the code
initially to Apache would be huge
[10:27] <nirmal> let's not go back now, let's start compiling change
list from alpha
[10:27] <alek_s> i a ok with it
[10:27] <alek_s> but please everybody who is commiting please keep this
file up to date:-)
[10:27] <antElder> so how long do you think btw alpha and beta1?
[10:28] <whitlock> would this change list document bug fixes and new
function, or just major items of new function?
[10:28] <whitlock> how would you match changes with the files they changed?
[10:28] <hughesj> ant: depends on how much doc we do ... lets list the
doc we do
[10:29] <whitlock> would I have to update the change list every time I
make a small bug fix?
[10:29] <hughesj> dims: what is the guidance for the axis change log?
[10:29] <whitlock> we should agree how we would use a change list
[10:29] <hughesj> ie how detailed, how often
[10:29] <antElder> i thing just major items, and another file for each
release referenceing every bugzilla fixed
[10:30] <nirmal> I vote to use your discretion when updating change list
- anything that is not absolutely minor (major bug fixes, new stuff
etc.) sould go in
[10:30] <hughesj> +1 for that
[10:30] <alek_s> i think that kind of chnages to write is determined by
how the file shoul dbe used
[10:30] <owenb> Something else for the pot: probably not in the alpha or
beta phase, but maybe for the release, we should create "proper" WSIF
pages on the xml.apache.org site and if possible have a link to them
from xml.apache.org/wsif
[10:30] <whitlock> changes due to bugs would be better documented in the
bug text?
[10:31] <alek_s> i thin if bug is fixed it shoul dbe in chnges with
hyperlink to bugzilla bug report
[10:32] <alek_s> anybody who downloaded some relelase of WSIF and is
thinking about geetting the laatest verion should look on chnages file
and *quickly* know what happened!
[10:32] <hughesj> agreed
[10:32] <nirmal> ok, major bug fixes: update change log, point to
bugzilla; new functionality: update change log with some explanation;
New change logs for each version
[10:32] *** Signoff: hughesj (Read error: EOF from client)
[10:33] <alek_s> so i think we have some picture what to do for this
alpha relelase and next beta/rc
[10:34] <alek_s> is Jeremy around?
[10:34] <antElder> could you summerise it?
[10:34] <alek_s> ok i was just writing it down
[10:34] <antElder> he's dialed in from home and keeps getting disconnected
[10:34] <alek_s> release: alpah (friday): just make it to have a
reference point
[10:35] <alek_s> release beta/rc (next week): work on documentation and
doing necessary chnages to get samples to run and document build
process (maybe also tests)
[10:36] <antElder> I'd still prefer to go straight to beta1, whats going
to happen in the few days till next week?
[10:36] <alek_s> look on having separate pages for WSIF inside Axis
[10:36] <owenb> I think the pages for WSIF should not be inside Axis at all
[10:37] <nirmal> ant: alpha will be a baseline, just something to
compare against
[10:38] <whitlock> I've been writing some documentation on the bits of
WSIF that I know about: jms bindings, trace and mime attachments. Do you
like it? do you hate it? is that the kind of thing that's needed?
[10:38] <nirmal> I tried to bring up the issue of a separate WSIF home
with Sam ruby, will ping him again on that
[10:39] <alek_s> yes - more testing :-)
[10:39] <nirmal> Any documentation is good, the litmus test is to see
whether the naive user can understand and use it
[10:39] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[10:40] <owenb> I think we should steal a lead on most of the other
Apache projects and try to use the new look and feel for our web pages
i.e. the one based on using Forrest
[10:40] <alek_s> as of documentation: could we make default CSS to be
less flashy and more black and white and easier to read ...
[10:40] <nirmal> I don't know what forrest is
[10:40] <owenb> not sure how simple this will be but it makes the pages
look much more professional
[10:41] <owenb> Forrest is a tool for taking xml files that define the
contents of a web site, and building the HTML from it
[10:41] <alek_s> it is defintely worth looking on
[10:42] <alek_s> but i have doubts if we can get "forrested" and have
relelase ...
[10:42] <owenb> To quote the Forrest web pages: Forrest is an XML
standards-oriented project documentation framework based on Apache
Cocoon, providing XSLT stylesheets and schemas, images and other
resources. Forrest uses these to render the XML source content into a
website via command-line, robot, or a dynamic web application.
[10:43] <nirmal> I don't mind using it if somebody (Owen? ;-)) does the
owrk of converting what we have to use forrest
[10:43] <owenb> Yes, maybe time is against us but I think we should
investigate what's involved. I volunteer
[10:43] <hughesj> Owen: would the docs within the WSIF package be
forrested to
[10:43] <alek_s> before any conversion i would liek to know what is
required to write documentation
[10:43] <alek_s> right now i can use any HTML editor ...
[10:44] <hughesj> ok agreed ... content is king for next friday
[10:44] <owenb> I think it's best that people just continue writing HTML
for now until we know what's involved in using Forrest
[10:44] <owenb> Better to get the information out there
[10:44] <nirmal> I volunteer to work on samples - writing them, building
them, and documentation for running them
[10:44] <alek_s> will anybody protest if i simplify wsif.css (less
colors bigger fonts)?
[10:45] <antElder> next friday?
[10:45] <nirmal> I hope to get samples done by next Friday, yes - so
let's aim for next Friday for beta
[10:45] <alek_s> also we need to break initial README.html into smaller
documents so README.html is just pointer to relelvant documentaion
[10:45] <owenb> Alek: no that's fine. Lots of colours and fonts looks
very bad
[10:46] <antElder> the 14th?
[10:46] <antElder> sorry 13th
[10:46] <nirmal> yes, remember we need to address two communities: WSIF
users and WSIF developers; README.html right now is kind of mixed up
[10:46] <alek_s> Firday 13th :-)
[10:46] <hughesj> where will we declare our alpha tomorrow
[10:47] <nirmal> Ant: yes I'll try to do samples by Fri the 13th
[10:47] <antElder> lets not declare it to loudly
[10:47] <hughesj> on the Axis page or on the WSIF page linked from the
Axis page
[10:47] <alek_s> ok i wil chnage README.html to have two major parts:
users and developers
[10:47] <nirmal> Ant would more or less prefer not having anything to do
with the existence of an alpha! ;-)
[10:48] <antElder> so beta1 on the 13th, would we intend a beta2? or
when would we anticapate a rc1?
[10:48] <nirmal> But I vote for low key alpha - maybe just announce on
axis-dev that it is an untested baseline release
[10:48] <antElder> +1
[10:48] <owenb> +1
[10:49] <nirmal> beta2, rc2, etc. may be released depdending on how
things go...
[10:49] <alek_s> +!
[10:49] <nirmal> But let's try beta1 for 13 Dec, rc1 for 18 Dec, WSIF
1.2 for 20 Dec?
[10:49] <alek_s> +1 for beta
[10:49] <hughesj> so what version number shall we use ... I think 2.0
because it is quite a major change from the days of 1.x com.ibm.wsif
[10:50] <antElder> surely we should have a vague plan? rc2's only if we
get something really wrong in rc1 isn't it?
[10:50] <nirmal> oh yes, 2.0 is much better
[10:50] <hughesj> plus that follows a precedence set by SOAP
[10:50] <hughesj> which went 2.0 for its first release on being donated
by IBM
[10:50] <nirmal> +1 for 2.0
[10:50] <antElder> +1
[10:50] <alek_s> +1 to 2.0
[10:50] <owenb> +1
[10:50] *** Signoff: hughesj (Read error: EOF from client)
[10:50] <nirmal> what are guidelines for releasing RCs?
[10:51] <antElder> did axis have an rc2?
[10:51] <antElder> i thought not
[10:51] <nirmal> I think we release RC1 on 18 Dec, then test
independently and if we encounter problems fix them and release a new RC
every day
[10:51] <alek_s> i think that RC is like final version - you just make
this last check ...
[10:52] <nirmal> i.e. if we don't encounter any problems there will be
no more than the first RC
[10:52] <antElder> I agree, get as many as we can to test rc1 then final
a couple of days later
[10:52] <alek_s> so i think we are all on the same page
[10:52] <antElder> who's working over xmas?
[10:53] <alek_s> i will be areound
[10:53] <nirmal> But I would like the last RC to be identical to the
final, barring non-functional changes
[10:53] <antElder> 18th is near the near the xmax break
[10:53] <nirmal> I'll be working until the 20th
[10:54] <alek_s> i agree final RCx == final release
[10:54] <alek_s> i think we have now all developer here so i would like
to ask this
[10:54] <alek_s> can we get those text files that were checked in as
binary converted back to text please :-)
[10:55] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[10:55] <alek_s> that requires that everybody either checks in any
pending versions or make copy of their repository
[10:56] <alek_s> hi Jeromy: i would like to talk about those text files
that were ,arked by Eclipse as binary ...
[10:56] <antElder> another part of that, the apache coding guidelines
say no tabs
[10:56] <antElder> could we change all the tabs to spaces at the same time/
[10:57] <hughesj> hi again
[10:57] <alek_s> hi Jeromy: i would like to talk about those text files
that were ,arked by Eclipse as binary ...
[10:57] <hughesj> yes ... I tried to change one back using eclipse
yesterday but it didn't work
[10:57] <alek_s> and about using *only* spaces
[10:57] <whitlock> when I create a new text file, how do I ask eclipse
to create it as text not binary?
[10:57] <alek_s> after you do chnage yopu need to refresh repository
(cvs update -d P -A)
[10:57] <alek_s> it should be createdas text
[10:58] <hughesj> alek do you use eclipse?
[10:58] <alek_s> unless you chnage default mode to binary (from FAQ doc
i have sent it says that problem is only if you move from older Eclipse
verion)
[10:58] <alek_s> i may have ot use eclipse :-)
[10:58] <hughesj> I really hope not
[10:58] <hughesj> do if you like :-)
[10:58] <nirmal> I don't - for WSIF anyway
[10:58] <alek_s> but i like more code guide (incredible incremmental
compiler and simplicity!)
[10:59] <nirmal> But I may in the future
[10:59] <hughesj> I volunteer to change the files to text
[10:59] <hughesj> but this will probably mean everyone needs to check
out all their files again
[10:59] <alek_s> OK so if anybody has files that are not in repository
[10:59] <owenb> Mark: You can change the file settings under the
Window->Preferences->Team->File Content
[10:59] <antElder> I'd like some notice!
[10:59] <alek_s> PLEASE make a copy of them before doing any cvs
operations and check out fresh xml-axis-wsif from CVS to see if all is ok
[10:59] <antElder> could you leave the change for a day or 2
[11:00] <alek_s> if possible make it today
[11:00] <antElder> no
[11:00] <alek_s> unless this chnaged is made i do not want to modify any
files in CVS ....
[11:00] <antElder> I've lots of pending changes it will be hard to see
them once its happened
[11:00] <hughesj> who's working over the weekend ... if no-one I'll do
it then
[11:00] <alek_s> i work on weekends ...
[11:01] <whitlock> please delay until at least this evening - weekend
would be better
[11:01] <alek_s> this change should be harmless unless your local files
are in wrong end of line encoding ...
[11:02] <alek_s> anyway if you keep copy of files you can always check
out from CVS current files and then copy over your files and use CVS to
merge all differences!!!
[11:02] <antElder> when we did the test yesterday of testrunner it
flagged the file as all changed even thought I think I had it as text to
start with
[11:02] <antElder> its really hard to get that right
[11:03] <alek_s> CVS handles end of line coonversions automatically
[11:03] <antElder> that was the one of the problems with Noramans JMS work
[11:03] <hughesj> once I've change the status to text for all relevant
files that won't be a problem
[11:03] <alek_s> if you are on windows files will be CR/LF but in
repository they will be only LF
[11:03] <antElder> but our local copies don't compare anymore, atleast
thats what the test yesterday showed
[11:04] <antElder> anyway if we can leave it till the weekend?
[11:04] <alek_s> just use some free utility to conver text files to
windows end-of-line endings
[11:04] <hughesj> ant: you'll need to 'throw away' your eclipse project
containing wsif and re-check out the whole project from cvs
[11:04] <antElder> or can we leave it til lthe weekend?
[11:04] <hughesj> then do a diff between old project and new project
[11:05] <hughesj> that has to be the cleanest way otherwise eclipse may
get mixed up
[11:05] <antElder> ok but before I throw away my eclipse project I'd
like time to check stuff in
[11:05] <alek_s> based on my experience CVS can merge and diff files
very effiently
[11:06] <antElder> well if you all vote for now I'll shutup
[11:06] <alek_s> so you can copy over files with your modifications
(make sure EOL is correct) and when you do cvs update it is merged
[11:06] <hughesj> alek: I think most of the problems are with eclipse
and you can't just go to the eclipse directory containing wsif project
and use the cvs command line
[11:06] <alek_s> Ant: just let me know when you will be doing it and i
will try to help you
[11:07] <alek_s> actually i am pretty sure you can ...
[11:07] <alek_s> anyway i willdownload the latest eclipse
[11:07] <antElder> if we wait til the weekend I'll have check in my code
and wont need help :)
[11:08] <alek_s> ok
[11:08] <antElder> +1 for the weekend, can we move along?
[11:08] <alek_s> let me know when you have it done
[11:08] <hughesj> how about I do the change Saturday at 11am GMT
[11:08] <owenb> +1 for Saturday 11am GMT change
[11:08] <alek_s> i will try to be on IRC in case if there are problems
(it should be 6 pm EST)
[11:09] <hughesj> 6am EST
[11:09] <alek_s> +1 on Sar 6pm EST
[11:09] <alek_s> sorry
[11:09] <alek_s> 6am that may be too early for me :-)
[11:09] <antElder> so there's 7 work days till the rc1 on the 18th by
which time we should have all we wanted done
[11:09] <hughesj> that's why I chose that time :)
[11:10] <hughesj> Alek are you still ok to be release mgr
[11:10] <alek_s> yes
[11:10] <nirmal> ok, so shall we announce what each of us will work on?
[11:10] <alek_s> it will be great to see WSIF released :-)
[11:10] <antElder> can we be a bit more specific about al lthe tasks 1st?
[11:11] <nirmal> yes, Alek, can you write down what needs to be done,
then we willvolunteer for various tasks?
[11:11] <alek_s> i am writing it down now
[11:11] <alek_s> however we need to be more precise when we say get
samples to work :-)
[11:11] *** Signoff: hughesj (Read error: EOF from client)
[11:11] <antElder> yes I agree
[11:12] <antElder> post the list now and we can refine each point
[11:12] <nirmal> yes, good idea
[11:12] <alek_s> TASKS:
[11:12] <alek_s> * [Ant Sat 11a GMT (6am EST)] fixing problem with text
files marked by Eclipse as binary in CVS
[11:12] <alek_s> * [alek] look on having separate pages for WSIF inside
Axis
[11:12] <alek_s> * [alek] for sampe sit would be good to have something
pernament for EJB/JMS
[11:12] <alek_s> hosting EJBs/JMS services, etc. can we do that?
I'm not a J2EE expert in any way, is that feasible?
[11:12] <alek_s> * [alek ...] LATER: modularisation
[11:12] <alek_s> * [nirmal + alek] samples and modularization
[11:12] <alek_s> * write/test sample that uses xmethods WSDL
(DynamicInvoker + stub)
[11:12] <alek_s> * ???
[11:13] <antElder> didn't Jeremy volonteer for 1
[11:13] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[11:14] <alek_s> oops
[11:14] <alek_s> * [owen] look on Forrest and having separate pages for
WSIF inside Axis
[11:14] <nirmal> [jeremy] fixing problems with test files
[11:14] <nirmal> er... test should be text
[11:14] <owenb> yes but outside of Axis
[11:15] <alek_s> * [Jeremy Sat 11a GMT (6am EST)] fixing problem with
text files marked by Eclipse as binary in CVS
[11:15] <alek_s> OK
[11:15] <alek_s> now it should be right:
[11:16] <hughesj> to do the hosting of EJB service I think we need to
use an opensource J2EE app server
[11:16] <hughesj> JBoss?
[11:16] <nirmal> Alek could oyu add organizing, documenting unit tests -
how to run them?
[11:16] <antElder> is JBoss feasable in 7 days?
[11:17] <hughesj> however since we're a 'client side' framework perhaps
we could put off testing with JBoss
[11:17] <hughesj> and say 'use your favourite J2EE app server;
[11:17] <alek_s> * document how to run samples (step by step)
[11:17] <alek_s> * document how to run tests (step by step)
[11:17] <alek_s> * document how to build (step by step)
[11:18] <alek_s> i will add JBoss to *later* category
[11:18] <nirmal> If the setup is as simple as dropping an ear file
somewhere it woul dbe ok, but it isn't - users will have to modify the
WSDL to point to the correct initial context, etc. - not very simple
[11:18] <alek_s> and we have it hosted somewhere
[11:19] <hughesj> just what I was thinking
[11:19] <alek_s> it would be the best on an apache server ...
[11:19] <hughesj> on an apache server
[11:19] <hughesj> :)
[11:19] <alek_s> :-)
[11:19] <nirmal> yes, if we have it hosted, we can make sure the WSDL is
correct so it takes no effort to use the EJB binding...
[11:19] <alek_s> * test process to build binary and source distributions
[11:20] <antElder> will it be possible to get the link to the API
javadoc off the home page working?
[11:21] <alek_s> it should if we have generated javadoc somewhere inside
web server
[11:21] <alek_s> * make sure that all dependencies are documented
[11:21] <alek_s> * [alek] check in JAR files that we know WSIF works OK
with LICENSE and README(and can be checked in)
[11:21] <alek_s> * get the link to the API javadoc off the home page
working
[11:21] <nirmal> certainly should be, we need to run javadoc on the
nightly build automatically and set that up
[11:21] <hughesj> Alek, I have a machine in IBM which builds bindist and
srcdist everyday
[11:21] <hughesj> that works well
[11:21] <alek_s> so it could also do this?
[11:22] <alek_s> possible taks
[11:22] <alek_s> * [jeremy] automatic generation of javadoc API
[11:22] <hughesj> I guess we need to make the GUMP machine is doing this
[11:22] <antElder> how about writing some Javadoc on the API
[11:23] <alek_s> and maybe also some kind of developer guide that
explains what different methods on WSIFOperation are doing with exampels
(such as executeRequestResponseAsync ...)
[11:24] <antElder> are the samples going to include JMS?
[11:24] <alek_s> more tasks
[11:24] <alek_s> * writing some Javadoc on the API
[11:24] <alek_s> * work on developer guide that explains what different
methods on WSIFOperation are doing with exampels (such as
executeRequestResponseAsync ...)
[11:25] <alek_s> i have not yet meanaged to run JMS sampels ...
[11:25] <nirmal> ant: yes I was thinking that one simple would have
*all* supported bindings - the others will hopefully use publicly
accessible SOAP/EJB service and local java services so they will require
no setup...
[11:25] <antElder> JMS is about as hard as EJB
[11:26] <nirmal> demonstrating JCA would be good too...what else do we
support?
[11:26] *** Signoff: hughesj (Read error: EOF from client)
[11:27] <antElder> apache soap, axis soap, soap/jms, axis/jms, java, ejb
[11:27] <antElder> JCA not really
[11:27] <alek_s> * document how to run sample interacting using JMS
[11:27] <alek_s> * document how to run samle interacting using JCA
[11:27] <alek_s> * document how to run samle interacting using JCA
[11:27] <alek_s> * document how to run samle interacting using EJB
[11:28] <nirmal> I also wanted a sample showing customisation of WSIF:
how to write simple code to pick your preferred port at runtime
[11:29] <alek_s> i think it was a very neat example :-)
[11:30] <nirmal> yes, very easy to do too
[11:30] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[11:30] <hughesj> sorry .. back again
[11:31] <alek_s> hi Jeremy :-)
[11:31] <antElder> so thats a lot of doc to write
[11:31] <hughesj> lets be realistic
[11:31] <alek_s> i will check into CVS list of tasks so anybody can edit
it and mark what task is taken (and finished)
[11:31] <hughesj> I would also like to 'release often' after 2.0
[11:32] <hughesj> like 2.0.1 after a month
[11:32] <antElder> are we running out of time? can we keep discussing
the list now?
[11:32] <hughesj> even if it is just doc change
[11:32] <hughesj> I have a proposal for some of the docs
[11:32] <hughesj> WAS 5.0 which was released a week ago includes WSIF
[11:32] <nirmal> would be good to have a stable release up for a long time
[11:32] <hughesj> and some documentation written in Hursley
[11:33] <hughesj> I will investigate if we can use that documentation
(or a form of it)
[11:33] <alek_s> that would be great!
[11:33] <hughesj> the guy who wrote it is back in on Monday
[11:33] <alek_s> +1 to release often
[11:33] <antElder> its available on the net now if the others want to
look in the meantime
[11:33] <hughesj> oh cool ...I couldn't find it just now
[11:34] <alek_s> i thin we could include link to it in our documentation?
[11:34] <hughesj> you got a URL
[11:34] <hughesj> alek: I'd prefer taking the contents and created a
self contained WSIF package
[11:34] <hughesj> if we can
[11:34] <hughesj> then WSIF users don't think they rely on IBM for
documentation
[11:34] <hughesj> :)
[11:35] <nirmal> I'm not so sure about releasing often - that's ok, as
long as we eventually have a stable release - and no more releases for a
long (few months) time
[11:35] <hughesj> 2.0.1 would be bug fixes only
[11:35] <alek_s> quick relelase are OK as long as there is baseline
known 'stable' release
[11:35] <hughesj> and doc changes
[11:35] <hughesj> baseline would be 2.0.x
[11:36] <hughesj> then if we really have something significant change the 0
[11:36] <alek_s> ok with me
[11:36] <nirmal> ok
[11:36] <antElder> (Link:
http://www-3.ibm.com/software/webservers/appserv/library/index.html)http://www-3.ibm.com/software/webservers/appserv/library/index.html
[11:37] <hughesj> I estimate 2.y.x where x increments monthly(ish) and y
increments every 4 to 6 months
[11:38] <hughesj> I think we need to define what changes in the version
number when an API changes
[11:38] <hughesj> ant: hey cool .... din't know it was up
[11:39] <hughesj> anyway enough about future releases for now
[11:39] <nirmal> ok, so we have a task list...everyone have an idea of
what they will be working on?
[11:40] <hughesj> Alek, could you post the list to axis-dev
[11:40] <hughesj> to summarise
[11:40] <hughesj> our plan
[11:41] <alek_s> i wil post it including chat log (if it is OK with
everybody)
[11:41] <hughesj> fine
[11:41] <nirmal> ok
[11:41] <owenb> ok
[11:42] <hughesj> are we done?
[11:43] <alek_s> i think so
[11:43] <alek_s> next chat next thursday?
[11:43] <antElder> (Link:
http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=NetworkDeployment)http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=NetworkDeployment
[11:43] <hughesj> sounds good
[11:43] <antElder> is diectly to the info centre then then Appilications
- web services - enabling wsif
[11:44] <nirmal> next chat same time next week?
[11:44] <hughesj> I could hang out here all the time while I'm at work
[11:44] <antElder> shouldn't we all for the next week or 2?
[11:44] <hughesj> lets make sure we're all here same time next week
though and anyone who wants to hang out on #wsif can
[11:45] <nirmal> ok, I could do the same...but I think we need to have
an announced chat prior to beta release just to make sure we know where
we are and agree on the release
[11:45] <hughesj> ok
[11:45] <alek_s> ok
[11:45] *** Signoff: hughesj (Read error: EOF from client)
[11:46] <alek_s> i will be around this channel often
[11:46] <antElder> so I'm not really clear if I have a task
[11:48] *** hughesj (~[EMAIL PROTECTED]) has joined channel #wsif
[11:49] <hughesj> Alek: I think there are some people with no tasks
[11:49] <antElder> who is still here?
[11:49] <hughesj> can you dump the list into irc once more
[11:49] <alek_s> ok dumping now
[11:50] <alek_s> TASKS:
[11:50] <alek_s> * [Jeremy Sat 11a GMT (6am EST)] fixing problem with
text files marked by Eclipse as binary in CVS
[11:50] <alek_s> * [owen] look on Forrest and having separate pages for
WSIF inside Axis
[11:50] <alek_s> * [nirmal + alek] samples and modularization
[11:50] <alek_s> * write/test sample that uses xmethods WSDL
(DynamicInvoker + stub)
[11:50] <alek_s> * [alek] split README.html into smaller pices and make
it addressing two communities: WSIF users and WSIF developers;
README.html right now is kind of mixed up
[11:50] <alek_s> * [alek] simplify wsif.css
[11:50] <alek_s> * [alek] check in JAR files that we know WSIF works OK
with LICENSE and README(and can be checked in)
[11:50] <alek_s> * [jeremy] automatic generation of javadoc API
[11:50] <alek_s> * get the link to the API javadoc off the home page
working
[11:50] <alek_s> * make sure that all dependencies are documented
[11:50] <alek_s> * test process to build binary and source distributions
[11:50] <alek_s> * document how to run samples (step by step)
[11:50] <alek_s> * document how to run tests (step by step)
[11:50] <alek_s> * document how to build (step by step)
[11:50] <alek_s> * writing some Javadoc on the API
[11:50] <alek_s> * work on developer guide that explains what different
methods on WSIFOperation are doing with exampels (such as
executeRequestResponseAsync ...)
[11:50] <alek_s> * document how to run sample interacting using JMS
[11:50] <alek_s> * document how to run samle interacting using JCA
[11:50] <alek_s> * document how to run samle interacting using EJB
[11:50] <alek_s> * sample showing customisation of WSIF: how to write
simple code to pick your preferred port at runtime
[11:50] <alek_s> also
[11:50] <alek_s> i am adding it now to CVS
[11:51] <alek_s> i think all taks are important
[11:51] <alek_s> so it would be good to see that all are take care of
(and everybody is sharing similar task 'load' :-))
[11:52] <antElder> jms, ejb, and jca are problematic
[11:52] <antElder> will the JCA people help?
[11:52] <nirmal> yes, we need to figure out how to host them publicly
and if not how to simplify use of those samples...
[11:52] <antElder> didn't notice any of them here
[11:53] <antElder> some of these are to big for 1 person
[11:53] <alek_s> Ant: that could be task too (figure out how to make JCA
sample to use as simple as possible maybe with some local JCA connetor...)
[11:54] <alek_s> if they are too big please edit file in CVS and split
ti inot smaller task
[11:54] <antElder> lets take javadoc, I think that would be beter
spliting all the classes up amoung a few people
[11:54] <alek_s> and if you think they can be done now move them to
LATER category
[11:55] <nirmal> ok I have to go away for some time - I'll work on
writing a list of samples, what we need for each - what code,
documentation, etc.
[11:55] <alek_s> correction: and if you think they can *not* be done now
move them to LATER category
[11:55] <nirmal> will check in something today
[11:55] <nirmal> bye for now
[11:55] <alek_s> i agree that javadoc task should be split
[11:55] <hughesj> bye nirmal
[11:55] <hughesj> thanks
[11:55] <alek_s> simply when you start working on javadoc for say Axis
jjust add such task :-)
[11:55] <alek_s> bye
[11:56] <hughesj> is there anyway we could pioritize the docs
[11:56] <antElder> I think there's a danger we wont have much Javadoc
get done like that
[11:57] <hughesj> we don't need javadoc for Axis provider ... as this
would only be for WSIF developers not WSIF users
[11:57] <owenb> In terms of Javadoc, the key APIs should be the priority
[11:57] <hughesj> right ... once org.apache.wsif has been doc'd lets release
[11:57] <antElder> ok, maybe there's not much to do then
[11:57] <hughesj> org.apache.wsif.<other packages> aren't so imporant
[11:57] <owenb> so the org.apache.wsif and possible org.apache.wsif.base
classes
[11:57] <hughesj> maybe WSIFUtils
[11:58] <alek_s> i will add to CVS seaprate javadoc taks for API and
packages
[11:58] <hughesj> so lets split this item right away into these things
[12:00] *** Signoff: whitlock (Quit)
[12:01] *** Signoff: hughesj (Read error: EOF from client)
--
The ancestor of every action is a thought. - Ralph Waldo Emerson
