Hi,
When developing the AJAX part of MyFaces 2.0 we encountered 2 locations
within the jsdoc part of the spec we'd propose for enhancement.
The first is about the hidden inputs for view state: The jsdocs for
jsf.ajax.response imply that each hidden input receives the id
Hi Werner,
After some testing with \s*html[^]*(.*)\/\s*html[^]* I couldn't
get it to work properly. Instead I used
var htmlStartEx = /\s*html[^]*/gi;
var htmlEndEx = /\/\s*html[^]*/gi;
and substring similar to Mojarra (same for head and body). Your approach
would be a
Hey everyone,
I completed a migration to Trinidad to allow it to work with either
Portlet 1.0 or Portlet 2.0. Portlet 2.0 containers will support AJAX.
So here is my problem. In order to support extra functionality of
Portlet 2.0, I need to compile against a Portlet 2.0 container. Most of
Ganesh,
have you filed an issue on their bug tracker ?
-M
On Tue, Apr 21, 2009 at 9:10 AM, Ganesh gan...@j4fry.org wrote:
Hi,
When developing the AJAX part of MyFaces 2.0 we encountered 2 locations
within the jsdoc part of the spec we'd propose for enhancement.
The first is about the
Theme property 'fontWidth' not found for renderer
-
Key: TOBAGO-752
URL: https://issues.apache.org/jira/browse/TOBAGO-752
Project: MyFaces Tobago
Issue Type: Bug
Components: Themes
[
https://issues.apache.org/jira/browse/TOBAGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Bunge updated TOBAGO-752:
--
Status: Patch Available (was: Open)
Theme property 'fontWidth' not found for renderer
Yes I agree Matthias. Anyone else have a contrary opinion?
Matthias Wessendorf wrote:
On Tue, Apr 21, 2009 at 10:23 AM, Scott O'Bryan darkar...@gmail.com wrote:
Hey everyone,
I completed a migration to Trinidad to allow it to work with either Portlet
1.0 or Portlet 2.0. Portlet 2.0
[
https://issues.apache.org/jira/browse/TOBAGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber updated TOBAGO-752:
Resolution: Fixed
Fix Version/s: 1.1.0
1.0.21
Status: Resolved
Update UIViewRoot to latest spec draft
--
Key: MYFACES-2205
URL: https://issues.apache.org/jira/browse/MYFACES-2205
Project: MyFaces Core
Issue Type: Task
Components: JSR-314
Affects
[
https://issues.apache.org/jira/browse/MYFACES-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701182#action_12701182
]
Matthias Weßendorf commented on MYFACES-1879:
-
Leonardo is there something
Implement javax.faces.view.ViewMetadata and associated methods
--
Key: MYFACES-2206
URL: https://issues.apache.org/jira/browse/MYFACES-2206
Project: MyFaces Core
Issue Type: Task
Hi,
Here's the response from Roger on my request for an enhancement of the
JSF 2.0 spec.
Best Regards,
Ganesh
Original-Nachricht
Betreff: Re: jsdoc spec enhancement request from MyFaces 2.0
development team
Datum: Tue, 21 Apr 2009 09:02:27 -0400
Von:Roger Kitain
Hi Matthias, Simon (K.) and Werner,
Sorry I need to come back on this again. We had agreed on putting the
extension attributes within f:attribute tags nested in f:ajax to avoid
compatibility issues with other implementations. In the meantime I
realized that f:ajax is a facelets-only tag, so
On Tue, Apr 21, 2009 at 6:42 PM, Ganesh gan...@j4fry.org wrote:
Hi Matthias, Simon (K.) and Werner,
no need to name only a few folks.
Choosing the right subject will bring attention
to folks that are interested ;-)
Sorry I need to come back on this again. We had agreed on putting the
I was wondering if we would want to create maven archetypes for
setting up trinidad, tomahawk, and other projects as a war file that
users can use to start a test case. Basically it would create a war
pom with a single page and a single managed bean with jetty support
built in so that it would be
+1 !!!
On Tue, Apr 21, 2009 at 10:32 AM, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
I was wondering if we would want to create maven archetypes for
setting up trinidad, tomahawk, and other projects as a war file that
users can use to start a test case. Basically it would create a
I will rework it on thursday, I wonder why your tests failed it worked
for me , anyway I will rework it...
I rather prefer to do it in one regexp instead of finding startEx and endEx
Ganesh schrieb:
Hi Werner,
After some testing with \s*html[^]*(.*)\/\s*html[^]* I couldn't
get it to work
Well then we have to go for a custom tag, we cannot put
the myfaces attribute into f:ajax, due to TCK restrictions, we probably
have to roll
an additonal myfaces:ajax tag!
I have no objections to that, since we add a load
of optional enhancements to the javascript core anyway, so adding
an
Hia, my mail was not answered so it probably went to /dev/null
because it was with the same content but not as exact as the one from
Ganesh regarding the id issue :-)
Werner
Matthias Wessendorf schrieb:
Sent from my iPod.
Am 21.04.2009 um 06:05 schrieb Ganesh gan...@j4fry.org:
Hi
Btw. I agree fully with the body issue
in the spec.
There are usecases where you need to replace the tag as well for instance
body.../body can become body class=../body
same goes for embedded onload handlers etc...
Sure there are workarounds but, why not fix it on the spec side as long
Hello since I post over gmane I cannot directly forward the mail.
I got an answer from Roger Kitain regarding the iframe issue, seems
like there is no /dev/null...
No seriously I did not get an answer to my first mail
regarding the javax.faces.ViewState issue (probably lost in the spam
[
https://issues.apache.org/jira/browse/MYFACES-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2171.
-
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
At last committed at revision
Hi
Just for information purposes and as start point, what we have right now is
this wiki page:
http://wiki.apache.org/myfaces/MyFaces_Archetypes_for_Maven
The archetypes available
myfaces-archetype-helloworld // myfaces 1.2 + tomahawk
myfaces-archetype-helloworld-facelets
Definitely +1
~ Simon
On Tue, Apr 21, 2009 at 3:27 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Just for information purposes and as start point, what we have right now is
this wiki page:
http://wiki.apache.org/myfaces/MyFaces_Archetypes_for_Maven
The archetypes available
[
https://issues.apache.org/jira/browse/MYFACES-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701248#action_12701248
]
Leonardo Uribe commented on MYFACES-1879:
-
If the two previous comments are
[
https://issues.apache.org/jira/browse/TRINIDAD-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701264#action_12701264
]
Paul Freeman commented on TRINIDAD-779:
---
Added a simple maven-based test case. To
Need the ability to bypass the Cache on ResourceServlet
---
Key: TRINIDAD-1457
URL: https://issues.apache.org/jira/browse/TRINIDAD-1457
Project: MyFaces Trinidad
Issue Type: New Feature
On Tue, Apr 21, 2009 at 8:13 PM, Werner Punz werner.p...@gmail.com wrote:
Actually We probably can provide a non facelets based solution
under the myfaces umbrella, tomahawk, extensions or impl I don´t care
but I am definitely sure we will be unable to provide it under
the standard f: tags...
for the notes.
Servlet 3.0 will provide a unified upload API.
Yeah !!!
On Tue, Apr 21, 2009 at 8:51 PM, Werner Punz werner.p...@gmail.com wrote:
Hello since I post over gmane I cannot directly forward the mail.
I got an answer from Roger Kitain regarding the iframe issue, seems
like there is
+1
On Tue, Apr 21, 2009 at 9:45 PM, Simon Lessard
simon.lessar...@gmail.com wrote:
Definitely +1
~ Simon
On Tue, Apr 21, 2009 at 3:27 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Just for information purposes and as start point, what we have right now
is this wiki page:
[
https://issues.apache.org/jira/browse/MYFACES-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701288#action_12701288
]
Leonardo Uribe commented on MYFACES-2098:
-
Just one minor comment: the current
[
https://issues.apache.org/jira/browse/MYFACES-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701329#action_12701329
]
Leonardo Uribe commented on MYFACES-1955:
-
Trying to check this issue, the
[
https://issues.apache.org/jira/browse/TRINIDAD-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701356#action_12701356
]
Andrew Robinson commented on TRINIDAD-779:
--
Okay I did some debugging and I
[
https://issues.apache.org/jira/browse/TRINIDAD-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-779.
--
Resolution: Invalid
Fix Version/s: 1.2.12-core
The fix is to remove the item
It looks like most of the work is done with the existing archetypes. I
think what would be nice:
Archetypes for each library (tomahawk, tobago, etc.)
Archetypes for each library with facelets (or just have comments in
the web.xml on how to convert the project to facelets)
And then a different
Another option is to reduce the work on our side and just have an SVN branch:
1) user uses SVN checkout to get the branch with the test case for the
given project
2) user makes changes as needed
3) submit the test case as a zip, or better yet as svn diff output zipped
Is that better, or do you
On Wed, Apr 22, 2009 at 12:09 AM, Matthias Wessendorf mat...@apache.org wrote:
On Tue, Apr 21, 2009 at 8:13 PM, Werner Punz werner.p...@gmail.com wrote:
Actually We probably can provide a non facelets based solution
under the myfaces umbrella, tomahawk, extensions or impl I don´t care
but I am
On Tue, Apr 21, 2009 at 8:13 PM, Werner Punz werner.p...@gmail.com wrote:
Actually We probably can provide a non facelets based solution
under the myfaces umbrella, tomahawk, extensions or impl I don´t care
but I am definitely sure we will be unable to provide it under
the standard f: tags...
38 matches
Mail list logo
