Re: [core] Introducing implee6 - MYFACES-2579

+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/3/8 Werner Punz werner.p...@gmail.com +1 for that idea, the less configuration the better. Werner Am 07.03.10 15:44,

TRINIDAD: ViewExpiredException

Hi, one of the most frustration things with Trinidad (IMHO) is the ViewExpiredException occurring if a session times out and a user invokes an ajax action. I found no solution to overcome this problem, since two years. There is also a critical bug reported in JIRA at February, 2008:

Re: Demo: MyFaces2 meets Apache OWB

Cool! --Gurkan From: Matthias Wessendorf mat...@apache.org To: MyFaces Development dev@myfaces.apache.org; d...@openwebbeans.apache.org Sent: Sat, March 6, 2010 3:38:56 PM Subject: Demo: MyFaces2 meets Apache OWB Some (simple) demo of the two:

[jira] Resolved: (MYFACES-2585) ajax doesn't work if target contains script with CDATA

[ https://issues.apache.org/jira/browse/MYFACES-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved MYFACES-2585. -- Resolution: Fixed I think my solution works for good now, I could not trigger any error

[Core] Problem with MYFACES-2577

Hi, It looks like MYFACES-2577 changed jsf.util.chain() to return false if one of the functions in the chain returns false, true otherwise. In the page we're rendering return jsf.util.chain(...) for things like onclick handlers. The problem here is that if someone has an f:ajax tag on a command

Re: [Core] Problem with MYFACES-2577

Hi Curtiss, It should only say return jsf.util.chain() if no client behavior is attached to the component which has its Hint set to SUBMITTING. If such a (SUBMITTING-)ClientBehavior is attached it should still be jsf.util.chain(); return false; Regards, Jakob 2010/3/8 Curtiss Howard

Re: [Core] Problem with MYFACES-2577

Jakob, This is the test our tester is using and the rendered markup shows return jsf.util.chain(...): h:body h:form id=form1 prependId=false h:outputScript name=jsf.js library=javax.faces target=head / h:outputText id=out1 value=#{incrementdecrement.value}/ br/

[jira] Created: (EXTSCRIPT-87) Classpath resolvement issue

Classpath resolvement issue --- Key: EXTSCRIPT-87 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-87 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee:

[jira] Resolved: (EXTSCRIPT-87) Classpath resolvement issue

[ https://issues.apache.org/jira/browse/EXTSCRIPT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-87. -- Resolution: Fixed Classpath resolvement issue ---

Re: [Core] Problem with MYFACES-2577

hi curtiss, yes, it should be, but I guess this is not implemented in the right way. I'll take a look at this later today! Regards, Jakob 2010/3/8, Curtiss Howard curtiss.how...@gmail.com: Jakob, This is the test our tester is using and the rendered markup shows return jsf.util.chain(...):

Re: TRINIDAD: ViewExpiredException

Mathias, I agree that we should do something about TRINIDAD-943. The discussion you pointed out does indeed show a workable solution (http://www.mail-archive.com/us...@myfaces.apache.org/msg53577.html) - the idea is that you would have a filter that would check: Check if the current

[jira] Resolved: (EXTSCRIPT-77) Handle the additionalclasspath config entries

[ https://issues.apache.org/jira/browse/EXTSCRIPT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-77. -- Resolution: Fixed Handle the additionalclasspath config entries

[jira] Resolved: (EXTSCRIPT-86) Add a taint history component

[ https://issues.apache.org/jira/browse/EXTSCRIPT-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-86. -- Resolution: Fixed Add a taint history component -

[jira] Created: (EXTSCRIPT-88) cleanup the faclet-config handling

cleanup the faclet-config handling -- Key: EXTSCRIPT-88 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-88 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz

core 2.0 build

Hi, Today I did my usual svn update and mvn and I get: [INFO] Compiling 36 source files to C:\projects\MyFaces_Trunk\impl\target\classes [INFO] [ERROR] BUILD FAILURE [INFO]

Re: core 2.0 build

have you checked out shared ? Take the current20 externals link: http://svn.apache.org/repos/asf/myfaces/current20/ On Mon, Mar 8, 2010 at 8:17 AM, Ganesh gan...@j4fry.org wrote: Hi, Today I did my usual svn update and mvn and I get: [INFO] Compiling 36 source files to

Re: core 2.0 build

Hi Ganesh, Did you build shared core and shared impl too? Regards, Jakob 2010/3/8 Ganesh gan...@j4fry.org Hi, Today I did my usual svn update and mvn and I get: [INFO] Compiling 36 source files to C:\projects\MyFaces_Trunk\impl\target\classes [INFO]

[jira] Created: (TRINIDAD-1749) Trinidad 2: UnsupportedOperationException during decode when h:form is on the page

Trinidad 2: UnsupportedOperationException during decode when h:form is on the page -- Key: TRINIDAD-1749 URL: https://issues.apache.org/jira/browse/TRINIDAD-1749

Re: core 2.0 build

No, I actually didn't. Shouldn't maven take care of dependencies? Until now it always did! Do I need to set up a seperate shared project now? Best regards, Ganesh Jakob Korherr schrieb: Hi Ganesh, Did you build shared core and shared impl too? Regards, Jakob 2010/3/8 Ganesh

[jira] Resolved: (TRINIDAD-1749) Trinidad 2: UnsupportedOperationException during decode when h:form is on the page

[ https://issues.apache.org/jira/browse/TRINIDAD-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Starets resolved TRINIDAD-1749. --- Resolution: Fixed Fix Version/s: 2.0.0-alpha-2 Trinidad 2:

Re: TRINIDAD: ViewExpiredException

FYI, it still does occur with JSF2, at least on the JSF2 AJAX branch we have. It results in a nice NullPointerException on the server actually, very ugly. -Andrew On Mon, Mar 8, 2010 at 8:06 AM, Max Starets max.star...@oracle.com wrote: Mathias, I agree that we should do something about

Re: core 2.0 build

Maven does take care of the dependencies, but I believe it takes a little time before the changes to the shared project are pushed to the global Maven repository, so in these cases, unless you can wait you need to build shared and deploy it to your local repository. Curtiss Howard On Mon, Mar

Re: core 2.0 build

The best way is to check out core20. Then you will get the core (api + impl) and the shared project and you won't have problems like that anymore! Regards, Jakob 2010/3/8 Curtiss Howard curtiss.how...@gmail.com Maven does take care of the dependencies, but I believe it takes a little time

Re: [core] Introducing implee6 - MYFACES-2579

Hi, Since there don't seem to be any big concerns about this, I will now commit the new submodule implee6. Regards, Jakob 2010/3/8 Gerhard Petracek gerhard.petra...@gmail.com +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in

Re: core 2.0 build

Of course, it is current20 not core20. My mistake! Regards, Jakob 2010/3/8 Jakob Korherr jakob.korh...@gmail.com The best way is to check out core20. Then you will get the core (api + impl) and the shared project and you won't have problems like that anymore! Regards, Jakob 2010/3/8

Re: core 2.0 build

yep, that's the way to go. Since continuum has some issues, it maybe the case that the shared snapshot aren't updated yet. However, checkout of the current20 is not a big deal. -Matthias On Mon, Mar 8, 2010 at 7:25 PM, Jakob Korherr jakob.korh...@gmail.com wrote: The best way is to check out

[jira] Created: (MYFACES-2590) Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans)

Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans) -- Key: MYFACES-2590 URL:

[jira] Created: (EXTSCRIPT-89) windows

windows --- Key: EXTSCRIPT-89 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-89 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz make sure that

Re: core 2.0 build

yes, works! Thank you, guys. Matthias Wessendorf schrieb: yep, that's the way to go. Since continuum has some issues, it maybe the case that the shared snapshot aren't updated yet. However, checkout of the current20 is not a big deal. -Matthias On Mon, Mar 8, 2010 at 7:25 PM, Jakob Korherr

Re: [core] Introducing implee6 - MYFACES-2579

Hi, So I committed everything. Please feel free to test it - I am curious about your opinions :) Regards, Jakob 2010/3/8 Jakob Korherr jakob.korh...@gmail.com Hi, Since there don't seem to be any big concerns about this, I will now commit the new submodule implee6. Regards, Jakob

[jira] Resolved: (MYFACES-2579) Support the dynamic adding of servlets and servlet-mappings on Servlet API 3.0 to make web.xml entries for Faces Servlet not mandatory

[ https://issues.apache.org/jira/browse/MYFACES-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2579. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 Assignee: Jakob Korherr

[jira] Commented: (MYFACES-2590) Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans)

[ https://issues.apache.org/jira/browse/MYFACES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842811#action_12842811 ] Jakob Korherr commented on MYFACES-2590: Can you explain this a little further

[jira] Created: (MYFACES-2591) buildBehaviorChain() should also check the ClientBehaviors for the second eventName for submitting

buildBehaviorChain() should also check the ClientBehaviors for the second eventName for submitting -- Key: MYFACES-2591 URL:

[jira] Resolved: (MYFACES-2591) buildBehaviorChain() should also check the ClientBehaviors for the second eventName for submitting

[ https://issues.apache.org/jira/browse/MYFACES-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2591. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 buildBehaviorChain() should also

Re: [Core] Problem with MYFACES-2577

Hi Curtiss, I found the bug and fixed it. See MYFACES-2591 for details. Regards, Jakob 2010/3/8 Jakob Korherr jakob.korh...@gmail.com hi curtiss, yes, it should be, but I guess this is not implemented in the right way. I'll take a look at this later today! Regards, Jakob 2010/3/8,

Re: [Core] Problem with MYFACES-2577

Thanks Jakob, much appreciated. Curtiss Howard On Mon, Mar 8, 2010 at 4:46 PM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Curtiss, I found the bug and fixed it. See MYFACES-2591 for details. Regards, Jakob 2010/3/8 Jakob Korherr jakob.korh...@gmail.com hi curtiss, yes, it

Helping the project

Hi, Is there any Junior jobs like KDE so i newbie like myself can knowing the internals of MyFaces can help the project. Best Regards Carlos Ortiz.

[jira] Commented: (TRINIDAD-1746) move InputStreamProvider to be a public API

[ https://issues.apache.org/jira/browse/TRINIDAD-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842900#action_12842900 ] Jeanne Waldman commented on TRINIDAD-1746: -- Instead of

[jira] Commented: (TRINIDAD-1729) provide a hook for for an external decorator of Skin InputStreamProvider

[ https://issues.apache.org/jira/browse/TRINIDAD-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842899#action_12842899 ] Jeanne Waldman commented on TRINIDAD-1729: -- The InputStreamProviderFactory is

[TRINIDAD][SKINNING] NameResolver to public API

While working on TRINIDAD-1729 provide a hook for for an external decorator of Skin InputStreamProvider, I realized that I need InputStreamProvider to be public. I also need NameResolver to be public. I can do this as part of https://issues.apache.org/jira/browse/TRINIDAD-1746 move