[jira] [Created] (TRINIDAD-2216) The partialSubmit does not work with JSF 2 RI
The partialSubmit does not work with JSF 2 RI
-
Key: TRINIDAD-2216
URL: https://issues.apache.org/jira/browse/TRINIDAD-2216
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 2.0.0-core
Environment: Mojarra 2.1.6 (SNAPSHOT 20111206)
Glassfish 3.1.1
Trinidad 2.0.0
Reporter: Tomas Havelka
Trinidad's partialSubmit does not work because the source parameter passed in
the jsf.ajax.request call is null. See XMLRequest.js on the line 358. The
source is part of the payload but is not assigned to the source parameter
itself. It causes the RI implementation of jsf.ajax.request throws an error
because of this code in it:
if (typeof source === 'undefined' || source === null) {
throw new Error(jsf.ajax.request: source not set);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3466) @PostConstruct not working when bean name is equal to class name
@PostConstruct not working when bean name is equal to class name
Key: MYFACES-3466
URL: https://issues.apache.org/jira/browse/MYFACES-3466
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.1.6
Environment: Tomcat 7.0.25, Java 1.6.0_03
Reporter: Mirko Strüßmann
Priority: Minor
When giving a managed bean the name of the class, methods annotated with
@PostConstruct are not called after construction of the bean.
Example:
@ManagedBean(TestBean)
public class TestBean {
@PostConstruct
void init() {
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Tobago 1.0.39
+1 On Tue, Feb 14, 2012 at 8:37 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Hello, I would like to release Tobago 1.0.39. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12319455 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-231/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Release Tobago 1.0.39
+1 On Thu, Feb 16, 2012 at 7:07 AM, Matthias Wessendorf mat...@apache.orgwrote: +1 On Tue, Feb 14, 2012 at 8:37 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Hello, I would like to release Tobago 1.0.39. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12319455 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-231/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [VOTE] Release Tobago 1.0.39
+1 Regards, Volker Am 16. Februar 2012 16:46 schrieb Grant Smith work.gr...@gmail.com: +1 On Thu, Feb 16, 2012 at 7:07 AM, Matthias Wessendorf mat...@apache.org wrote: +1 On Tue, Feb 14, 2012 at 8:37 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Hello, I would like to release Tobago 1.0.39. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12319455 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-231/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC. -- inexso - information exchange solutions GmbH Ofener Str. 30 | 26121 Oldenburg Tel.: +49 441 219 730 56 | FAX: +49 441 219 730 66 | eMail: volker.we...@inexso.de Firmensitz: Oldenburg | Amtsgericht Oldenburg HRB 205251 Geschäftsführer: Stefan Schulte, Michael Terschüren
Result (was: Re: [VOTE] Release of Extensions CDI (CODI) 1.0.4)
thank you for voting! 6 binding +1 votes (pmc): - Werner Punz - Grant Smith - Mark Struberg - Jakob Korherr - Leonardo Uribe - Gerhard Petracek 1 non-binding +1 vote: - Martin Koci no -1 votes regards, gerhard 2012/2/13 Gerhard Petracek gpetra...@apache.org Hi, I was running the needed tasks to get the 11th release of Apache MyFaces Extensions CDI (aka MyFaces CODI) out. The artifacts are deployed to Nexus [1] (and [2]). The release contains the following modules: - CODI Core - CODI JSF Module (for 1.2 and 2.0 and 2.1) - CODI JPA Module - CODI BV Module - CODI I18N-Message Module - CODI Scripting Module - CODI Trinidad Support Module (for 1.x and 2.x) - CODI Java-EE5 Support Module (for OpenWebBeans and Weld) - CODI Alternative Config and Impl Modules - CODI Bundles - CODI OSGi Bundles - CODI Base Test-Infrastructure Module - CODI JUnit-Support Module - CODI Cargo-Support Module - CODI OpenWebBeans Test-Support Module - CODI JSF Test-Support Module - CODI JSF Example Please take a look at the 1.0.4 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Gerhard [1] https://repository.apache.org/content/repositories/orgapachemyfaces-224/ [2] https://repository.apache.org/content/repositories/orgapachemyfaces-224/org/apache/myfaces/extensions/cdi/myfaces-extcdi-parent/1.0.4/myfaces-extcdi-parent-1.0.4-source-release.zip [3] http://www.apache.org/foundation/voting.html#ReleaseVotes
[jira] [Resolved] (EXTCDI-267) preparations for v1.0.4
[ https://issues.apache.org/jira/browse/EXTCDI-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-267. - Resolution: Fixed preparations for v1.0.4 --- Key: EXTCDI-267 URL: https://issues.apache.org/jira/browse/EXTCDI-267 Project: MyFaces CODI Issue Type: Task Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3467) [PERF] Use index-based loop where possible - part II
[PERF] Use index-based loop where possible - part II Key: MYFACES-3467 URL: https://issues.apache.org/jira/browse/MYFACES-3467 Project: MyFaces Core Issue Type: Sub-task Environment: myfaces core trunk Reporter: Martin Kočí Assignee: Martin Kočí Priority: Trivial see MYFACES-3130 for details -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MYFACES-3467) [PERF] Use index-based loop where possible - part II
[ https://issues.apache.org/jira/browse/MYFACES-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Kočí updated MYFACES-3467: - Status: Patch Available (was: Open) [PERF] Use index-based loop where possible - part II Key: MYFACES-3467 URL: https://issues.apache.org/jira/browse/MYFACES-3467 Project: MyFaces Core Issue Type: Sub-task Components: JSR-314 Environment: myfaces core trunk Reporter: Martin Kočí Assignee: Martin Kočí Priority: Trivial Attachments: ApplicationImpl.patch, HtmlAjaxBehaviorRenderer.patch, HtmlFormatRenderer.patch, HtmlRendererUtils.patch, PartialVisitContext.patch, RenderResponseExecutor.patch, UIComponentBase.patch, UIData.patch, UIViewRoot.patch, _ComponentChildrenList.patch, _DeltaList.patch, _DeltaList2.patch see MYFACES-3130 for details -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2217) when using partial state saving markInitialState called many times
when using partial state saving markInitialState called many times -- Key: TRINIDAD-2217 URL: https://issues.apache.org/jira/browse/TRINIDAD-2217 Project: MyFaces Trinidad Issue Type: Bug Reporter: Gabrielle Crawford We have been calling markInitialState in our tagHandler since before JSF had partial state saving. In JSF 2 they support partial state saving, so the framework should always be the one calling markInitialState and we should remove it from our tag handlers, but there is a bug in the framework which means it doesn't always call markInitialState in render response, see http://java.net/jira/browse/JAVASERVERFACES-2285 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TRINIDAD-2217) when using partial state saving markInitialState called many times
[ https://issues.apache.org/jira/browse/TRINIDAD-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13209749#comment-13209749 ] Gabrielle Crawford commented on TRINIDAD-2217: -- One possible fix is to remove it from our tag handlers, but new components added during restore view will be fully state saved due to the issue in 2285(see above). Another possible fix is to continue to call markInitialState in our tag handler but only during render response, and only if initialStateMarked returns false (otherwise any deltas saved between restore view and render response may get blown away). This still leaves the issue that if someone calls clearInitialState on a component before render response, presumable because they want to force full state saving on the component, then the tag handler will call markInitialState again. Since calling clearInitialState is unusual this is probably acceptable while waiting for the RI fix. when using partial state saving markInitialState called many times -- Key: TRINIDAD-2217 URL: https://issues.apache.org/jira/browse/TRINIDAD-2217 Project: MyFaces Trinidad Issue Type: Bug Reporter: Gabrielle Crawford We have been calling markInitialState in our tagHandler since before JSF had partial state saving. In JSF 2 they support partial state saving, so the framework should always be the one calling markInitialState and we should remove it from our tag handlers, but there is a bug in the framework which means it doesn't always call markInitialState in render response, see http://java.net/jira/browse/JAVASERVERFACES-2285 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2218) Need an ability for the WindowManager implementation to be executed before all Configurators and filters and to complete teh response
Need an ability for the WindowManager implementation to be executed before all Configurators and filters and to complete teh response - Key: TRINIDAD-2218 URL: https://issues.apache.org/jira/browse/TRINIDAD-2218 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 2.0.2-core Reporter: Max Starets Assignee: Max Starets Since WindowManager is expected to make the Window Map available to all Configurators, we need a way to ensure that it is executed before all Configurators and filters. Also, WindowManager needs to be able to complete a response, so that it can send a script response to the client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2218) Need an ability for the WindowManager implementation to be executed before all Configurators and filters and to complete teh response
[ https://issues.apache.org/jira/browse/TRINIDAD-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Starets updated TRINIDAD-2218: -- Status: Patch Available (was: Open) Need an ability for the WindowManager implementation to be executed before all Configurators and filters and to complete teh response - Key: TRINIDAD-2218 URL: https://issues.apache.org/jira/browse/TRINIDAD-2218 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 2.0.2-core Reporter: Max Starets Assignee: Max Starets Attachments: trinidad-2218.patch Since WindowManager is expected to make the Window Map available to all Configurators, we need a way to ensure that it is executed before all Configurators and filters. Also, WindowManager needs to be able to complete a response, so that it can send a script response to the client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TRINIDAD-2217) when using partial state saving markInitialState called many times
[ https://issues.apache.org/jira/browse/TRINIDAD-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabrielle Crawford resolved TRINIDAD-2217. -- Resolution: Fixed Assignee: Gabrielle Crawford when using partial state saving markInitialState called many times -- Key: TRINIDAD-2217 URL: https://issues.apache.org/jira/browse/TRINIDAD-2217 Project: MyFaces Trinidad Issue Type: Bug Reporter: Gabrielle Crawford Assignee: Gabrielle Crawford We have been calling markInitialState in our tagHandler since before JSF had partial state saving. In JSF 2 they support partial state saving, so the framework should always be the one calling markInitialState and we should remove it from our tag handlers, but there is a bug in the framework which means it doesn't always call markInitialState in render response, see http://java.net/jira/browse/JAVASERVERFACES-2285 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
