Re: [VOTE] release for myfaces core 2.0.0-beta
+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/1/27 Matthias Wessendorf mat...@apache.org +1 -Matthias On Wed, Jan 27, 2010 at 2:57 AM, Bruno Aranda brunoara...@gmail.com wrote: +1 2010/1/27 Leonardo Uribe lu4...@gmail.com: +1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta 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, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (EXTVAL-82) Add the EmptyValueAwareValidationStrategy annotation to the Length and Pattern Annotations
[
https://issues.apache.org/jira/browse/EXTVAL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805407#action_12805407
]
Rudy De Busscher commented on EXTVAL-82:
I did some more testing to verify compatibility with previous releases (1.2.2)
and standard JSF (without Extval)
Here are the results.
Myfaces 1.2.7
ExtVal 1.2.2
@Length(minimum=3, maximum=50) -- Validation error when field left empty
@Pattern(value={[a-z]{3,}}) -- Validation error when field left empty
ExtVal 1.2.3-SnapShot + javax.faces.VALIDATE_EMPTY_FIELDS = true
@Length(minimum=3, maximum=50) -- No validation error when field left
empty
@Pattern(value={[a-z]{3,}}) -- No validation error when field left
empty
ValidationInterceptor.isValidationStrategyCompatibleWithValue return
false since no EmptyValueAwareValidationStrategy annotation present
ExtVal 1.2.3-SnapShot + javax.faces.VALIDATE_EMPTY_FIELDS = false
@Length(minimum=3, maximum=50) -- No validation error when field left
empty
@Pattern(value={[a-z]{3,}}) -- No validation error when field left
empty
AbstractValidationInterceptor.validateValue because empty field and Web
parameter is set to false.
ExtVal 1.2.3-SnapShot + ExtVal-82 Implemented +
javax.faces.VALIDATE_EMPTY_FIELDS = false
@Length(minimum=3, maximum=50) -- No validation error when field left
empty
@Pattern(value={[a-z]{3,}}) -- No validation error when field left
empty
AbstractValidationInterceptor.validateValue because empty field and Web
parameter is set to false.
ExtVal 1.2.3-SnapShot + ExtVal-82 Implemented +
javax.faces.VALIDATE_EMPTY_FIELDS = true
@Length(minimum=3, maximum=50) -- Validation error when field left empty
@Pattern(value={[a-z]{3,}}) -- Validation error when field left empty
Since EmptyValueAwareValidationStrategy is now found
Myfaces 2.0.0-SNAPSHOT
ExtVal 2.0.3-SnapShot + javax.faces.VALIDATE_EMPTY_FIELDS = true
@Length(minimum=3, maximum=50) -- No validation error when field left
empty
@Pattern(value={[a-z]{3,}}) -- No validation error when field left
empty
ValidationInterceptor.isValidationStrategyCompatibleWithValue return
false since no EmptyValueAwareValidationStrategy annotation present
ExtVal 2.0.3-SnapShot + javax.faces.VALIDATE_EMPTY_FIELDS = false
@Length(minimum=3, maximum=50) -- No validation error when field left
empty
@Pattern(value={[a-z]{3,}}) -- No validation error when field left
empty
AbstractValidationInterceptor.validateValue because empty field and Web
parameter is set to false.
Without Extval
Myfaces 2.0.0-SNAPSHOT
javax.faces.VALIDATE_EMPTY_FIELDS = true
f:validateLength minimum=3 maximum=50/ -- Validation error when
field left empty
f:validateRegex pattern=[a-z]{3,}/ -- Validation error when field
left empty
javax.faces.VALIDATE_EMPTY_FIELDS = false
f:validateLength minimum=3 maximum=50/ -- No validation error when
field left empty
f:validateRegex pattern=[a-z]{3,}/ -- No validation error when field
left empty
UIInput.shouldValidateEmptyFields return false since web parameter is set
to false.
MyFaces 1.2.7
f:validateLength minimum=3 maximum=50/ -- No validation error when
field left empty
UIInput.validateValue doesn't do anything since the field is empty and not
required.
Add the EmptyValueAwareValidationStrategy annotation to the Length and
Pattern Annotations
--
Key: EXTVAL-82
URL: https://issues.apache.org/jira/browse/EXTVAL-82
Project: MyFaces Extensions Validator
Issue Type: Improvement
Components: Property Validation
Affects Versions: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
Reporter: Rudy De Busscher
Priority: Minor
Adding the EmptyValueAwareValidationStrategy allows in JSF 2.0 that Length
and Pattern validations are triggered (with the
javax.faces.VALIDATE_EMPTY_FIELDS parameter set).
They will cause a validation error with an empty string (Length annotation
with minimum set or Pattern) so the Required annotation is no longer needed.
Tested it out with ExtVal 2.0.3-SNAPSHOT and Myfaces 2.0.0-SNAPHOT (of 21/01)
and it works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1695) Lightweight dialogs broken with Firefox 3.6
[
https://issues.apache.org/jira/browse/TRINIDAD-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805424#action_12805424
]
Matthias Weßendorf commented on TRINIDAD-1695:
--
the 1.2.13 is out...
Lightweight dialogs broken with Firefox 3.6
---
Key: TRINIDAD-1695
URL: https://issues.apache.org/jira/browse/TRINIDAD-1695
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.12-core
Environment: Trinidad 1.2.12
JSF 1.2_14 majorra
Tomcat 6.0.20
Firefox 3.6
Reporter: Tobias Freier
Assignee: Matthias Weßendorf
Priority: Critical
Fix For: 1.2.13-core
We have a major problem with the lightweight dialogs and the new firefox 3.6.
It's just not working anymore.
In Firebug I get this error:
[object Object]
http://myserver/adf/jsLibs/Common1_2_12.js
Line 7042
[Break on this error] var a11=a10.getBoxObjectFor(a8);\n
TypeError:a10.getBoxObjectFor is not a function {
message=a10.getBoxObjectFor is not a function, more... }
Looks like Firefox killed the function getBoxObjectFor.
a10 is a Document
a8 is body
Code at this place is:
7037 if(_agent.isGecko)
7038 {
7039 TrUIUtils._getElemLoc=function(a8)
7040 {
7041 var a10=a8.ownerDocument;
7042 var a11=a10.getBoxObjectFor(a8);
7043 var a12={x:a11.screenX,y:a11.screenY};
7044 a11=a10.getBoxObjectFor(a10.documentElement);
7045 a12.x-=a11.screenX;
7046 a12.y-=a11.screenY;
7047 return a12;
7048 }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1701) Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup and possible other components non functional
Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup and possible other components non functional - Key: TRINIDAD-1701 URL: https://issues.apache.org/jira/browse/TRINIDAD-1701 Project: MyFaces Trinidad Issue Type: Bug Components: Components Environment: Bug is at least in trinidad 1.2.12 Reporter: Tobias Eisenträger This function getBoxObjectFor() seems to have been deprecated until 3.5.x, and has been removed with Firefox 3.6. I just updated FF and noticed that problem. This makes for example the tr:panelPopup method non functional. There might be other examples where this function has been used. I think someone who understands javascript good needs to search through the Trinidad sources and replace it with an alternative function? The panelPopup demo page: http://www.irian.at/trinidad-demo/faces/components/panelPopup.jspx works as an example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1701) Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup and possible other components non functional
[ https://issues.apache.org/jira/browse/TRINIDAD-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Eisenträger resolved TRINIDAD-1701. -- Resolution: Duplicate Fix Version/s: 1.2.13-core TRINIDAD-1695 1.2.13 fixes it Firefox 3.6 has removed the getBoxObjectFor() function - tr:panelPopup and possible other components non functional - Key: TRINIDAD-1701 URL: https://issues.apache.org/jira/browse/TRINIDAD-1701 Project: MyFaces Trinidad Issue Type: Bug Components: Components Environment: Bug is at least in trinidad 1.2.12 Reporter: Tobias Eisenträger Fix For: 1.2.13-core Original Estimate: 2h Remaining Estimate: 2h This function getBoxObjectFor() seems to have been deprecated until 3.5.x, and has been removed with Firefox 3.6. I just updated FF and noticed that problem. This makes for example the tr:panelPopup method non functional. There might be other examples where this function has been used. I think someone who understands javascript good needs to search through the Trinidad sources and replace it with an alternative function? The panelPopup demo page: http://www.irian.at/trinidad-demo/faces/components/panelPopup.jspx works as an example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Fwd: Google Summer of Code 2010 is On......
FYI -- Forwarded message -- From: Luciano Resende luckbr1...@gmail.com Date: Wed, Jan 27, 2010 at 2:34 AM Subject: Fwd: Google Summer of Code 2010 is On.. To: d...@community.apache.org FYI, GSoC 2010 is On... -- Forwarded message -- From: LH lho...@gmail.com Date: Tue, Jan 26, 2010 at 4:09 PM Subject: Google Summer of Code 2010 is On.. To: Google Summer of Code Discuss google-summer-of-code-disc...@googlegroups.com Hello everyone, Many of you were wondering if Google Summer of Code 2010 is on for 2010 and the answer is yes! We will begin accepting application from would-be mentoring organizations beginning March 8th at approximately 19:00 UTC, with applications closing on March 12th at 23:00 UTC. Students can apply between 19:00 UTC on March 29th to 19:00 UTC on April 9th. We will be updating the program website [0], including the FAQs [1], over the next few days. Not much is going to change except the timeline, though there are a few FAQs that will be added. If you have any questions in the interim please do send them to the list. Please note that questions about which project you should select, etc., will likely be responded to with depends on your skill set, so please take the time to do some research [2] about which project is right for you. While mentoring organizations for 2010 will be announced until March 18th, a great number of the projects that have participated in the past [3] will return once again in 2010. Of course, that's not a guarantee and we cannot accept every great project that applies. But if you want to get a jump start on your participation in GSoC 2010, considering lurking in the IRC channel of a past participating project and seeing what useful things you can learn about their code base and community. Check out project forums to see if it's a place you'd like to spend your time. I'll be sending a follow up message in a few minutes about what to expect in the next few days/weeks and how you can help Google Summer of Code 2010. Google Summer of Code 2010 is on! Celebrate! [0] - http://socghop.appspot.com [1] - http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2009/faqs [2] - http://delicious.com/gsoc2009 [3] - http://socghop.appspot.com/gsoc/program/accepted_orgs/google/gsoc2009 Cheers, LH -- Leslie Hawthorn Program Manager - Open Source Google Inc. http://code.google.com/opensource/ I blog here: http://google-opensource.blogspot.com - http://www.hawthornlandings.org -- You received this message because you are subscribed to the Google Groups Google Summer of Code Discuss group. To post to this group, send email to google-summer-of-code-disc...@googlegroups.com. To unsubscribe from this group, send email to google-summer-of-code-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-summer-of-code-discuss?hl=en. -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSOC]HTML5 RenderKit Project Structure
Hi ali, the Google Summer of code has been announced (see my other email). Regarding the strcuture, IMO this should be a separate project, that just targets to implement JSF widgets offered by HTML5. The implementation should be done with JSF 2.0+ tooling. So, not supporting older versions, e.g. JSF 1.x is totally fine (- goal?) IMO this work is related to Tomahawk. Once there is more code, we can talk about distribution: -myfaces core extension -standalone HTML5 renderkit (- need to find a (nice) name) etc -Matthias On Mon, Jan 25, 2010 at 12:05 AM, Ali Ok al...@aliok.com.tr wrote: Hi all, We have talked about HTML5 components on MyFaces earlier. I tried some HTML5 components and I think this project will be interesting. Now I want to create the project structure and start playing with the components. I want to learn how stuff are packed, how the components are generated, etc. Keeping in mind these HTML5 components will be a part of MyFaces 2.0 (I hope, someday), how can I set the correct project structure? Do you think changing Tomahawk 2.0 to HTML5 components project in my local workspace is a good idea? Or should I add my stuff into MyFaces 2.0 core? In fact, this question is: what is the correct place of HTML5 components and render kit? Will it be a seperate project, and distributed separately? Or will it be under MyFaces core and distributed with it? Thanks, Ali -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSoc] Google Summer of Code Idea
Hey Ali, the Google Summer of code has been announced (see my other email). Regarding this idea on HTML5 related stuff, I would like to sign as a mentor for it. @GAE: I saw your path; Jakob did a quick review. So, I hope we can commit that soon. Some more documentation, e.g. a guide or a tutorial would be nice :-) -Matthias On Wed, Jan 20, 2010 at 8:34 PM, Ali Ok al...@aliok.com.tr wrote: Hi all, I sent a couple of mails about MyFaces on Google App Engine GSOC proposal. But after some progress and a conversation with Matthias, I realized that it is too small for GSOC. And I am willing to implement HTML5 Renderkit. Meanwhile, I will work on GAE support in parallel. I will post my patch to JIRA after some -more- tests. Regards, Ali On Wed, Jan 6, 2010 at 11:52 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +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/1/6 Matthias Wessendorf mat...@apache.org as the mentioned behavior support already said, I'd like to see this ONLY for JSF2.0 (MyFaces 2.0) -Matze On Wed, Jan 6, 2010 at 8:35 AM, Matthias Wessendorf mat...@apache.org wrote: Hi guys, running into this document: http://diveintohtml5.org/forms.html I started playing with some of the new widgets in my Chromium browser (I wasn't aware that spinbox/sliders are part of HTML5). What about trying to find someone for a GSoC project, to add a (raw) HTML 5 renderkit? Bernd and I talked about a potential renderkit last time we saw each other, but now there is actually some (raw) support on it inside of some browsers... Why not introducing an hx:*** namespace that could contain stuff as the following: -hx:inputRangeSlider -hx:inputColor -hx:whatEverNewWidgetIsPartOfHTML5 / And/or some more functional stuff, like drag-and-drop: -fx:dragAndDrop... (could be done as a behavior) etc. What do folks think about that? -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GSoc] Google Summer of Code Idea
Hi Matthias, Thanks for your support. I think this GSOC will be cool:) Since this will be a seperate project, I will start modifiying my local Tomahawk code-base, and inspecting how it works, right away. About GAE, I've started preparing the document yesterday, but couldn't finished. I will send the APT document, and a tutorial explaining how to set up a Eclipse project, this night for sure. Best Regards, Ali On Wed, Jan 27, 2010 at 11:25 AM, Matthias Wessendorf mat...@apache.orgwrote: Hey Ali, the Google Summer of code has been announced (see my other email). Regarding this idea on HTML5 related stuff, I would like to sign as a mentor for it. @GAE: I saw your path; Jakob did a quick review. So, I hope we can commit that soon. Some more documentation, e.g. a guide or a tutorial would be nice :-) -Matthias On Wed, Jan 20, 2010 at 8:34 PM, Ali Ok al...@aliok.com.tr wrote: Hi all, I sent a couple of mails about MyFaces on Google App Engine GSOC proposal. But after some progress and a conversation with Matthias, I realized that it is too small for GSOC. And I am willing to implement HTML5 Renderkit. Meanwhile, I will work on GAE support in parallel. I will post my patch to JIRA after some -more- tests. Regards, Ali On Wed, Jan 6, 2010 at 11:52 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +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/1/6 Matthias Wessendorf mat...@apache.org as the mentioned behavior support already said, I'd like to see this ONLY for JSF2.0 (MyFaces 2.0) -Matze On Wed, Jan 6, 2010 at 8:35 AM, Matthias Wessendorf mat...@apache.org wrote: Hi guys, running into this document: http://diveintohtml5.org/forms.html I started playing with some of the new widgets in my Chromium browser (I wasn't aware that spinbox/sliders are part of HTML5). What about trying to find someone for a GSoC project, to add a (raw) HTML 5 renderkit? Bernd and I talked about a potential renderkit last time we saw each other, but now there is actually some (raw) support on it inside of some browsers... Why not introducing an hx:*** namespace that could contain stuff as the following: -hx:inputRangeSlider -hx:inputColor -hx:whatEverNewWidgetIsPartOfHTML5 / And/or some more functional stuff, like drag-and-drop: -fx:dragAndDrop... (could be done as a behavior) etc. What do folks think about that? -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0-beta
+1 regards Michael Am 27.01.2010 09:05, schrieb Gerhard Petracek: +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/1/27 Matthias Wessendorf mat...@apache.org mailto:mat...@apache.org +1 -Matthias On Wed, Jan 27, 2010 at 2:57 AM, Bruno Aranda brunoara...@gmail.com mailto:brunoara...@gmail.com wrote: +1 2010/1/27 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com: +1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com mailto:jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta 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, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (MYFACES-2480) @ResourceDependencies does not work on custom behaviors
[
https://issues.apache.org/jira/browse/MYFACES-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805449#action_12805449
]
Matthias Weßendorf commented on MYFACES-2480:
-
Ingo,
I know: http://svn.apache.org/viewvc?view=revisionrevision=903221
needed a quick fix...
Thanks for the patch, will review it.
@ResourceDependencies does not work on custom behaviors
---
Key: MYFACES-2480
URL: https://issues.apache.org/jira/browse/MYFACES-2480
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.0-alpha
Reporter: Matthias Weßendorf
Attachments: BehaviorResources.patch
I created a simple custom behavior, that requires (more ships :-) ) a simple
JS file. On the RI (run-time testing) it works. Not so on myfaces2 trunk
My class:
package net.wessendorf;
import java.util.EnumSet;
import java.util.Set;
import javax.faces.application.ResourceDependencies;
import javax.faces.application.ResourceDependency;
import javax.faces.component.behavior.ClientBehaviorBase;
import javax.faces.component.behavior.ClientBehaviorContext;
import javax.faces.component.behavior.ClientBehaviorHint;
import javax.faces.component.behavior.FacesBehavior;
@FacesBehavior(net.wessendorf.Confirm)
@ResourceDependencies({
@ResourceDependency(name=tester.js, library=wessi, target=head)
})
public class TestConfirmBehavior extends ClientBehaviorBase
{
@Override
public String getScript(ClientBehaviorContext behaviorContext)
{
return return confirm('Really');
}
@Override
public SetClientBehaviorHint getHints() {
return EnumSet.of(ClientBehaviorHint.SUBMITTING);
}
}
taglib.xml file:
facelet-taglib xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://wessendorf.net/behavior/namespace
tag
tag-nameconfirm/tag-name
behavior
behavior-idnet.wessendorf.Confirm/behavior-id
/behavior
/tag
/facelet-taglib
tester.js file:
test = function()
{
alert('HALLO JSF2');
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2513) Update examples from test web application 1.2 and merge with 2.0
Update examples from test web application 1.2 and merge with 2.0 Key: MYFACES-2513 URL: https://issues.apache.org/jira/browse/MYFACES-2513 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-alpha Reporter: Ingo Hofmann Update JSP examples from test-webapp 1.2 to facelets and merge the examples with the MyFaces 2.0 examples project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2480) @ResourceDependencies does not work on custom behaviors
[
https://issues.apache.org/jira/browse/MYFACES-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-2480.
-
Resolution: Fixed
Fix Version/s: 2.0.0-beta-2
Assignee: Matthias Weßendorf
annotation handling done in revs: 903211 and 903221
target and new test by Ingo Hofmann. Thanks Ingo
@ResourceDependencies does not work on custom behaviors
---
Key: MYFACES-2480
URL: https://issues.apache.org/jira/browse/MYFACES-2480
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.0-alpha
Reporter: Matthias Weßendorf
Assignee: Matthias Weßendorf
Fix For: 2.0.0-beta-2
Attachments: BehaviorResources.patch
I created a simple custom behavior, that requires (more ships :-) ) a simple
JS file. On the RI (run-time testing) it works. Not so on myfaces2 trunk
My class:
package net.wessendorf;
import java.util.EnumSet;
import java.util.Set;
import javax.faces.application.ResourceDependencies;
import javax.faces.application.ResourceDependency;
import javax.faces.component.behavior.ClientBehaviorBase;
import javax.faces.component.behavior.ClientBehaviorContext;
import javax.faces.component.behavior.ClientBehaviorHint;
import javax.faces.component.behavior.FacesBehavior;
@FacesBehavior(net.wessendorf.Confirm)
@ResourceDependencies({
@ResourceDependency(name=tester.js, library=wessi, target=head)
})
public class TestConfirmBehavior extends ClientBehaviorBase
{
@Override
public String getScript(ClientBehaviorContext behaviorContext)
{
return return confirm('Really');
}
@Override
public SetClientBehaviorHint getHints() {
return EnumSet.of(ClientBehaviorHint.SUBMITTING);
}
}
taglib.xml file:
facelet-taglib xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://wessendorf.net/behavior/namespace
tag
tag-nameconfirm/tag-name
behavior
behavior-idnet.wessendorf.Confirm/behavior-id
/behavior
/tag
/facelet-taglib
tester.js file:
test = function()
{
alert('HALLO JSF2');
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2511) Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly
[ https://issues.apache.org/jira/browse/MYFACES-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805465#action_12805465 ] Jakob Korherr commented on MYFACES-2511: Furthermore application.getDefaultValidatorInfo() should not include the BeanValidator. Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly - Key: MYFACES-2511 URL: https://issues.apache.org/jira/browse/MYFACES-2511 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr If javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR is set to true, the BeanValidator is not installed automatically on all input components. This already works fine. However, the BeanValidator can still be added manually via f:validateBean /, which is not handled correctly at the moment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2514) An empty default-validators in faces-config should disable default validators
An empty default-validators in faces-config should disable default validators --- Key: MYFACES-2514 URL: https://issues.apache.org/jira/browse/MYFACES-2514 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2511) Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly
[ https://issues.apache.org/jira/browse/MYFACES-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2511. Resolution: Fixed Fix Version/s: 2.0.0-beta-2 Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly - Key: MYFACES-2511 URL: https://issues.apache.org/jira/browse/MYFACES-2511 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr Fix For: 2.0.0-beta-2 If javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR is set to true, the BeanValidator is not installed automatically on all input components. This already works fine. However, the BeanValidator can still be added manually via f:validateBean /, which is not handled correctly at the moment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-1481) t:inputCalendar requiredMessage problem
t:inputCalendar requiredMessage problem
---
Key: TOMAHAWK-1481
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1481
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Calendar
Affects Versions: 1.1.8
Reporter: Klaus Schuster
Using the t:inputCalendar together with an facelet, with dynamically using the
required attribute, an requiredMessage could only be fixed coded to see the
result.
example:
t:inputCalendar id=#{id}#{linkPrefix} forceId=true title=#{title}
value=#{value}
disabled=#{disabled} renderAsPopup=true
popupDateFormat=#{empty pattern ? 'dd.MM.' : pattern}
converter=date validator=date futureAllowed=#{empty
futureAllowed ? 'false' : 'true'}
styleClass=#{styleClass}
popupTodayString=#{msg.aktdate}:
renderPopupButtonAsImage=true
readonly=true
popupButtonImageUrl=/images/calendar.gif
imageLocation=/images/calendar required=#{required}
requiredMessage=#{requiredMessage}
In this case, nothing is shown, if required is true, and a text lies behind
requiredMessage variable.
If I put a hardcoded text, everything works:
example:
t:inputCalendar id=#{id}#{linkPrefix} forceId=true title=#{title}
value=#{value}
disabled=#{disabled} renderAsPopup=true
popupDateFormat=#{empty pattern ? 'dd.MM.' : pattern}
converter=date validator=date futureAllowed=#{empty
futureAllowed ? 'false' : 'true'}
styleClass=#{styleClass}
popupTodayString=#{msg.aktdate}:
renderPopupButtonAsImage=true
readonly=true
popupButtonImageUrl=/images/calendar.gif
imageLocation=/images/calendar required=#{required}
requiredMessage=ERROR TEXT HERE IS SHOWN
Same problem using the f:param attribute in case of the required attribute
(Nothing is shown in case of error):
t:inputCalendar id=#{id}#{linkPrefix} forceId=true title=#{title}
value=#{value}
disabled=#{disabled} renderAsPopup=true
popupDateFormat=#{empty pattern ? 'dd.MM.' : pattern}
converter=date validator=date futureAllowed=#{empty
futureAllowed ? 'false' : 'true'}
styleClass=#{styleClass}
popupTodayString=#{msg.aktdate}:
renderPopupButtonAsImage=true
readonly=true
popupButtonImageUrl=/images/calendar.gif
imageLocation=/images/calendar required=#{required}
f:attribte name=requiredMessage name=#{requiredMessage} /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2515) Archetype for MyFaces 2.0 hekllo world app
Archetype for MyFaces 2.0 hekllo world app -- Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-2515) Archetype for MyFaces 2.0 hekllo world app
[ https://issues.apache.org/jira/browse/MYFACES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Kurz updated MYFACES-2515: -- Status: Patch Available (was: Open) Archetype for MyFaces 2.0 hekllo world app -- Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz Attachments: MYFACES-2515.patch I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2515) Archetype for MyFaces 2.0 hello world app
[ https://issues.apache.org/jira/browse/MYFACES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805530#action_12805530 ] Matthias Weßendorf commented on MYFACES-2515: - what's up with the @author tags ? Archetype for MyFaces 2.0 hello world app - Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz Attachments: MYFACES-2515.patch I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2515) Archetype for MyFaces 2.0 hello world app
[ https://issues.apache.org/jira/browse/MYFACES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805531#action_12805531 ] Matthias Weßendorf commented on MYFACES-2515: - would it be possible to have another archetype, that combines MyFaces2 w/ apache openwebbeans ? why ? @ManagedBean(name = helloWorld) @RequestScoped = using 299/330 annotations is way nicer... I can send you a set-up, if you like. -Matthias Archetype for MyFaces 2.0 hello world app - Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz Attachments: MYFACES-2515.patch I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-54) Add also annotation handling in the bytecode dependency scanner
[ https://issues.apache.org/jira/browse/EXTSCRIPT-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-54. -- Resolution: Fixed Add also annotation handling in the bytecode dependency scanner --- Key: EXTSCRIPT-54 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-54 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2515) Archetype for MyFaces 2.0 hello world app
[ https://issues.apache.org/jira/browse/MYFACES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805570#action_12805570 ] Michael Kurz commented on MYFACES-2515: --- Sure, I could do another archetype with openwebbeans. If you send me your set-up I will have a look at it. Should the @author tags be removed completely? I copied parts of the archetype from the old one because I had some troubles with the created archetype. I think there is a new version of the archetype plugin with some changes in the way an archetype is created. Archetype for MyFaces 2.0 hello world app - Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz Attachments: MYFACES-2515.patch I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1697) New Trinidad Components Showcase demo application
[ https://issues.apache.org/jira/browse/TRINIDAD-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Catalin Kormos resolved TRINIDAD-1697. -- Resolution: Fixed Code integrated. Many thanks Cosmin, great work! New Trinidad Components Showcase demo application - Key: TRINIDAD-1697 URL: https://issues.apache.org/jira/browse/TRINIDAD-1697 Project: MyFaces Trinidad Issue Type: New Feature Components: Components Affects Versions: 1.2.14-core Reporter: Cosmin Martinconi Assignee: Catalin Kormos Fix For: 1.2.14-core Attachments: trinidad-components-showcase.zip A new and improved Trinidad components showcase demo application: - the demo is working only with facelets (there is no jsp version) - we tried to build it so it can be searched online also, currently tried with Google Custom Search, but this didn't work out so smoothly so far. - in general, it replicates the examples available already for Trinidad in the existing demo, in some places slightly or more improved. - it tries to provide a platform on which to build much more demos as required as there can be always new ideas about demoing a meaningfull use case on Trinidad, or some component behavior. I have attached the zip file, containing the source code of the showcase Regards, Cosmin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-1472) Add Support for new Resource API in tomahawk 2.0 module
[ https://issues.apache.org/jira/browse/TOMAHAWK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805681#action_12805681 ] Leonardo Uribe commented on TOMAHAWK-1472: -- In order to provide the community a way to contribute or hear how will be tomahawk for jsf 2.0 module, it is better to do a full discussion of this issue here. First of all we need a comparison between Resource API and Tomahawk AddResource API, to identify possible problems of use one of another. TOMAHAWK RESOURCE API The AddResource api is used for add and server resources. It is capable of serve static and dynamic resources. Below there is a list of the classes involved with a brief description of the purpose: AddResourceFactory: This class provides the ability to instantiate AddResource objects. By default it check if the environment is correctly set. AddResource: This interface defines methods necessary to render links to resources used by custom components. Mostly used to avoid having to include [script src=...][/script] in the head of the pages before using a component. ResourceLoader: A class which can interpret the URI generated by a corresponding ResourceHandler implementation, locate that resource and write it to the servlet response stream. ResourceProvider: A class which can provide the resource itself. It represents a resource like Resource class in jsf 2.0, but it is used only on the algorithm that serve resources ResourceHandler: Represents a single resource that a component in a page needs a browser to fetch. This class helps generate the URI that is emitted into the page, and specifies the class that should be invoked to handle the request for that URI when the browser makes it. Below there is a list of components using AddResource api: t:inputCalendar t:inputDate t:captcha t:documentHead t:dojoInitializer t:inputHtml t:inputTextHelp t:jsValueChangeListener t:panelNavigation2 t:jscookMenu t:selectManyPicklist t:popup t:schedule t:swapImage t:panelTab t:togglePanel t:tree t:tree2 t:stylesheet It is possible to use several strategies to put resources in a web page: NonBufferingAddResource: Put the link or script directly on the web page, in other words, it inserts them into the body of the page instead. Used in portlets. StreamingAddResource: Works like NonBufferingAddResource, but has a hack with t:documentHead to solve the problem with css styles on head section. DefaultAddResource: When used together with the ExtensionsFilter, this class can allow components in the body of a page to emit script and stylesheet references into the page head section. The relevant methods on this object simply queue the changes, and when the page is complete the ExtensionsFilter calls back into this class to allow it to insert the commands into the buffered response. There are different ways to serve resources: MyFacesResourceLoader: Look the javascript file scanning the package org.apache.myfaces.custom. StreamingResourceLoader: Allows the hack with t:documentHead to solve the problem with css styles. CAPTCHARenderer: Render the image used by t:captcha. NEW JSF 2.0 RESOURCE API In JSF 2.0 a new api was introduced to solve the problem of Resource Handling. This tags were introduced in this version: h:head h:body h:outputScript h:outputStylesheet This tags DO NOT exists in JSP, because all new features are for facelets, now bundled with JSF. By default, it only handle static resources. DISCUSSION If we load all resources used by components with the new api, pages created with JSF 1.2 or earlier will not work on JSP as is. We could implement a variant of h:head, h:body, h:outputScript and h:outputStylesheet that works for jsp. t:head and t:body are easy but t:outputScript and t:outputStylesheet cannot be relocated on the component tree, instead we need to create a copy to register it in UIViewRoot, using a custom JSP Tag class. The current implementation of javax.faces.webapp.UIComponentELTag calls Application.createComponent(componentType) and Application.createComponent(ValueExpression, FacesContext, componentType). The problem with this one is that renderers are not scanned looking for ResourceDependency or ListenerFor annotations, but it is not a big deal, because we can put those annotations on component class instead. If someone wants to run tomahawk using its resource api, there is no technical reason why not run tomahawk12 with myfaces core 2.0 in JSP. Use tomahawk resource api and the new jsf 2.0 resource api seems to be confusing. Finally we end in all renderers with the following: if
[jira] Issue Comment Edited: (MYFACES-2504) Google App Engine Support
[ https://issues.apache.org/jira/browse/MYFACES-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805695#action_12805695 ] Ali Ok edited comment on MYFACES-2504 at 1/27/10 11:31 PM: --- Here is the patch for APT doc. Need to edit version information. was (Author: aliok-com-tr): Here is the patch for APT doc. Google App Engine Support - Key: MYFACES-2504 URL: https://issues.apache.org/jira/browse/MYFACES-2504 Project: MyFaces Core Issue Type: Improvement Components: JSR-252, JSR-314 Affects Versions: 1.2.8, 2.0.0-alpha Environment: Google App Engine 1.3 Reporter: Ali Ok Priority: Minor Attachments: 2504-2.diff, 2504-3.diff, 2504-doc.diff, 2504.diff Support for Google App Engine for MyFaces 1.2 and 2.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1619) Width attribute of tr:column is not working
[ https://issues.apache.org/jira/browse/TRINIDAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamallan Uthaman updated TRINIDAD-1619: --- Resolution: Fixed Fix Version/s: 1.2.14-core Status: Resolved (was: Patch Available) Width attribute of tr:column is not working -- Key: TRINIDAD-1619 URL: https://issues.apache.org/jira/browse/TRINIDAD-1619 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.12-core Environment: Safari 4.0 Reporter: Mamallan Uthaman Priority: Minor Fix For: 1.2.14-core Attachments: TRINIDAD-1619-1.2.12.1.patch, TRINIDAD-1619-1.2.12.2.patch, TRINIDAD-1619.patch In the case where all columns of a tr:table have empty headerText attributes, width attributes of the columns are not working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1617) In mobile browsers, PPR is not supported in TR:PANELTABBED
[ https://issues.apache.org/jira/browse/TRINIDAD-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamallan Uthaman updated TRINIDAD-1617: --- Resolution: Fixed Fix Version/s: 1.2.13-core Status: Resolved (was: Patch Available) In mobile browsers, PPR is not supported in TR:PANELTABBED - Key: TRINIDAD-1617 URL: https://issues.apache.org/jira/browse/TRINIDAD-1617 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.12-core Environment: BlackBerry 4.7 Reporter: Mamallan Uthaman Priority: Minor Fix For: 1.2.13-core Attachments: TRINIDAD-1617.patch In mobile browsers, only full-page submit is supported for TR:PANELTABBED. Also in the case of Nokia S60, TR:PANELPABBED is not working as it is not submittable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1616) NOKIA S60 NOT SUPPORTING TR:NAVIGATIONPANE
[ https://issues.apache.org/jira/browse/TRINIDAD-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamallan Uthaman updated TRINIDAD-1616: --- Resolution: Fixed Fix Version/s: 1.2.13-core Status: Resolved (was: Patch Available) NOKIA S60 NOT SUPPORTING TR:NAVIGATIONPANE Key: TRINIDAD-1616 URL: https://issues.apache.org/jira/browse/TRINIDAD-1616 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.12-core Environment: NOKIA S60 Reporter: Mamallan Uthaman Priority: Minor Fix For: 1.2.13-core Attachments: TRINIDAD-1616.patch Nokia's webkit browser is not supporting tr:navigationPane if its hint attribute is 'tab'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1618) In mobile browsers, styleClass for the detailstamp facet of tr:table is not rendered
[ https://issues.apache.org/jira/browse/TRINIDAD-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamallan Uthaman updated TRINIDAD-1618: --- Resolution: Fixed Fix Version/s: 1.2.13-core Status: Resolved (was: Patch Available) In mobile browsers, styleClass for the detailstamp facet of tr:table is not rendered --- Key: TRINIDAD-1618 URL: https://issues.apache.org/jira/browse/TRINIDAD-1618 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.12-core Environment: Windows Mobile 6 Reporter: Mamallan Uthaman Priority: Minor Fix For: 1.2.13-core Attachments: TRINIDAD-1618-branch-1.2.12.2.patch, TRINIDAD-1618.patch In the case of mobile browsers, styleClass for the detailStamp facet of tr:table is not rendered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2515) Archetype for MyFaces 2.0 hello world app
[ https://issues.apache.org/jira/browse/MYFACES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805762#action_12805762 ] Leonardo Uribe commented on MYFACES-2515: - We need a release of myfaces-archetypes. I usually use the snapshot ones, because they have some corrections. I'll keep an eye on this one and after commit the two new archetypes, I'll do a release of this project. Archetype for MyFaces 2.0 hello world app - Key: MYFACES-2515 URL: https://issues.apache.org/jira/browse/MYFACES-2515 Project: MyFaces Core Issue Type: New Feature Reporter: Michael Kurz Attachments: MYFACES-2515.patch I created an archetype for a MyFaces 2.0 hello world app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1647) HTML Escapes writes out characters illegal in HTML
[ https://issues.apache.org/jira/browse/TRINIDAD-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805789#action_12805789 ] Jeanne Waldman commented on TRINIDAD-1647: -- See TRINIDAD-1655 Fix to JIRA-1647 introduced bug where HTMLEscapes._writeText isn't paying attention to startIndex This is needed as well for any backporting. HTML Escapes writes out characters illegal in HTML -- Key: TRINIDAD-1647 URL: https://issues.apache.org/jira/browse/TRINIDAD-1647 Project: MyFaces Trinidad Issue Type: Bug Environment: All Reporter: Blake Sullivan Assignee: Blake Sullivan Fix For: 1.2.13-core Attachments: datePicker.gif, HTMLEscapes.patch, JIRA_1647_1_2_12_2.patch Original Estimate: 24h Remaining Estimate: 24h The HTML specification disallows certain code points from appearing in HTML files (XML has essentially the same list, minus the high ISO characters) as specified in http://www.w3.org/TR/REC-html40/sgml/sgmldecl.html. The Trinidad HtmlEscapes utilities allow the low control characters and the high characters that are technically outside of Unicode to be output. This causes problems if the content is validated. The fix is to use numeric character references such as #1; rather than outputting code point 1 directly. In addition, Internet Explorer has a bug where #0; is output as #0; so it is preferable to suppress this character rather then outputting it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
