Considering the huge number of responses in this thread, this is
obviously a big problem. While there were good suggestions on how to
improve the situation, with all of them, we are only making (better)
alternatives to the broken base functionality. And yes, some say it's
not really broken because
[
http://issues.apache.org/jira/browse/MYFACES-877?page=comments#action_12358544
]
Kalle Korhonen commented on MYFACES-877:
... and by specification, h:outputText isn't supposed to render a span tag
around the text if no styleclass is spec
[
http://issues.apache.org/jira/browse/MYFACES-877?page=comments#action_12358543
]
Kalle Korhonen commented on MYFACES-877:
Not a bug, JSF EL notation does not import the Tiles attribute. Use
tag to
import it into a JSP scope of your choice
[
http://issues.apache.org/jira/browse/MYFACES-710?page=comments#action_12332321
]
Kalle Korhonen commented on MYFACES-710:
IMHO, it definitely should work in both modes. If the maySelectInFuture gets
accepted in the mainline, I'm sure we
[
http://issues.apache.org/jira/browse/MYFACES-674?page=comments#action_12331674
]
Kalle Korhonen commented on MYFACES-674:
JavaBean spec section 8.3 specifies design patterns for properties. The default
is get and in addition 8.3.2 defines is for
[
http://issues.apache.org/jira/browse/MYFACES-272?page=comments#action_12324510
]
Kalle Korhonen commented on MYFACES-272:
We are done with our in-house testing and everything worked as expected. I've
personally tested with simple example
[ http://issues.apache.org/jira/browse/MYFACES-272?page=all ]
Kalle Korhonen updated MYFACES-272:
---
Attachment: myfaces-272-conditionallyEncodeChars.patch
This is a slightly modified version of the previous patch, built against
MyFaces head on 09/01
[
http://issues.apache.org/jira/browse/MYFACES-435?page=comments#action_12319738
]
Kalle Korhonen commented on MYFACES-435:
Yeah, there's some pressure on our side as well to get the patch in into the
mainline. I've been working on
[
http://issues.apache.org/jira/browse/MYFACES-435?page=comments#action_12319547
]
Kalle Korhonen commented on MYFACES-435:
If I understood the issue correctly (not sure about the "render the unicode
text as jsp" part) this should be
[
http://issues.apache.org/jira/browse/MYFACES-402?page=comments#action_12318673
]
Kalle Korhonen commented on MYFACES-402:
Correct. You could use j4j:param within a form to pass parameters with the
submit.
> Can't put f:param or f:attri
[
http://issues.apache.org/jira/browse/MYFACES-272?page=comments#action_12318183
]
Kalle Korhonen commented on MYFACES-272:
I'm very surprised that this change could cause double output, unless, you
intentionally set the encoding to UTF
[
http://issues.apache.org/jira/browse/MYFACES-279?page=comments#action_12313171
]
Kalle Korhonen commented on MYFACES-279:
I sort of agree with Bruno that the technical message might confuse users, but
in many cases it might also make sense to
[ http://issues.apache.org/jira/browse/MYFACES-272?page=all ]
Kalle Korhonen updated MYFACES-272:
---
Attachment: myfaces-272-conditionallyEncodeChars.patch
Patch created against the latest code from SVN.
I generally don't like the quality of co
-272
URL: http://issues.apache.org/jira/browse/MYFACES-272
Project: MyFaces
Type: Improvement
Versions: Nightly Build
Reporter: Kalle Korhonen
Encoding all non-latin characters is unnecessary if the response specifies
UTF-8 as character encoding and causes a major
[
http://issues.apache.org/jira/browse/MYFACES-47?page=comments#action_66947 ]
Kalle Korhonen commented on MYFACES-47:
---
I can assure you that pageIndexVar is not read-only (and if you think about it,
it cannot be), since we are currently using a
[
http://issues.apache.org/jira/browse/MYFACES-230?page=comments#action_65691 ]
Kalle Korhonen commented on MYFACES-230:
The patch breaks characters represented with full 8-bits in Latin-1 character
set for obvious reasons (while the actual
[ http://issues.apache.org/jira/browse/MYFACES-230?page=all ]
Kalle Korhonen updated MYFACES-230:
---
Attachment: myfaces-utf8resourcebundle.patch
This patch was made on 2005-05-03 just before the move to SVN. I'm having
problems with connecting t
Reporter: Kalle Korhonen
Priority: Minor
Struts supports UTF-8 encoded property files and caching of property values
with its PropertyMessageResources class. MyFaces uses standard Java
ResourceBundle and its PropertyResourceBundle, which only allows Latin-1
encoded property files
[ http://issues.apache.org/jira/browse/MYFACES-199?page=all ]
Kalle Korhonen updated MYFACES-199:
---
Attachment: myfaces-popcalendar.patch
Patch created against src synched to CVS on 2005-04-19. Simply commented out
setting the src property when the
: Kalle Korhonen
Priority: Minor
When image objects for the calendar are created in the dom, the src property
was also set, which causes them to be requested when the scripts is parsed.
However, the default path is wrong and four unnecessary requests are made. The
actual path is set later
[
http://issues.apache.org/jira/browse/MYFACES-152?page=comments#action_61975 ]
Kalle Korhonen commented on MYFACES-152:
I don't know too much about this, so ignore if I'm way off. But couldn't we add
the dummyForm and Javas
[
http://issues.apache.org/jira/browse/MYFACES-145?page=comments#action_61404 ]
Kalle Korhonen commented on MYFACES-145:
Since I implemented this component, I guess my responsibility to fix it as
well. The component definitely shouldn't
22 matches
Mail list logo