A non-final, expert community draft of JSF 2.1 specification available on java.net.
Hello Ed announced an update of the jsf spec on twitter: edburns: http://bit.ly/c5CSfD non-final, expert community draft of JSF 2.1 specification available on java.net. --http://www.twitter.com/edburns/status/24793552027
[jira] Created: (EXTCDI-57) revisit Conversation#end
revisit Conversation#end Key: EXTCDI-57 URL: https://issues.apache.org/jira/browse/EXTCDI-57 Project: MyFaces CODI Issue Type: Task Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek we should think about the naming of this important api, because std. cdi conversations offer the same method. codi conversations are very similar to orchestra conversations. in orchestra #end means that the conversation gets terminated immediately. currently we have the same with codi conversations. if we would like to add an additional api which terminates the conversation after the rendering process (= behavior of std. cdi conversations), we would have to introduce a name which might confuse users. we have the following options: #1: renaming #end to #close - it's more clear to users that it works differently (compared to std. cdi conversations). so we still have #end if we add an additional api for terminating the conversation at the end of the request. if we won't introduce the additional api, we still have a method which indicates that the termination process works differently compared to std. cdi conversations. the only disadvantage is that it isn't intuitive for users who used orchestra. #2: keeping the current api (#end) for terminating the conversation immediately. so we will need a name for an api which ends the conversation after the rendering process. (we could use #close. but then we have #end which works differently (compared to std. cdi conversations) and #close also doesn't really express the difference (and other names might sound strange). so we might end up with confused users.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (EXTCDI-57) revisit Conversation#end
+1 for #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/9/18 Gerhard Petracek (JIRA) dev@myfaces.apache.org revisit Conversation#end Key: EXTCDI-57 URL: https://issues.apache.org/jira/browse/EXTCDI-57 Project: MyFaces CODI Issue Type: Task Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek we should think about the naming of this important api, because std. cdi conversations offer the same method. codi conversations are very similar to orchestra conversations. in orchestra #end means that the conversation gets terminated immediately. currently we have the same with codi conversations. if we would like to add an additional api which terminates the conversation after the rendering process (= behavior of std. cdi conversations), we would have to introduce a name which might confuse users. we have the following options: #1: renaming #end to #close - it's more clear to users that it works differently (compared to std. cdi conversations). so we still have #end if we add an additional api for terminating the conversation at the end of the request. if we won't introduce the additional api, we still have a method which indicates that the termination process works differently compared to std. cdi conversations. the only disadvantage is that it isn't intuitive for users who used orchestra. #2: keeping the current api (#end) for terminating the conversation immediately. so we will need a name for an api which ends the conversation after the rendering process. (we could use #close. but then we have #end which works differently (compared to std. cdi conversations) and #close also doesn't really express the difference (and other names might sound strange). so we might end up with confused users.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] Release Tobago 1.0.29
The vote has passed with the following results: +1 werpu (binding) matzew (binding) lofwyr (binding) bommel (binding) I will proceed with the next steps. Regards Bernd On Fri, Sep 17, 2010 at 8:30 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Here is my +1 Regards Bernd On Fri, Sep 17, 2010 at 10:08 AM, Udo Schnurpfeil u...@schnurpfeil.de wrote: +1 Am 15.09.10 09:51, schrieb Matthias Wessendorf: +1 On Wed, Sep 15, 2010 at 9:45 AM, Werner Punzwerner.p...@gmail.com wrote: +1 Am 15.09.10 08:30, schrieb Bernd Bohmann: Hello again, I would like to release Tobago 1.0.29. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315262 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-025/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd
AW: [jira] Created: (EXTCDI-57) revisit Conversation#end
+1 for #1 Yes, is is obvious that close() closes immediately. Ciao, Mario Von: Gerhard [mailto:gerhard.petra...@gmail.com] Gesendet: Samstag, 18. September 2010 17:52 An: MyFaces Development Betreff: Re: [jira] Created: (EXTCDI-57) revisit Conversation#end +1 for #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/9/18 Gerhard Petracek (JIRA) dev@myfaces.apache.org revisit Conversation#end Key: EXTCDI-57 URL: https://issues.apache.org/jira/browse/EXTCDI-57 Project: MyFaces CODI Issue Type: Task Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek we should think about the naming of this important api, because std. cdi conversations offer the same method. codi conversations are very similar to orchestra conversations. in orchestra #end means that the conversation gets terminated immediately. currently we have the same with codi conversations. if we would like to add an additional api which terminates the conversation after the rendering process (= behavior of std. cdi conversations), we would have to introduce a name which might confuse users. we have the following options: #1: renaming #end to #close - it's more clear to users that it works differently (compared to std. cdi conversations). so we still have #end if we add an additional api for terminating the conversation at the end of the request. if we won't introduce the additional api, we still have a method which indicates that the termination process works differently compared to std. cdi conversations. the only disadvantage is that it isn't intuitive for users who used orchestra. #2: keeping the current api (#end) for terminating the conversation immediately. so we will need a name for an api which ends the conversation after the rendering process. (we could use #close. but then we have #end which works differently (compared to std. cdi conversations) and #close also doesn't really express the difference (and other names might sound strange). so we might end up with confused users.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. smime.p7s Description: S/MIME cryptographic signature
Re: AW: [jira] Created: (EXTCDI-57) revisit Conversation#end
+1 LieGrue, strub --- On Sat, 9/18/10, Mario Ivankovits ma...@ops.co.at wrote: From: Mario Ivankovits ma...@ops.co.at Subject: AW: [jira] Created: (EXTCDI-57) revisit Conversation#end To: MyFaces Development dev@myfaces.apache.org Date: Saturday, September 18, 2010, 7:36 PM +1 for #1 Yes, is is obvious that close() closes immediately. Ciao,Mario Von: Gerhard [mailto:gerhard.petra...@gmail.com] Gesendet: Samstag, 18. September 2010 17:52 An: MyFaces Development Betreff: Re: [jira] Created: (EXTCDI-57) revisit Conversation#end +1 for #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/9/18 Gerhard Petracek (JIRA) dev@myfaces.apache.orgrevisit Conversation#end Key: EXTCDI-57 URL: https://issues.apache.org/jira/browse/EXTCDI-57 Project: MyFaces CODI Issue Type: Task Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek we should think about the naming of this important api, because std. cdi conversations offer the same method. codi conversations are very similar to orchestra conversations. in orchestra #end means that the conversation gets terminated immediately. currently we have the same with codi conversations. if we would like to add an additional api which terminates the conversation after the rendering process (= behavior of std. cdi conversations), we would have to introduce a name which might confuse users. we have the following options: #1: renaming #end to #close - it's more clear to users that it works differently (compared to std. cdi conversations). so we still have #end if we add an additional api for terminating the conversation at the end of the request. if we won't introduce the additional api, we still have a method which indicates that the termination process works differently compared to std. cdi conversations. the only disadvantage is that it isn't intuitive for users who used orchestra. #2: keeping the current api (#end) for terminating the conversation immediately. so we will need a name for an api which ends the conversation after the rendering process. (we could use #close. but then we have #end which works differently (compared to std. cdi conversations) and #close also doesn't really express the difference (and other names might sound strange). so we might end up with confused users.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTCDI-58) support for @Inject in converters and validators
support for @Inject in converters and validators
Key: EXTCDI-58
URL: https://issues.apache.org/jira/browse/EXTCDI-58
Project: MyFaces CODI
Issue Type: New Feature
Components: JEE-JSF12-Module, JEE-JSF20-Module
Reporter: Gerhard Petracek
the qualifier annotation @Advanced should be re-used as marker annotation for
marking jsf converters and validators which should benefit from dependency
injection.
example in combination with jsf2:
@Advanced
@FacesValidator(...)
public class DependencyInjectionAwareValidator implements Validator
{
@Inject
private CustomValidationService customValidationService;
public void validate(FacesContext ctx, UIComponent component, Object value)
throws ValidatorException
{
Violation violation = this.customValidationService.validate(value);
//...
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTCDI-58) support for @Inject in converters and validators
[
https://issues.apache.org/jira/browse/EXTCDI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved EXTCDI-58.
Fix Version/s: 1.0.0-SNAPSHOT
Resolution: Fixed
support for @Inject in converters and validators
Key: EXTCDI-58
URL: https://issues.apache.org/jira/browse/EXTCDI-58
Project: MyFaces CODI
Issue Type: New Feature
Components: JEE-JSF12-Module, JEE-JSF20-Module
Reporter: Gerhard Petracek
Fix For: 1.0.0-SNAPSHOT
the qualifier annotation @Advanced should be re-used as marker annotation for
marking jsf converters and validators which should benefit from dependency
injection.
example in combination with jsf2:
@Advanced
@FacesValidator(...)
public class DependencyInjectionAwareValidator implements Validator
{
@Inject
private CustomValidationService customValidationService;
public void validate(FacesContext ctx, UIComponent component, Object value)
throws ValidatorException
{
Violation violation = this.customValidationService.validate(value);
//...
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
