balunasj
:
FYI - agenda posted for team meeting http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda11-24-2009
[
11:00am
]
balunasj
:
amarkhel: hi
[
11:00am
]
balunasj
:
Hi all
[
11:00am
]
nbelaevski
:
hello all
[
11:00am
]
ppitonak
:
hi
[
11:00am
]
pyaschenko joined the chat room.
[
11:01am
]
amarkhel
:
balunasj: first of all, I am sorry about reports etc... I answer on your letter later ok?
[
11:01am
]
pyaschenko
:
Hi All
[
11:01am
]
abelevich
:
hi
[
11:02am
]
Alex_Kolonitsky joined the chat room.
[
11:02am
]
balunasj
:
We'll give a 1-2 more minutes for people to join.
[
11:03am
]
ircwidget joined the chat room.
[
11:03am
]
ircwidget2 joined the chat room.
[
11:05am
]
balunasj
:
ok guys
[
11:05am
]
ircwidget3 joined the chat room.
[
11:05am
]
balunasj
:
Alex, Nick, and I have a meeting with the JSF Ajax EG group at 12:00 so we have a hard stop then.
[
11:05am
]
ircwidget4 joined the chat room.
[
11:05am
]
balunasj
:
anyone know what these ircwidgets are?
[
11:06am
]
ircwidget5 joined the chat room.
[
11:07am
]
ircwidget6 joined the chat room.
[
11:07am
]
ircwidget7 joined the chat room.
[
11:07am
]
nbelaevski
:
balunasj: you can ban them
[
11:07am
]
ircwidget2 left the chat room. (Read error: 104 (Connection reset by peer))
[
11:07am
]
ircwidget left the chat room. (Read error: 104 (Connection reset by peer))
[
11:07am
]
ircwidget7 left the chat room. (Read error: 104 (Connection reset by peer))
[
11:07am
]
ircwidget6 left the chat room. (Read error: 104 (Connection reset by peer))
[
11:07am
]
ircwidget3 left the chat room. (Read error: 131 (Connection reset by peer))
[
11:07am
]
ircwidget4 left the chat room. (Read error: 131 (Connection reset by peer))
[
11:07am
]
ircwidget5 left the chat room. (Read error: 131 (Connection reset by peer))
[
11:07am
]
nbelaevski
:
balunasj: as channel op
[
11:07am
]
balunasj
:
Nick and I talked about some of the remaining jira's yesterday, and I would like to go over them now.  Plus get a status on ones in progress?
[
11:08am
]
balunasj
:
First nbelaevski completed the merge from 3.3.X_JSF2!!!
[
11:08am
]
balunasj
:
so nothing more should be going into that branch
[
11:08am
]
balunasj
:
Here are the RF jira's that are still unresolved
[
11:09am
]
balunasj
:
https://jira.jboss.org/jira/secure/BrowseVersion.jspa?id=12310341&versionId=12314119&showOpenIssuesOnly=true
[
11:09am
]
balunasj
:
https://jira.jboss.org/jira/browse/RF-8135
[
11:10am
]
balunasj
:
amarkhel: have you been able to look into this?
[
11:11am
]
amarkhel
:
balunasj: no I haven't yet.. I am tru to fix the issueses related to RichFaces-demo https://jira.jboss.org/jira/browse/RF-8151 and https://jira.jboss.org/jira/browse/RF-8150
[
11:11am
]
ircwidget joined the chat room.
[
11:11am
]
balunasj
:
tru == through/done?
[
11:11am
]
amarkhel
:
balunasj: try)
[
11:12am
]
amarkhel
:
sorry for misprint
[
11:12am
]
alexsmirnov
:
balunasj: I afraid we can do nothing but recommend to increase transaction timeout for that. Seam starts transaction for every request, and that feature is hardcoded into Seam.
[
11:12am
]
balunasj
:
amarkhel: np - how long do you think you need on the demo issues?
[
11:12am
]
amarkhel
:
balunasj: I thought problem in upgrading Nekko Parser
[
11:13am
]
amarkhel
:
balunasj: I found the problem but i didn't found solution yet..
[
11:13am
]
alexsmirnov
:
amarkhel: What is problem there ?
[
11:13am
]
balunasj
:
amarkhel: ok - if it is truly a demo only issue we should shift you off of that if it is taking too long
[
11:14am
]
amarkhel
:
alexsmirnov: new Nekko suddenly cut chunks of html.. this is strange
[
11:14am
]
balunasj
:
alexsmirnov: nbelaevski and I talked about 8135 a while back and it does not seem to happen with older RF v
[
11:15am
]
amarkhel
:
alexsmirnov: I need to time to determine what exactly broken//but when i revert changes - all work fine
[
11:15am
]
balunasj
:
alexsmirnov: that is why  we wanted it investigated.  Upping time out is an option, and using conversation scope was going to be investigted.
[
11:16am
]
alexsmirnov
:
amarkhel: Yes, I,ve seen that. I tried to render enclosed <html> tags for ajax response and it helps.
[
11:16am
]
balunasj
:
amarkhel: just to be clear "revert changes" == use older parser?
[
11:17am
]
amarkhel
:
balunasj: No I am update project to revision before upgrading Nekko Parser
[
11:17am
]
balunasj
:
ok gotcha using older parser works
[
11:17am
]
abelevich left the chat room. (Read error: 54 (Connection reset by peer))
[
11:18am
]
amarkhel
:
balunasj: Yes You are right
[
11:18am
]
abelevich joined the chat room.
[
11:18am
]
balunasj
:
amarkhel, alexsmirnov : is this limited to the demo, or is this a possible bigger issue for users that are using the parser?
[
11:19am
]
amarkhel
:
balunasj: it is all users problem as I thought
[
11:19am
]
balunasj
:
amarkhel: ok please up the priority to ctitical for the effected jira's
[
11:20am
]
amarkhel
:
balunasj:ok
[
11:20am
]
balunasj
:
is it only Rf-8151 and RF-8150 that are effected?  They should also be linked.
[
11:20am
]
balunasj
:
amarkhel: thanks
[
11:20am
]
amarkhel
:
balunasj: agree
[
11:21am
]
balunasj
:
amarkhel: ok so you need to keep working on that one
[
11:21am
]
balunasj
:
alexsmirnov: any other hints or ideas related to it please post in jira, or offline for now.
[
11:21am
]
alexsmirnov
:
ok
[
11:22am
]
amarkhel
:
balunasj: yes, I think one day is enough for fix that
[
11:22am
]
balunasj
:
nbelaevski: the two minor issues - I think we should just most to future
[
11:22am
]
nbelaevski
:
balunasj: agree
[
11:22am
]
balunasj
:
Alex_Kolonitsky: what issue are you looking at now?
[
11:23am
]
Alex_Kolonitsky
:
https://jira.jboss.org/jira/browse/RF-8052
[
11:24am
]
balunasj
:
Alex_Kolonitsky: ok - just assigned to you
[
11:24am
]
Alex_Kolonitsky
:
ok
[
11:24am
]
balunasj
:
we discussed that one as well - I will be curious what you find.
[
11:24am
]
balunasj
:
please post info or updates to the jira
[
11:25am
]
balunasj
:
RF-8149
[
11:25am
]
balunasj
:
Assigned to Ilya atm
[
11:25am
]
amarkhel
:
balunasj: I think https://jira.jboss.org/jira/browse/RF-8159 can be related to nekko too
[
11:25am
]
balunasj
:
alexsmirnov: you though RF-8149 was an easy update to the jar - right?
[
11:26am
]
balunasj
:
amarkhel: looking...
[
11:26am
]
balunasj
:
amarkhel: ok please assign link, and update priority for it.
[
11:26am
]
amarkhel
:
sure
[
11:27am
]
balunasj
:
amarkhel: If they are all the same issue please create a separate issue with the "real" problem ( nekko ) and close these as duplicates.
[
11:27am
]
balunasj
:
amarkhel: that can wait for after solution.
[
11:27am
]
amarkhel
:
ok but Rf-8159 need to check
[
11:28am
]
amarkhel
:
if there are one problem I close RF-8159
[
11:28am
]
balunasj
:
amarkhel: yup - understood
[
11:28am
]
balunasj
:
ok
[
11:28am
]
LexD left the chat room.
[
11:31am
]
balunasj
:
That leaves RF-8149 and RF-8135 that need investigation or moving
[
11:32am
]
balunasj
:
ppitonak: was RF-8149 found on the RF-demo
[
11:32am
]
balunasj
:
or a diff test app?
[
11:33am
]
ppitonak
:
balunasj:  demo
[
11:33am
]
balunasj
:
ppitonak: ok
[
11:33am
]
alexsmirnov
:
balunasj: I did a minor change in the framework to let RichFaces works with the last neko version. Probably, that requires much more code changes, so it had better to switch back to previvious version and mark that issue as known incompatibility.
[
11:33am
]
ppitonak
:
it doesn't behave as demo from 3.3.3.SR1
[
11:33am
]
ppitonak
:
balunasj: ^
[
11:34am
]
balunasj
:
alexsmirnov: the issues amarkhel is looking at, or a different one?
[
11:34am
]
alexsmirnov
:
8149 has been inspired by JSFUnit problem.
[
11:34am
]
balunasj
:
ppitonak: ok
[
11:35am
]
alexsmirnov
:
balunasj: Yes, I suspect what all of them are related to Neko version.
[
11:35am
]
balunasj
:
alexsmirnov: I thought https://jira.jboss.org/jira/browse/RF-8149 was found by ppitonak with the demo and selenium
[
11:35am
]
balunasj
:
alexsmirnov:
[
11:35am
]
ppitonak
:
balunasj: exactly
[
11:36am
]
balunasj
:
Upgrading the neko version was because of JSFUnit correct?
[
11:36am
]
amarkhel
:
balunasj: https://jira.jboss.org/jira/browse/RF-8159 isn't related to nekko..
[
11:36am
]
amarkhel
:
so it is only 2 issueses
[
11:37am
]
balunasj
:
alexsmirnov: just so we are on same page - which issues do you think are neko related?
[
11:38am
]
amarkhel
:
balunasj: https://jira.jboss.org/jira/browse/RF-8150
[
11:38am
]
amarkhel
:
and https://jira.jboss.org/jira/browse/RF-8151
[
11:38am
]
balunasj
:
amarkhel: right - those I know but it sounded like alexsmirnov thought some others were involved too
[
11:39am
]
amarkhel
:
ok
[
11:39am
]
amarkhel
:
understand now
[
11:39am
]
balunasj
:
amarkhel: np
[
11:40am
]
alexsmirnov
:
Oops, sorry - 8159 is a complete different case, but 8150/1 seem like Neko-inspired.
[
11:40am
]
balunasj
:
alexsmirnov: oh ok - good I thought I missed something
[
11:41am
]
balunasj
:
alexsmirnov: RF-8149 - the validator issue with the demo - you thought that was an easy lib change right?
[
11:42am
]
alexsmirnov
:
8159 is expected warning for incorrect project configuration. That means what bean validator has found JSR-303 API but old Hibernate Validator implementation.
[
11:42am
]
alexsmirnov
:
validation-api requires HibernateValidator 4.x
[
11:43am
]
balunasj
:
alexsmirnov: just to be clear you mean https://jira.jboss.org/jira/browse/RF-8149 not RF-8159 - right?
[
11:45am
]
alexsmirnov
:
Right
[
11:45am
]
balunasj
:
alexsmirnov: ok
[
11:46am
]
balunasj
:
alexsmirnov: we still need to resolve the issue though because it is throwing an exception in demo. 
[
11:46am
]
balunasj
:
although since it is a demo only and BETAs and CRs are not deployed it could be posponed to CR1
[
11:46am
]
balunasj
:
it should not be a risky update since not much of the demo relies on validator
[
11:47am
]
amitev left the chat room. ("Although nobody can come back and make a new start, anyone can start now and make a new end")
[
11:48am
]
balunasj
:
that still leaves RF-8135.
[
11:48am
]
balunasj
:
There seems to be a clear workaround and other possible workaround
[
11:48am
]
wesleyhales joined the chat room.
[
11:48am
]
balunasj
:
nbelaevski: alexsmirnov : what do you think of updating the jira with increasing timeout and postponing to future
[
11:49am
]
nbelaevski
:
balunasj: let's do that
[
11:49am
]
balunasj
:
ok good
[
11:49am
]
balunasj
:
That leave amarkhel looking at the neko issues
[
11:49am
]
balunasj
:
Alex_Kolonitsky: looking at frames and calendars
[
11:50am
]
balunasj
:
plus hopefully RF-8159 if possible.
[
11:50am
]
alexsmirnov
:
balunasj: Agree. I would ever require Seam changes.
[
11:50am
]
balunasj
:
all of the RFPL issues are actually QE related and not critical to BETA1 code freeze
[
11:51am
]
alexsmirnov
:
balunasj, nick: 9 minutes to JSF meeting.
[
11:51am
]
balunasj
:
RFPL are not issues that are typically "required" to be resolved prior to code freeze or release ( they can be issues like updating demos online ).
[
11:51am
]
balunasj
:
so we can leave those.
[
11:52am
]
balunasj
:
alexsmirnov: yup thanks - I need to look over nbelaevski updates to the wiki
[
11:52am
]
nbelaevski
:
balunasj: I've found some issue with Maven configuration for jsf2 artifacts yesterday - working on it right now and hope to finish today
[
11:52am
]
balunasj
:
so amarkhel when do you think you can finish.
[
11:52am
]
nbelaevski
:
balunasj: that's for 3.3.3
[
11:52am
]
balunasj
:
Alex_Kolonitsky: same for you?
[
11:53am
]
balunasj
:
nbelaevski: ok - hopefully nothing too major.
[
11:53am
]
amarkhel
:
balunasj: I think one day.. If solution wasn't be found it is make sense to revert nekko parser to old version, what you think?
[
11:53am
]
nbelaevski
:
need to set up distribution and examples configuration for JSF 2.0
[
11:53am
]
balunasj
:
nbelaevski: I have not reviewed the build since the merge
[
11:53am
]
balunasj
:
nbelaevski: yup
[
11:54am
]
balunasj
:
amarkhel: My only concern there would be JSFUnit integration issues - but that is part of the problem with JSFUnit it pollutes the classloader
[
11:55am
]
amarkhel
:
balunasj: ok understand.. i try to fix any way
[
11:55am
]
balunasj
:
amarkhel: If there is no good solution - yes we should revert.  Please email team with details.
[
11:55am
]
balunasj
:
we'll need to discuss with stan if that is needed
[
11:55am
]
amarkhel
:
balunasj: ok
[
11:55am
]
balunasj
:
so we need to shift freeze out one more day to tomorrow EOD with build to QE Thursday. 
[
11:55am
]
amarkhel
:
balunasj: Thare are RF-8159  issue exist. I take a look tomorrow also, I think it isn't hard to fix
[
11:56am
]
amarkhel
:
there are..
[
11:56am
]
balunasj
:
This will need to be handled by Minks team as US is on holiday Thursday and friday.
[
11:56am
]
balunasj
:
amarkhel: ok
[
11:57am
]
alexsmirnov
:
balunasj: For JSFUnit tests we have a workaround: tests may use other parsers to run.
[
11:58am
]
balunasj
:
alexsmirnov: then I feel even better about it if we can't resolve in time.
[
11:58am
]
balunasj
:
ok guys we have another meeting we need to go to. 
[
11:58am
]
balunasj
:
Anything thing else we can discuss offline or in email/forums
[
11:59am
]
ppitonak_ joined the chat room.
[
11:59am
]
balunasj
:
We need to get the release out by week after JSFSummit, so we need to be solid on code freeze tomorrow.
[
12:00pm
]
balunasj
:
If we get QE a release they can test Thursday and then all next week hopefully we'll be ready to go. 
[
12:00pm
]
•
balunasj
 
obviously we need to wait and see how testing goes....