[
10:58am
]
balunasj
:
FYI - agenda posted here for the meeting today - http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2-15-2010
[
11:00am
]
Marauder joined the chat room.
[
11:01am
]
balunasj
:
We've got a lot to get through, and we have enough people to get started
[
11:01am
]
pyaschenko joined the chat room.
[
11:01am
]
pyaschenko
:
Hi All
[
11:01am
]
Marauder
:
Hello all!
[
11:01am
]
Marauder is now known as ilya_shaikovsky.
[
11:01am
]
balunasj
:
Hi all
[
11:02am
]
balunasj
:
First lets take a loo at items that are still in investigation with 3.3.3.CR1
[
11:02am
]
abelevich
:
hi
[
11:02am
]
balunasj
:
https://jira.jboss.org/jira/browse/RF/fixforversion/12313806
[
11:02am
]
balunasj
:
amarkhel: can you update us on the status of these 4 issues.
[
11:03am
]
balunasj
:
please keep in mind that unless showstoppers at this point we will shift to future or GA
[
11:03am
]
amarkhel
:
balunasj: I am in process right now
[
11:04am
]
balunasj
:
amarkhel: nbelaevski ilya_shaikovsky : are there any here that look like they could be show stoppers - from a high level
[
11:05am
]
prabhat
:
balunasj: RF-8347 seems non blocker to me
[
11:05am
]
prabhat
:
https://jira.jboss.org/jira/browse/RF-8347
[
11:06am
]
prabhat
:
balunasj: https://jira.jboss.org/jira/browse/RF-8368 is a concern
[
11:06am
]
balunasj
:
Agree on RF-8347
[
11:07am
]
prabhat
:
balunasj: https://jira.jboss.org/jira/browse/RF-8357 is a concern as well
[
11:08am
]
balunasj
:
RF-8368 - does not seem like a show stopper.  amarkhel : were you able to determin ( when you originally resolved ) if this was a regression?
[
11:09am
]
balunasj
:
RF-8371 - -seems like a demo issue to me and not signs of a bigger problem.
[
11:09am
]
amarkhel
:
balunasj: no it isn't regression and should be fixed. I t is really strange(I am check it right now)
[
11:09am
]
balunasj
:
right now we have 2 issues in GA.
[
11:09am
]
amarkhel
:
balunasj: I am talking about RF-8368
[
11:10am
]
balunasj
:
I do not want to hold off CR1 anylonger - imo.
[
11:10am
]
balunasj
:
I think we should move RF-8368 to GA.  Hopefully it is a small fix since it was resolved before.
[
11:10am
]
balunasj
:
amarkhel: true/false?
[
11:11am
]
amarkhel
:
true
[
11:11am
]
prabhat
:
balunasj: just have simple roll call on 3 issues..you know me, I am always up for more focus on 4.0
[
11:11am
]
amarkhel
:
I am agree
[
11:11am
]
nbelaevski
:
I cannot reproduce RF-8347 - is it a Linux-only thing?
[
11:12am
]
ilya_shaikovsky
:
https://jira.jboss.org/jira/browse/RF-8371 - also just minor demo issue (which present since 3.2.x if I'm not mistaken)
[
11:12am
]
balunasj
:
RF-8368 --> GA
[
11:13am
]
nbelaevski
:
balunasj: agree for RF-8368
[
11:13am
]
balunasj
:
RF-8347 --> future - not critical imo to put into GA release.
[
11:13am
]
ppitonak
:
nbelaevski: it appeared in JSF2 version of demo
[
11:13am
]
nbelaevski
:
ok, I see
[
11:14am
]
nbelaevski
:
balunasj: we can take a look at RF-8347 for GA
[
11:14am
]
nbelaevski
:
balunasj: very quick look
[
11:14am
]
amarkhel
:
balunasj: RF-8368 not reproduced on my side, it should be fixed... strange situation
[
11:14am
]
balunasj
:
nbelaevski: ok + if minor risk
[
11:14am
]
ppitonak
:
nbelaevski: balunasj RF-8347 appeared in all trees in demo
[
11:15am
]
balunasj
:
ilya_shaikovsky: RF-8371 - agree minor, and likely demo - lets move too future
[
11:15am
]
ilya_shaikovsky
:
balunasj, agree\
[
11:15am
]
nbelaevski
:
agree
[
11:15am
]
lfryc
:
amarkhel: RF-8368 - I will recheck that I was used 3.3.3.CR1 right binaries
[
11:15am
]
balunasj
:
amarkhel: what about RF-8357
[
11:16am
]
balunasj
:
it is just a simple math issue?
[
11:16am
]
balunasj
:
it was resolved so likely a minor tweek?
[
11:16am
]
amarkhel
:
balunasj: It is minor fix and related only to demo
[
11:16am
]
amarkhel
:
balunasj: Time to fix - about 15-20 minutes
[
11:16am
]
balunasj
:
amarkhel: oh - it is not part of component?
[
11:17am
]
amarkhel
:
balunasj: yes it is error in custom datascroller class
[
11:18am
]
balunasj
:
ok but lets make it "minor"
[
11:18am
]
amarkhel
:
lfryc:ok
[
11:18am
]
amarkhel
:
balunasj: agree
[
11:19am
]
balunasj
:
so these three issues are shifting to GA
[
11:19am
]
balunasj
:
all are low risk, with minor fixes from what it sounds like
[
11:19am
]
balunasj
:
done
[
11:20am
]
balunasj
:
amarkhel: if any of those start to effect many files, and/or become risky let me know.
[
11:20am
]
amarkhel
:
balunasj: ok
[
11:20am
]
balunasj
:
anything going into the GA release needs to be reviewed carefully.
[
11:21am
]
balunasj
:
Lets move on to QE status with the CR1 testing.
[
11:21am
]
balunasj
:
prabhat: lfryc ppitonak :...
[
11:21am
]
prabhat
:
balunasj: everything else looks good
[
11:22am
]
balunasj
:
testing is complete?  we can start uploads and verifications?
[
11:22am
]
lfryc
:
balunasj: I also tried new binaries inside Embjopr and it again works fine for me (no other testing was done)
[
11:22am
]
prabhat
:
balunasj: i meant is that we have not found any other issues..except 4 that was reopened
[
11:23am
]
balunasj
:
lfryc: they said that we were in good shape with the last release so we should be good to go with that.
[
11:23am
]
balunasj
:
prabhat: ok
[
11:23am
]
balunasj
:
prabhat: estimate for testing complete for CR1?
[
11:24am
]
prabhat
:
balunasj: i am hoping to wrap testing tomorrow
[
11:24am
]
prabhat
:
lfryc: ppitonak agree? ^
[
11:25am
]
lfryc
:
prabhat: I agree
[
11:25am
]
balunasj
:
ok good
[
11:25am
]
balunasj
:
given that and the timing - I think that we should begin the upload process now with the bits that you have been testing.
[
11:26am
]
ppitonak
:
ppitonak: I agree
[
11:26am
]
balunasj
:
It would need to be a serious issue to hold up CR1 at this point
[
11:26am
]
lfryc
:
amarkhel: I reproduced the RF-8368 on 3.3.3.CR1 with samples I attached and it's definitely right binaries
[
11:27am
]
balunasj
:
Konstantin1: can you upload the correct bits to the download site, and verify the binaries in the mvn repo are all there?
[
11:27am
]
balunasj
:
Konstantin1: i.e. https://jira.jboss.org/jira/browse/RFPL-377
[
11:27am
]
balunasj
:
all: looking at https://jira.jboss.org/jira/browse/RFPL-372
[
11:28am
]
balunasj
:
ppitonak: amarkhel : did you guys ever get together to verify memory testing?
[
11:28am
]
ppitonak
:
balunasj: working on it right now
[
11:28am
]
balunasj
:
ppitonak: ok good
[
11:29am
]
ppitonak
:
nbelaevski: what about https://jira.jboss.org/jira/browse/RF-8216
[
11:30am
]
nbelaevski
:
how about testing this with application undeployment?
[
11:30am
]
prabhat
:
ppitonak: i replied to that
[
11:31am
]
prabhat
:
ppitonak: i think with JConsole and few deploy/undeploy, you should be able to verify
[
11:31am
]
nbelaevski
:
i.e. you deploy application, navigate to view (it's enough for tag handler to work), then do undeploy & jhat dump
[
11:31am
]
nbelaevski
:
then search for class names in jhat dump
[
11:32am
]
ppitonak
:
nbelaevski: prabhat ok
[
11:33am
]
balunasj
:
nbelaevski: good appoach
[
11:33am
]
alexsmirnov joined the chat room.
[
11:34am
]
prabhat
:
on another note, I tested more this time with portal setup
[
11:34am
]
balunasj
:
alexsmirnov: just in time - any updates on portal items for 3.3.3? 
[
11:34am
]
prabhat
:
alexsmirnov: the only issue I had is known issue and I wanted to verify with you
[
11:35am
]
balunasj
:
Konstantin1: ping regarding upload of artifacts?
[
11:36am
]
prabhat
:
alexsmirnov: selectOneRadioButton tied to a boolean value in managed bean. You get IllegalArgument exception. But it only happens with AS 4.2.3 but not with AF 4.1
[
11:36am
]
prabhat
:
ooops not with AS 5.1.0.GA
[
11:36am
]
Konstantin1
:
balunasj: I will start to upload in 5 min.
[
11:37am
]
balunasj
:
Konstantin1: just wanted to now you heard, and had on plate   But that is what I call service
[
11:37am
]
alexsmirnov
:
Hi! There was network update in concord office, so I spent some time to restore connection.
[
11:37am
]
balunasj
:
alexsmirnov: np
[
11:39am
]
alexsmirnov
:
balunasj: I do not get any updates that need for portlet bridge in 3.3.3, but JBDS-4500 would need a little update to replace getResourceAsStream bu getResource call.
[
11:40am
]
alexsmirnov
:
I'm going to test that today. If that fix work, I'll submit changes to branch.
[
11:40am
]
balunasj
:
alexsmirnov: was the solution to work around the AS changes, or the right thing to do in the long run?
[
11:40am
]
balunasj
:
alexsmirnov: That would be for GA then.
[
11:41am
]
alexsmirnov
:
I suspect that is JBDS server adapter issue. I need a some time to isolate the source of problem.
[
11:42am
]
prabhat
:
alexsmirnov: did you see my question before?
[
11:42am
]
balunasj
:
alexsmirnov: ok, since it will be for GA we have some time, but I'm concerned that we might need a change here.  after your investigation is sounds like tools/AS issue
[
11:44am
]
balunasj
:
ilya_shaikovsky: can you start site updates in draft form?
[
11:44am
]
balunasj
:
I'll finish the blog announcement.
[
11:44am
]
alexsmirnov
:
prabhat: Yes, I see but I have no idea about that. Can you provide code snippet to reproduce that ?
[
11:45am
]
balunasj
:
alexsmirnov: prabhat : you guys will need to take this offline I think - if we are going to have time for 4.0 discussion.
[
11:45am
]
ilya_shaikovsky
:
balunasj, already done in draft
[
11:45am
]
prabhat
:
alexsmirnov: yes
[
11:45am
]
prabhat
:
alexsmirnov: i have it ready
[
11:45am
]
ilya_shaikovsky
:
except the announcement.. because I do not want problems with autocommit as for prev release
[
11:45am
]
balunasj
:
ilya_shaikovsky: agreed
[
11:45am
]
alexsmirnov
:
prabhat: It would be JSF RI issue, 4.2.3 and 5.1 use different implementations.
[
11:46am
]
prabhat
:
alexsmirnov: i think so too and I think it's a known issue but wondering if there is a work around
[
11:46am
]
prabhat
:
alexsmirnov: code is at http://anonsvn.jboss.org/repos/qa/prabhat/twitter-portlet/
[
11:46am
]
balunasj
:
alexsmirnov: prabhat : can you guys take offline for now.
[
11:46am
]
prabhat
:
alexsmirnov: oops http://anonsvn.jboss.org/repos/qa/prabhat/tictactoe-portlet/
[
11:46am
]
prabhat
:
balunasj: sure..
[
11:46am
]
balunasj
:
so for 3.3.3.CR1
[
11:47am
]
balunasj
:
all open issues moved to GA
[
11:47am
]
balunasj
:
QE should wrap up testing tomorrow
[
11:47am
]
balunasj
:
artifacts will be uploaded
[
11:47am
]
balunasj
:
ilya and I will prep site and announcement.
[
11:47am
]
balunasj
:
please updated RFPL-372 when you are ready with you various tasks.
[
11:47am
]
balunasj
:
I will email sean and make sure he knows to build bundle
[
11:48am
]
balunasj
:
and discuss with him at tomorrows doc meeting
[
11:48am
]
balunasj
:
prabhat: please let us know asap if something needs review for CR1.
[
11:48am
]
balunasj
:
lets move on to the 4.0 part of the agenda
[
11:49am
]
balunasj
:
As stated in agenda - we has a mixture of tool, and priorties issues come up that delayed the plan.
[
11:49am
]
balunasj
:
We are moving forward though and are looking for ways to cut back.
[
11:50am
]
•
balunasj
 
I'll create a forum post of the milestone release names
[
11:50am
]
balunasj
:
we can skip that for now.
[
11:50am
]
balunasj
:
ilya_shaikovsky: Where did you want to start with the tables or client lib?
[
11:51am
]
ilya_shaikovsky
:
balunasj, any
[
11:51am
]
balunasj
:
ilya_shaikovsky: can you start that conversation - I need to give fingers a break
[
11:52am
]
ilya_shaikovsky
:
sure
[
11:52am
]
ilya_shaikovsky
:
so we reduced count of planned tasks related to tables
[
11:52am
]
ilya_shaikovsky
:
as you could see from the doc
[
11:53am
]
ilya_shaikovsky
:
so we implementing only base functionality, moving old models (resolving some known issues)
[
11:54am
]
balunasj
:
so lets review straight DT
[
11:55am
]
balunasj
:
and what will not be done for A2
[
11:55am
]
ilya_shaikovsky
:
some questions still open like default controls for filter/sort operations
[
11:55am
]
balunasj
:
Columns Visibility
[
11:55am
]
balunasj
:
Column Menus
[
11:55am
]
balunasj
:
Selection(different modes e.g. keyboard free)
[
11:55am
]
nbelaevski
:
balunasj: agree
[
11:55am
]
balunasj
:
Customizable built-in statuses for ajax table processing (on built in sorting, filtering, etc..)
[
11:55am
]
balunasj
:
Sortring, menus, scroolling etc.. accessebility
[
11:55am
]
balunasj
:
client side sorting
[
11:55am
]
balunasj
:
client side filtering
[
11:56am
]
balunasj
:
Columns with selects/checkboxes
[
11:56am
]
balunasj
:
(ADDED)Support rerendering inidividual rows of tables?
[
11:56am
]
nbelaevski
:
also grouping
[
11:56am
]
balunasj
:
those are ones that have + in first column and a - in the A2
[
11:56am
]
ilya_shaikovsky
:
yes
[
11:57am
]
balunasj
:
nbelaevski: true - just did client side for now.
[
11:57am
]
nbelaevski
:
yes, but it's in client-side too
[
11:57am
]
abelevich
:
ilya_shaikovsky: selection also
[
11:57am
]
nbelaevski
:
#12
[
11:57am
]
ilya_shaikovsky
:
abelevich, was in list
[
11:57am
]
balunasj
:
hmm - how did I miss that
[
11:58am
]
ilya_shaikovsky
:
next points were dropped because the functionlity is completelly new for us
[
11:58am
]
ilya_shaikovsky
:
[18:55:57] balunasj: client side sorting
[
11:58am
]
ilya_shaikovsky
:
[18:55:57] balunasj: client side filtering
[
11:58am
]
ilya_shaikovsky
:
[18:56:05] balunasj: Columns with selects/checkboxes
[
11:58am
]
ilya_shaikovsky
:
[18:56:14] balunasj: (ADDED)Support rerendering inidividual rows of tables?
[
11:58am
]
abelevich
:
nbelaevski: mean grouping?
[
11:58am
]
balunasj
:
so there will be no sorting support at all for A2
[
11:58am
]
ilya_shaikovsky
:
client side
[
11:59am
]
ilya_shaikovsky
:
only ajax one as for 3.3.x
[
11:59am
]
balunasj
:
ah ok
[
11:59am
]
ilya_shaikovsky
:
[18:55:42] balunasj: Column Menus - should be redesigned and more customizable than it was for EDT for 3.3 (not cusomizable almost at all)
[
12:00pm
]
balunasj
:
ilya_shaikovsky: that is fine to slip for A2
[
12:00pm
]
nbelaevski
:
client API section should be split to A2 & post-A2 parts
[
12:00pm
]
ilya_shaikovsky
:
[18:55:42] balunasj: Selection(different modes e.g. keyboard free) - some problems with implementation in EDT which Kostya revising now. And as both tables should use common mechanisms - also postponed for DT
[
12:00pm
]
nbelaevski
:
do we need it at all for A2?
[
12:00pm
]
ilya_shaikovsky
:
nbelaevski, yes
[
12:00pm
]
ilya_shaikovsky
:
nbelaevski, we need to design api on existent features carefully from the beggining
[
12:01pm
]
balunasj
:
nbelaevski: r. client API selection?
[
12:01pm
]
balunasj
:
same question
[
12:01pm
]
ilya_shaikovsky
:
section
[
12:01pm
]
ilya_shaikovsky
:
i think
[
12:01pm
]
nbelaevski
:
yes, selection is not in A2, but API for this is there
[
12:01pm
]
ilya_shaikovsky
:
[
12:01pm
]
balunasj
:
ilya_shaikovsky: next line down
[
12:02pm
]
ilya_shaikovsky
:
ic.. API on A2 and will be improved after that's true
[
12:02pm
]
ilya_shaikovsky
:
I just not highlighted it
[
12:03pm
]
ilya_shaikovsky
:
Sortring, menus, scroolling etc.. accessebility - just need to be discussed more and have no requirements at al for now so postponed
[
12:03pm
]
ilya_shaikovsky
:
Customizable built-in statuses for ajax table processing (on built in sorting, filtering, etc..) - minor feature so was also moved
[
12:04pm
]
balunasj
:
since we are running late in meeting - do you want to focus just on specific questions?
[
12:04pm
]
balunasj
:
and any specific topics?
[
12:04pm
]
ilya_shaikovsky
:
I think it could be finisherd offline
[
12:04pm
]
ilya_shaikovsky
:
finished
[
12:04pm
]
ilya_shaikovsky
:
And on client side library..
[
12:05pm
]
ilya_shaikovsky
:
Pavel done with prototyping Event API.. we propose not to restrict old API usage at all but extend it to use event like described in wiki document as it could be more convenient in many cases.. So waiting your guys review on that approach in general
[
12:07pm
]
nbelaevski
:
ilya_shaikovsky: please clarify on old API
[
12:07pm
]
nbelaevski
:
ilya_shaikovsky: either you mean calling convention or API itself?
[
12:07pm
]
ilya_shaikovsky
:
$('componentId').component.doSomthing() direct method call usage proposed to be replaced with sending event to component object
[
12:08pm
]
nbelaevski
:
frankly speaking, I disagree with this approach
[
12:09pm
]
nbelaevski
:
IMO, it's more logical that component sends events as response to some actions (triggered by methods call or by user's actions) and not that component is being sent events forcing it to do something
[
12:09pm
]
balunasj
:
I just started to review wiki doc and need more time to sink in.
[
12:09pm
]
amitev
:
balunasj: got url?
[
12:09pm
]
ilya_shaikovsky
:
nbelaevski, component could notify the user with some events but also could use events to notify each other that some handler should be called
[
12:09pm
]
nbelaevski
:
alexsmirnov: wdyt?
[
12:10pm
]
balunasj
:
amitev: http://community.jboss.org/docs/DOC-14819
[
12:10pm
]
ilya_shaikovsky
:
alexsmirnov, yes.. Alex please also revise the approach we will wait for your feedback also
[
12:11pm
]
nbelaevski
:
ilya_shaikovsky: np on that, but I'd like to have the only old calling convention
[
12:11pm
]
ilya_shaikovsky
:
balunasj, B.t.w.
[
12:11pm
]
ilya_shaikovsky
:
as I written we seems need to have componentControl in A2 scope
[
12:11pm
]
ilya_shaikovsky
:
and it includes into tables document with estimations
[
12:11pm
]
balunasj
:
nbelaevski: is it having two ways to do it the problem.  Or the appoach with the events?
[
12:11pm
]
alexsmirnov
:
nbelaevski, ilya_shaikovsky: I always prefer do not put everything into spagetty-like code, but have extension points that let to easy append additional features.
[
12:12pm
]
nbelaevski
:
ilya_shaikovsky: events approach doesn't allow to call nested subcomponents without knowing their ids
[
12:12pm
]
ilya_shaikovsky
:
as we do not want explicitly rerender the table on it's own operations but just call filtering/sorting api on the table and it should process it smoothly as for internal controls
[
12:13pm
]
nbelaevski
:
balunasj: approach with events I think
[
12:13pm
]
•
balunasj
 
