so, there are no objections in making the MyFaces 2.0 efforts become trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd Bohmann
bernd.bohm...@atanion.com wrote:
Hello,
+1
I would prefer
/trunk - 2.0
/branches/myfaces-1.1.x
/branches/myfaces-1.2.x
because we are not using cvs
Hi,
sure MyFaces 2.0 is not yet there, but I want to share an idea...
Since JSF 2.0 has the new Facelets support to easily create (custom) components,
would it be a good idea to start a new (sandbox) project that defines
a JSF 2.0 set
of components, only written via the Facelets way ?
I had to
Hi,
It sounds like a good idea to me. Tomahawk has been always one of the
main reasons of people using MyFaces. I would say that having such a
sandbox can be the start or a much modern Tomahawk for the future.
Cheers,
Bruno
2009/5/27 Matthias Wessendorf mat...@apache.org:
Hi,
sure MyFaces
+1 sounds good to me
2009/5/27 Matthias Wessendorf mat...@apache.org:
so, there are no objections in making the MyFaces 2.0 efforts become trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd Bohmann
bernd.bohm...@atanion.com wrote:
Hello,
+1
I would prefer
/trunk - 2.0
On Wed, May 27, 2009 at 9:52 AM, Bruno Aranda brunoara...@gmail.com wrote:
Hi,
It sounds like a good idea to me. Tomahawk has been always one of the
main reasons of people using MyFaces. I would say that having such a
sandbox can be the start or a much modern Tomahawk for the future.
+1
+1 for sure
On Wed, May 27, 2009 at 8:53 AM, Bruno Aranda brunoara...@gmail.com wrote:
+1 sounds good to me
2009/5/27 Matthias Wessendorf mat...@apache.org:
so, there are no objections in making the MyFaces 2.0 efforts become
trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd
Hi Matthias,
Funny you're asking this today: Last night I've released the J4Fry
dojoFacelets library on sourceforge. It's a pure JSF template/dojo
library, it was build on JSF 1.1/1.2 w/Facelets and it runs on JSF 2.0
out of the box. The templates are AJAX enabled via ui:define. The first
not sure I read that article, but I agree that it is worth to go the
Facelets road, for new things.
Not sure if EVERY 2.0 library needs to contain only template-based
components; old-fashion
renderers are still, ok...
so generally you also think it is worth to host something like that ?
I
Tomahawk already has dojo a huge dependency.
For the new lib I'd favor using jquery UI plus stable jquery plugins instead
of dojo.
On Wed, May 27, 2009 at 9:33 AM, Matthias Wessendorf mat...@apache.orgwrote:
not sure I read that article, but I agree that it is worth to go the
Facelets road,
Hi,
yes, sure, declarative languages have more limitations then procedural
ones and sometimes we must swich to the procedural backup and again yes
I think it it is worth working on something like that.
IMHO we should first of all discuss the basis we want to work upon.
Which are your
HtmlResponseStateManager always serialize state on writeViewStateField
--
Key: MYFACES-2237
URL: https://issues.apache.org/jira/browse/MYFACES-2237
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/TOBAGO-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-757.
Resolution: Fixed
ResourceLocator should detect resources from JAR files in the
Bruno Aranda schrieb:
Hi,
It sounds like a good idea to me. Tomahawk has been always one of the
main reasons of people using MyFaces. I would say that having such a
sandbox can be the start or a much modern Tomahawk for the future.
Cheers,
Bruno
2009/5/27 Matthias Wessendorf
Ganesh schrieb:
Hi,
yes, sure, declarative languages have more limitations then procedural
ones and sometimes we must swich to the procedural backup and again yes
I think it it is worth working on something like that.
IMHO we should first of all discuss the basis we want to work upon.
On Wed, May 27, 2009 at 10:57 AM, Ganesh gan...@j4fry.org wrote:
Hi,
yes, sure, declarative languages have more limitations then procedural ones
and sometimes we must swich to the procedural backup and again yes I think
it it is worth working on something like that.
IMHO we should first of
On Wed, May 27, 2009 at 11:18 AM, Werner Punz werner.p...@gmail.com wrote:
Ganesh schrieb:
Hi,
yes, sure, declarative languages have more limitations then procedural
ones and sometimes we must swich to the procedural backup and again yes I
think it it is worth working on something like
Actually here is the state of our current works on the component set:
I have dojo covered currently in mine which still is undecided what to
do with it by about 80% on the dijit side. The big points missing in my
own one is the table and the tree. For the tree I have gathered the
knowledge to
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713490#action_12713490
]
Torsten Liermann commented on TOMAHAWK-1126:
Hi,
why closed? I have exactly
On Wed, May 27, 2009 at 11:31 AM, Werner Punz werner.p...@gmail.com wrote:
Actually here is the state of our current works on the component set:
I have dojo covered currently in mine which still is undecided what to do
with it by about 80% on the dijit side. The big points missing in my own
Matthias Wessendorf schrieb:
On Wed, May 27, 2009 at 11:31 AM, Werner Punz werner.p...@gmail.com wrote:
Actually here is the state of our current works on the component set:
I have dojo covered currently in mine which still is undecided what to do
with it by about 80% on the dijit side. The
I had terrible experiences with dojo in the past, if you say flaws are
fixed, documentation is improved, then I'd be 0 instead of -1 :) Dojo is
like ejb2 to me. I'd consider ExtJS as well instead of dojo. Maybe it's a
better match of widgets compared to jquery ui.
On Wed, May 27, 2009 at 10:40
Hi,
Yes, sure, we're happy to share it. It's already under the apache
license and the copyrights belong to Alex and me, so there is no
problem. What name do you have in mind? Once we have a name, we can set
up a svn subproject and I can check in our dojoFacelets.
For the multi-library
I think the ExtJS has a GPL-style license, right ?
On Wed, May 27, 2009 at 11:54 AM, Cagatay Civici
cagatay.civ...@gmail.com wrote:
I had terrible experiences with dojo in the past, if you say flaws are
fixed, documentation is improved, then I'd be 0 instead of -1 :) Dojo is
like ejb2 to me.
Afaik gpl3 is compatible with apache v2?
On Wed, May 27, 2009 at 11:15 AM, Matthias Wessendorf mat...@apache.orgwrote:
I think the ExtJS has a GPL-style license, right ?
On Wed, May 27, 2009 at 11:54 AM, Cagatay Civici
cagatay.civ...@gmail.com wrote:
I had terrible experiences with dojo in
AFAIK ExtJS may not be altered and resold commercially - they have a 2nd
commercial license. The whole thing is developed commercially. IMHO they
use OS just to get their excellent product into the market, but they
don't have the OS spirit.
Cagatay Civici schrieb:
Afaik gpl3 is compatible
[
https://issues.apache.org/jira/browse/MYFACES-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713522#action_12713522
]
Torsten Liermann commented on MYFACES-2013:
---
Hi,
please fix this. I have the
On Wed, May 27, 2009 at 12:17 PM, Cagatay Civici
cagatay.civ...@gmail.com wrote:
Afaik gpl3 is compatible with apache v2?
I think that you can't extend it to offer asl based enhancements.
-M
On Wed, May 27, 2009 at 11:15 AM, Matthias Wessendorf mat...@apache.org
wrote:
I think the ExtJS
On Wed, May 27, 2009 at 12:23 PM, Ganesh gan...@j4fry.org wrote:
AFAIK ExtJS may not be altered and resold commercially - they have a 2nd
commercial license. The whole thing is developed commercially. IMHO they use
OS just to get their excellent product into the market, but they don't have
the
[
https://issues.apache.org/jira/browse/MYFACES-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713530#action_12713530
]
Matthias Weßendorf commented on MYFACES-2013:
-
have you done some debugging
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1464.
--
Resolution: Fixed
Fix Version/s: 1.2.12-core
max upload size
Hi,
We are having a meeting on the dojo facelets with the J4Fry people
tonight in munich. As this might come to MyFaces you are invited to join
us. If you aren't in located munich, don't panic: I'll outline our
results tomorrow.
Best regards,
Ganesh
Original-Nachricht
[
https://issues.apache.org/jira/browse/TRINIDAD-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Schwartz updated TRINIDAD-1488:
Status: Patch Available (was: Open)
ChangeManager: Ability to apply component changes
ResourceServlet should set the status 404, if the resource could not be found
-
Key: TOBAGO-759
URL: https://issues.apache.org/jira/browse/TOBAGO-759
Project: MyFaces Tobago
[
https://issues.apache.org/jira/browse/TOBAGO-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-759.
Resolution: Fixed
Fix Version/s: 1.1.0
1.0.21
ResourceServlet
[
https://issues.apache.org/jira/browse/TRINIDAD-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1488:
-
Resolution: Fixed
Fix Version/s: 1.2.12-core
Assignee:
Yes, I looked at this library for GWT work a couple weeks ago. It's
compatible in theory, but not in practice.
On Wed, May 27, 2009 at 6:23 AM, Ganesh gan...@j4fry.org wrote:
AFAIK ExtJS may not be altered and resold commercially - they have a 2nd
commercial license. The whole thing is
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713655#action_12713655
]
Leonardo Uribe commented on TOMAHAWK-1126:
--
For reproduce the error it is just
I'm testing out the latest snapshot of the 1.0 portlet bridge with Mojarra
1.2_10 and Liferay 5.2, and I noticed some peculiar behavior -- the app is
expecting the file invoke.jspx regardless of which view I've configured
for GenericFacesPortlet. It turns out that Liferay for some reason appends
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713664#action_12713664
]
Torsten Liermann commented on TOMAHAWK-1126:
Yes, a caption facet is enough.
Hi Werner,
AFAIK, this hasn't made it into Mojarra.
regards,
Martin
On 5/16/09, Werner Punz werner.p...@gmail.com wrote:
Two additional things:
first of all all has to be resolved by the f:ajax tag for the javascript
call into absolute client ids, otherwise the server cannot identify the
Leonardo,hey thanks for looking at that again. I tried to resolve on my own
and edited the same class on the same line instead I just tried to and a
space:
writer.write( );
// Also remove extra white space two lines above at the end of the line
When I built the jar and used the jar the problem
IMHO, Dojo, Prototype.js, JQuery and most other big JS libraries are
more or less the same.
Dojo was very bloated in the past, but the Dojo team have cleaned a
lot, which makes it a quite lean and mean library atm.
I've always been a Prototype.js fan because the programming model
looks the most
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe reopened TOMAHAWK-1126:
--
Assignee: Leonardo Uribe
Reopened because conditions where this issue occur
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved TOMAHAWK-1126.
--
Resolution: Fixed
Fix Version/s: 1.1.9-SNAPSHOT
Using facet name=caption in
[
https://issues.apache.org/jira/browse/TOMAHAWK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713833#action_12713833
]
Leonardo Uribe commented on TOMAHAWK-1126:
--
The error comes from MYFACES-1613.
[
https://issues.apache.org/jira/browse/MYFACES-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713832#action_12713832
]
Leonardo Uribe commented on MYFACES-2013:
-
The error comes from MYFACES-1613.
[
https://issues.apache.org/jira/browse/MYFACES-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2013.
-
Resolution: Fixed
Fix Version/s: 1.2.7-SNAPSHOT
Assignee: Leonardo
[
https://issues.apache.org/jira/browse/MYFACES-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713834#action_12713834
]
Leonardo Uribe commented on MYFACES-2237:
-
This is not a bug. The file
[
https://issues.apache.org/jira/browse/MYFACES-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1841:
Resolution: Fixed
Fix Version/s: 1.2.7-SNAPSHOT
1.1.7-SNAPSHOT
[
https://issues.apache.org/jira/browse/MYFACES-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2156:
Resolution: Fixed
Fix Version/s: 1.2.7-SNAPSHOT
Status: Resolved (was:
+1, but just a small suggestion. Right now I'm running the necessary steps
for release myfaces core 1.2.7, core 1.1.7, so I would like if it is
possible to delay this change after the release.
regards
Leonardo Uribe
2009/5/27 Cagatay Civici cagatay.civ...@gmail.com
+1 for sure
On Wed, May
51 matches
Mail list logo