I think the Binding handlers to component events needs for description.
[
12:13pm
]
balunasj
:
nbelaevski: ok
[
12:13pm
]
nbelaevski
:
balunasj: calling function is straightforward, you can always check if it exists
[
12:14pm
]
balunasj
:
true
[
12:14pm
]
nbelaevski
:
balunasj: if non-existing functions is called, then it's an error,, not record in log
[
12:14pm
]
balunasj
:
ilya_shaikovsky: pyaschenko : in this approach will all components need to register for events to listen for?
[
12:14pm
]
nbelaevski
:
balunasj: how to know why UI logic breaks several lines of code below - read logs?
[
12:14pm
]
balunasj
:
or is this something the user needs to do with the binding?
[
12:14pm
]
prabhat is now known as prabhat_brb.
[
12:16pm
]
nbelaevski
:
one more point - event is sent to the disabled component - what's the response then? all handlers bound to this event are triggered?..
[
12:16pm
]
balunasj
:
nbelaevski: good points - could you add these to a comment in the wiki
[
12:16pm
]
amitev left the chat room. (Quit: Although nobody can come back and make a new start, anyone can start now and make a new end)
[
12:16pm
]
balunasj
:
nbelaevski: what happens today with disabled component and JS API call?
[
12:17pm
]
nbelaevski
:
IMO, component should control events emission - it knows it's internal state and can select the proper time/conditions
[
12:17pm
]
lfryc left the chat room. (Quit: Leaving)
[
12:17pm
]
ilya_shaikovsky
:
for your questions.. alsmost nothing changed for the developer
[
12:17pm
]
ilya_shaikovsky
:
if in the past he called methods - now he will send events
[
12:17pm
]
ilya_shaikovsky
:
now - in proposal
[
12:17pm
]
nbelaevski
:
balunasj: nothing. but in methods approach we can return status
[
12:17pm
]
alexsmirnov
:
Most JavaScript libraries associate UI element with widget object that can be manipulated by public methods. I think RF 4.0 should follow that pattern.
[
12:18pm
]
nbelaevski
:
balunasj: we can't return status with events, especially for multi-elements calls
[
12:18pm
]
alexsmirnov
:
If we going to use Jquery as base library public API should follow its architecture.
[
12:19pm
]
nbelaevski
:
BTW, Craig Larman refers to methods calls as events sending in his OOP book
[
12:19pm
]
balunasj
:
I agree with alexsmirnov - if I am following.
[
12:19pm
]
nbelaevski
:
the difference is that methods have interanl logic
[
12:19pm
]
balunasj
:
nbelaevski: That seems like stretching the definition a bit
[
12:19pm
]
nbelaevski
:
balunasj: I agree too
[
12:20pm
]
nbelaevski
:
balunasj: yes, somewhat
[
12:20pm
]
nbelaevski
:
the target of Events API was to isolate the user from changes in event API caused by base library replacement
[
12:21pm
]
balunasj
:
lets make some arguments back and forth on the wiki page and take it from there.
[
12:21pm
]
balunasj
:
There are obviously different opinions.
[
12:21pm
]
nbelaevski
:
ok, good
[
12:21pm
]
balunasj
:
fyi - I'm not against the event idea - JSF2 did a lot with events and it might make sense, but I need to understand impact a little more.
[
12:22pm
]
balunasj
:
plus there are different idea as well.
[
12:22pm
]
nbelaevski
:
balunasj: IMO, events should be there, but not in such flavor
[
12:23pm
]
balunasj
:
Does anyone else have something to bring up?
[
12:23pm
]
balunasj
:
clerum : has some concerns over http://community.jboss.org/thread/18034?start=0&tstart=0
[
12:23pm
]
balunasj
:
ilya_shaikovsky and I will discuss offline